On Sat, Oct 17, 2009 at 05:02:45AM -, Wayne McDougall wrote:
> How do I check what version of Grub2 I have installed?
>
> I have experienced this bug on an up-to-date system, but it's possible
> the mirror was out of date. It is still at this moment telling me I am
> completely up to date.
Yo
Am Samstag, den 17.10.2009, 05:02 + schrieb Wayne McDougall:
> How do I check what version of Grub2 I have installed?
>
> I have experienced this bug on an up-to-date system, but it's possible
> the mirror was out of date. It is still at this moment telling me I am
> completely up to date.
>
On Wed, Oct 14, 2009 at 01:55:37PM -, Kamus wrote:
> one hour ago I tried to upgrade Karmic (to date) and I get this issue
> too,
I don't think you gave it a chance to build and get to the mirrors.
--
invalid: environment block
https://bugs.launchpad.net/bugs/439784
You received this bug not
Am Dienstag, den 13.10.2009, 18:59 + schrieb Jordan:
> However, it looks like grub-editenv is still not atomic: If you run
> "grub-editenv /boot/grub/grubenv set foo=bar" the first thing it does
> in
> create_env_blk_file() is call fopen( "/boot/grub/grubenv", "wb" )
> truncating the actual fil
On Tue, Oct 13, 2009 at 06:59:11PM -, Jordan wrote:
> However, it looks like grub-editenv is still not atomic: If you run
> "grub-editenv /boot/grub/grubenv set foo=bar" the first thing it does in
> create_env_blk_file() is call fopen( "/boot/grub/grubenv", "wb" )
> truncating the actual file,
On Tue, Oct 13, 2009 at 05:29:10PM -, Jordan wrote:
> I have not confirmed this yet by looking at any code, but the reason
> that grubenv is ending up zero bytes is likely that some code is writing
> to grubenv ( from linux, not grub itself ) by doing something like:
> write file "grubenv.tmp";
FWIW, if you change /etc/grub.d/10_linux, you don't need to make
grub.cfg unwritable - /etc/grub.d/10_linux is an input to update-grub,
not an output from it, and furthermore it's a conffile so changes to it
are preserved on upgrade.
--
invalid: environment block
https://bugs.launchpad.net/bugs/4
Incidentally, there is a very good reason why loadenv doesn't create the
environment block itself - GRUB's filesystem modules don't have write
support, and adding that would expose us to a whole range of exciting
new possible bugs. For this reason, we create the file when we're in a
real operating
I'd like to know why an explicit create is necessary for you, as
'grub-editenv /boot/grub/grubenv unset recordfail' will create the
environment block implicitly, as verified from the code and demonstrated
here:
$ rm -f grubenv
$ grub-editenv grubenv unset recordfail
$ ls -l grubenv
-rw-r--
On Thu, Oct 01, 2009 at 10:14:51AM -, Glen Turner wrote:
> I just had a look at the fix,
Not sure how you managed that, since it's only on my laptop hard disk
right now!
--
invalid: environment block
https://bugs.launchpad.net/bugs/439784
You received this bug notification because you are a
10 matches
Mail list logo
