On Sat, 2011-04-09 at 21:41 -0400, Kent A. Reed wrote:
> Kudos, brickbats, big yawns, gleeful
> nitpicking, all willingly accepted,
Well, here's a heaping double handful of kudos from me!
Your script bottles up a whole bunch of magic that I certainly couldn't
have figured out on my own.
Thanks
Hello,
I was thinking to write something on isolcpus on the wiki.
As I see that all the work has already been done wonderfully,
I decided to include a reference to it at the Troubleshooting section
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?TroubleShooting#The_isolcpus_Boot_parameter
I think t
On 4/10/2011 9:22 AM, Stuart Stevenson wrote:
> Would this be an FYI to submit to the grub developers?
>
> On Sun, Apr 10, 2011 at 5:35 AM, Mark Wendt (Contractor)<
> mark.we...@nrl.navy.mil> wrote:
>
>> On 4/9/2011 9:41 PM, Kent A. Reed wrote:
>>> Ok, gang, my work is out there for all to see at
Would this be an FYI to submit to the grub developers?
On Sun, Apr 10, 2011 at 5:35 AM, Mark Wendt (Contractor) <
mark.we...@nrl.navy.mil> wrote:
> On 4/9/2011 9:41 PM, Kent A. Reed wrote:
> > Ok, gang, my work is out there for all to see at
> >
> >
> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?T
On 4/9/2011 9:41 PM, Kent A. Reed wrote:
> Ok, gang, my work is out there for all to see at
>
> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?The_Isolcpus_Boot_Parameter_And_GRUB2
>
> There's a link to this page from the main EmcKnowledgeBase page under
> the 'Misc Stuff' heading. Kudos, brickbats, b
On 4/7/2011 11:44 PM, Kent A. Reed wrote:
> On 4/6/2011 9:00 AM, Kent A. Reed wrote:
>> ...
>> 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
On Apr 7, 2011, at 11:44 PM, Kent A. Reed wrote:
> Now that I know how easy it is, I may try a second approach, just
> modifying 10_linux so that it differentiates between rtai- and non-rtai
> linux kernels. [Although I'm not sure that's the answer for me because I
> like being able to boot the
On 4/6/2011 9:00 AM, Kent A. Reed wrote:
> ...
> 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
On Wednesday, April 06, 2011 01:04:20 PM Kent A. Reed did opine:
> 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-mk
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
On Wed, Apr 06, 2011 at 09:00:15AM -0400, Kent A. Reed 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
>
On Apr 6, 2011, at 8:46 AM, Ed Nisley wrote:
> 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 th
On Wed, Apr 06, 2011 at 08:46:21AM -0400, Ed Nisley wrote:
> 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
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
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 / maint
On Tue, Apr 05, 2011 at 11:14:47AM -0400, Tom Easterday wrote:
> On Apr 5, 2011, at 8:45 AM, Stephen Wille Padnos wrote:
> > Note that with grub2, ie Ubuntu 10.04, there is a directory of files
> > which are executed in order whenever grub is reconfigured. It looks
> > like the output of those f
Good to see that the Grub developers finally realized that their setup
was too easy and decided to make it worse than lilo. If anyone gets
this working well, it would be really great to see a writeup on the
wiki. The writeup on the Ubuntu forums seems a little too complete
for our purposes. It d
On Apr 5, 2011, at 8:45 AM, Stephen Wille Padnos wrote:
> Note that with grub2, ie Ubuntu 10.04, there is a directory of files
> which are executed in order whenever grub is reconfigured. It looks
> like the output of those files is concatenated, or the config file is
> piped from one to the ne
It works on a file in /tmp, but not on the actual /boot/grub/grub.cfg file on
my machine. Not sure why, permissions look fine...
I will attempt to RTFM from Stephen's message and see if I can do it the Right
Way (tm) ;-)
-Tom
On Apr 5, 2011, at 3:33 AM, Erik Christiansen wrote:
> On Mon, Apr
Erik Christiansen wrote:
> On Mon, Apr 04, 2011 at 09:51:20AM -0400, Tom Easterday wrote:
>
>> On Apr 4, 2011, at 9:22 AM, Tom Easterday wrote:
>>
>>> Your instructions didn't work for me (I am on 10.04). I assume it is due
>>> to the above. Looks like the lines start with "linux" not
On Tue, Apr 05, 2011 at 05:33:06PM +1000, Erik Christiansen wrote:
> Removing the "^" (anchor to start of line) allows your "linux"
s/Removing/Substituting/
After all, it ended up still playing a part.
Erik
--
On Mon, Apr 04, 2011 at 09:51:20AM -0400, Tom Easterday wrote:
>
> On Apr 4, 2011, at 9:22 AM, Tom Easterday wrote:
> > Your instructions didn't work for me (I am on 10.04). I assume it is due
> > to the above. Looks like the lines start with "linux" not kernel? See
> > attached snipped f
On Apr 4, 2011, at 9:22 AM, Tom Easterday wrote:
> Your instructions didn't work for me (I am on 10.04). I assume it is due to
> the above. Looks like the lines start with "linux" not kernel? See
> attached snipped from Grub.cfg.
Hmm, I tried substituting "linux" for "kernel" and that di
On Apr 4, 2011, at 8:41 AM, Erik Christiansen wrote:
> Caveat: I have made one unverified assumption, and that is that
> /boot/grub/grub.cfg identifies kernel command lines with "kernel" at the
> start of the line, as in menu.lst. If that "ain't so", then either you
> could substitute for "kernel"
On Sun, Apr 03, 2011 at 08:29:33AM -0400, Ed Nisley wrote:
> On Sun, 2011-04-03 at 17:47 +1000, Erik Christiansen wrote:
> > a kosher way to make grub take boot parameters
>
> That's easy: GRUB_CMDLINE_LINUX isolcpus=1
>
> What's hard (at least for me) is putting that parameter *only* on the
> R
On Sun, 2011-04-03 at 17:47 +1000, Erik Christiansen wrote:
> a kosher way to make grub take boot parameters
That's easy: GRUB_CMDLINE_LINUX isolcpus=1
What's hard (at least for me) is putting that parameter *only* on the
RTAI kernel line and leaving the stock kernel lines untouched.
If you can
26 matches
Mail list logo
