📄 1150-1151.html
字号:
<HTML>
<HEAD>
<TITLE>Linux Complete Command Reference:File Formats: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=05 //-->
<!-- PAGES=1103-1208 //-->
<!-- UNASSIGNED1 //-->
<!-- UNASSIGNED2 //-->
<P><CENTER>
<a href="1148-1149.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="1152-1154.html">Next</A></CENTER></P>
<A NAME="PAGENUM-1150"><P>Page 1150</P></A>
<TABLE>
<TR><TD>
table=device
</TD><TD>
This specifies the device that contains the partition table. The boot loader will not
pass partition information to the booted operating system if this variable is omitted.
(Some operating systems have other means to determine from which partition they have
been booted. For example, MS-DOS usually stores the geometry of the boot disk or partition
in its boot sector.) Note that /sbin/lilo must be rerun if a partition table mapped
referenced with table is modified.
</TD></TR><TR><TD>
unsafe
</TD><TD>
Do not access the boot sector at map creation time. This disables some sanity
checks, including a partition table check. If the boot sector is on a fixed-format floppy disk
device, using UNSAFE avoids the need to put a readable disk into the drive when running the
map installer. unsafe and table are mutually incompatible.
</TD></TR></TABLE>
<P>In both cases, the following options apply:
</P>
<TABLE>
<TR><TD>
label=name
</TD><TD>
The boot loader uses the main file
name (without its path) of each image specification
to identify that image. A different name can be used by setting the variable
label.
</TD></TR><TR><TD>
alias=name
</TD><TD>
A second name for the same entry can be used by specifying an alias.
</TD></TR><TR><TD>
lock
</TD><TD>
(See previous description.)
</TD></TR><TR><TD>
optional
</TD><TD>
Omit the image if it is not available at map creation time. This is useful to specify
test kernels that are not always present.
</TD></TR><TR><TD>
password=password
</TD><TD>
Protect the image by a password.
</TD></TR><TR><TD>
restricted
</TD><TD>
A password is only required to boot the image if parameters are specified on the
command line (such as single).
</TD></TR></TABLE>
<P><B>
KERNEL OPTIONS
</B></P>
<P>If the booted image is a Linux kernel, then one may pass command-line parameters to this kernel.
</P>
<TABLE>
<TR><TD>
append=string
</TD><TD>
Appends the options specified to the parameter line passed to the kernel. This is
typically used to specify parameters of hardware that can't be entirely autodetected or for
which probing may be dangerous. Example: append =
"hd=64,32,202".
</TD></TR><TR><TD>
literal=string
</TD><TD>
Like append but removes all other options (such as setting of the root device). Because
vital options can be removed unintentionally with
literal, this option cannot be set in the global options section.
</TD></TR><TR><TD>
ramdisk=size
</TD><TD>
This specifies the size of the optional RAM disk. A value of zero indicates that no RAM
disk should be created. If this variable is omitted, the RAM disk size configured into the
boot image is used.
</TD></TR><TR><TD>
read-only
</TD><TD>
This specifies that the root filesystem should be mounted read-only. Typically, the
system startup procedure remounts the root filesystem read-write later (such as after
fscking it).
</TD></TR><TR><TD>
read-write
</TD><TD>
This specifies that the root filesystem should be mounted read-write.
</TD></TR><TR><TD>
root=root-device
</TD><TD>
This specifies the device that should be mounted as root. If the special name
current is used, the root device is set to the device on which the root filesystem is currently mounted. If
the root has been changed with -r, the respective device is used. If the variable
root is omitted, the root device setting contained in the kernel image is used. (That is set at compile
time using the ROOT DEV variable in the kernel makefile and can later be changed with the
rdev(8) program.)
</TD></TR><TR><TD>
vga=mode
</TD><TD>
This specifies the VGA text mode that should be selected when booting. The
following values are recognized (case is ignored):
</TD></TR><TR><TD>
</TD><TD>
normal: Select normal 80x25 text mode.
</TD></TR><TR><TD>
</TD><TD>
extended (or ext): Select 80x50 text mode.
</TD></TR><TR><TD>
</TD><TD>
ask: Stop and ask for user input (at boot time).
</TD></TR><TR><TD>
</TD><TD>
<number>: Use the corresponding text mode. A list of available modes can be obtained
by booting with vga=ask and pressing Enter.
</TD></TR></TABLE>
<A NAME="PAGENUM-1151"><P>Page 1151</P></A>
<TABLE>
<TR><TD>
</TD><TD>
If this variable is omitted, the VGA mode setting contained in the kernel image is
used. (That is set at compile time using the SVGA
MODE variable in the kernel makefile and can later be changed with the
rdev(8) program.)
</TD></TR></TABLE>
<P><B>
SEE ALSO
</B></P>
<P>lilo(8), rdev(8). The LILO distribution comes with very extensive documentation of which the preceding information is
an extract.
</P>
<P>28 July 1995</P>
<H3><A NAME="ch05_ 30">
MAKEDEV.cfg
</A></H3>
<P>MAKEDEV.cfg—Configuration for MAKEDEV(8).</P>
<P><B>
DESCRIPTION
</B></P>
<P>MAKEDEV.cfg is a text file that tells MAKEDEV(8) what to do (and equally importantly, what not to do). Unlike
DEVINFO(5), which is meant to be centrally maintained, it contains all local configuration for a particular site and all customization. There
are basically two kinds of declaration in this file: a "class" declaration and an "omit" declaration.
</P>
<P>A class declaration has the form
</P>
<!-- CODE SNIP //-->
<PRE>
class name : owner group-owner permissions
</PRE>
<!-- END CODE SNIP //-->
<P>This says that any devices placed in the specified class by
DEVINFO should be created with this ownership and these
permissions. A sample entry might be
</P>
<!-- CODE SNIP //-->
<PRE>
class public: root system 0666
</PRE>
<!-- END CODE SNIP //-->
<P>This says that devices marked public should be owned by
root.system and have mode 666.
</P>
<P>An omit declaration has the form
</P>
<!-- CODE SNIP //-->
<PRE>
omit { device... }
</PRE>
<!-- END CODE SNIP //-->
<P>This causes the specified devices to never be created, even if explicitly specified. Use caution when setting this up. The
intent is to be able to run MAKEDEV update and not have it create all sorts of useless devices you'd never use.
</P>
<P><B>
SEE ALSO
</B></P>
<P>MAKEDEV(8), DEVINFO(5)
</P>
<P>Version 1.4, January 1995
</P>
<H3><A NAME="ch05_ 31">
moderators
</A></H3>
<P>moderators—Mail addresses for moderated Usenet newsgroups.
</P>
<P><B>
DESCRIPTION
</B></P>
<P>The GetModeratorAddress(3) routine reads the file
/news/lib/moderators to determine how to reach the moderator of
a newsgroup. This is used by inews(1) when an unapproved local posting is made to a moderated newsgroup.
</P>
<P>The file is read until a match is found. Blank lines and lines starting with a number sign
(#) are ignored. All other lines should consist of two fields separated by a colon.
</P>
<P>The first field is a wildmat(3)-style pattern. If it matches the name of the newsgroup, then the second field is taken to be
a format string for sprintf(3). This string should have at most one
%s parameter, which will be given the name of the newsgroup with periods transliterated to dashes.
</P>
<P><CENTER>
<a href="1148-1149.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="1152-1154.html">Next</A></CENTER></P>
</td>
</tr>
</table>
<!-- begin footer information -->
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -