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 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. 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. 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. Thanks to all for exploring some solutions that I was only dimly aware of... -- Ed http://softsolder.com ------------------------------------------------------------------------------ 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
