Your message dated Fri, 28 Mar 2008 14:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#435708: fixed in grub 0.97-35
has caused the Debian Bug report #435708,
regarding update-grub fails to recognize mount points in /etc/fstab if the
entry contains a trailing slash
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
435708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435708
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: grub
Version: 0.97-27
Severity: important
Tags: patch
Hello,
on my machine, I have a separate /boot partition. I found that
update-grub did not recognize this fact, but wrote the complete path
/boot/vmlinuz... into the /boot/grub/menu.lst file. Because of this,
the system did not boot after a call to update-grub.
I checked /sbin/update-grub. I found out that update-grub indeed looks
for mount points; nevertheless, it did not recognize it in my case. The
reason was found rather quickly: My /etc/fstab contained a line like
/dev/sda7 /boot/ ...
If I remove the trailing shlash from the mount point and make the line
look like follows, update-grub happily recognizes the mount point and
does not behave erroneously anymore:
/dev/sda7 /boot ...
>From my understanding and what I have found so far, the original entry
in fstab is fully legal; thus, update-grub is wrong.
I rated this bug as "important" as it leaves the user's machine in a
non-booting state. In fact, my first "solution" was to replaced
update-grub with a tool that called the old update-grub and performed a
sed to fix the paths.
The attached patch fixes the problem in a straight-forward way. I am not
sure if it is the best way, however. It might be a better idea to fix
fix find_device(). I did not perform this change, as I am not sure about
any side-effects this might cause.
Note: I tested this problem with Debian Sarge, Debian Etch, and even
with a Ubuntu 6.10 system: All show the same behaviour.
Regards,
Spiro
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i586)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-486
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages grub depends on:
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libncurses5 5.5-5 Shared libraries for terminal hand
grub recommends no packages.
-- debconf-show failed
update-grub_boot.diff.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: grub
Source-Version: 0.97-35
We believe that the bug you reported is fixed in the latest version of
grub, which is due to be installed in the Debian FTP archive:
grub-disk_0.97-35_all.deb
to pool/main/g/grub/grub-disk_0.97-35_all.deb
grub-doc_0.97-35_all.deb
to pool/main/g/grub/grub-doc_0.97-35_all.deb
grub-legacy-doc_0.97-35_all.deb
to pool/main/g/grub/grub-legacy-doc_0.97-35_all.deb
grub_0.97-35.diff.gz
to pool/main/g/grub/grub_0.97-35.diff.gz
grub_0.97-35.dsc
to pool/main/g/grub/grub_0.97-35.dsc
grub_0.97-35_amd64.deb
to pool/main/g/grub/grub_0.97-35_amd64.deb
multiboot-doc_0.97-35_all.deb
to pool/main/g/grub/multiboot-doc_0.97-35_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Robert Millan <[EMAIL PROTECTED]> (supplier of updated grub package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 28 Mar 2008 14:27:07 +0100
Source: grub
Binary: grub grub-disk grub-doc grub-legacy-doc multiboot-doc
Architecture: source amd64 all
Version: 0.97-35
Distribution: unstable
Urgency: low
Maintainer: Grub Maintainers <[EMAIL PROTECTED]>
Changed-By: Robert Millan <[EMAIL PROTECTED]>
Description:
grub - GRand Unified Bootloader (Legacy version)
grub-disk - GRUB bootable disk image (dummy package)
grub-doc - Documentation for GRand Unified Bootloader (dummy package)
grub-legacy-doc - Documentation for GRUB Legacy
multiboot-doc - The Multiboot specification
Closes: 284790 301373 435708 441080 443897 450951 463274
Changes:
grub (0.97-35) unstable; urgency=low
.
* Upload to unstable.
.
grub (0.97-34) experimental; urgency=low
.
* patches/128gib_disk_limit.diff: Extend disk addressing up to 2 TiB.
(Closes: #450951)
.
grub (0.97-33) experimental; urgency=low
.
* control (grub): Suggest multiboot-doc.
* update-grub: Rewrite find_device() and convert() using grub-probe from
grub-common package. (Closes: #435708, #443897, #463274, #301373, #284790)
* patches/use_grub-probe_in_grub-install.diff: Do the same for grub-install.
(Closes: #441080)
Files:
b18b08fbea9f6cde0e5ebcbf70fba381 941 admin optional grub_0.97-35.dsc
7e06aeeeea11d65d646dbe1cf332abb3 76780 admin optional grub_0.97-35.diff.gz
db67a6b700f1b682f8bec6ba159a2c70 902882 admin optional grub_0.97-35_amd64.deb
79efadb0dd46383954a5435b597b68a9 112944 admin optional
grub-disk_0.97-35_all.deb
8992e395b331699a0c608b3066e05ba1 112950 doc optional grub-doc_0.97-35_all.deb
b7b36b164aa6dbeee7f3be3f2eba27d2 233994 doc optional
grub-legacy-doc_0.97-35_all.deb
59bec81423e4ba333f32175ee38258a5 158086 doc optional
multiboot-doc_0.97-35_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH7P/VC19io6rUCv8RAskWAJ465APVT1M1GCVgI5gOYuu9Xg+I5gCffOJK
LLMix1+iIZCmu1GDtCqZ3Ww=
=0m8h
-----END PGP SIGNATURE-----
--- End Message ---
