Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The only boot disk I've ever used is the one you can setup on installation of Linux (Mandrake, in my case). I believe that this simply has a lilo.conf file that points to the kernel image on the HDD, rather than having another image on the floppy, in which case, I believe that simply adding the lines to the lilo.conf file on your floppy will work just as well as if you were actually booting from the HDD (as, in theory, you are). If I'm wrong, then my most sincere appologies for wasting your time - in which case, I shall be learning something aswell.
i use a boot disk as lilo on my system is defaulted to windwos, and i can't change it, and i've got andditional hardware, which slows the boot down, so by putting in a boot disk, i can go to the loo while linux boots!
i've tried running lilo to update the boot disk, created using mkbootdisk, but it always complains that various files aren't where they should be, which i can see, cos the fs would look different at boot time, as it wouldn't have mounhted /dev/hda5 or anything.. my floppy lilo says:
but simply changing the append line doesn't affect it. I know if it's on a HD then you need to run lilo, but i thought i read somewhere that you don't on a floppy, cos there's no MBR to update....
naturally, all paths listed are relative to the floppy disk, not the normal file system...
so what do i need to do to make my changes in lilo.conf have effect?
Why can't you use the lilo on your hard drive to boot into linux and why can't you change the default from windows to linux?
It's true there is no mbr on the floppy, but there is a boot sector that lilo gets written to.
When I had TurboLinux installed, I made a boot disk using mkbootdisk. I looked at the mkbootdisk file and found it to be a script file. The file used the command /sbin/lilo -r /mount_point to set up lilo on the floppy. Try it, but change ' /mount_point ' to where you mount the floppy. Let's say you mount it in the ' /mnt/floppy ' directory. Then it would be /sbin/lilo -r /mnt/floppy.
First, mount the floppy disk then check your /mnt and /floppy directories to see if the permissions are correct. Do an ls -l /mnt and an ls -l /mnt/floppy. You'll need to have read and write permission. If you don't, then use chmod u+rw /mnt and chmod u+rw /mnt/floppy.