1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
<TITLE>Yard Documentation: Options for Config.pl</TITLE>
<LINK HREF="Yard_doc-14.html" REL=next>
<LINK HREF="Yard_doc-12.html" REL=previous>
<LINK HREF="Yard_doc.html#toc13" REL=contents>
</HEAD>
<BODY>
<A HREF="Yard_doc-14.html">Next</A>
<A HREF="Yard_doc-12.html">Previous</A>
<A HREF="Yard_doc.html#toc13">Contents</A>
<HR>
<H2><A NAME="s13">13. Options for Config.pl</A></H2>
<P>
<P>Here is a distillation of the options allowed in Config.pl. For convenience,
most of this text also exists as comments in the Config.pl file. These
options should have reasonable defaults, so if you don't understand what an
option is for you can probably leave it alone.
<P>
<DL>
<P>
<DT><B>$verbosity</B><DD><P>This controls only what is printed to the screen.
If 0, only the important messages will be printed;
if 1, all messages.
All messages end up in the log file regardless of the setting.
<P>
<DT><B>$floppy and $floppy_capacity</B><DD><P>These variables specify the floppy
device where the rescue disk will be written and its capacity.
Make sure the two agree. If $floppy is a non-standard size (eg,
1722K), make sure to use the complete name (eg, /dev/fd0H1722).
<P>
<DT><B>$disk_set</B><DD><P>One of "single", "double" or "base+extra"
<P>
<UL>
<LI>SINGLE: Both the kernel and entire compressed root filesystem will
be put on one disk.
</LI>
<LI> DOUBLE: The kernel will be put on the first disk and the compressed
root fs will be put on the second.
</LI>
<LI> BASE+EXTRA: THIS OPTION NOT YET IMPLEMENTED. The first disk will
contain the kernel plus a base set of files (enough to boot and run
tar). The second disk will contain the remaining files.</LI>
</UL>
<P>It is safe to keep this at SINGLE. If Yard detects that you need an
extra disk, it will offer to make a double disk set automatically.
<P>NB. With double disk sets, both disks <EM>must</EM> be formatted
identically.
<P>
<DT><B>$mount_point</B><DD><P>A directory to be used as a mount point. This is where the root
filesystem will be mounted during creation and where the floppy
will be mounted when the rescue disk is being written.
<P>
<DT><B>$device</B><DD><P>The device for building the compressed filesystem. This can be
/dev/ram0 or a spare partition. You can turn off swapping
temporarily and use the swap partition on your hard disk. You can
use a loopback device if your kernel supports them -- see section
asdfasdf for instructions.
<P>
<DT><B>$fs_size</B><DD><P>The size limit of $device, in Kilobytes. For
/dev/ram0, this value should be no more than the ramsize
specified in your /etc/lilo.conf. For most devices,
Yard can check this value against the available space.
<P>
<DT><B>$kernel</B><DD><P>The absolute filename of the compressed kernel to be put on the
rescue disk. This should be the <EM>compressed</EM> kernel. This
is usually something like /vmlinuz, /zImage or
/boot/zImage. If you've just remade your kernel (via <CODE>make
zImage</CODE>) the kernel file will reside in
/usr/src/linux/arch/i386/boot/zImage.
<P>
<DT><B>$kernel_version</B><DD><P>make_root_fs will examine $kernel and try to determine
its version. If Yard guesses incorrectly, or if you want to
force it anyway, set $kernel_version. The value should
be a version string such as that returned by "uname -r".
<P>(If you compile your kernel properly via mrproper so that
/usr/src/linux/arch/i386/boot/setup is recompiled, Yard's
method will work).
<P>
<P>
<DT><B>$contents_file</B><DD><P>The file specifying the bootdisk contents specification file.
The default is <CODE>Bootdisk_Contents</CODE> in the installation
directory.
<P>
<DT><B>$rootfsz</B><DD><P>The file that will temporarily hold the compressed root filesystem.
<P>
<DT><B>$oldroot</B><DD><P>Where the old (hard disk) root filesystem will be mounted on the
ramdisk filesystem. create_fstab uses this to adapt your
/etc/fstab for use on the rescue disk so you'll be able to mount
hard disk partitions more easily. You shouldn't need to change
this, but run <CODE>create_fstab</CODE> again if you do.
<P>
<DT><B>$strip_objfiles</B><DD><P>If set to 1, binary executables and libraries will be stripped of
their debugging symbols (using <CODE>objcopy</CODE>) as they're copied
to the root filesystem. This may reduce their size somewhat. If
you don't understand what this means, leave it at 1. If you're
sure you don't have objcopy, or for some reason you want debugging
symbols, set it to 0.
<P>
<DT><B>$yard_temp</B><DD><P>If non-null, specifies directory where log files will be written.
If null, log files will be written to current working directory.
<P>
<DT><B>$use_lilo</B><DD><P>Controls whether to use Lilo for transferring the kernel to the boot disk.
<P>
<UL>
<LI> If 1, Yard will use Lilo to boot the kernel (configuration file is
in ./Replacements/etc/lilo.conf, created by <CODE>make copies</CODE>).
This allows you to use Lilo's APPEND clause and various other Lilo
options.
</LI>
<LI> If 0, Yard will copy the kernel directly to the rescue disk. This
saves a small amount of space.</LI>
</UL>
<P>
<DT><B>@additional_dirs</B><DD><P>This is an array that should contain any additional directories
(besides those in $PATH) to be searched for rescue disk
files. Directories inside the list must be separated by
commas. You don't need a trailing slash on these directory
names. Any directories you list here will be searched BEFORE
those in $PATH.
<P>
</DL>
<P>
<P>
<HR>
<A HREF="Yard_doc-14.html">Next</A>
<A HREF="Yard_doc-12.html">Previous</A>
<A HREF="Yard_doc.html#toc13">Contents</A>
</BODY>
</HTML>
|
