On 4/6/2011 7:28 AM, Erik Christiansen wrote: > ... > That would rely on the fact that we do not output to stdout, so that if > grub-mkconfig ends without spontaneous output, there is nothing to write > to disk when grub-mkconfig closes its filedescriptor _after_ all the > helper scripts, including ours, have run. > > Safer ways to achieve boot parameter customisation are then: > > a) Append "sync" and editing snippet to update-grub, so that it runs > after grub-mkconfig has done its stuff, and the file is written to > disk. (We previously didn't sync.) > > OR > > b) Put a wrapper around update-grub, so that our snippet lives in > either ~/bin/update-grub or /usr/local/bin/update-grub, and we > ensure in /etc/bash.bashrc that the chosen directory is first in > $PATH. (Avoids modifying any grub stuff.) > > OR > > c) Modify the update-grub stub, to redirect output to our script, > which in turn redirects to /boot/grub/grub.cfg (Since > /usr/local/bin/update-grub is just a wrapper around grub-mkconfig, > make it do more useful work.) > > Perhaps b) is the way to go? >
I'm getting too old to want to play this game but doesn't it seem there is another alternative? Namely, insert another script to grub.d, call it 05_rtai, say, that adds the isocpus parameter just to rtai entries. If 10_linux results in the same kernels being entered later in the boot order with the standard parameters, so what? Regards, Kent ------------------------------------------------------------------------------ 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
