From owner-svn-doc-head@FreeBSD.ORG Mon Oct 29 00:50:21 2012 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E09FE1C; Mon, 29 Oct 2012 00:50:21 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:4f8:fff6::2c]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0538FC0C; Mon, 29 Oct 2012 00:50:21 +0000 (UTC) Received: from svn.freebsd.org (localhost [127.0.0.1]) by svn.freebsd.org (8.14.4/8.14.4) with ESMTP id q9T0oLYj039635; Mon, 29 Oct 2012 00:50:21 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.4/8.14.4/Submit) id q9T0oL1S039633; Mon, 29 Oct 2012 00:50:21 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201210290050.q9T0oL1S039633@svn.freebsd.org> From: Warren Block Date: Mon, 29 Oct 2012 00:50:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r39831 - head/en_US.ISO8859-1/books/handbook/basics X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2012 00:50:21 -0000 Author: wblock Date: Mon Oct 29 00:50:20 2012 New Revision: 39831 URL: http://svn.freebsd.org/changeset/doc/39831 Log: Whitespace-only fixes. Translators, please ignore. Modified: head/en_US.ISO8859-1/books/handbook/basics/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/basics/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/basics/chapter.xml Sun Oct 28 22:47:52 2012 (r39830) +++ head/en_US.ISO8859-1/books/handbook/basics/chapter.xml Mon Oct 29 00:50:20 2012 (r39831) @@ -9,7 +9,7 @@ - Chris + Chris Shumway Rewritten by @@ -22,75 +22,88 @@ Synopsis - The following chapter will cover the basic commands and - functionality of the FreeBSD operating system. Much of this - material is relevant for any &unix;-like operating system. Feel - free to skim over this chapter if you are familiar with the - material. If you are new to FreeBSD, then you will definitely - want to read through this chapter carefully. + The following chapter will cover the basic commands and + functionality of the FreeBSD operating system. Much of this + material is relevant for any &unix;-like operating system. Feel + free to skim over this chapter if you are familiar with the + material. If you are new to FreeBSD, then you will definitely + want to read through this chapter carefully. After reading this chapter, you will know: - How to use the virtual consoles of + How to use the virtual consoles of FreeBSD. + How &unix; file permissions work along with understanding file flags in &os;. + The default &os; file system layout. + The &os; disk organization. + How to mount and unmount file systems. + What processes, daemons, and signals are. + What a shell is, and how to change your default login - environment. + environment. + How to use basic text editors. + What devices and device nodes are. + What binary format is used under &os;. + How to read manual pages for more information. - Virtual Consoles and Terminals + virtual consoles terminals - FreeBSD can be used in various ways. One of them is typing commands - to a text terminal. A lot of the flexibility and power of a &unix; - operating system is readily available at your hands when using FreeBSD - this way. This section describes what terminals and - consoles are, and how you can use them in FreeBSD. + FreeBSD can be used in various ways. One of them is typing + commands to a text terminal. A lot of the flexibility and power + of a &unix; operating system is readily available at your hands + when using FreeBSD this way. This section describes what + terminals and consoles are, and + how you can use them in FreeBSD. The Console + console - If you have not configured FreeBSD to automatically start a - graphical environment during startup, the system will present you with - a login prompt after it boots, right after the startup scripts finish - running. You will see something similar to: + If you have not configured FreeBSD to automatically start + a graphical environment during startup, the system will + present you with a login prompt after it boots, right after + the startup scripts finish running. You will see something + similar to: Additional ABI support:. Local package initialization:. @@ -102,25 +115,26 @@ FreeBSD/i386 (pc3.example.org) (ttyv0) login: - The messages might be a bit different on your system, but you will - see something similar. The last two lines are what we are interested - in right now. The second last line reads: + The messages might be a bit different on your system, but + you will see something similar. The last two lines are what + we are interested in right now. The second last line + reads: FreeBSD/i386 (pc3.example.org) (ttyv0) - This line contains some bits of information about the system you - have just booted. You are looking at a FreeBSD - console, running on an Intel or compatible processor of the x86 - architecture - This is what i386 means. Note that even if - you are not running FreeBSD on an Intel 386 CPU, this is going to - be i386. It is not the type of your processor, - but the processor architecture that is shown - here. - . The name of this machine (every &unix; machine has a - name) is pc3.example.org, and you are now looking - at its system console—the ttyv0 - terminal. + This line contains some bits of information about the + system you have just booted. You are looking at a + FreeBSD console, running on an Intel or + compatible processor of the x86 architecture + This is what i386 means. Note that + even if you are not running FreeBSD on an Intel 386 CPU, + this is going to be i386. It is not + the type of your processor, but the processor + architecture that is shown here. + . The name of this machine (every &unix; machine + has a name) is pc3.example.org, and you are + now looking at its system console—the + ttyv0 terminal. Finally, the last line is always: @@ -135,110 +149,121 @@ login: Logging into FreeBSD FreeBSD is a multiuser, multiprocessing system. This is - the formal description that is usually given to a system that can be - used by many different people, who simultaneously run a lot of - programs on a single machine. + the formal description that is usually given to a system that + can be used by many different people, who simultaneously run a + lot of programs on a single machine. Every multiuser system needs some way to distinguish one user from the rest. In FreeBSD (and all the - &unix;-like operating systems), this is accomplished by requiring that - every user must log into the system before being able - to run programs. Every user has a unique name (the - username) and a personal, secret key (the - password). FreeBSD will ask for these two before - allowing a user to run any programs. + &unix;-like operating systems), this is accomplished by + requiring that every user must log into the + system before being able to run programs. Every user has a + unique name (the username) and a personal, + secret key (the password). FreeBSD will ask + for these two before allowing a user to run any + programs. startup scripts Right after FreeBSD boots and finishes running its startup scripts - Startup scripts are programs that are run automatically by - FreeBSD when booting. Their main function is to set things up for - everything else to run, and start any services that you have - configured to run in the background doing useful things. - , it will present you with a prompt and ask for a valid - username: + Startup scripts are programs that are run + automatically by FreeBSD when booting. Their main + function is to set things up for everything else to run, + and start any services that you have configured to run in + the background doing useful things. + , it will present you with a prompt and ask for a + valid username: login: - For the sake of this example, let us assume that your username is - john. Type john at this prompt and press - Enter. You should then be presented with a prompt to - enter a password: + For the sake of this example, let us assume that your + username is john. Type + john at this prompt and press + Enter. You should then be presented with a + prompt to enter a password: login: john Password: - Type in john's password now, and press - Enter. The password is not - echoed! You need not worry about this right now. Suffice - it to say that it is done for security reasons. - - If you have typed your password correctly, you should by now be - logged into FreeBSD and ready to try out all the available - commands. + Type in john's password now, and + press Enter. The password is + not echoed! You need not worry about this + right now. Suffice it to say that it is done for security + reasons. + + If you have typed your password correctly, you should by + now be logged into FreeBSD and ready to try out all the + available commands. You should see the MOTD or message of the day followed by a command prompt (a #, - $, or % character). This - indicates you have successfully logged into FreeBSD. + $, or % character). + This indicates you have successfully logged into + FreeBSD. Multiple Consoles - Running &unix; commands in one console is fine, but FreeBSD can - run many programs at once. Having one console where commands can be - typed would be a bit of a waste when an operating system like FreeBSD - can run dozens of programs at the same time. This is where - virtual consoles can be very helpful. - - FreeBSD can be configured to present you with many different - virtual consoles. You can switch from one of them to any other - virtual console by pressing a couple of keys on your keyboard. Each - console has its own different output channel, and FreeBSD takes care - of properly redirecting keyboard input and monitor output as you - switch from one virtual console to the next. + Running &unix; commands in one console is fine, but + FreeBSD can run many programs at once. Having one console + where commands can be typed would be a bit of a waste when an + operating system like FreeBSD can run dozens of programs at + the same time. This is where virtual consoles + can be very helpful. + + FreeBSD can be configured to present you with many + different virtual consoles. You can switch from one of them + to any other virtual console by pressing a couple of keys on + your keyboard. Each console has its own different output + channel, and FreeBSD takes care of properly redirecting + keyboard input and monitor output as you switch from one + virtual console to the next. Special key combinations have been reserved by FreeBSD for switching consoles - A fairly technical and accurate description of all the details - of the FreeBSD console and keyboard drivers can be found in the - manual pages of &man.syscons.4;, &man.atkbd.4;, &man.vidcontrol.1; - and &man.kbdcontrol.1;. We will not expand on the details here, - but the interested reader can always consult the manual pages for - a more detailed and thorough explanation of how things + A fairly technical and accurate description of all the + details of the FreeBSD console and keyboard drivers can be + found in the manual pages of &man.syscons.4;, + &man.atkbd.4;, &man.vidcontrol.1; and &man.kbdcontrol.1;. + We will not expand on the details here, but the interested + reader can always consult the manual pages for a more + detailed and thorough explanation of how things work. - . You can use + . You can use AltF1, - AltF2, through - AltF8 to switch - to a different virtual console in FreeBSD. - - As you are switching from one console to the next, FreeBSD takes - care of saving and restoring the screen output. The result is an - illusion of having multiple virtual - screens and keyboards that you can use to type commands for - FreeBSD to run. The programs that you launch on one virtual console - do not stop running when that console is not visible. They continue - running when you have switched to a different virtual console. + AltF2, + through + AltF8 + to switch to a different virtual console in FreeBSD. + + As you are switching from one console to the next, FreeBSD + takes care of saving and restoring the screen output. The + result is an illusion of having multiple + virtual screens and keyboards that you can use + to type commands for FreeBSD to run. The programs that you + launch on one virtual console do not stop running when that + console is not visible. They continue running when you have + switched to a different virtual console. The <filename>/etc/ttys</filename> File - The default configuration of FreeBSD will start up with eight - virtual consoles. This is not a hardwired setting though, and - you can easily customize your installation to boot with more - or fewer virtual consoles. The number and settings of the - virtual consoles are configured in the - /etc/ttys file. - - You can use the /etc/ttys file to configure - the virtual consoles of FreeBSD. Each uncommented line in this file - (lines that do not start with a # character) contains - settings for a single terminal or virtual console. The default - version of this file that ships with FreeBSD configures nine virtual - consoles, and enables eight of them. They are the lines that start with + The default configuration of FreeBSD will start up with + eight virtual consoles. This is not a hardwired setting + though, and you can easily customize your installation to boot + with more or fewer virtual consoles. The number and settings + of the virtual consoles are configured in the + /etc/ttys file. + + You can use the /etc/ttys file to + configure the virtual consoles of FreeBSD. Each uncommented + line in this file (lines that do not start with a + # character) contains settings for a single + terminal or virtual console. The default version of this file + that ships with FreeBSD configures nine virtual consoles, and + enables eight of them. They are the lines that start with ttyv: # name getty type status comments @@ -254,21 +279,22 @@ ttyv6 "/usr/libexec/getty Pc" ttyv7 "/usr/libexec/getty Pc" cons25 on secure ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure - For a detailed description of every column in this file and all - the options you can use to set things up for the virtual consoles, - consult the &man.ttys.5; manual page. + For a detailed description of every column in this file + and all the options you can use to set things up for the + virtual consoles, consult the &man.ttys.5; manual page. Single User Mode Console - A detailed description of what single user mode is - can be found in . It is worth noting - that there is only one console when you are running FreeBSD in single - user mode. There are no virtual consoles available. The settings of - the single user mode console can also be found in the - /etc/ttys file. Look for the line that starts - with console: + A detailed description of what + single user mode is can be found in + . It is worth noting that + there is only one console when you are running FreeBSD in + single user mode. There are no virtual consoles available. + The settings of the single user mode console can also be found + in the /etc/ttys file. Look for the line + that starts with console: # name getty type status comments # @@ -277,18 +303,20 @@ ttyv8 "/usr/X11R6/bin/xdm -nodaemon" console none unknown off secure - As the comments above the console line - indicate, you can edit this line and change secure to - insecure. If you do that, when FreeBSD boots - into single user mode, it will still ask for the - root password. + As the comments above the console + line indicate, you can edit this line and change + secure to insecure. + If you do that, when FreeBSD boots into single user mode, it + will still ask for the root + password. Be careful when changing this to - insecure. If you ever forget - the root password, booting into single user - mode is a bit involved. It is still possible, but it might be a bit - hard for someone who is not very comfortable with the FreeBSD - booting process and the programs involved. + insecure. If you ever + forget the root password, booting into + single user mode is a bit involved. It is still possible, + but it might be a bit hard for someone who is not very + comfortable with the FreeBSD booting process and the + programs involved. @@ -307,19 +335,21 @@ options SC_PIXEL_MODE Once the kernel has been recompiled with these two options, you can then determine what video modes are supported by your hardware by using the &man.vidcontrol.1; utility. To - get a list of supported video modes issue the following: + get a list of supported video modes issue the + following: &prompt.root; vidcontrol -i mode The output of this command is a list of video modes that are supported by your hardware. You can then choose to use a - new video mode by passing it to &man.vidcontrol.1; in a root console: + new video mode by passing it to &man.vidcontrol.1; in a + root console: &prompt.root; vidcontrol MODE_279 If the new video mode is acceptable, it can be permanently - set on boot by setting it in the /etc/rc.conf - file: + set on boot by setting it in the + /etc/rc.conf file: allscreens_flags="MODE_279" @@ -327,23 +357,24 @@ options SC_PIXEL_MODE Permissions + UNIX - FreeBSD, being a direct descendant of BSD &unix;, is based on - several key &unix; concepts. The first and - most pronounced is that FreeBSD is a multi-user operating system. - The system can handle several users all working simultaneously on - completely unrelated tasks. The system is responsible for properly - sharing and managing requests for hardware devices, peripherals, - memory, and CPU time fairly to each user. + FreeBSD, being a direct descendant of BSD &unix;, is based + on several key &unix; concepts. The first and most pronounced + is that FreeBSD is a multi-user operating system. The system + can handle several users all working simultaneously on + completely unrelated tasks. The system is responsible for + properly sharing and managing requests for hardware devices, + peripherals, memory, and CPU time fairly to each user. Because the system is capable of supporting multiple users, - everything the system manages has a set of permissions governing who - can read, write, and execute the resource. These permissions are - stored as three octets broken into three pieces, one for the owner of - the file, one for the group that the file belongs to, and one for - everyone else. This numerical representation works like - this: + everything the system manages has a set of permissions governing + who can read, write, and execute the resource. These + permissions are stored as three octets broken into three pieces, + one for the owner of the file, one for the group that the file + belongs to, and one for everyone else. This numerical + representation works like this: permissions @@ -419,7 +450,8 @@ options SC_PIXEL_MODE argument to &man.ls.1; to view a long directory listing that includes a column with information about a file's permissions for the owner, group, and everyone else. For example, a - ls -l in an arbitrary directory may show: + ls -l in an arbitrary directory may + show: &prompt.user; ls -l total 530 @@ -433,48 +465,49 @@ total 530 -rw-r--r-- - The first (leftmost) character - tells if this file is a regular file, a directory, a special - character device, a socket, or any other special - pseudo-file device. In this case, the - - indicates a regular file. The next three characters, - rw- in this example, give the permissions for the owner of the - file. The next three characters, r--, give the - permissions for the group that the file belongs to. The final three + The first (leftmost) character tells if this file is a + regular file, a directory, a special character device, a socket, + or any other special pseudo-file device. In this case, the + - indicates a regular file. The next three + characters, rw- in this example, give the + permissions for the owner of the file. The next three characters, r--, give the permissions for the - rest of the world. A dash means that the permission is turned off. - In the case of this file, the permissions are set so the owner can - read and write to the file, the group can read the file, and the - rest of the world can only read the file. According to the table + group that the file belongs to. The final three characters, + r--, give the permissions for the rest of the + world. A dash means that the permission is turned off. In the + case of this file, the permissions are set so the owner can read + and write to the file, the group can read the file, and the rest + of the world can only read the file. According to the table above, the permissions for this file would be - 644, where each digit represents the three parts - of the file's permission. + 644, where each digit represents the three + parts of the file's permission. This is all well and good, but how does the system control permissions on devices? FreeBSD actually treats most hardware - devices as a file that programs can open, read, and write data to - just like any other file. These special device files are stored on - the /dev directory. - - Directories are also treated as files. They have read, write, - and execute permissions. The executable bit for a directory has a - slightly different meaning than that of files. When a directory is - marked executable, it means it can be traversed into, that is, it is - possible to cd (change directory) into it. This also means that - within the directory it is possible to access files whose names are - known (subject, of course, to the permissions on the files + devices as a file that programs can open, read, and write data + to just like any other file. These special device files are + stored on the /dev directory. + + Directories are also treated as files. They have read, + write, and execute permissions. The executable bit for a + directory has a slightly different meaning than that of files. + When a directory is marked executable, it means it can be + traversed into, that is, it is possible to cd + (change directory) into it. This also means that within the + directory it is possible to access files whose names are known + (subject, of course, to the permissions on the files themselves). - In particular, in order to perform a directory listing, - read permission must be set on the directory, whilst to delete a file + In particular, in order to perform a directory listing, read + permission must be set on the directory, whilst to delete a file that one knows the name of, it is necessary to have write and execute permissions to the directory containing the file. - There are more permission bits, but they are primarily used in - special circumstances such as setuid binaries and sticky - directories. If you want more information on file permissions and - how to set them, be sure to look at the &man.chmod.1; manual + There are more permission bits, but they are primarily used + in special circumstances such as setuid binaries and sticky + directories. If you want more information on file permissions + and how to set them, be sure to look at the &man.chmod.1; manual page. @@ -489,12 +522,17 @@ total 530 Symbolic Permissions - permissionssymbolic - Symbolic permissions, sometimes referred to as symbolic expressions, - use characters in place of octal values to assign permissions to files - or directories. Symbolic expressions use the syntax of (who) (action) - (permissions), where the following values are available: + + permissions + symbolic + + + Symbolic permissions, sometimes referred to as symbolic + expressions, use characters in place of octal values to assign + permissions to files or directories. Symbolic expressions use + the syntax of (who) (action) (permissions), where the + following values are available: @@ -506,101 +544,102 @@ total 530 - - - (who) - u - User - + + + (who) + u + User + - - (who) - g - Group owner - + + (who) + g + Group owner + - - (who) - o - Other - + + (who) + o + Other + - - (who) - a - All (world) - + + (who) + a + All (world) + - - (action) - + - Adding permissions - + + (action) + + + Adding permissions + - - (action) - - - Removing permissions - + + (action) + - + Removing permissions + - - (action) - = - Explicitly set permissions - + + (action) + = + Explicitly set permissions + - - (permissions) - r - Read - + + (permissions) + r + Read + - - (permissions) - w - Write - + + (permissions) + w + Write + - - (permissions) - x - Execute - + + (permissions) + x + Execute + - - (permissions) - t - Sticky bit - + + (permissions) + t + Sticky bit + - - (permissions) - s - Set UID or GID - - - - + + (permissions) + s + Set UID or GID + + + + - These values are used with the &man.chmod.1; command - just like before, but with letters. For an example, you could use - the following command to block other users from accessing - FILE: - - &prompt.user; chmod go= FILE - - A comma separated list can be provided when more than one set - of changes to a file must be made. For example the following command - will remove the group and world write permission - on FILE, then it adds the execute - permissions for everyone: + These values are used with the &man.chmod.1; command + just like before, but with letters. For an example, you could + use the following command to block other users from accessing + FILE: + + &prompt.user; chmod go= FILE + + A comma separated list can be provided when more than one + set of changes to a file must be made. For example the + following command will remove the group and + world write permission on + FILE, then it adds the execute + permissions for everyone: - &prompt.user; chmod go-w,a+x FILE + &prompt.user; chmod go-w,a+x FILE @@ -618,18 +657,19 @@ total 530 &os; File Flags In addition to file permissions discussed previously, &os; - supports the use of file flags. These flags - add an additional level of security and control over files, but + supports the use of file flags. These flags add + an additional level of security and control over files, but not directories. These file flags add an additional level of control over files, helping to ensure that in some cases not even the root can remove or alter files. - File flags are altered by using the &man.chflags.1; utility, - using a simple interface. For example, to enable the system - undeletable flag on the file file1, - issue the following command: + File flags are altered by using the &man.chflags.1; + utility, using a simple interface. For example, to enable the + system undeletable flag on the file + file1, issue the following + command: &prompt.root; chflags sunlink file1 @@ -649,10 +689,10 @@ total 530 -rw-r--r-- 1 trhodes trhodes sunlnk 0 Mar 1 05:54 file1 Several flags may only added or removed to files by the - root user. In other cases, the file owner - may set these flags. It is recommended that administrators read - over the &man.chflags.1; and &man.chflags.2; manual pages for - more information. + root user. In other cases, the file + owner may set these flags. It is recommended that + administrators read over the &man.chflags.1; and + &man.chflags.2; manual pages for more information. @@ -666,7 +706,8 @@ total 530 - The <literal>setuid</literal>, <literal>setgid</literal>, and <literal>sticky</literal> Permissions + The <literal>setuid</literal>, <literal>setgid</literal>, + and <literal>sticky</literal> Permissions Other than the permissions already discussed, there are three other specific settings that all administrators should @@ -693,9 +734,9 @@ total 530 The nosuid &man.mount.8; option will cause these binaries to silently fail. That is, they will fail to execute without ever alerting the user. That option - is also not completely reliable as a nosuid - wrapper may be able to circumvent it; according to the - &man.mount.8; manual page. + is also not completely reliable as a + nosuid wrapper may be able to circumvent + it; according to the &man.mount.8; manual page. The setuid permission may be set by prefixing a permission @@ -772,8 +813,8 @@ root 5211 0.0 0.2 3620 1724 2 that can strengthen the security of a system: the sticky bit. - The sticky bit, when set on a directory, - allows file deletion only by the file owner. This + The sticky bit, when set on a + directory, allows file deletion only by the file owner. This permission set is useful to prevent file deletion in public directories, such as /tmp, by users who do @@ -797,6 +838,7 @@ root 5211 0.0 0.2 3620 1724 2 Directory Structure + directory hierarchy The FreeBSD directory hierarchy is fundamental to obtaining @@ -805,23 +847,25 @@ root 5211 0.0 0.2 3620 1724 2 /. This directory is the first one mounted at boot time and it contains the base system necessary to prepare the operating system for multi-user operation. The root - directory also contains mount points for other file systems - that are mounted during the transition to multi-user + directory also contains mount points for other file systems that + are mounted during the transition to multi-user operation. - A mount point is a directory where additional file systems can - be grafted onto a parent file system (usually the root file system). - This is further described in . - Standard mount points include - /usr, /var, /tmp, - /mnt, and /cdrom. These - directories are usually referenced to entries in the file - /etc/fstab. /etc/fstab is - a table of various file systems and mount points for reference by the - system. Most of the file systems in /etc/fstab - are mounted automatically at boot time from the script &man.rc.8; - unless they contain the option. - Details can be found in . + A mount point is a directory where additional file systems + can be grafted onto a parent file system (usually the root file + system). This is further described in + . Standard mount points + include /usr, /var, + /tmp, /mnt, and + /cdrom. These directories are usually + referenced to entries in the file + /etc/fstab. + /etc/fstab is a table of various file + systems and mount points for reference by the system. Most of + the file systems in /etc/fstab are mounted + automatically at boot time from the script &man.rc.8; unless + they contain the option. Details can be + found in . A complete description of the file system hierarchy is available in &man.hier.7;. For now, a brief overview of the @@ -829,7 +873,7 @@ root 5211 0.0 0.2 3620 1724 2 - + Directory @@ -837,326 +881,366 @@ root 5211 0.0 0.2 3620 1724 2 - + / Root directory of the file system. - + - /bin/ + /bin/ User utilities fundamental to both single-user - and multi-user environments. + and multi-user environments. - /boot/ + /boot/ Programs and configuration files used during - operating system bootstrap. + operating system bootstrap. - /boot/defaults/ + /boot/defaults/ Default bootstrapping configuration files; see - &man.loader.conf.5;. + &man.loader.conf.5;. - /dev/ + /dev/ Device nodes; see &man.intro.4;. - /etc/ + /etc/ System configuration files and scripts. - /etc/defaults/ - Default system configuration files; see &man.rc.8;. + /etc/defaults/ + Default system configuration files; see + &man.rc.8;. - /etc/mail/ - Configuration files for mail transport agents such - as &man.sendmail.8;. + /etc/mail/ + Configuration files for mail transport agents + such as &man.sendmail.8;. - /etc/namedb/ + /etc/namedb/ named configuration files; see - &man.named.8;. + &man.named.8;. - /etc/periodic/ + /etc/periodic/ Scripts that are run daily, weekly, and monthly, via &man.cron.8;; see &man.periodic.8;. *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***