>> GRUB_DEFAULT=saved
> That's the one. Thanks for the reminder.
You're welcome.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/6d4219cc1003171940u1b4d4b28qef440a1
On Tue, 16 Mar 2010 21:46:47 -0400 (EDT)
Stephen Powell wrote:
Hello Stephen,
> I'm glad to know that there is a way. Thanks.
YW.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Now I found you out, I don't think you're so
On Tue, 16 Mar 2010 20:40:43 -0400
Tom H wrote:
Hello Tom,
> GRUB_DEFAULT=saved
That's the one. Thanks for the reminder.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Life goes quick and it goes without warning
Bombsite B
>>> Again, is there no way to set a default in grub2? Is there no
>>> way, for example, to make the last-booted kernel the default kernel?
>> Modify /etc/default/grub to point to the relevant stanza, then run
>> grub-update. Changes made directly to /boot/grub/grub.cfg will get
>> overwritten nex
On Tue, 16 Mar 2010 14:48:39 -0400 (EDT), Brad Rogers wrote:
> On Tue, 16 Mar 2010 10:29:16 -0400 (EDT), Stephen Powell wrote:
>> Again, is there no way to set a default in grub2? Is there no
>> way, for example, to make the last-booted kernel the default kernel?
>
> Modify /etc/default/grub to p
>> Again, is there no way to set a default in grub2? Is there no
>> way, for example, to make the last-booted kernel the default kernel?
> Modify /etc/default/grub to point to the relevant stanza, then run
> grub-update. Changes made directly to /boot/grub/grub.cfg will get
> overwritten next upd
On Tue, 16 Mar 2010 10:29:16 -0400 (EDT)
Stephen Powell wrote:
Hello Stephen,
> Again, is there no way to set a default in grub2? Is there no
> way, for example, to make the last-booted kernel the default kernel?
Modify /etc/default/grub to point to the relevant stanza, then run
grub-update. C
On Tue, Mar 16, 2010 at 10:17 -0500, Mark Allums wrote:
> On 3/16/2010 8:28 AM, Wolodja Wentland wrote:
>
> >The easiest way would be to enforce a strict naming scheme (maybe with
> >lintian) so the aforementioned code can stay as simple as it is today.
> In the short run, an easy thing to do is
On 3/16/2010 8:28 AM, Wolodja Wentland wrote:
The easiest way would be to enforce a strict naming scheme (maybe with
lintian) so the aforementioned code can stay as simple as it is today.
In the short run, an easy thing to do is remove -trunk- image and all
corresponding packages, as it is a
On Tue, 16 Mar 2010 09:28:18 -0400 (EDT), Wolodja Wentland wrote:
> On Tue, Mar 16, 2010 at 09:03 -0400, Stephen Powell wrote:
>>
>> My guess is that grub2 simply makes a list of all files in /boot which begin
>> with linux-image, sorts them in descending order by the ASCII collating
>> sequence, a
On Tue, Mar 16, 2010 at 09:03 -0400, Stephen Powell wrote:
> On Tue, 16 Mar 2010 08:26:40 -0400 (EDT), Mitchell Laks wrote:
> >
> > I notice that others had problems with grub not updating the kernel
> > from linux-image-2.6.32-trunk-686 to linux-image-2.6.32-3-amd64
> > and I had this same probl
On Tue, Mar 16, 2010 at 07:53 -0500, Ron Johnson wrote:
> On 2010-03-16 07:26, Mitchell Laks wrote:
> Interesting thought. Does the system boot if you manually edit the
> grub config file?
The system boots fine if you select the new (-3-) kernel manually, so I
would think that it would also boot
On Tue, 16 Mar 2010 08:26:40 -0400 (EDT), Mitchell Laks wrote:
>
> I notice that others had problems with grub not updating the kernel
> from linux-image-2.6.32-trunk-686 to linux-image-2.6.32-3-amd64
> and I had this same problem.
>
> I suspect that this is because the heuristic that dpkg or ap
On 2010-03-16 07:26, Mitchell Laks wrote:
I notice that others had problems with grub not updating the kernel
from linux-image-2.6.32-trunk-686 to linux-image-2.6.32-3-amd64
and I had this same problem.
I suspect that this is because the heuristic that dpkg or apt or aptitude update
is using
f
I notice that others had problems with grub not updating the kernel
from linux-image-2.6.32-trunk-686 to linux-image-2.6.32-3-amd64
and I had this same problem.
I suspect that this is because the heuristic that dpkg or apt or aptitude update
is using
finds that linux-image-2.6.32-trunk-686 is gr
15 matches
Mail list logo
