intrigeri: > Hi, > > adrelanos wrote (27 Feb 2013 16:32:36 GMT) : >> Why not just add it to /etc/grub.d/? > > What grub.d/ facility allows to modify config snippets generated by > another grub.d/ script??
Yes the .d directory magic is awesome. Scripts are on purpose loaded in alphabetical order. I try to explain it with an example. /etc/apt/apt.conf.d/10periodic comes with some Debian package. I don't like the defaults for Whonix. The defaults in /etc/apt/apt.conf.d/10periodic are. APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "1"; APT::Periodic::Unattended-Upgrade "1"; I created a file /etc/apt/apt.conf.d/20noperiodic with the content. APT::Periodic::Update-Package-Lists "0"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; 2 comes after 1 in alphabet. Therefore 20noperiodic supersedes 10periodic. apt-config dump shows, that it has been changed to my liking. The advantage is, that I never have to fight with manually modifying /etc/apt/apt.conf or /etc/apt/apt.conf.d/10periodic when the package maintainer updates it. With that knowledge I imagine, that the variables GRUB_CMDLINE_LINUX_DEFAULT and/or GRUB_CMDLINE_LINUX from /etc/default/grub could be extended using /etc/grub.d/somenumber_apparmor. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
