Ken Moffat wrote:
> For update-grub, at least in grub2, the kernel has to be called
> vmlinuz-something.
Yes. Look at the scripts in /etc/grub.d.
> I assume, perhaps wrongly, that update-grub will
> create all sorts of weird and stupid combinations for what it finds
> (e.g. ubuntu kernel for LFS system).
You assume, I know. I had 40 or 50 combinations the last time I
installed Ubuntu.
> People here mostly avoid update-grub and edit grub.cfg. I expect
> you can fix this by editing that file n ubuntu [ it's probably set to
> be read-only, perhaps only for root ] to ensure that for the LFS
> system it uses the correct kernel and does not reference an initrd.
There is an issue. Where does the grub base look for
/boot/grub/grub.cfg? Most of the time it's a little tricky to get it
right after a distro does what *it* thinks is right. It depends on
whether you mount /boot as a separate partition or not.
> Once that is working (possibly, you may also need to rebuild your
> kernel if you didn't include the necessary drivers and kept them as
> modules), you should save details of what is in the LFS entr{y,ies}
> so you can restore them if you ever let ubuntu update its kernel.
>
> I think someone offered a suggestion of how to set up the files so
> that update-grub would handle an LFS install, probably in the last 6
> months, but since the list archives are offline at the moment I
> can't suggest where to search.
I suggested just copying the grub.cfg to something like
grub.cfg.20120125 and then copy it back and modify it by hand after the
other distro changes things.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
