[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#41771: boot-floppies 2.1.9 does not include bootdisk.sh



Package: boot-floppies
Version: 2.1.9

The following exerpt is from the Debian FAQ:

11.2 How can I make a custom boot floppy? 

This task is greatly aided by the Debian package boot-floppies, normally
found in the devel section of the Debian FTP archive. Shell
scripts in this package produce boot floppies in the SYSLINUX format.
These are MS-DOS formatted floppies whose master boot records
have been altered so that they boot Linux directly (or whatever other
operating system has been defined in the syslinux.cfg file on the floppy).
Other shell scripts in this package produce emergency root disks and can
even reproduce the base disks. 

When the boot-floppies package is installed, it produces files which
reside in /usr/src/boot-floppies/, including the three scripts,
called bootdisk.sh, rootdisk.sh, and basedisk.sh. Users of these scripts
are encouraged to read them and customize as
appropriate. In particular, one should include the kernel of your choice
when invoking the bootdisk.sh script. Be aware that this kernel
cannot be used to load the root disk into a RAMDISK unless it was compiled
with CONFIG_RAMDISK=y, and CONFIG_INITRD=y. 

To write the kernel-image-2.0.36 package to the 1.44 MByte disk in drive
A: run this command: 

    ./bootdisk.sh /usr/src/kernel-image-2.0.36_1.00.deb /dev/fd0 1440

Be sure to include the editor and whatever other tools you prefer when
building your custom root disk with ./rootdisk.sh. 

Some people found that the boot and root disks make good emergency
floppies. 






The process of going from a kernel to a bootdisk has been quite a  
harrowing experience.  It would be nice to see how other people manage
it.


Debian 2.1, kernel 2.0.36, blah blah blah


Reply to: