On 2019-01-14 20:20:49 +0100, Pascal Hambourg wrote: > Le 14/01/2019 à 11:09, Vincent Lefevre a écrit : > > On 2019-01-14 11:06:01 +0100, Vincent Lefevre wrote: > > > On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote: > > > > This issue is not specific to lilo. It would affect grub-pc updates too, > > > > because the boot device is specified by device id. > > > > > > > > For example on my system : > > > > $ debconf-show grub-pc > > > > (...) > > > > * grub-pc/install_devices: /dev/disk/by-id/ata-WDC_WD1200BEVE-00WZT0_... > > > > > > > > The issue would happen less often - only when updating the grub-pc > > > > package instead of on any kernel update - but it would still happen. > > > > > > ... which was what happened to me a few days ago! > > > > BTW, a display bug in the terminal made the problem worse, because > > I could not select a device for GRUB installation. So, currently, > > new GRUB versions are no longer installed. > > Which display bug ?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919029 > During the system installation ? During grub upgrade, when (re-)configuring due to the udev bug. > You can install new versions of GRUB by hand with > > # grub-install /dev/disk/by-id/... Yes, but one issue is one may not know where GRUB was installed in the first place (ditto with the other methods). > Or you can reconfigure grub-pc with > > # dpkg-reconfigure grub-pc which yields the display issue... unless I increase the terminal window size *before* I run this command. > If the display bug is still present in the default "dialog" (curses-like) > front-end, you can try to use the "readline" (command line-like) front-end > with "--frontend=readline" when running dpkg-reconfigure. OK, thanks, I didn't know. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
