From owner-p4-projects@FreeBSD.ORG Tue Jan 31 17:10:48 2012 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 4EBFF106566C; Tue, 31 Jan 2012 17:10:48 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 100B7106564A for ; Tue, 31 Jan 2012 17:10:48 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id EF7E88FC0A for ; Tue, 31 Jan 2012 17:10:47 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id q0VHAlMF054148 for ; Tue, 31 Jan 2012 17:10:47 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id q0VHAlrv054140 for perforce@freebsd.org; Tue, 31 Jan 2012 17:10:47 GMT (envelope-from rene@FreeBSD.org) Date: Tue, 31 Jan 2012 17:10:47 GMT Message-Id: <201201311710.q0VHAlrv054140@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 205476 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 17:10:48 -0000 http://p4web.freebsd.org/@@205476?ac=10 Change 205476 by rene@rene_acer on 2012/01/31 17:09:47 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#36 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/boot/chapter.sgml#9 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.sgml#10 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#19 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml#8 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mac/chapter.sgml#10 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#21 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#126 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/contributing-ports/article.sgml#19 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/boot/chapter.sgml#11 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#28 integrate .. //depot/projects/docproj_nl/share/mk/doc.common.mk#2 integrate .. //depot/projects/docproj_nl/share/mk/doc.docbook.mk#3 integrate .. //depot/projects/docproj_nl/share/mk/doc.html.mk#2 integrate .. //depot/projects/docproj_nl/share/mk/doc.xml.mk#4 integrate .. //depot/projects/docproj_nl/share/sgml/freebsd-html.dsl#9 integrate .. //depot/projects/docproj_nl/share/sgml/mirrors.xml#33 integrate .. //depot/projects/docproj_nl/www/en/developers.sgml#68 integrate .. //depot/projects/docproj_nl/www/en/index.xsl#13 integrate .. //depot/projects/docproj_nl/www/en/releng/index.sgml#47 integrate .. //depot/projects/docproj_nl/www/nl/administration.sgml#38 integrate .. //depot/projects/docproj_nl/www/share/mk/web.site.mk#6 integrate .. //depot/projects/docproj_nl/www/share/sgml/common.ent#6 integrate .. //depot/projects/docproj_nl/www/share/sgml/events2012.xml#4 integrate .. //depot/projects/docproj_nl/www/share/sgml/header.ent#11 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#129 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#36 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -976,62 +976,60 @@ identifies the type of each network and the capabilities of the stations operating there: - - - E + + Station Capability Codes - - Extended Service Set (ESS). Indicates that the - station is part of an infrastructure network (in - contrast to an IBSS/ad-hoc network). - - + + + + Capability Code + Meaning + + - - I + + + E + Extended Service Set (ESS). Indicates that + the station is part of an infrastructure network + (in contrast to an IBSS/ad-hoc network). + - - IBSS/ad-hoc network. Indicates that the station - is part of an ad-hoc network (in contrast to an ESS - network). - - + + I + IBSS/ad-hoc network. Indicates that the + station is part of an ad-hoc network (in contrast + to an ESS network). + - - P + + P + Privacy. Data confidentiality is required + for all data frames exchanged within the BSS. + This means that this BSS requires the station to + use cryptographic means such as WEP, TKIP or + AES-CCMP to encrypt/decrypt data frames being + exchanged with others. + - - Privacy. Data confidentiality is required for - all data frames exchanged within the BSS. This means - that this BSS requires the station to use - cryptographic means such as WEP, TKIP or AES-CCMP to - encrypt/decrypt data frames being exchanged with - others. - - + + S + Short Preamble. Indicates that the network + is using short preambles (defined in 802.11b High + Rate/DSSS PHY, short preamble utilizes a 56 bit + sync field in contrast to a 128 bit field used in + long preamble mode). + - - S - - - Short Preamble. Indicates that the network is - using short preambles (defined in 802.11b High - Rate/DSSS PHY, short preamble utilizes a 56 bit sync - field in contrast to a 128 bit field used in long - preamble mode). - - - - - s - - - Short slot time. Indicates that the 802.11g - network is using a short slot time because there are - no legacy (802.11b) stations present. - - - + + s + Short slot time. Indicates that the 802.11g + network is using a short slot time because there + are no legacy (802.11b) stations present. + + + +
One can also display the current list of known networks with: ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/boot/chapter.sgml#9 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -12,76 +12,80 @@ booting bootstrap - The process of starting a computer and loading the operating system - is referred to as the bootstrap process, or simply - booting. FreeBSD's boot process provides a great deal of - flexibility in customizing what happens when you start the system, - allowing you to select from different operating systems installed on the - same computer, or even different versions of the same operating system - or installed kernel. + The process of starting a computer and loading the operating + system is referred to as the bootstrap process, + or simply booting. FreeBSD's boot process + provides a great deal of flexibility in customizing what happens + when you start the system, allowing you to select from different + operating systems installed on the same computer, or even + different versions of the same operating system or installed + kernel. - This chapter details the configuration options you can set and how - to customize the FreeBSD boot process. This includes everything that - happens until the FreeBSD kernel has started, probed for devices, and - started &man.init.8;. If you are not quite sure when this happens, it - occurs when the text color changes from bright white to grey. + This chapter details the configuration options you can set + and how to customize the FreeBSD boot process. This includes + everything that happens until the FreeBSD kernel has started, + probed for devices, and started &man.init.8;. If you are not + quite sure when this happens, it occurs when the text color + changes from bright white to grey. After reading this chapter, you will know: - What the components of the FreeBSD bootstrap system are, and how - they interact. + What the components of the FreeBSD bootstrap system are, + and how they interact. - The options you can give to the components in the FreeBSD - bootstrap to control the boot process. + The options you can give to the components in the + FreeBSD bootstrap to control the boot process. - + - The basics of &man.device.hints.5;. + The basics of &man.device.hints.5;. x86 Only - This chapter only describes the boot process for FreeBSD running - on Intel x86 systems. + This chapter only describes the boot process for FreeBSD + running on Intel x86 systems. The Booting Problem - Turning on a computer and starting the operating system poses an - interesting dilemma. By definition, the computer does not know how to - do anything until the operating system is started. This includes - running programs from the disk. So if the computer can not run a - program from the disk without the operating system, and the operating - system programs are on the disk, how is the operating system - started? + Turning on a computer and starting the operating system + poses an interesting dilemma. By definition, the computer does + not know how to do anything until the operating system is + started. This includes running programs from the disk. So if + the computer can not run a program from the disk without the + operating system, and the operating system programs are on the + disk, how is the operating system started? - This problem parallels one in the book The Adventures of - Baron Munchausen. A character had fallen part way down a - manhole, and pulled himself out by grabbing his bootstraps, and - lifting. In the early days of computing the term - bootstrap was applied to the mechanism used to - load the operating system, which has become shortened to - booting. + This problem parallels one in the book The + Adventures of Baron Munchausen. A character had + fallen part way down a manhole, and pulled himself out by + grabbing his bootstraps, and lifting. In the early days of + computing the term bootstrap was applied + to the mechanism used to load the operating system, which has + become shortened to booting. BIOS - Basic Input/Output SystemBIOS + Basic Input/Output + SystemBIOS - On x86 hardware the Basic Input/Output System (BIOS) is responsible - for loading the operating system. To do this, the BIOS looks on the - hard disk for the Master Boot Record (MBR), which must be located on a - specific place on the disk. The BIOS has enough knowledge to load and - run the MBR, and assumes that the MBR can then carry out the rest of the - tasks involved in loading the operating system, - possibly with the help of the BIOS. + On x86 hardware the Basic Input/Output System (BIOS) is + responsible for loading the operating system. To do this, the + BIOS looks on the hard disk for the Master Boot Record (MBR), + which must be located on a specific place on the disk. The BIOS + has enough knowledge to load and run the MBR, and assumes that + the MBR can then carry out the rest of the tasks involved in + loading the operating system, possibly with the help of the + BIOS. Master Boot Record (MBR) @@ -89,51 +93,57 @@ Boot Loader - The code within the MBR is usually referred to as a boot - manager, especially when it interacts with the user. In this case - the boot manager usually has more code in the first - track of the disk or within some OS's file system. (A - boot manager is sometimes also called a boot loader, - but FreeBSD uses that term for a later stage of booting.) Popular boot - managers include boot0 (a.k.a. Boot - Easy, the standard &os; boot manager), - Grub, GAG, and - LILO. - (Only boot0 fits within the MBR.) + The code within the MBR is usually referred to as a + boot manager, especially when it interacts + with the user. In this case the boot manager usually has more + code in the first track of the disk or + within some OS's file system. (A boot manager is sometimes also + called a boot loader, but FreeBSD uses that + term for a later stage of booting.) Popular boot managers + include boot0 (a.k.a. + Boot Easy, the standard &os; boot + manager), Grub, + GAG, and + LILO. (Only + boot0 fits within the MBR.) - If you have only one operating system installed on your disks then - a standard PC MBR will suffice. This MBR searches for the first bootable - (a.k.a. active) slice on the disk, and then runs the code on that slice to - load the remainder of the operating system. The MBR installed by - &man.fdisk.8;, by default, is such an MBR. It is based on + If you have only one operating system installed on your + disks then a standard PC MBR will suffice. This MBR searches + for the first bootable (a.k.a. active) slice on the disk, and + then runs the code on that slice to load the remainder of the + operating system. The MBR installed by &man.fdisk.8;, by + default, is such an MBR. It is based on /boot/mbr. - If you have installed multiple operating systems on your disks then - you can install a different boot manager, one that can display a list of - different operating systems, and allows you to choose the one to boot - from. Two of these are discussed in the next subsection. + If you have installed multiple operating systems on your + disks then you can install a different boot manager, one that + can display a list of different operating systems, and allows + you to choose the one to boot from. Two of these are discussed + in the next subsection. - The remainder of the FreeBSD bootstrap system is divided into three - stages. The first stage is run by the MBR, which knows just enough to - get the computer into a specific state and run the second stage. The - second stage can do a little bit more, before running the third stage. - The third stage finishes the task of loading the operating system. The - work is split into these three stages because the PC standards put - limits on the size of the programs that can be run at stages one and - two. Chaining the tasks together allows FreeBSD to provide a more + The remainder of the FreeBSD bootstrap system is divided + into three stages. The first stage is run by the MBR, which + knows just enough to get the computer into a specific state and + run the second stage. The second stage can do a little bit + more, before running the third stage. The third stage finishes + the task of loading the operating system. The work is split + into these three stages because the PC standards put limits on + the size of the programs that can be run at stages one and two. + Chaining the tasks together allows FreeBSD to provide a more flexible loader. kernel init - The kernel is then started and it begins to probe for devices - and initialize them for use. Once the kernel boot - process is finished, the kernel passes control to the user process - &man.init.8;, which then makes sure the disks are in a usable state. - &man.init.8; then starts the user-level resource configuration which - mounts file systems, sets up network cards to communicate on the - network, and generally starts all the processes that usually - are run on a FreeBSD system at startup. + The kernel is then started and it begins to probe for + devices and initialize them for use. Once the kernel boot + process is finished, the kernel passes control to the user + process &man.init.8;, which then makes sure the disks are in a + usable state. &man.init.8; then starts the user-level resource + configuration which mounts file systems, sets up network cards + to communicate on the network, and generally starts all the + processes that usually are run on a FreeBSD system at + startup. @@ -143,22 +153,31 @@ The Boot Manager - Master Boot Record (MBR) + Master Boot Record + (MBR) + + The code in the MBR or boot manager is sometimes referred + to as stage zero of the boot process. + This subsection discusses two of the boot managers previously + mentioned: boot0 and + LILO. - The code in the MBR or boot manager is sometimes referred to as - stage zero of the boot process. This subsection - discusses two of the boot managers previously mentioned: - boot0 and LILO. + + The <application>boot0</application> Boot + Manager: - The <application>boot0</application> Boot Manager: - The MBR installed by FreeBSD's installer or &man.boot0cfg.8;, by - default, is based on /boot/boot0. - (The boot0 program is very simple, since the - program in the MBR can only be 446 bytes long because of the slice - table and 0x55AA identifier at the end of the MBR.) - If you have installed boot0 and - multiple operating systems on your hard disks, then you will see a - display similar to this one at boot time: + The MBR installed by FreeBSD's installer or + &man.boot0cfg.8;, by default, is based on + /boot/boot0. (The + boot0 program is very simple, + since the program in the MBR can only be + 446 bytes long because of the slice table and + 0x55AA identifier at the end of the MBR.) + If you have installed boot0 and + multiple operating systems on your hard disks, then you will + see a display similar to this one at boot + time: + <filename>boot0</filename> Screenshot @@ -172,71 +191,77 @@ Default: F2 - Other operating systems, in particular &windows;, have been known - to overwrite an existing MBR with their own. If this happens to you, - or you want to replace your existing MBR with the FreeBSD MBR then use - the following command: + Other operating systems, in particular &windows;, have + been known to overwrite an existing MBR with their own. If + this happens to you, or you want to replace your existing MBR + with the FreeBSD MBR then use the following command: &prompt.root; fdisk -B -b /boot/boot0 device - where device is the device that you - boot from, such as ad0 for the first IDE - disk, ad2 for the first IDE disk on a second - IDE controller, da0 for the first SCSI disk, - and so on. Or, if you want a custom configuration of the MBR, - use &man.boot0cfg.8;. + where device is the device that + you boot from, such as ad0 for the + first IDE disk, ad2 for the first IDE + disk on a second IDE controller, da0 + for the first SCSI disk, and so on. Or, if you want a custom + configuration of the MBR, use &man.boot0cfg.8;. - The LILO Boot Manager: + + The LILO Boot Manager: - To install this boot manager so it will also boot FreeBSD, first - start Linux and add the following to your existing - /etc/lilo.conf configuration file: + To install this boot manager so it will also boot + FreeBSD, first start Linux and add the following to your + existing /etc/lilo.conf configuration + file: + other=/dev/hdXY table=/dev/hdX loader=/boot/chain.b label=FreeBSD - In the above, specify FreeBSD's primary partition and drive using - Linux specifiers, replacing X with the Linux - drive letter and Y with the Linux primary - partition number. If you are using a SCSI drive, you - will need to change /dev/hd to read something - similar to /dev/sd. The - line can be omitted if you have - both operating systems on the same drive. Now run - /sbin/lilo -v to commit your new changes to the - system; this should be verified by checking its screen messages. + In the above, specify FreeBSD's primary partition and + drive using Linux specifiers, replacing + X with the Linux drive letter and + Y with the Linux primary partition + number. If you are using a SCSI drive, you + will need to change /dev/hd to read + something similar to /dev/sd. The + line can be omitted if + you have both operating systems on the same drive. Now run + /sbin/lilo -v to commit your new + changes to the system; this should be verified by checking its + screen messages. - + - Stage One, <filename>/boot/boot1</filename>, and Stage Two, - <filename>/boot/boot2</filename> - - Conceptually the first and second stages are part of the same - program, on the same area of the disk. Because of space constraints - they have been split into two, but you would always install them - together. They are copied from the combined file - /boot/boot by the installer or - bsdlabel (see below). + Stage One, <filename>/boot/boot1</filename>, and Stage + Two, <filename>/boot/boot2</filename> + + Conceptually the first and second stages are part of the + same program, on the same area of the disk. Because of space + constraints they have been split into two, but you would + always install them together. They are copied from the + combined file /boot/boot by the installer + or bsdlabel (see below). + + They are located outside file systems, in the first track + of the boot slice, starting with the first sector. This is + where boot0, or any other + boot manager, expects to find a program to run which will + continue the boot process. The number of sectors used is + easily determined from the size of + /boot/boot. - They are located outside file systems, in the first track of - the boot slice, starting with the first sector. This is where boot0, or any other boot manager, - expects to find a program to run which will - continue the boot process. The number of sectors used is easily - determined from the size of /boot/boot. + boot1 is very simple, since it can + only be 512 bytes in size, and knows just enough about the + FreeBSD bsdlabel, which stores + information about the slice, to find and execute + boot2. - boot1 is very simple, since it - can only be 512 bytes - in size, and knows just enough about the FreeBSD - bsdlabel, which stores information - about the slice, to find and execute boot2. - - boot2 is slightly more sophisticated, and understands - the FreeBSD file system enough to find files on it, and can - provide a simple interface to choose the kernel or loader to - run. + boot2 is slightly more sophisticated, + and understands the FreeBSD file system enough to find files + on it, and can provide a simple interface to choose the kernel + or loader to run. Since the loader is much more sophisticated, and provides a nice easy-to-use @@ -255,261 +280,270 @@ If you ever need to replace the installed boot1 and boot2 use &man.bsdlabel.8;: - + &prompt.root; bsdlabel -B diskslice - where diskslice is the disk and slice - you boot from, such as ad0s1 for the first - slice on the first IDE disk. + where diskslice is the disk and + slice you boot from, such as ad0s1 + for the first slice on the first IDE disk. Dangerously Dedicated Mode If you use just the disk name, such as - ad0, in the &man.bsdlabel.8; command you - will create a dangerously dedicated disk, without slices. This is - almost certainly not what you want to do, so make sure you double - check the &man.bsdlabel.8; command before you press - Return. + ad0, in the &man.bsdlabel.8; + command you will create a dangerously dedicated disk, + without slices. This is almost certainly not what you want + to do, so make sure you double check the &man.bsdlabel.8; + command before you press Return. - - Stage Three, <filename>/boot/loader</filename> + + Stage Three, <filename>/boot/loader</filename> + + boot-loader + + The loader is the final stage of the three-stage + bootstrap, and is located on the file system, usually as + /boot/loader. + + The loader is intended as a user-friendly method for + configuration, using an easy-to-use built-in command set, + backed up by a more powerful interpreter, with a more complex + command set. + + + Loader Program Flow + + During initialization, the loader will probe for a + console and for disks, and figure out what disk it is + booting from. It will set variables accordingly, and an + interpreter is started where user commands can be passed + from a script or interactively. + + loader + loader configuration + + The loader will then read + /boot/loader.rc, which by default reads + in /boot/defaults/loader.conf which + sets reasonable defaults for variables and reads + /boot/loader.conf for local changes to + those variables. loader.rc then acts + on these variables, loading whichever modules and kernel are + selected. + + Finally, by default, the loader issues a 10 second wait + for key presses, and boots the kernel if it is not + interrupted. If interrupted, the user is presented with a + prompt which understands the easy-to-use command set, where + the user may adjust variables, unload all modules, load + modules, and then finally boot or reboot. + + + + Loader Built-In Commands + + These are the most commonly used loader commands. For a + complete discussion of all available commands, please see + &man.loader.8;. - boot-loader - The loader is the final stage of the three-stage - bootstrap, and is located on the file system, usually as - /boot/loader. - - The loader is intended as a user-friendly method for - configuration, using an easy-to-use built-in command set, - backed up by a more powerful interpreter, with a more complex - command set. + + + autoboot seconds - - Loader Program Flow - - During initialization, the loader will probe for a - console and for disks, and figure out what disk it is - booting from. It will set variables accordingly, and an - interpreter is started where user commands can be passed from - a script or interactively. - loader - loader configuration + + Proceeds to boot the kernel if not interrupted + within the time span given, in seconds. It displays a + countdown, and the default time span is 10 + seconds. + + - The loader will then read - /boot/loader.rc, which by default reads - in /boot/defaults/loader.conf which - sets reasonable defaults for variables and reads - /boot/loader.conf for local changes to - those variables. loader.rc then acts - on these variables, loading whichever modules and kernel are - selected. + + boot + -options + kernelname - Finally, by default, the loader issues a 10 second wait - for key presses, and boots the kernel if it is not interrupted. - If interrupted, the user is presented with a prompt which - understands the easy-to-use command set, where the user may - adjust variables, unload all modules, load modules, and then - finally boot or reboot. + + Immediately proceeds to boot the kernel, with the + given options, if any, and with the kernel name given, + if it is. Providing a kernel name on the command-line + is only applicable after an + unload command has been issued, + otherwise the previously-loaded kernel will be + used. + + - - - - Loader Built-In Commands - - These are the most commonly used loader commands. For a - complete discussion of all available commands, please see - &man.loader.8;. + + boot-conf - - - autoboot seconds + + Goes through the same automatic configuration of + modules based on variables as what happens at boot. + This only makes sense if you use + unload first, and change some + variables, most commonly kernel. + + - - Proceeds to boot the kernel if not interrupted - within the time span given, in seconds. It displays a - countdown, and the default time span is 10 - seconds. - - + + help + topic - - boot - -options - kernelname + + Shows help messages read from + /boot/loader.help. If the topic + given is index, then the list of + available topics is given. + + - - Immediately proceeds to boot the kernel, with the - given options, if any, and with the kernel name given, - if it is. Providing a kernel name on the command-line - is only applicable after an unload - command has been issued, otherwise the previously-loaded - kernel will be used. - - + + include filename + … - - boot-conf + + Processes the file with the given filename. The + file is read in, and interpreted line by line. An + error immediately stops the include command. + + - - Goes through the same automatic configuration of - modules based on variables as what happens at boot. - This only makes sense if you use - unload first, and change some - variables, most commonly kernel. - - + + load + type + filename - - help - topic + + Loads the kernel, kernel module, or file of the + type given, with the filename given. Any arguments + after filename are passed to the file. + + - - Shows help messages read from - /boot/loader.help. If the topic - given is index, then the list of - available topics is given. - - + + ls + path - - include filename - … + + Displays a listing of files in the given path, or + the root directory, if the path is not specified. If + is specified, file sizes will be + shown too. + + - - Processes the file with the given filename. The - file is read in, and interpreted line by line. An - error immediately stops the include command. - - - - load - type - filename + + lsdev + - - Loads the kernel, kernel module, or file of the - type given, with the filename given. Any arguments - after filename are passed to the file. - - - - ls - path + + Lists all of the devices from which it may be + possible to load modules. If is + specified, more details are printed. + + - - Displays a listing of files in the given path, or - the root directory, if the path is not specified. If - is specified, file sizes will be - shown too. - - - - lsdev + + lsmod + - - Lists all of the devices from which it may be - possible to load modules. If is - specified, more details are printed. - - + + Displays loaded modules. If + is specified, more details are shown. + + - - lsmod + + more filename - - Displays loaded modules. If is - specified, more details are shown. - - + + Displays the files specified, with a pause at each + LINES displayed. + + - - more filename + + reboot - - Displays the files specified, with a pause at each - LINES displayed. - - + + Immediately reboots the system. + + - - reboot + + set variable + set + variable=value - - Immediately reboots the system. - - + + Sets the loader's environment variables. + + - - set variable - set - variable=value + + unload - - Sets the loader's environment variables. - - + + Removes all loaded modules. + + + + - - unload + + Loader Examples - - Removes all loaded modules. - - - - + Here are some practical examples of loader usage: - - Loader Examples + + single-user mode - Here are some practical examples of loader usage: + + To simply boot your usual kernel, but in single-user + mode: - - single-user mode - - To simply boot your usual kernel, but in single-user - mode: + boot -s + - boot -s - + + To unload your usual kernel and modules, and then + load just your old (or another) kernel: - - To unload your usual kernel and modules, and then - load just your old (or another) kernel: - - kernel.old - + + kernel.old + - unload + unload load kernel.old - You can use kernel.GENERIC to - refer to the generic kernel that comes on the install - disk, or kernel.old to refer to - your previously installed kernel (when you have upgraded - or configured your own kernel, for example). + You can use kernel.GENERIC to + refer to the generic kernel that comes on the install + disk, or kernel.old to refer to + your previously installed kernel (when you have upgraded + or configured your own kernel, for example). >>> TRUNCATED FOR MAIL (1000 lines) <<<