On Wed, Jun 30, 2010 at 5:24 PM, Bruce Dubbs <bruce.du...@gmail.com> wrote:
> Andrew Benton wrote:
>> On 30/06/10 19:33, Stuart Stegall wrote:
>>> Seems like it should be the simplest way possible. Personally I don't
>>> like the grub-mkconfig - has failed to work for me a few times, and I
>>> believe it does that due to my host system.
>>>
>> grub-mkconfig has never worked for me as I use btrfs for my root partition
>>
>>> Seems like a much more simple approach of:
>>>
>>> # cat<<EOF> /boot/grub/grub.cfg
>>> set timeout=10
>>> set default=0
>>> menuentry "LFS x.x" {
>>> set root=(hd0,1)
>>> linux /vmlinuz root=/dev/sda2
>>> }
>>> EOF
>>>
>>> Would be better.
>>>
>> I agree. I've always written grub.cfg by hand from examples found with
>> google.
>
> I understand your thought, but I think it better for the book to explain
> what is going on in a way similar to more traditional distros.
>
> I personally generate grub.cfg once and then edit from then on. I did
> some experimenting to get an image to come up in grub and using
> grub-mkconfig would break that.
>
> Really, the only things that need to change are menuentry items. If you
> set root=(hd0,1) outside of the menuentry, then that degenerates down to
> one line:
>
> menuentry "LFS SVN 20100627, Linux 2.6.34" {
> linux /linux-2.6.34 root=/dev/sda13 ro
> }
>
> -- Bruce
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-dev
> FAQ: http://www.linuxfromscratch.org/faq/
> Unsubscribe: See the above information page
>
I have 3 roots on my two test machines. :D (actually as soon as I can
get an ARM together, I'll have 3 test machines.)
ro is also unnecessary since around 2.2.x (I don't swear to that, it
could have been 2.1.x or 0.99.) The kernel is read-only by default.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
