📄 1217-1218.html
字号:
<HTML>
<HEAD>
<TITLE>Linux Complete Command Reference:Miscellaneous:EarthWeb Inc.-</TITLE>
</HEAD>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<SCRIPT>
<!--
function displayWindow(url, width, height) {
var Win = window.open(url,"displayWindow",'width=' + width +
',height=' + height + ',resizable=1,scrollbars=yes');
}
//-->
</SCRIPT>
</HEAD>
-->
<!-- ISBN=0672311046 //-->
<!-- TITLE=Linux Complete Command Reference//-->
<!-- AUTHOR=Red Hat//-->
<!-- PUBLISHER=Macmillan Computer Publishing//-->
<!-- IMPRINT=Sams//-->
<!-- CHAPTER=07 //-->
<!-- PAGES=1213-1256 //-->
<!-- UNASSIGNED1 //-->
<!-- UNASSIGNED2 //-->
<P><CENTER>
<a href="1213-1216.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="0000-0000.html">Next</A></CENTER></P>
<A NAME="PAGENUM-1217"><P>Page 1217</P></A>
<P>Any remaining arguments that were not picked up by the kernel and were not interpreted as environment variables are
then passed onto process one, which is usually the init program. The most common argument that is passed to the init process
is the word single, which instructs init to boot the computer in single-user mode and not launch all the usual daemons.
Check the manual page for the version of init installed on your system to see what arguments it accepts.
</P>
<P><B>
GENERAL NON-DEVICE-SPECIFIC BOOT ARGS
</P></B>
<P>
no387<BR>
Some i387 coprocessor chips have bugs that show up when used in 32-bit protected mode.
</P>
<P>For example, some of the early ULSI-387 chips cause solid lockups while performing floating-point calculations. Using
the `no387' boot arg causes Linux to ignore the maths coprocessor even if you have one. Of course, you must then have
your kernel compiled with math emulation support!
</P>
<P>
no-hlt<BR>
Some of the early i486DX-100 chips have a problem with the
hlt instruction in that they can't reliably return to
operating mode after this instruction is used. Using the
`no-hlt' instruction tells Linux to just run an infinite loop when there
is nothing else to do and to not halt the CPU. This allows people with these broken chips to use Linux.
</P>
<P>
root=...
<BR>
This argument tells the kernel what device is to be used as the root filesystem while booting. The default of this setting
is determined at compile time and usually is the value of the root device of the system that the kernel was built on. To
override this value and select the second floppy drive as the root device, one uses
`root=/dev/fd1'. (The root device can also be set using
rdev(8).)</P>
<P>The root device can be specified symbolically or numerically. A symbolic specification has the form
/dev/XXYN, where XX designates the device type (hd for ST-506-compatible hard disk with
Y in a-h; sd for SCSI-compatible disk with Y in
a-e; xd for XT-compatible disk with Y either a or
b; fd for floppy disk with Y the floppy drive
number—fd0 is the DOS A: drive and fd1 is B:),
Y is the driver letter or number, and N is the number of the partition on this device (absent in the case of floppies).
</P>
<P>Note that this has nothing to do with the designation of these devices on your filesystem. The
/dev/ part is purely conventional.
<P>The more awkward and less portable numeric specification of the previous possible root devices in major/minor format
is also accepted. (For example, /dev/sda3 is major 8, minor 3, so you can use
root=0x803 as an alternative.)
</P>
<P>ro and rw
</P>
<P>The ro option tells the kernel to mount the root filesystem as
readonly so that filesystem consistency check programs
(fsck) can do their work on a quiescent file system. No processes can write to files on the filesystem in question until it is
remounted as read/write capable, such as by mount -w -n -o remount
/. (See also mount(8).)
</P>
<P>The rw option tells the kernel to mount the root filesystem read/write. This is the default.
</P>
<P>The choice between read-only and read/write can also be set
usingrdev(8).
</P>
<!-- CODE SNIP //-->
<PRE>
debug
</PRE>
<!-- END CODE SNIP //-->
<P>Kernel messages are handed off to the kernel log daemon
klogd so that they can be logged to disk. Messages with a
priority above console_loglevel are also printed on the console. (For these levels, see
<linux/kernel.h>.) By default, this variable is
set to log anything more important than debug messages. This boot argument causes the kernel to also print the messages
of DEBUG priority. The console log level can also be set at runtime via an option to
klogd. See klogd(8).
</P>
<!-- CODE SNIP //-->
<PRE>
reserve=...
</PRE>
<!-- END CODE SNIP //-->
<P>This is used to protect I/O port regions from probes. The form of the command is
</P>
<!-- CODE SNIP //-->
<PRE>
reserve=iobase,extent[,iobase,extent]...
</PRE>
<!-- END CODE SNIP //-->
<A NAME="PAGENUM-1218"><P>Page 1218</P></A>
<P>In some machines, it might be necessary to prevent device drivers from checking for devices (auto-probing) in a
specific region. This may be because of hardware that reacts badly to the probing, hardware that would be mistakenly identified,
or hardware you don't want the kernel to initialize.
</P>
<P>The reserve boot-time argument specifies an I/O port region that shouldn't be probed. A device driver does not probe
a reserved region unless another boot argument explicitly specifies that it do so.
</P>
<P>For example, the boot line
</P>
<!-- CODE SNIP //-->
<PRE>
reserve=0x300,32 blah=0x300
</PRE>
<!-- END CODE SNIP //-->
<P>keeps all device drivers except the driver for
blah from probing 0x300-0x31f.
</P>
<!-- CODE SNIP //-->
<PRE>
ramdisk=...
</PRE>
<!-- END CODE SNIP //-->
<P>This option is obsolete since Linux 1.3.48 or so. It specifies the size in kilobytes of the optional RAM disk device.
For example, if one wants to have a root filesystem on a 1.44MB floppy loaded into the RAM disk device, they use
</P>
<!-- CODE SNIP //-->
<PRE>
ramdisk=1440
</PRE>
<!-- END CODE SNIP //-->
<P>This option is set at compile time (default is no RAM disk), and can be modified using
rdev(8).
</P>
<!-- CODE SNIP //-->
<PRE>
mem=...
</PRE>
<!-- END CODE SNIP //-->
<P>The BIOS call defined in the PC specification that returns the amount of installed memory was only designed to be able
to report up to 64MB. Linux uses this BIOS call at boot to determine how much memory is installed. If you have more
than 64MB of RAM installed, you can use this boot arg to tell Linux how much memory you have. The value is in decimal
or hexadecimal (prefix 0x), and the suffixes K (times 1024) or
M (times 1048576) can be used. The following quote from
Linus describes the use of the mem= parameter:
</P>
<P>"The kernel will accept any mem=xx parameter you give it, and if it turns out that you lied to it, it will crash horribly sooner
or later. The parameter indicates the highest addressable RAM address, so
`mem=0x1000000' means you have 16MB of memory, for example. For a 96MB machine this would be
mem=0x6000000.
</P>
<P><B>
NOTE
</B></P>
<P>
Some machines might use the top of memory for BIOS caching or whatever, so you might not actually have up
to the full 96MB addressable. The reverse is also true: Some chipsets will map the physical memory that is covered by the
BIOS area into the area just past the top of memory, so the top-of-mem might actually be 96MB + 384KB, for example. If you
tell Linux that it has more memory than it actually does have, bad things will happen: maybe not at once, but surely eventually."
</P>
<!-- CODE SNIP //-->
<PRE>
reboot=warm
</PRE>
<!-- END CODE SNIP //-->
<P>Since 2.0.22, a reboot is by default a cold reboot. This command-line option changes back to the old default, a warm reboot.
</P>
<P><B>
BOOT ARGUMENTS FOR SCSI DEVICES
</P></B>
</P>
<P>General notation for this section:
</P>
<P>iobase—the first I/O port that the SCSI host occupies. These are specified in hexadecimal notation and usually lie in
the range from 0x200 to 0x3ff.
</P>
<P>irq—the hardware interrupt that the card is configured to use. Valid values are dependent on the card in question but
are usually 5, 7, 9, 10, 11, 12, and 15. The other values are usually used for common peripherals such as IDE hard disks,
floppies, serial ports, and so on.
</P>
<P>scsi-id—the ID that the host adapter uses to identify itself on the SCSI bus. Only some host adapters allow you to
change this value because most have it permanently specified internally. The usual default value is
7, but the Seagate and Future Domain TMC-950 boards use
6.
</P>
<P>parity—whether the SCSI host adapter expects the attached devices to supply a parity value with all information
exchanges. Specifying a 1 indicates parity checking is enabled, and a
0 disables parity checking. Again, not all adapters support
selection of parity behavior as a boot argument.
</P>
<P><CENTER>
<a href="1213-1216.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="0000-0000.html">Next</A></CENTER></P>
</td>
</tr>
</table>
<!-- begin footer information -->
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -