On Sun, Mar 18, 2012 at 5:00 PM, Michael D. Setzer II
mi...@kuentos.guam.net wrote:
Just did an update and it included a new kernel, but then on
reboot after running grub2-mkconfig noticed that the newest one
was not first. Seems to be sorting the 9 before the 10?
Is this a bug?
I use the
On 18 March 2012 15:00, Michael D. Setzer II mi...@kuentos.guam.net wrote:
Just did an update and it included a new kernel, but then on
reboot after running grub2-mkconfig noticed that the newest one
was not first. Seems to be sorting the 9 before the 10?
Is this a bug?
I have been using
On 19 Mar 2012 at 17:39, Piscium wrote:
Date sent: Mon, 19 Mar 2012 17:39:43 +
Subject:Re: grub2-mkconfig with 3.2.10 kernels?
From: Piscium grok...@gmail.com
To: Community support for Fedora users
users
On 19 March 2012 19:53, Michael D. Setzer II mi...@kuentos.guam.net wrote:
I have had some messages on the grub list, and they confirmed
the bug, and a fix seems to be to modify the
/usr/lib/grub/grub_mkconfig_lib by changing one line from sort -n
to sort -V. Note: That is an unofficial
...@gmail.com
Date: Mon, 19 Mar 2012 13:30:10 -0700
Subject: Re: grub2-mkconfig with 3.2.10 kernels?
On Sun, Mar 18, 2012 at 2:50 PM, Michael D. Setzer II
mi...@kuentos.guam.net wrote:
Just did an update and it included a new kernel, but then on
reboot after running grub2-mkconfig noticed that the newest
Just did an update and it included a new kernel, but then on
reboot after running grub2-mkconfig noticed that the newest one
was not first. Seems to be sorting the 9 before the 10?
Is this a bug?
I use the default=0, so this makes it not use the latest?
On 03/18/2012 11:00 PM, Michael D. Setzer II wrote:
Just did an update and it included a new kernel, but then on
reboot after running grub2-mkconfig noticed that the newest one
was not first. Seems to be sorting the 9 before the 10?
Is this a bug?
I use the default=0, so this makes it not
On 19 Mar 2012 at 7:47, Ed Greshko wrote:
Date sent: Mon, 19 Mar 2012 07:47:47 +0800
From: Ed Greshko ed.gres...@greshko.com
To: Community support for Fedora users
users@lists.fedoraproject.org
Subject:Re: grub2-mkconfig
On Monday 19 Mar 2012 10:09:50 Michael D. Setzer II wrote:
On 19 Mar 2012 at 7:47, Ed Greshko wrote:
On 03/18/2012 11:00 PM, Michael D. Setzer II wrote:
Just did an update and it included a new kernel, but then on
reboot after running grub2-mkconfig noticed that the newest one was
On 03/19/2012 08:09 AM, Michael D. Setzer II wrote:
The issue is that the order is coming up wrong.
On my sytem, it adds the new kernel, but it is the in this order
from the grub.cfg file.
menuentry 'Fedora Linux, with Linux 3.2.9-2.fc16.x86_64'
menuentry 'Fedora Linux, with Linux
Am 19.03.2012 01:39, schrieb Ed Greshko:
On 03/19/2012 08:09 AM, Michael D. Setzer II wrote:
The issue is that the order is coming up wrong.
On my sytem, it adds the new kernel, but it is the in this order
from the grub.cfg file.
menuentry 'Fedora Linux, with Linux 3.2.9-2.fc16.x86_64'
On 03/19/2012 08:49 AM, Reindl Harald wrote:
because /etc/default/grub in Fedora contains GRUB_DISABLE_RECOVERY=true?
No, it isn't even listed there But it is listed in grub.rpmnew.
Learning about grub2 is on my list of things to learn more about. May have to
bump
the priority a bit.
--
On 19 Mar 2012 at 8:39, Ed Greshko wrote:
Date sent: Mon, 19 Mar 2012 08:39:00 +0800
From: Ed Greshko ed.gres...@greshko.com
To: Community support for Fedora users
users@lists.fedoraproject.org
Subject:Re: grub2-mkconfig
On 03/19/2012 09:22 AM, Michael D. Setzer II wrote:
Did you run grub2-mkconfig -o /boot/grub2/grub.cfg?
From what I have seen, when a new kernel is installed, it runs
grubby, which doesn't make the recover option, so I generally run
the grub2-mkconfig to get it have the listing, but it may
14 matches
Mail list logo
