On Mon, Jan 19, 2015 at 06:59:28AM -0500, [email protected] wrote: > Changing the "set root="hd0,msdos3' to msdo1 and no other change also > produced the grub rescue> prompt. However that may be because my LFS build > along with all its /boot/grub/... /etc/grub.d/... files are all contained > in sda3 per the LFS instructions.
As it said in the mail you replied to: > When replying, please edit your Subject line so it is more specific than > "Re: Contents of lfs-support digest..." and > Do not top post on this list. > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > Also, please trim what you are replying to. > > > At the time the drive was initially prepared I didn't create a separate > 100MB boot partition. I just put Lubuntu in sda1 and the MBR pointed to it. > It was my expectation (perhaps erronesously) that after LFS was built in > sda3 and grub-install executed it would reset the MBR to point to sda3's > /boot/grub/...,kernel, etc and from that point forward the drive would boot > exclusively to LFS in sda3. That has not been the case in my situation. > > For the sake of simplicity I'd like to keep the content of LFS's sda3 > partition and Lubuntu's sda1 separate. The reason is that once LFS is > booting I no longer need the host OS or its partition, and the other is that > I believe the LFS documentation assumes they are separate. It's helpful > for now if I can stay close to LFS documentation. > > Is it possible to configure the drive to boot to LFS (sda3) only without > putting LFS's kernel or other files into Lubuntu's sda1? Or can I > reconfigure the boot drive with a separate 100MB boot partition now and boot > only to LFS? Basically do multi-boot and follow LFS grub instructions for > handling separate /boot partition? > If you have unpartitioned space, and a spare partition, you can create a new partition. If not, it will be much easier to keep the host system workable - many people, me included, have had to rebuild kernels many times on new machines[1] before our configs were satisfactory, and it is much easier if you can drop back to a host system and use a graphical browser to research the problems you encounter. You managed to get lubuntu booting by using the rescue disk, so I suggest you get back to that situation, boot lubuntu, then _copy_ the LFS kernel (only) to your lubuntu system and add the menu entry to lubuntu's grub.cfg. Then, try booting LFS again. Getting a grub rescue prompt is not common, perhaps the LFS and lubuntu grub files conflicted with each other. When you have your LFS/BLS system usable (for _your_ definition of usable), back up both systems, repartition, restore, chroot from your rescue system, fix up the new /boot, try to boot, repeat until working. Hint: if you intend to continue to use LFS, you will almost certainly want a second system for when you decide to upgrade, and in the meantime it might as well have the old host system (I assume your rescue system is less convenient to use :) just in case you do something which trashes your LFS system and need to recover to your most recent backup - we ALL make mistakes from time to time. 1. Until you have successfully built your own recent kernel, without an initrd, for this machine it counts as 'new'. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
