Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Here's a recipe I have used and know works. (had problems with mkbootdisk in Debian);
Creation of a floppy with LILO on MBR:
Lilo is the "Boot Loader" for Linux which typically resides on the MBR of your hard drive. This may easily get wiped out on a multiboot system where a re-loading of the Windows operating system will reload the MBR. If the MBR is overwritten and LILO removed, there will be no way of booting to Linux. Thus it is wise to have a floppy with LILO residing on the MBR of the floppy which can point the system to boot off of the Linux kernel residing on your hard drive. Here is how it is created:
fdformat /dev/fd0 # Lay tracks on new diskette
mkfs -t minix /dev/fd0 # Create minix file system on floppy
cp -p /boot/chain.b /floppy # Copy chain loader
cp -p /boot/boot* /floppy
lilo -v -C /etc/lilo.floppy # Install lilo and the map onto floppy
Note that LILO sets the MBR to the settings as defined by the configuration file /etc/lilo.floppy.
Sample file: /etc/lilo.floppy
boot=/dev/fd0 - Floppy drive (Location of Lilo boot sector)
map=/mnt/floppy/map - Locations on hard drive where the kernel can be found for boot
prompt
linear - Specific to SCSI configurations
timeout=50 - Give the user time to decide (number of seconds) if there are multiple choices
image=/boot/vmlinuz-2.4.18-k7 - Boot this Linux kernel. This depends on your release of the operating system.
label=hd_linux
root=/dev/sdb6 - System instructed to boot from this drive. It is unique to your system. It could be /dev/hda4, it depends on your installation.
initrd=/boot/initrd.img-2.4.18-k7 - This is specific to systems using SCSI hard drives. This line is omitted for IDE.
read-only
Note:
Actual kernel name and version will depend on your Linux release.
Most of the information for /etc/lilo.floppy should be copied from /etc/lilo.conf
Actual names for the files to be used may be seen in the directory /boot
The file initrd-2.2.17-14.img is required by systems using modular SCSI support.
It is generated using the command: mkinitrd /boot/initrd-2.2.17-14.img 2.2.17-14
and should also be copied to the floppy.
This worked great for me and I'll certainly remember it. I can never be arsed with a boot floppy at install and always regret it! :-)
Incidentally, I noticed a step that was missed off the floppy creation, namely mounting it. After the line:
mkfs -t minix /dev/fd0 # Create minix file system on floppy
you should enter
mount /mnt/floppy # On Redhat systems or mount /floppy on Debian
And when you're finished, before taking it out, type umount /mnt/floppy (or wherever it was mounted)
Also, I found that in the lilo.floppy config, changing the line "map=/mnt/floppy/map" to "map=/boot/map" worked better as I didn't have to copy the map to the floppy. Can't say whether that's a good thing or not though :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.