On Sun 21 May 2017 at 22:18:11 (+0200), Dejan Jocic wrote: > On 21-05-17, David Wright wrote: > > -rw-r--r-- 1 root root 134839 Apr 27 16:52 config-3.2.0-4-686-pae > > drwxr-xr-x 3 root root 12288 Apr 28 07:44 grub > > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae > > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae > > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae > > > > (I have to notice these upgrades myself because they overwrite > > my edited version of /boot/grub/grub.cfg which I then replace.) > > > > Sorry, but you are doing it wrong way. Grub 2 should not be customized > by editing /boot/grub/grub.cfg , but by editing /etc/default/grub and > files in /etc/grub.d/. Reason is obvious, your customization is lost > whenever something related to linux-image is upgraded. Just saying :)
Yes, it would be nice to use the Debian Way. But there is not enough flexibility in their scripts to do what I want. a) the logic of # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true is odd and, unfortunately, there's no facility for GRUB_ENABLE_LINUX_LABEL=true (I did have a shot at modifying the scripts, but it's less trivial than it would seem at first sight). b) they insert entries for sysvinit and recovery but not for fsck. I modify the first subentry, using the ids fsck and fsck so I can use grub-reboot 'fsck>fsck' to invoke it from a script that also logs a timestamp. I refuse to type monstrosities like grub-reboot 'Advanced options for Debian GNU/Linux>gnulinux-advanced-7ccc1c1c-a690-418b-96c0-edcce6ebd3c1' So it's far easier to write one python script to parse /run/udev/data, automatically make the changes I want, and keep the original and edited files as /boot/grub/grub.cfg-{uuids,edited}. After any upgrade, if the former matches /boot/grub/grub.cfg, it gets overwritten by the latter. Cheers, David.