|
134
|
1 <refentry id="cobbler">
|
|
|
2 <refnamediv>
|
|
|
3 <refname>COBBLER</refname>
|
|
|
4 <refpurpose>Make a bootstrap file</refpurpose>
|
|
|
5 </refnamediv>
|
|
|
6
|
|
|
7 <refsynopsisdiv>
|
|
|
8 <cmdsynopsis>
|
|
|
9 <command>COBBLER</command>
|
|
|
10 <arg choice="plain">
|
|
|
11 &replstart;device name&replend;
|
|
|
12 </arg>
|
|
|
13 </cmdsynopsis>
|
|
|
14 </refsynopsisdiv>
|
|
|
15
|
|
|
16 <refsect1><title>Description</title>
|
|
|
17 <para>
|
|
|
18 COBBLER is used to create the "OS9Boot" file required on any disk
|
|
|
19 from which OS-9 is to be bootstrapped. The boot file will consist
|
|
|
20 of the <emphasis>same modules which were loaded into memory during the most
|
|
|
21 recent boostrap.</emphasis>
|
|
|
22 To add modules to the bootstrap file use the
|
|
|
23 "OS9Gen" command. COBBLER also writes the OS-9 kernel on the first
|
|
|
24 fifteen sectors of track 34, and excludes these sectors from the
|
|
|
25 disk allocation map. If any files are present on these sectors
|
|
|
26 COBBLER will display an error message.
|
|
|
27 </para>
|
|
|
28 <para>
|
|
|
29 NOTE: The boot file must fit into one contiguous block on the mass-storage
|
|
|
30 device. For this reason COBBLER is normally used on a
|
|
|
31 freshly formatted disk. If COBBLER is used on a disk and there is
|
|
|
32 not a contiguous block of storage large enough to hold the boot
|
|
|
33 file, the old boot file may have been destroyed and OS-9 will not be
|
|
|
34 able to boot from that disk until it is reformatted.
|
|
|
35 </para>
|
|
|
36 <para>
|
|
|
37 For more information see: 1.1.2, 6.1
|
|
|
38 </para>
|
|
|
39 </refsect1>
|
|
|
40 <refsect1><title>Examples</title>
|
|
|
41 <screen>
|
|
|
42 OS9: cobbler /D1
|
|
|
43 </screen>
|
|
|
44 </refsect1>
|
|
|
45 </refentry>
|
|
|
46
|
