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.
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.
I have a situation which I believe many of you might have encountered.
Here are some facts,
1. I dual boot linux with 98 and NT.
2. Use floppy to boot into Linux.
3. Partition table looks something like this
hda1 - primary (C drive, for Wing 98)
hda2 - extended
hda5 - ntfs for NT
hda6 - linux swap
hda7 - linux root
hda8 - other..
There exists some unallocaed space between hda5 and hda6. I create another logican partition. This results in swap (hda6) becomming hda7, and root(hda7) becomming hda8. This causes linux not to boot.
Under such circumstances, how to regain linux?
Has anyone had to deal with this situation before? If yes, how did u fix the problem?
-----------------------
One solution I have used is temporary, but still works.. I used the params (linux root=/dev/hda8' to boot into linux, then changed the /etc/fstab file to point to appropriate partitions. But this wont' solve my problem as lilo is not updated. I then edited the /etc/lilo.conf file in the floppy to point the root to the appropriate partition.
I would like to know if this is the right way to do it? Is there a better way to do this?
Thanks,
C F
-----------------
".. not tonite dear, I have a modem.."
That pretty much the way that I've always done it - get onto the system using a boot disk, get to and edit your lilo.conf and fstab files to reflect the changes, then run lilo with the edited file and all should be good.
Well, theres a few ways around.
One is using loadlin from dos, have a loadlin script where you would just edit the "root=" statement, else I just use a rescue or bootdisk, at the bootprompt type "linux rescue, mount the partition under /(partition) chroot to /(partition), edit the /etc/lilo.conf and rerun "lilo -v -t" (testing) and if all goes well "lilo -v" to install.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.