I've just updated again the kernel and the update-grub bug is still happens.
Today (07/06/08) I've updated the system through update manager and the kernel
was updated to 2.6.24.18.20.
Then ucf ask for an option about what to do with menu.lst option, and i
selected 1st (used the new proposed or
parq,
The fix for this bug is that, when your locally-modified menu.lst
disagrees with how update-grub would calculate the boot entries, a
warning is shown letting you know about this inconsistency. There is no
way that we can reliably fix the fact that the autogenerated entries
don't match your
Ted Cabeen: The exact same thing is happening to me. I filed this as a
separate bug report:
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/229656
--
Default update-grub behaviour is not intuitive with respect to user
modifications
https://bugs.launchpad.net/bugs/21412
You received this bug
The ucf changes in 0.97-29ubuntu7 seem to have broken some update-grub
workflows.
In gutsy and before, you could setup a basic menu.list containing
update-grub options but no kernels, run update-grub, and get your
kernels correctly added to the menu.lst file. Now, if a menu.lst exists
at all
On Wed, Feb 27, 2008 at 06:04:02PM -0800, Steve Langasek wrote:
FWIW, this was tracked down to a difference in the content of the entries
being written out by grub based on the output of 'lsb_release -d', and was
resolved in grub 0.97-29ubuntu14.
Thanks for following up.
--
- mdz
--
Hi Steve,
Thanks very much. I don't understand all the details but to hear it's
been fixed makes me happy :)
BR,
Cheski
- Original Message
From: Steve Langasek [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, February 28, 2008 3:04:02 AM
Subject: Re: [Bug 21412] Re: Default
On Tue, Jan 29, 2008 at 09:36:12AM +, Matt Zimmerman wrote:
Attached are /boot/grub/menu.lst and /boot/grub/menu.lst~. Assuming this is
the backup from ucf, this should be what you need. Notice that all of the
kernel lines are unmodified.
I saw exactly the same behaviour on both my
I have such a partition configuration:
/dev/sda1: /boot
/dev/sda2: swap
/dev/sda3: windows
/dev/sda5: /
/dev/sda6: /home
In my menu.lst file I have lines containing: root (hd0,0) which is
true. Nonetheless, after every kernel update, it automatically changes
to hd(0,1) which breaks running of
On Tue, Jan 29, 2008 at 12:07:01AM -, Steve Langasek wrote:
In my pre-upload tests, I did not find that the first upgrade to
0.97-29ubuntu7 triggered a ucf prompt except in the case where there was
already a detectable difference between the magic comments and the
kernel list. This is
On Mon, Jan 28, 2008 at 09:56:25PM -, Steve Langasek wrote:
This bug has been fixed in hardy, in grub version 0.97-29ubuntu7 and
above:
grub (0.97-29ubuntu7) hardy; urgency=low
* debian/update-grub: use ucf to record changes to the autogenerated
kernel list
It is still
This bug has been fixed in hardy, in grub version 0.97-29ubuntu7 and
above:
grub (0.97-29ubuntu7) hardy; urgency=low
* debian/update-grub: use ucf to record changes to the autogenerated
kernel list
It is still advisable that boot options for other operating systems such
as Windows be
Matt,
In my pre-upload tests, I did not find that the first upgrade to
0.97-29ubuntu7 triggered a ucf prompt except in the case where there was
already a detectable difference between the magic comments and the
kernel list. This is AFAICS a necessary evil in order to get the
current state of the
** Tags added: qa-hardy-list
--
Default update-grub behaviour is not intuitive with respect to user
modifications
https://bugs.launchpad.net/bugs/21412
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I agree with mdz, of course. Untargeting from Gutsy.
** Changed in: grub (Ubuntu)
Target: ubuntu-7.10-beta = None
--
Default update-grub behaviour is not intuitive with respect to user
modifications
https://bugs.launchpad.net/bugs/21412
You received this bug notification because you are
** Changed in: grub (Ubuntu)
Target: None = ubuntu-7.10-beta
--
Default update-grub behaviour is not intuitive with respect to user
modifications
https://bugs.launchpad.net/bugs/21412
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
On Wed, Sep 05, 2007 at 07:58:22AM -, Henrik Nilsen Omma wrote:
** Changed in: grub (Ubuntu)
Target: None = ubuntu-7.10-beta
Unfortunately, fixing this isn't straightforward, and requires designing a
different solution, documenting it, and hopefully pushing it up to Debian to
avoid
Colin, is something we have a realistic hope of addressing for Gutsy or
should we spec up better grub management as a feature for Gutsy+1? (we
could also do with a boot config GUI)
--
Default update-grub behaviour is not intuitive with respect to user
modifications
** Changed in: grub (Ubuntu)
Assignee: (unassigned) = Ubuntu Installer Team
--
Default update-grub behaviour is not intuitive with respect to user
modifications
https://bugs.launchpad.net/bugs/21412
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
If changing this, note that there are installer implications and that
this needs to be handled carefully. In general this needs careful design
to ensure that the result isn't just as bad ...
--
Default update-grub behaviour is not intuitive with respect to user
modifications
Adding the Windows boot options before the Automagic lines results in
the Splashimage not appearing, so the bootlist really has to come after
all the options, so there is no proper way of reordering the bootlist
with anything before Ubuntu.
--
Default update-grub behaviour is not intuitive with
** Bug 59895 has been marked a duplicate of this bug
--
Default update-grub behaviour is not intuitive with respect to user
modifications
https://launchpad.net/bugs/21412
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
To get Windows (or any other OS) to appear first in the list, it is necessary
to add it BEFORE the Automagic section, which is before all the Options and
example comments, which is less than ideal. It would be OK to have an Ubuntu
section with all its kernels, as long as you can add entries
** Summary changed:
- Default update-grub behaviour is not intuitive
+ Default update-grub behaviour is not intuitive with respect to user
modifications
--
Default update-grub behaviour is not intuitive with respect to user
modifications
https://launchpad.net/bugs/21412
--
ubuntu-bugs
23 matches
Mail list logo
