Rosetta Stone for Unix

Total Page:16

File Type:pdf, Size:1020Kb

Rosetta Stone for Unix This custom drawing feature now works in both Mozilla and in IE 5 or better for Solaris, HP-UX, or Windows. Use click, shift-click, control-click, and the "set" and "clear" buttons to select the desired subset of OSs. Then select "Draw table" to launch a new window with your custom table. Thanks to Mårten Svantesson <[email protected]> for the improved JavaScript. A Sysadmin's Unixersal Translator (ROSETTA STONE) OR What do they call that in this world? Contributions and corrections gratefully accepted. Please help us fill in the blanks. New "tasks" are welcome, too! PDF version (for best results print US legal size, landscape orientation. If your browser plug-in has trouble with the PDF, then download it and load it in stand-alone acroread). Framed version. Based on Pat Wilson's version. OS versions in parentheses; e.g. 10+ means version 10 and greater; 9- means version 9 and previous. $=extra cost If not specified, commands are in one of the following directories: /usr/bin, /usr/sbin, /sbin, /bin Categories: hardware, firmware, devices disks kernel, boot, swap files, volumes networking security, backup software, patching, tracing, logging references TASK \ OS AIX Darwin DG/UX FreeBSD HP-UX IRIX Linux NetBSD OpenBSD Reliant SCO UnixWare Solaris SunOS 4 Tru64 Ultrix UNICOS OS / TASK Cray Inc., formed SCO UnixWare 7.0.1& The Open Source Fujitsu Siemens. Based from the March SCO UnixWare 7.1.1 Solaris 2.0-2.6, 7, 8, 9 (Digital Unix, OSF/1) foundation for Mac OS (rh) = Red Hat, on DC/OSX from Solaris 1.* 2000 merger of OS notes SVR4-based Mandrake, Suse,... became Caldera Open (SunOS 5.*) (4)= 4.0F/G OS notes X, descended from Pyramid, SINIX BSD-based Tera Computer (deb) = Debian, Libranet,... Unix and later became SVR4-based (5)= 5.0A NeXTStep from Siemens, and SVR4. Company and Cray SCO again. Research smit Aqua: System /usr/sysadm/bin/sysmgr (6.3+) solstice checklist linuxconf sysadm checklist administrative GUI smitty Preferences, NetInfo sysadm /stand/sysinstall sam toolchest sushi ? scoadmin admintool ? ? /etc/install/install administrative GUI yast2 (Suse) WebSysAdmin (5) sysman wsm Manager /usr/Cadmin/bin/* smc (8 01/01+) xmenu lsuser xadmin Aqua: System adduser useradd useradd useradd sysadm scoadmin mkuser useradd useradd useradd udbgen managing users Preferences, Users rmuser userdel /usr/Cadmin/bin/cpeople userdel userdel useradd useradd ? ? ? managing users chuser userdel userdel userdel udbrstrict niutil pw usermod (deb) adduser adduser (interactive) userdel userdel rmuser nu scripts dia -R full dmesg (if you're lucky) prtconf -v ioscan vmstat -P /proc/cpuinfo /usr/platform/`uname -i`/ dmesg (if you're lucky) hwconfig hwmgr -get category prtconf /proc/pci dmesg sbin/prtdiag -v (sun4u and dmesg adb hw (5) hwmgr -show machid list hardware lscfg /proc/meminfo more dmesg sun4d only) dmesg (if you're list hardware ioreg -bls dg_sysreport -g hardware cat /var/run/dmesg.boot model hinv autoconf -l scoadmin/DCU devices ? getconf configuration lsattr /proc/interrupts /var/run/dmesg.boot cat /var/run/dmesg.boot psrinfo -v lucky) configuration pciconf -l stm (from the SupportPlus psrinfo uname -a lsdev /proc/ioports cat /kern/msgbuf /usr/lib/X11/testtools/ isainfo -v CDROM) pset_info lspci z35SysInfo dmesg bdf (like most vendors' df) sys_check hwinfo (SuSE) iostat -En /usr/bin/X11/dxsysinfo show/set setboot nvram openprom (on in bdm show/set dg_sysctl | /dev/nvram (if you have it) EEPROM/NVRAM bootlist -o -m normal nvram ? bootadmin (at boot PROM) printenv/setenv (at command eeprom OpenFirmware (at boot stop ? eeprom ? (4.0D+) consvar ? ? EEPROM/NVRAM grep BOOTPATH hwclock values stm monitor) architectures) or ctrl-a) values (3.2.*) scu scan edt devfsadm. pre-Solaris 7, modprobe (4.0) scu scan edt; disklabel -rw add device without (automatic — camcontrol ioscan -fnCdevtype; scsiha -pr reinitdev use: add device without cfgmgr -v N/A kerneld ? ? mkdev ? rzXX label (for disks) ? ? reboot autdodiskmounter) kldload insf -Cdevtype ioconfig -f /hw changedev drvconfig; devlinks; {disks, reboot insmod (5.x) dsfmgr -k; disklabel -rw tapes, ports} dskn auto /dev/tape tape device /dev/rmt0 ? /dev/rmt/0 /dev/rsa0 /dev/rmt/0 /dev/st0 /dev/st0 /dev/st0 /dev/ios0/rstape001 /dev/rct0 /dev/rmt/0 ? (5.x) /dev/ntape /dev/tape ? tpmnt tape device /dev/nrtape X kvm config ? ? ? xf86config ? ? xf86config ? ? ? hwconfig kdmconfig (x86) ? ? ? ? X kvm config disklabel -r admpdisk -o list diskinfo read a disk label lspv -l Disk Utility disklabel -r prtvtoc fdisk -l disk fdisk -r OR disklabel -rl dkpart -l fsname prtvtoc dkinfo disklabel -r chpt -q ? read a disk label admvdisk -o list pvdisplay mbrlabel (non-root partitions are c or d /dev/ios0/rsdisk???s7 whole disk in partition N/A mounted under ? c ? 10 ? c /dev/1s# (#=0,1,...) 2 c c c ? whole disk in partition sysctl kern.rawpartition (???=000-999) /Volumes) fdisk cfdisk dvhtool disklabel -wr label a disk mkvg (labels unused) admpdisk disklabel -wr pvcreate fdisk disklabel -wr dksetup ? format format disklabel -rw chpt -a /etc/labelit label a disk fx -x mbrlabel sysinstall e2label parted (if you have it) fdisk lvcreate format partition a disk mklv pdisk admpdisk fx fdisk disklabel -i fdisk -e OR disklabel -E dkpart -e ? format disklabel -e chpt -p /etc/install/install partition a disk sysinstall sam fmthard pdisk (on a MAC) /kernel/genunix /platform/`uname -m`/ /hpux (9) /boot/vmlinuz kernel /unix /mach_kernel /dgux /kernel /unix /netbsd /bsd /unix /unix kernel/unix /vmunix /vmunix /vmunix /unicos kernel /stand/vmunix (10+) /boot/bootlx /platform/`uname -m`/ kernel/sparcv9/unix (7+) /usr/samples/kernel/vmtune sysdef sam (installed with the bos vi /var/Build/ /boot/kernel.conf getconf show/set kernel sysdef /proc/* sysctl dxkerneltuner show/set kernel adt.samples fileset) /usr/sbin/sysctl system.hostname;; sysctl systune /etc/sysctl.conf idtune /etc/conf/cf.d/configure -x cat /etc/system ? ? ? parameters kmtune (11+) /proc/sys/* /etc/sysctl.conf sysconfig parameters /usr/sbin/no reboot /etc/sysctl.conf ndd getconf (network-related) adb -k show runlevel who -r (runlevels unused) who -r ? who -r who -r /sbin/runlevel N/A ? who -r who -r who -r ? who -r ? who -r show runlevel installboot /usr/platform/ fdisk -A(and lilo to fdisk -i `uname -m` (4.x+) disklabel -rw -t make disk bootable bosboot -a bless dg_sysctl ? mkboot dvhtool ? dksetup ? ? ? ? make disk bootable manipulate mbr) installboot /lib/fs/ufs/bootblk [ufs|advfs] raw_device_file /System/Library/ /etc/rc* (9) StartupItems/*, /etc/rc* /etc/rc* /etc/rc* (but may vary) /etc/rc* startup scripts /etc/rc* /etc/rc* /sbin/rc* (10+) /etc/rc* /etc/rc* /etc/rc* /sbin/init.d; links in /sbin/rc?.d /etc/rc* ? startup scripts /Library/StartupItems/, /usr/local/etc/rc.d/ /etc/init.d/ /etc/init.d/ /etc/rc* /etc/rc* /etc/init.d/ /sbin/init.d/ /etc/rc* 0: shut down 0: firmware monitor 0: power-down 0: power-down run levels s,S: single-user s,S: single-user run levels s,S: single-user 0: halt s,S: single-user 0: shut down *=normalstates 1: sys admin -1: permanent insecure 1: sys admin *=normalstates 1: sys admin s,S,1: vendor-dependent 1: sys admin 1: single user for more detail 2: multiuser 0: insecure 2: multiuser for more detail ? ? ? ? 2: multiuser (no NFS) 1: single-user ? 2*: multiuser ? ? ? 2: multi-user, no NFS ? see 3*: share NFS 1: secure 3*: share NFS see 3*: multiuser 2-5*: multiuser 3+4*: user-defined 3: multi-user home.earthlink.net/ 4*: start GUI 2: highly secure 4*: user-defined home.earthlink.net/ 4: user-defined 6: reboot 5: firmware update 6: reboot ~jaymzh666/runlevels.html 5: user-defined 5: power-down ~jaymzh666/runlevels.html 5: firmware monitor 6: reboot 6: user-defined 6: reboot admswap -o list -buv swapinfo swap -s cat /proc/meminfo swap -s check swap space lsps -a ls -l /var/vm swapinfo swapctl -l swapctl swap -l swap -l pstat -s swapon -s ? /etc/swapper check swap space dg_sysreport -p freeswap pstat -s swap -l free swap -l ext2 ufs vxfs (4) ufs NC1FS "normal" filesystem jfs dg/ux ufs hfs efs, xfs ext3 ffs (was ufs) ffs (was ufs) htfs ufs 4.2 ufs "normal" filesystem hfs+ ufs (root) (5) AdvFS C2FS ReiserFS jfs (vxfs) ccd Solstice DiskSuite Advfs volume-based filesystem jfs ? ? LVM xlv, xvm, xfs LVM vdisk vdisk ? ? ? volume-based filesystem ccd, raidframe ccd VxVM ($) vinum VxVM ($) LSM /etc/checklist /etc/mnttab file system (9) /etc/vfstab /etc/default/filesys /etc/fstab file system /etc/filesystems NetInfo /etc/fstab /etc/fstab /etc/fstab /etc/fstab /etc/fstab /etc/fstab /etc/vfstab (local) /etc/fstab /etc/fstab /etc/fstab description /etc/fstab /etc/dktab /etc/vfstab (local) AdvFS: /etc/fdmns description (10+) /etc/rmtab (remote) smitty vg /opt/VRTSvxva/bin/vxva AdvFS: mkfdmn, mkfset, smitty lvm e2fsadm vg*; lv*; pv* (Veritas) addvol, showfdmn smitty jfs vinum xlv_mgr lvcreate ccdconfig dkconfig volume manipulation Disk Utility / pdisk sysadm extendfs ? ? /usr/opt/SUNWmd/ ? LSM: volassist or volmake, ? /etc/install/install volume manipulation mkvg; chvg; rmvg ccdconfig xvm lvremove raidctl dkmirror fsadm sbin/metatool volume, volplex and volsd, mklv; chlv; rmlv lvextend (DiskSuite) volprint mkfs; crfs; rmfs AdvFS: mkfdmn bb mkfs mkfs newfs create filesystem crfs (automatic) admfilesystem newfs mkfs mke2fs newfs newfs ? ? UFS: newfs ? mkfs create filesystem newfs newfs mkfs MFS: mfs labelit truncate -s size[K|M|G] dd if=/dev/zero filename dd if=/dev/zero dd if=/dev/zero dd if=/dev/zero dd if=/dev/zero create non-0-length dd if=/dev/zero dd if=/dev/zero of=filename create non-0-length lmktemp of=filename bs=1024 ? dd if=/dev/zero of=filename prealloc mkfile of=filename of=filename bs=1m of=filename bs=1024k of=filenmae bs=1024 mkfile ? ? ? empty file of=filename bs=1k bs=1024k count=desired empty file count=desired bs=size[b|k|m|g] \ bs=1024k count=desired count=desired count=desired count=desired count=desired pfs_mountd /etc/init.d/vold start; mount /dev/disk/cdromXa mount -v cdrfs -o ro mount /cdrom pfsd (automatic — mount -t cdrom (mounts automatically when CD mount -t cd9660 -r mount -F hs ..
Recommended publications
  • Kutrace: Where Have All the Nanoseconds Gone?
    KUTrace: Where have all the nanoseconds gone? Richard Sites, Invited Professor EPFL 2017.10.27 Tracing Summit 2017, Prague Richard Sites 2017.10.27 Outline Observability problem statement KUTrace solution Tracing design goals Goals drive the design Results Display Design Comparisons Conclusions Richard Sites 2017.10.27 Observability problem statement Richard Sites 2017.10.27 3 Problem statement This talk is about tail latency in real user-facing datacenter transactions. It is not about batch processing throughput, nor about benchmarks. Context: A datacenter of perhaps 20,000 servers running software services that spread work for a user-facing transaction across a few hundred or thousand machines in parallel. Each server handles hundreds of transactions per second. Some transactions are unusually slow, but not repeatably. Slow transactions occur unpredictably, but there are several per minute. We wish to observe where all the time goes in such transactions, and observe why they are slow. Richard Sites 2017.10.27 Problem statement ☞ Some transactions are unusually slow, but not repeatably. ∴ There is some source of interference just before or during a slow transaction. Understanding tail latency requires complete traces of CPU events over a few minutes, with small enough CPU and memory overhead to be usable under busiest-hour live load. Existing tracing tools have much-too-high overhead. Problem: build better tail-latency observation tools Richard Sites 2017.10.27 KUTrace solution Richard Sites 2017.10.27 6 KUTrace solution KUTrace uses minimal Linux kernel patches on a single server to trace every transition between kernel- and user-mode execution, on every CPU core, with small enough overhead to use routinely on live loads.
    [Show full text]
  • Embedding Redhat Linux in a Diskonchip - HOWTO
    Embedding Redhat Linux in a DiskOnChip - HOWTO Don Davies, Prosig Ltd ( [email protected]) October 2002 Describes the configuration and setup of a development environment for a Single Board Computer running Redhat Linux from a DiskOnChip device. Contents 1.0 Introduction ..........................................................................................................3 1.1 Hardware Details..................................................................................................3 1.2 System Configuration ...........................................................................................4 2.0 DOS Development Environment...........................................................................5 2.1 DiskOnChip Tools ................................................................................................5 2.2 Boot Loader..........................................................................................................6 2.3 MS-DOS System Startup......................................................................................6 3.0 Linux Development Environment ......................................................................7 3.1 Custom Kernel Configuration ............................................................................8 3.2 Building Custom Kernel ..................................................................................10 3.3 Booting Custom Kernel ...................................................................................10 3.4 Formatting DiskOnChip for Linux
    [Show full text]
  • Practice Test Version 1.8 LPI 117-101: Practice Exam QUESTION NO: 1 CORRECT TEXT
    LPI 117-101 117-101 LPI 101 General Linux, Part I Practice Test Version 1.8 LPI 117-101: Practice Exam QUESTION NO: 1 CORRECT TEXT You suspect that a new ethernet card might be conflicting with another device. Which file should you check within the /proc tree to learn which IRQs are being used by which kernel drives? Answer: interrupts QUESTION NO: 2 How many SCSI ids for peripherals can SCSI-1 support? A. 5 B. 6 C. 7 D. 8 Answer: C Explanation: SCSI-1 support total 7 peripherals. There are several different types of SCSI devices. The original SCSI specification is commonly referred to as SCSI-1. The newer specification, SCSI-2, offers increased speed and performance, as well as new commands. Fast SCSI increases throughput to more than 10MB per second. Fast-Wide SCSI provides a wider data path and throughput of up to 40MB per second and up to 15 devices. There there are Ultra-SCSI and Ultra-Wide-SCSI QUESTION NO: 3 You need to install a fax server. Which type of fax/modem should you install to insure Linux compatibility? Test-King.com A. External Serial Fax/modem B. External USB Fax/modem C. Internal ISA Fax/modem D. Internal PCI Fax/modem Answer: A QUESTION NO: 4 You are running Linux 2.0.36 and you need to add a USB mouse to your system. Which of the following statements is true? "Welcome to Certification's Main Event" - www.test-king.com 2 LPI 117-101: Practice Exam A. You need to rebuild the kernel.
    [Show full text]
  • Solid Truss to Shell Numerical Homogenization of Prefabricated Composite Slabs
    materials Article Solid Truss to Shell Numerical Homogenization of Prefabricated Composite Slabs Natalia Staszak 1, Tomasz Garbowski 2 and Anna Szymczak-Graczyk 3,* 1 Research and Development Department, FEMat Sp. z o. o., Romana Maya 1, 61-371 Pozna´n,Poland; [email protected] 2 Department of Biosystems Engineering, Poznan University of Life Sciences, Wojska Polskiego 50, 60-627 Pozna´n,Poland; [email protected] 3 Department of Construction and Geoengineering, Poznan University of Life Sciences, Pi ˛atkowska94 E, 60-649 Pozna´n,Poland * Correspondence: [email protected] Abstract: The need for quick and easy deflection calculations of various prefabricated slabs causes simplified procedures and numerical tools to be used more often. Modelling of full 3D finite element (FE) geometry of such plates is not only uneconomical but often requires the use of complex software and advanced numerical knowledge. Therefore, numerical homogenization is an excellent tool, which can be easily employed to simplify a model, especially when accurate modelling is not necessary. Homogenization allows for simplifying a computational model and replacing a complicated composite structure with a homogeneous plate. Here, a numerical homogenization method based on strain energy equivalence is derived. Based on the method proposed, the structure of the prefabricated concrete slabs reinforced with steel spatial trusses is homogenized to a single plate element with an effective stiffness. There is a complete equivalence between the full 3D FE model built with solid elements combined with truss structural elements and the simplified Citation: Staszak, N.; Garbowski, T.; Szymczak-Graczyk, A. Solid Truss to homogenized plate FE model.
    [Show full text]
  • Debugging Kernel Problems
    Debugging Kernel Problems by GregLehey Edition for AsiaBSDCon 2004 Taipei, 13 March 2004 Debugging Kernel Problems by GregLehey([email protected]) Copyright © 1995-2004 GregLehey 3Debugging Kernel Problems Preface Debugging kernel problems is a black art. Not manypeople do it, and documentation is rare, in- accurate and incomplete. This document is no exception: faced with the choice of accuracyand completeness, I chose to attempt the latter.Asusual, time was the limiting factor,and this draft is still in beta status. This is a typical situation for the whole topic of kernel debugging: building debug tools and documentation is expensive,and the people who write them are also the people who use them, so there'satendencytobuild as much of the tool as necessary to do the job at hand. If the tool is well-written, it will be reusable by the next person who looks at a particular area; if not, it might fall into disuse. Consider this book a starting point for your own develop- ment of debugging tools, and remember: more than anywhere else, this is an area with ``some as- sembly required''. Debugging Kernel Problems 4 1 Introduction Operating systems fail. All operating systems contain bugs, and theywill sometimes cause the system to behave incorrectly.The BSD kernels are no exception. Compared to most other oper- ating systems, both free and commercial, the BSD kernels offer a large number of debugging tools. This tutorial examines the options available both to the experienced end user and also to the developer. In this tutorial, we’ll look at the following topics: • Howand whykernels fail.
    [Show full text]
  • Reference Guide
    Reference Guide Scyld ClusterWare Release 5.10.1-5101g0000 December 18, 2013 Reference Guide: Scyld ClusterWare Release 5.10.1-5101g0000; December 18, 2013 Revised Edition Published December 18, 2013 Copyright © 1999 - 2013 Penguin Computing, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise) without the prior written permission of Penguin Computing, Inc.. The software described in this document is "commercial computer software" provided with restricted rights (except as to included open/free source). Use beyond license provisions is a violation of worldwide intellectual property laws, treaties, and conventions. Scyld ClusterWare, the Highly Scyld logo, and the Penguin Computing logo are trademarks of Penguin Computing, Inc.. Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Infiniband is a trademark of the InfiniBand Trade Association. Linux is a registered trademark of Linus Torvalds. Red Hat and all Red Hat-based trademarks are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries. All other trademarks and copyrights referred to are the property of their respective owners. Table of Contents Preface .....................................................................................................................................................................................v
    [Show full text]
  • I.MX Linux® Reference Manual
    i.MX Linux® Reference Manual Document Number: IMXLXRM Rev. 1, 01/2017 i.MX Linux® Reference Manual, Rev. 1, 01/2017 2 NXP Semiconductors Contents Section number Title Page Chapter 1 About this Book 1.1 Audience....................................................................................................................................................................... 27 1.1.1 Conventions................................................................................................................................................... 27 1.1.2 Definitions, Acronyms, and Abbreviations....................................................................................................27 Chapter 2 Introduction 2.1 Overview.......................................................................................................................................................................31 2.1.1 Software Base................................................................................................................................................ 31 2.1.2 Features.......................................................................................................................................................... 31 Chapter 3 Machine-Specific Layer (MSL) 3.1 Introduction...................................................................................................................................................................37 3.2 Interrupts (Operation)..................................................................................................................................................
    [Show full text]
  • Intel FPGA Programmable Acceleration Card N3000
    Intel® Acceleration Stack User Guide Intel FPGA Programmable Acceleration Card N3000 Updated for Intel® Acceleration Stack for Intel® Xeon® CPU with FPGAs: 1.1 Subscribe UG-20244 | 2021.06.14 Send Feedback Latest document on the web: PDF | HTML Contents Contents 1. About this Document...................................................................................................... 4 1.1. Acronym List ........................................................................................................5 2. System Requirements..................................................................................................... 7 2.1. Cooling Requirements............................................................................................ 7 3. Hardware Installation................................................................................................... 11 3.1. Installing the Intel FPGA PAC N3000.......................................................................11 4. Installing the OPAE Software........................................................................................16 4.1. Install Additional Packages.................................................................................... 17 4.2. Install the Release Package................................................................................... 17 4.2.1. Remove Previous OPAE Packages............................................................... 18 4.2.2. Install the Acceleration Stack for Runtime..................................................
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • Optimization of System's Performance with Kernel Tracing by Cohort Intelligence
    I.J. Information Technology and Computer Science, 2017, 6, 59-66 Published Online June 2017 in MECS (http://www.mecs-press.org/) DOI: 10.5815/ijitcs.2017.06.08 Optimization of System’s Performance with Kernel Tracing by Cohort Intelligence Aniket B. Tate Dept. of Computer Engineering, Vishwakarma Institute of Information Technology, Pune, 411048, India E-mail: [email protected] Laxmi A. Bewoor Dept. of Computer Engineering, Vishwakarma Institute of Information Technology, Pune, 411048, India E-mail: [email protected] Abstract—Linux tracing tools are used to record the execution time etc. which shows better results. While events running in the background on the system. But scheduling a process on one of the cores, the scheduler these tools lack to analyze the log data. In the field of considers the average waiting time, turnaround time, time Artificial Intelligence Cohort Intelligence (CI) is recently quantum for a process, number of context switches, proposed technique, which works on the principle of self- earliness, the tardiness of process etc. But the scheduler learning within a cohort. This paper presents an approach does not take CPU load into consideration. As a result of to optimize the performance of the system by tracing the this, the cores get unevenly loaded and many of the cores system, then extract the information from trace data and will be kept in ideal state. Cohort Intelligence (CI) is pass it to cohort intelligence algorithm. The output of recently introduced meta-heuristics [6][7] it works on cohort intelligence algorithm shows, how the load of the self-supervised learning behavior in a cohort.
    [Show full text]
  • OS Awareness Manual Linux
    OS Awareness Manual Linux TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... OS Awareness Manuals ................................................................................................................ OS Awareness and Run Mode Debugging for Linux .............................................................. OS Awareness Manual Linux ................................................................................................. 1 Overview ............................................................................................................................... 4 Terminology 4 Brief Overview of Documents for New Users 5 Supported Versions 5 Configuration ........................................................................................................................ 6 Quick Configuration Guide 6 Hooks & Internals in Linux 6 Features ................................................................................................................................ 8 Display of Kernel Resources 8 Task-Related Breakpoints 8 Task Context Display 9 MMU Support 11 Space IDs 11 MMU Declaration 11 Debugger Table Walk 17 Symbol Autoloader 18 SMP Support 19 Dynamic Task Performance Measurement 20 Task Runtime Statistics 20 Process / thread switch support for ARM using context ID register: 21 Task State Analysis 21 Function Runtime Statistics 22 Linux Specific Menu 24 Debugging Linux Kernel
    [Show full text]
  • BSD UNIX Toolbox 1000+ Commands for Freebsd, Openbsd
    76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page iii BSD UNIX® TOOLBOX 1000+ Commands for FreeBSD®, OpenBSD, and NetBSD®Power Users Christopher Negus François Caen 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page ii 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page i BSD UNIX® TOOLBOX 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page ii 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page iii BSD UNIX® TOOLBOX 1000+ Commands for FreeBSD®, OpenBSD, and NetBSD®Power Users Christopher Negus François Caen 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page iv BSD UNIX® Toolbox: 1000+ Commands for FreeBSD®, OpenBSD, and NetBSD® Power Users Published by Wiley Publishing, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 www.wiley.com Copyright © 2008 by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 978-0-470-37603-4 Manufactured in the United States of America 10 9 8 7 6 5 4 3 2 1 Library of Congress Cataloging-in-Publication Data is available from the publisher. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permis- sion should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4355, or online at http://www.wiley.com/go/permissions.
    [Show full text]