Bug#689753: Still an issue

2015-02-13 Thread Gregor Riepl
I think this bug should be reopened and not closed as WONTFIX. The suggested workaround with /etc/kernel-img.conf doesn't seem to work, and implementing some extra logic to support filesystems without hardlinks shouldn't be too difficult. Why not just create a copy instead if hardlinking fails?

Bug#689753:

2012-12-27 Thread Max Tsepkov
I would vote it to be a `normal` priority but not wishlist. Because it's actually breaks intall/update of packages. Preconfiguring packages ... (Reading database ... 170200 files and directories currently installed.) Preparing to replace linux-image-3.2.0-4-amd64 3.2.32-1 (using .../linux-image-3.

Bug#689753: linux-image-3.5-trunk-amd64: Please support /boot being vfat, or another way of having the kernel on the EFI system partition

2012-10-05 Thread Ben Hutchings
On Sat, 2012-10-06 at 00:06 +0200, Maik Zumstrull wrote: > Package: src:linux > Version: 3.5.5-1~experimental.1 > Severity: normal > > Call me a masochist, but I've been using UEFI boot on systems new enough > to support it. For this, it makes sense to have the kernel and initrd > images on the EF

Bug#689753: linux-image-3.5-trunk-amd64: Please support /boot being vfat, or another way of having the kernel on the EFI system partition

2012-10-05 Thread Maik Zumstrull
Package: src:linux Version: 3.5.5-1~experimental.1 Severity: normal Call me a masochist, but I've been using UEFI boot on systems new enough to support it. For this, it makes sense to have the kernel and initrd images on the EFI system partition. It's not an absolute requirement. One could have g