No subject

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

--y0ulUmNC+osPPQO6
Content-Type: application/octet-stream
Content-Disposition: attachment; filename="update-grub_boot.diff.gz"
Content-Transfer-Encoding: base64

H4sICLMiskYAA3VwZGF0ZV9ncnViX2Jvb3QuZGlmZgCFUNFqg0AQfM59xWB9aNlcbnMVK4aA
T/2JUkTjXXNgVPQstF9fL01B2ofuy+7szgzDSimhptp1ah6ayhv5Ns71RjOnkp8kJ9D7nLP8
MdnxT4F4uQsiwi/NIsgka2jOdZYnfzVFAanTdJuCQtszikLgDv5s0Jh3dzKw/XiFqu57D+ta
M31M3lwEwqL8Zh3je+u65oYQXcnRg4AgZ/EC+YkoXvEjvB6Caydo85+NWnzIOkEh2PPcthgq
f4bvVyl3l2oQt7lc5mMcXlA2blRrgvgC2VsUlF4BAAA=

--y0ulUmNC+osPPQO6--