Hendrik Boom wrote:
> Let me see if I understand grub's interpretation of menu.lst correctly.
> I have a boot stanza in my menu.lst:
>
> title Debian GNU/Linux, kernel 3.0.0-1-686-pae testing
> (squeeze-grub) OK
> root(hd0,5)
> kernel /vmlinuz-3.0.0-1-686-pae root=/
On Sun, 26 Feb 2012 20:54:31 +, Hendrik Boom wrote:
> I have two different Debian systems on my EEEPC -- stable and testing.
>
Let me see if I understand grub's interpretation of menu.lst correctly.
I have a boot stanza in my menu.lst:
title Debian GNU/Linux, kernel 3.0.0-1-686-pae
On Tue, Feb 28, 2012 at 1:50 PM, Hendrik Boom wrote:
> On Mon, 27 Feb 2012 01:15:40 -0700, Bob Proulx wrote:
>> Hendrik Boom wrote:
>>>
>>> I'm getting the kernels in the /boot partition of one system matched
>>> with the file-system root partition of the other system.
>>
>> I looked at the update
Hendrik Boom wrote:
> Bob Proulx wrote:
> > Hendrik Boom wrote:
> >> I'm getting the kernels in the /boot partition of one system matched
> >> with the file-system root partition of the other system.
> >
> > I looked at the update-grub script and at first glance I don't see how
> > that is possibl
On Mon, 27 Feb 2012 01:15:40 -0700, Bob Proulx wrote:
> Hendrik Boom wrote:
>> I'm getting the kernels in the /boot partition of one system matched
>> with the file-system root partition of the other system.
>
> I looked at the update-grub script and at first glance I don't see how
> that is poss
On Du, 26 feb 12, 20:54:31, Hendrik Boom wrote:
> I have two different Debian systems on my EEEPC -- stable and testing.
>
> Whenever testing installs a new kernel as a result of the routing update,
> my grub/menu.list file gets rewritten. WHen it does this, it matches the
> kernels I have in o
Hendrik Boom wrote:
> I'm getting the kernels in the /boot partition of one system matched with
> the file-system root partition of the other system.
I looked at the update-grub script and at first glance I don't see how
that is possible It looks for kernels in /boot. I don't see how it
can be p
On Sun, 26 Feb 2012 14:39:06 -0700, Bob Proulx wrote:
> Hendrik Boom wrote:
>> I have two different Debian systems on my EEEPC -- stable and testing.
>>
>> Whenever testing installs a new kernel as a result of the routing
>> update, my grub/menu.list file gets rewritten. WHen it does this, it
>>
Hendrik Boom writes:
...
>
> (b) If I were to progress to grub2, where I gather I can't take control
> of the boot process by editing menu.lst, is there some other way of
> making sure things go right? I fear that one of these years, upgrading
> to grub2 will become inevitable.
>
With grub2 y
Hendrik Boom wrote:
> I have two different Debian systems on my EEEPC -- stable and testing.
>
> Whenever testing installs a new kernel as a result of the routing update,
> my grub/menu.list file gets rewritten. WHen it does this, it matches the
> kernels I have in one Debian sysstem with the f
On Sun 26 Feb 2012 at 20:54:31 +, Hendrik Boom wrote:
> I have two different Debian systems on my EEEPC -- stable and testing.
>
> Whenever testing installs a new kernel as a result of the routing update,
> my grub/menu.list file gets rewritten. WHen it does this, it matches the
> kernels
26/02/2012 21:54, Hendrik Boom wrote:
> I have two different Debian systems on my EEEPC -- stable and testing.
>
> Whenever testing installs a new kernel as a result of the routing update,
> my grub/menu.list file gets rewritten. WHen it does this, it matches the
> kernels I have in one Debian
I have two different Debian systems on my EEEPC -- stable and testing.
Whenever testing installs a new kernel as a result of the routing update,
my grub/menu.list file gets rewritten. WHen it does this, it matches the
kernels I have in one Debian sysstem with the fie-system root I have in
the
13 matches
Mail list logo
