This bug is to the best of my knowlegde fixed in version 0.97-1.
Kristian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The files are placed in /lib/grub/i386-pc in Debian instead of
/usr/lib/grub/i386-pc.
I attached a pacth for the documentation, if that is of any use.
Kristian
=
--- grub-0.97/docs/grub.texi.orig2005-12-06 03:22:16.0 +0100
+++ grub-0.97/docs/grub.texi2005-12-06
This sounds like the same bug as #264312, you might want to consider
merging them.
Kristian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
In 0.97-1 grub-set-default is included.
I think that closes this bug.
Kristian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Since the last part only partly solved one of the problems. here is a
new patch that actually solves both problems. My test list of kernels is
sorted:
/boot/vmlinuz-2.6.15
/boot/vmlinuz-2.6.14.2+pre2
/boot/vmlinuz-2.6.14.2-ac99
/boot/vmlinuz-2.6.14.2pre2
/boot/vmlinuz-2.6.14.2-pre2
I just updated the patch to fit on the 0.97-3 release on grub.
I have attached the patch
Kristian
--- update-grub.orig2006-01-10 13:57:26.0 +0100
+++ update-grub 2006-01-10 13:58:55.0 +0100
@@ -760,7 +760,7 @@
echo $splashimage_path $buffer
echo $buffer
grub-set-default is included in the 0.97-1 release of grub. This fixes
this bug as far as I know.
Kristian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I made a patch that I think will sort the kernels correctly.
When comparing the kernel version if the kernel looks like
vmlinuz-2.6.14-pre2 it will change it to vmlinuz-2.6.14.0-pre2
thereby ensuring that 2.6.14.2 is treated as newer since 20 and
therefore it is placed higher in the menu than
I just realised, this pacth will not fix this problem, since it the
kernel name looked different from the standard.
So please disregard the info on this bug, it should still close #342221
though.
Kristian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
This seems to be a bug in a version of grub that was used before woody,
does anybuddy know if this if this bug exists in the newer releases of grub?
Kristian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
This bug is reported in 0.92-3.0.skolelinux.1, is it still the case in
newer versions of the grub?
Kristian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Seems that I was wrong before, I accidently broke the script so it was
not updating correctly, so the patch for 346596 did not fix the problem.
However, I made a patch and applied it, so now it is really fixed and
pending. No really, I promise :)
--
Best Regards
Kristian Edlund
GPG ID: 7DD7559F
Hi
Hi I am new on the grub development team, and I found your bugreport
a few days ago, I intend to look into it, and test it. But I haven't
had the time so far. So the patch has not been merged and the current
status is still that nothing is done afaik.
Kristian
On 1/16/06, Martin-Éric Racine
Hi everyone
Do you know the status of the xfs bug in grub which casues #309218,
#239111, #243835 and #246111. There is a supplied patch, but I do not
have the possibility to test it.
--
Best Regards
Kristian Edlund
GPG ID: 7DD7559F
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Package: aterm
Version: 1.0.0-1
Severity: normal
Aterm crashes when I try to copy and paste stuff.
I can reproduce it by:
1. opening two terminal.
2. In terminal 1 mark some text with the mouse
3. Use the 3rd mousebutton (whatever it is called, the one that is used to
paste text) to paste the
A little additional infomation. I realised I can get the error message:
XIO: fatal IO error 14 (Bad address) on X server :0.0
after 2514 requests (2513 known processed) with 0 events remaining.
--
Best Regards
Kristian Edlund
GPG ID: 7DD7559F
--
To UNSUBSCRIBE, email to [EMAIL
The first installation report states that /grub/stage1 exists. Is that
indeed true?
Checking if /boot/grub/stage1 exists... no
Checking if /grub/stage1 exists... yes
Checking if /grub/stage2 exists... yes
Checking if /grub/e2fs_stage1_5 exists... yes
Can you reproduce the error when you run update-grub with sh update-grub?
Can you send supply your menu.lst file, and try to run update-grub
with sh -x update-grub and send the output of that file as well.
Kristian
PROTECTED] wrote:
Le samedi 11 février 2006 à 10:19 +0100, Kristian Edlund a écrit :
Can you reproduce the error when you run update-grub with sh update-grub?
Can you send supply your menu.lst file, and try to run update-grub
with sh -x update-grub and send the output of that file as well
[EMAIL PROTECTED] wrote:
Le dimanche 12 février 2006 à 19:22 +0100, Kristian Edlund a écrit :
Hi again
It doesn't fail on my machine, so either it is caused by the amd64
architecture or the raid device.
It seems to fail around the command readlink -f /dev/sda1
Can you send the output
runs without problems. So
I doubt that #349291, is related to this bug.
When you try to purge your kernel, what command are you using and what
happens?
--
Best Regards
Kristian Edlund
GPG ID: 7DD7559F
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
21 matches
Mail list logo
