Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
I'm currently dual booting redhat 7.0 and windows 2000 adv. server and booting into linux via boot disk.
I just downloaded and compiled kernel-2.4.18.
bzimage said after successfully compiling that the kernel was too big for a floppy and so I wanted to configure LILO to boot from the hard disk. When I run LILO from the command line, it kicks back the following error:
Warning device 0x0306 exceeds 1024 cylinder limit
Fatal: sector 28903800 too large for linear mode (try 'lba32' instead) I suspect this means that LILO hasn't been installed correctly.
So I have the following questions:
Is there an easy way to reinstall LILO?
Is Win2K Adv. Server not allowing LILO to work with the Master Boot Record?
i just pasted that from the top of my lilo.conf - yours might be a bit different. but all you need to do is get the lba32 near the top, under the other basic stuff. after that, run lilo to install it, and reboot. that should fix it for the 1024 limit.
Location: Rome, Italy ; Novi Sad, Srbija; Brisbane, Australia
Distribution: Ubuntu / ITOS2008
Don't listen to me until you are absolutely sure what you are doing.
It might be that win2k boot loader is not letting lilo install in the mbr. So if you do a fdisk /mbr from DOS to erase anything in the mbr and then install lilo it might work. However first try everything else since if you do this you migh stay without any bootloader which means you will maybe have to format and reinstall everything.
Hope this helps, and again this should be the very last thing to try and only if you have your stuff backed up since you might not be able to access your OSes after doing this. Well i assume you could always use a bootdosk to get into your OS...
well, thank you all for the responses... I have gone with my better judgement and formated my windows partitions... I only installed win2k adv.ser. to experiment with it... and to say the least, I was not impressed!
I've pretty much reformatted the whole system and have successfully installed LILO.
I recompiled 2.4.18 and am at the final stage (editing lilo.conf).
I have a few questions about this proceedure that the how-to's seem to breeze through without enough detail. after running make bzImage, I found a file named "bzImage" in /usr/src/linux/arch/i386/boot/ and i think the is my newly compiled kernel. however the is another file named "vmlinux" in /usr/src/linux/ which I am unsure of.
My /boot/ directory has a symbolic link "vmlinuz" which point to "vmlinuz-2.2.16-22". there is also the "vmlinux-2.2.16-22" file within /boot/ which i am unsure of.
Can anyone tell me what the next step is to enable LILO to boot my new kernel?
i think the /usr/src/linux/vmlinux file is the uncompressed kernel image. i'm actually not positive about this, but i've compiled many a kernel, and never found a use for that file. i think you'll need to browse some kernel hacking sites to find out what it is. that, or just ignore it.