blob: e78097d55b0bfc4b70f27df2384da97ebe8a0db9 (
plain)
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
|
To install the tarfile bootsector
---------------------------------
Create the makeboot program:
$ make makeboot
Create the tarfile
$ tar cvfV /dev/fd0 ENIAC monitor.out item2 item3
Make it bootable
$ makeboot tar /dev/fd0
Note, the distribution tar file is made using this procedure and can be booted
if uncompressed and copied onto a raw floppy.
To install the dosfs boot sector
--------------------------------
$ make makeboot
$ makeboot dosfs /dev/fd0
or
$ make makeboot.com
C:\> makeboot dos a:
Place a Linux-8086 executable in the root directory of the floppy.
$ make monitor.out
$ mcopy monitor.out a:BOOTFILE.SYS
or
C:\> copy monitor.out a:\bootfile.sys
This works on my 3 1/5 floppy and my 5 1/4, and it _should_ work on
any double sided drive. (It does work on a 3.5/720k floppy too)
For single sided floppies you need to alter msdos.s (the heads var)
and remove the check in makeboot.c
To install the minixfs boot sector
----------------------------------
Make a minix filesystem on the floppy:
$ mkfs -t minix /dev/fd0 1440
or
$ mkfs -t minix /dev/fd0 1200
Make the bootblock program.
$ make minix.bin
Install it
$ cp minix.bin /dev/fd0
Place a Linux-8086 executable in the root directory.
$ make monitor.out
$ mount -t minix /dev/fd0 /mnt
$ cp monitor.out /mnt/linux
$ umount /dev/fd0
This works on my 3 1/4 floppy, and it _should_ work on any double sided
drive. Be sure to make the filesystem the full size of the floppy.
Booting a Linux-386 bzImage
---------------------------
NOTE: This only works with bzImage files NOT zImage files.
Take 1 msdos floppy.
$ makeboot dos /dev/fd0
$ mount -t msdos /dev/fd0 /mnt
$ cp monitor.out /mnt/bootfile.sys
$ cp /usr/src/linux/arch/i386/boot/bzImage /mnt/vmlinuz
$ echo 'root=/dev/ram ramdisk_file=ramdisk.gz mem=80M' > /mnt/vmlinuz.cmd
$ cp /archive/ramdisk.gz /mnt/ramdisk.gz
$ umount /dev/fd0
The stuff about ramdisk is only if you want an init ramdisk. You can also use:
vmlinuz.app: Arguments prepended to the Linux command line.
vmlinuz.cmd: Arguments appended to the Linux command line.
vmlinux.dfl: Arguments appended to the Linux command line.
If there's a *.cmd file you won't be asked anything. If there's a *.dfl or
neither you'll be asked:
vmlinuz:
where you can type a command line to override the *.dfl file. If there's
a *.cmd file the *.dfl file is ignored, the *.app file is placed at the
start of the line whichever you do.
If the file isn't called 'vmlinuz' you can still boot it by typing "=linux"
at the prompt '>' where 'linux' is the name of the bzImage file.
Escape or ^C will interrupt the boot and drop you to the '>' prompt.
Esacpe or ^C at the '>' prompt will reboot
(This may be a little sensitive :-)
A file called 'help.txt' will be displayed upto the first line that starts
with a '%', chunks after that (seperated by '%'s) will be displayed when
the user presses a function key, home, page up or page down. (Note it's
best if you try to ensure 'help.txt' is completely contained on one track
so the file is entirely in the track buffer)
|
