From: giggz <giggzounet@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Question about menu.lst
Date: Sun, 04 May 2008 14:49:35 +0200 [thread overview]
Message-ID: <fvkbfo$qqu$1@ger.gmane.org> (raw)
In-Reply-To: <1209904920.2773.4.camel@localhost.localdomain>
Lubomir Rintel a écrit :
> On Sun, 2008-05-04 at 14:10 +0200, giggz wrote:
>> Hi,
>>
>> Sorry If it isn't the right place to post...I don't find a grub users
>> list...
>>
>> I have several kernel on my laptop. Most of them are compiled by myself.
>> But to compare the performance I have an official debian kernel (486).
>> The problem is that official debian kernels are compiled with ide (so
>> hd* device) and my personal jkernel with PATA support (so sd* device).
>> So the root= option is not the same.
>>
>> I would like to define a regle to set root=/dev/hda1 for all the *-486
>> kernels through the # kopt_*_486=root=/dev/hda1 ro option. But I want
>> to keep the general regle : # kopt=root=/dev/sda1 ro
>> Is there a way to do that ?
>
> Actually, you might want to use UUID or LABEL of the file system instead
> of device file name.
>
> You can get or set UUID or label with tune2fs like this:
>
> # tune2fs -l /dev/sda1 (get information)
> # tune2fs -L root-fs /dev/sda1 (set label)
>
> And then set a kernel root parameter as follows:
>
> root=LABEL=my-root-fs
>
Hi,
thx for your quick answer. my /etc/fstab sill use it. But I have read
that in order to use uuid in the grub menu.lst I must have an
initrd...and in my self-compiled kernels I don't build any initrd...
Cheers
> Hope that helps.
>
next prev parent reply other threads:[~2008-05-04 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 12:10 Question about menu.lst giggz
2008-05-04 12:42 ` Lubomir Rintel
2008-05-04 12:49 ` giggz [this message]
2008-05-06 15:08 ` Robert Millan
2008-05-06 18:47 ` Vesa Jääskeläinen
2008-05-07 12:49 ` Robert Millan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fvkbfo$qqu$1@ger.gmane.org' \
--to=giggzounet@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.