On Wednesday, April 06, 2011 12:40:39 PM Ed Nisley did opine: > On Wed, 2011-04-06 at 21:28 +1000, Erik Christiansen wrote: > > Perhaps b) is the way to go? > > At the risk of appearing an ungrateful wretch, it seems the problem has > been transformed from: > > - remember to edit /boot/grub/grub.cfg after each kernel update > > into one or more of: > > - modify / debug / maintain various system scripts > - maintain wrappers around various grub scripts > - maintain / remember to apply filter scripts for grub.cfg > - risk grub update failures due to locally modified files
Add one more step to this recipe Ed, as root, do a chattr -R +i on the whole /etc/grub.d tree once it works. Any update scripts then will either silently fail until you fix them by hand because the "upgrade?" didn't work, or yell bloody murder, reminding you that something tried to poach your hard fought work. In either case you are protected. I, being paranoid, even did the chattr +i to /boot/grub/grub.cfg (or menu.lst as the case might be) which may be the ultimate hammer of self defense. This has nothing to do with being an "ungrateful wretch" though. :) > While script twiddling may be a cleaner solution, the whole apparat can > cause even more mysterious failures than my usual "Whoops, forgot to > edit grub.cfg again!" error. Any system update that clobbers those files > or the assumptions going into them will (silently) cause a boot with > EMC2 unable to run. > > Worst case, the mods may trigger truly weird & wonderful behavior by > unexpectedly (and silently) pooching grub.cfg, perhaps rendering the > entire system unbootable by mere mortals. Hey, we're supposed to be immortal, after all, we know enough bash to be dangerous. ;-) > It's now painfully obvious that the requirement for different kernel > options on different kernels wasn't part of the *cough* Grub2 system > architecture planning process. Yeah. Seems the coders want more and more control, provided they do it right, not a bad idea, but our definitions of right seem to be at odds with theirs. > Fortunately, we *may* get a new leach field in the next few days, after > which I can think about something other than sewage. Suffice it to say > some projects have been backing up around here. I think thats an "oh shit" situation, I got it here too, on city sewer lines occasionally, so I bought a powered 100 foot snake, which didn't work very well, but did get it going well enough that we have now learned to hold the handle down until the flush tank is empty, seems our new half a gallon of water per flush toilet, was not supplying enough water to keep it moving. One of the hazards of being 1 of only 2 houses on the whole block with a full basement, there isn't enough fall between us and the mainline. >From the lay of the land, no way there is too much fall. > Thanks to all for exploring some solutions that I was only dimly aware > of... Yes, this discussion has been enlightening. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) <http://tinyurl.com/ddg5bz> <http://www.cantrip.org/gatto.html> "Experience has proved that some people indeed know everything." -- Russell Baker ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
