138
|
1 <refentry id="os9gen">
|
|
2 <refnamediv>
|
|
3 <refname>OS9GEN</refname>
|
|
4 <refpurpose>Build and Link a Bootstrap File</refpurpose>
|
|
5 </refnamediv>
|
|
6
|
|
7 <refsynopsisdiv>
|
|
8 <cmdsynopsis>
|
|
9 <command>OS9GEN</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 OS9Gen is used to create and link the "OS9Boot" file required on any
|
|
19 disk from which OS-9 is to be bootstrapped. OS9Gen is used to add
|
|
20 modules to an existing boot or to create an entirely new boot file.
|
|
21 If an exact copy of the existing OS9Boot file is desired, the
|
|
22 COBBLER command should be used instead.
|
|
23 </para>
|
|
24 <para>
|
|
25 The name of the device on which the "OS9Boot" file is to be
|
|
26 installed is passed to OS9Gen as a command line parameter. OS9Gen then
|
|
27 creates a working file called "TempBoot" on the device specified.
|
|
28 Next it reads file names (pathlists) from its standard input, one
|
|
29 pathlist per line. Every file named is opened and copied to
|
|
30 "TempBoot". This is repeated until end-of-file or a blank line is
|
|
31 reached on OS9Gen's standard input. All boot files must contain the
|
|
32 OS-9 component modules listed in section 6.1.
|
|
33 </para>
|
|
34 <para>
|
|
35 After all input files have been copied to "TempBoot", the old
|
|
36 "OS9Boot" file, if present, is deleted. "TempBoot" is then renamed
|
|
37 to "OS9Boot", and its starting address and size is linked in the
|
|
38 disk's Identification Sector (LSN 0) for use by the OS-9 bootstrap
|
|
39 firmware.
|
|
40 </para>
|
|
41 <para>
|
|
42 WARNING: Any "OS9Boot" file must be stored in physically contiguous
|
|
43 sectors. Therefore, OS9Gen is normally used on a freshly formatted
|
|
44 disk. If the "OS9Boot" file is fragmented, OS9Gen will print a
|
|
45 warning message indicated the disk cannot be used to bootstrap OS-9.
|
|
46 </para>
|
|
47 <para>
|
|
48 The list of file names given to OS9Gen can be entered from a keyboard, or
|
|
49 OS9Gen's standard input may be redirected to a text file
|
|
50 containing a list of file names (pathlists) . If names are entered
|
|
51 manually, no prompts are given, and the end-of-file key (usually
|
|
52 ESCAPE) or a blank line is entered after the line containing the
|
|
53 last pathlist.
|
|
54 </para>
|
|
55 <para>
|
|
56 For more information see: 6.0, 6.1, 6.6
|
|
57 </para>
|
|
58 </refsect1>
|
|
59 <refsect1><title>Examples</title>
|
|
60 <para>
|
|
61 To manually install a boot file on device "d1" which is an exact
|
|
62 copy of the "OS9Boot" file on device "d0":
|
|
63 </para>
|
|
64 <screen>
|
|
65 OS9: os9gen /d1 (run OS9Gen)
|
|
66 /d0/os9boot (enter file to be installed)
|
|
67 [ESCAPE] (enter end-of-file)
|
|
68 </screen>
|
|
69 <para>
|
|
70 To manually install a boot file on device "d1" which is a copy of
|
|
71 the "OS9Boot" file on device "do" with the addition of
|
|
72 modules stored in the files "/d0/tape.driver" and "/d2/video.driver":
|
|
73 </para>
|
|
74 <screen>
|
|
75 OS9: os9gen /d1 (run OS9Gen)
|
|
76 /d0/os9boot (enter main boot file name)
|
|
77 /d0/tape.driver (enter name of first file to be added)
|
|
78 /d2/video.driver (enter name of second file to be added)
|
|
79 [ESCAPE] (enter end-of-file)
|
|
80 </screen>
|
|
81 <para>
|
|
82 As above, but automatically by redirecting OS9Gen standard input:
|
|
83 </para>
|
|
84 <screen>
|
|
85 OS9: build /d0/bootlist (use "build" to create file "bootlist")
|
|
86 ? /d0/os9boot (enter first file name)
|
|
87 ? /d0/tape.driver (enter second file name)
|
|
88 ? /d2/video.driver (enter third file name)
|
|
89 ? [RETURN] (terminate "build")
|
|
90 OS9: os9gen /d1 </d0/bootlist (run OS9gen with redirected input)
|
|
91 </screen>
|
|
92 </refsect1>
|
|
93 </refentry>
|
|
94
|