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.
You should just be able to edit the lilo.conf file and change the location lilo looks for the kernel. So if you are booting (for example...) image=/vmlinuz you would change it to image=/boot/vmlinuz. Obviously using your own kernel name if it's not vmlinuz.
Have the impression lilo does not participate in the boot process when booting from a floppy disk.
Every changes I have done to lilo.conf did not work at all.
However I have noticed a file in floppy boot disk very similar to lilo.conf but uses different syntax, the file name is syslinux.cfg and seems to point to available linux kernel images (actually to only one).
I have an installation disk for TurboLinux that has the same file on it ( syslinux.cfg ). It has a line that says kernel vmlinuz . On the floppy disk is a file named vmlinuz . So, the kernel appears to be on the floppy disk. Do you see any file on your floppy disk that appears to be a kernel image? You might have to copy your new image to the floppy over the old one. If it will fit on the floppy. Could you post a copy of your syslinux.cfg file?
Thank you for the tip.
No doubt, vmlinuz file on the floppy refers to the kernel image. And to be able to boot the new image I had to overwite vmlinuz file on the floppy disk with the new kernel image. And that worked for me. The image size jumped from 7xx kb to 9xx kb !
The next issue I would need more clarifications about is the boot loader used on the boot disk.
If lilo is used when booting normally from the hard disk, then what about the floppy?
The boot loader that is used on your floppy is called Syslinux. I think that's right.
lilo can be installed on a floppy. There are two ways I know of. One is to install lilo into the boot sector of the floppy and nothing else on the floppy. The other is install not only lilo in the boot sector, but also to create a file structure on the floppy. Directories like /etc and /boot and others are created. In the /etc directory, there is even an lilo.conf file. The program that creates this kind of disk is mkbootdisk.
There is also a kernel disk. The compressed kernel is copied onto the floppy using the ' dd ' command. This type of disk is very inflexible because it won't allow you to enter any parameters if something goes wrong.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.