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.
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.
I have gentoo on my machine and I want to give arch a try. I used parted to adjust my partitions. Before installing anything, I rebooted to make sure that gentoo still worked and it did. So I went ahead and installed arch. I thought I did the right thing in not installing the bootloader because I already had grub on the mbr. SO i rebooted. and all I get is a screen full of "grub grub grub grub grub grub etc."
I'm not at home so I can't fix it right now, but this is what I think I should try. Using the gentoo live cd, I can get into the system, mount everything, and chroot into it. SHould things be okay if I re-emerge grub, reset it up on the mbr, and then edit my grub file to the arch partition. Does this sound like the right process, or am I missing something?
Distribution: Slack Puppy Debian DSL--at the moment.
cheat. I have usually installed lilo when it happens, after updating the /etc/lilo.conf with some cut-n-pasting and tweaks.
Then until the next time you update the kernel just use lilo--who cares as long as it boots?
The missing commands to use are the "mount", "swapon", and "cp" command, use RIP or rescue.
After booting (and then mounting the system "/" to /mnt/sysimage if the rescue disk doesn't do it for you) then make sure all of the respective portions of the grub installer are present in the /etc in ram--this is the system you are running. If they are not there, cp them.
Use mount to mount your real /boot (either on /mnt/sysimage/boot or label=/boot for a partition) over the existing /boot directory in ram--the "rescue-/boot".
Now, when you reference your "real" /boot when running the grub commands you are giving the correct locations for grub stage 1.5 and stage 2 plus the correct reference to "boot.b" for the installer to write into the MBR--via the variable/expression/test pre-processing for commands built into the shell.
The reason I use lilo is that the only syntax I have to remember in that of the /etc/lilo.conf file. Otherwise, the process is identical.
Wow--great info, thanks. However, I have no idea what you're talking about with regards to copying grub onto the ram /etc and all that business. If you could explain that a little more specifically I'd really appreciate it. Thanks so much.