Hi All, On this machine I am using right now on which I developed netman, I have grub2 installed. Since I never agreed with how grub2 should be managed, I opted to use a manual method to update grub.cfg. This machine has about 9 Debian/Devuan installations installed to separate partitions on a GPT formatted disk. The first partition is the one dedicated to maintain grub2 with only a terminal and root as a user. I found that grub.cfg uses an easy syntax that I can adopt to manually edit the file to achieve more or less the same ease of use I used to enjoy with grub1. In case grub2 overwrites grub.cfg, I keep a backup so as to easily restore it to the prior state. All other installations do not have a bootloader installed so that the primary bootloader would always continue to load the correct manually written grub.cfg as I wanted.
My setup prevents any installation from modifying grub.cfg without my knowledge. It also makes it impossible for any installation to modify the primary bootloader except the one with grub2 installed that I almost seldom boot. In fact, there is no grub menu entry for the installation that I use to manage grub2. When I need to do that, I press 'e' as soon as the grub2 menu is displayed and edit the menu entry's stanza as appropriate. Although it may sound complicated, this setup saved me quite a lot of headaches about changing menus without my approval. Edward On 19/01/2016, Joel Roth <jo...@pobox.com> wrote: > Steve Litt wrote: >> On Tue, 19 Jan 2016 17:20:10 +0100 >> Adam Borowski <kilob...@angband.pl> wrote: >> >> > On Tue, Jan 19, 2016 at 11:02:17AM -0500, Steve Litt wrote: >> > > Grub is the systemd of bootloaders. It's all about pretty colors, >> > > nice images, and hiding the fact that processes are being >> > > instantiated. >> > >> > Grub is complex, but that's caused by what it tries to do (read the >> > kernel image from real filesystems instead of a blockmap like lilo). >> > It doesn't go beyond its scope, unlike systemd. >> >> The preceding paragraph was much more true of Grub1 than its gargantuan >> spawn, Grub2. >> >> Grub1 read filesystems just fine. Grub2 has prioritized all sorts of >> pretty, and the simplicity of Grub1 has been lost. > > The grub developers wrote that they began grub2 due > to limitations and maintenance problems with grub1. > >> SteveT >> >> Steve Litt >> January 2016 featured book: Twenty Eight Tales of Troubleshooting >> http://www.troubleshooters.com/28 >> >> >> _______________________________________________ >> Dng mailing list >> Dng@lists.dyne.org >> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > -- > Joel Roth > > > _______________________________________________ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
