Re: [Emc-developers] halrun messages

2012-11-20 Thread andy pugh
On 19 November 2012 21:07, John Kasunich wrote: > The "tail -f" thing is significantly more elegant - you only > have to do it once, and the messages automatically > appear in the terminal as the kernel modules produce > them. I wonder if halrun could display that data? (possibly only loadrt nee

Re: [Emc-developers] halrun messages

2012-11-19 Thread andy pugh
On 19 November 2012 22:28, Charles Steinkuehler wrote: > ...or as indicated above, you can build one of the user-mode flavors I can, but that doesn't help anyone else…. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto --

Re: [Emc-developers] halrun messages

2012-11-19 Thread Sebastian Kuzminsky
On 11/19/12 15:28 , Charles Steinkuehler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 11/19/2012 1:53 PM, Sebastian Kuzminsky wrote: >> On 11/19/12 12:49 , andy pugh wrote: >>> Is there any way to have the messages from a HAL realtime >>> component print to the halrun prompt (ie

Re: [Emc-developers] halrun messages

2012-11-19 Thread Charles Steinkuehler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/19/2012 1:53 PM, Sebastian Kuzminsky wrote: > On 11/19/12 12:49 , andy pugh wrote: >> Is there any way to have the messages from a HAL realtime >> component print to the halrun prompt (ie stdio) rather than to >> dmesg? >> >> I have a command-li

Re: [Emc-developers] halrun messages

2012-11-19 Thread John Kasunich
On Mon, Nov 19, 2012, at 03:27 PM, andy pugh wrote: > On 19 November 2012 20:19, Sebastian Kuzminsky wrote: > > > "tail -f /var/log/kern.log" in an adjacent xterm? > > I just keep a second terminal open, and type "dmesg" a lot, but it's > not elegant. > The "tail -f" thing is significantly m

Re: [Emc-developers] halrun messages

2012-11-19 Thread andy pugh
On 19 November 2012 20:19, Sebastian Kuzminsky wrote: > "tail -f /var/log/kern.log" in an adjacent xterm? I just keep a second terminal open, and type "dmesg" a lot, but it's not elegant. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto --

Re: [Emc-developers] halrun messages

2012-11-19 Thread Sebastian Kuzminsky
On 11/19/12 13:15 , andy pugh wrote: > On 19 November 2012 19:53, Sebastian Kuzminsky wrote: > >> Realtime components in the RTAI world run in the kernel, so there is no >> stdout for them to print to. > I may be misinterpreting > http://elinux.org/Debugging_by_printing#Log_Levels > When it talks

Re: [Emc-developers] halrun messages

2012-11-19 Thread andy pugh
On 19 November 2012 19:53, Sebastian Kuzminsky wrote: > Realtime components in the RTAI world run in the kernel, so there is no > stdout for them to print to. I may be misinterpreting http://elinux.org/Debugging_by_printing#Log_Levels When it talks about printing to "the console" -- atp If you

Re: [Emc-developers] halrun messages

2012-11-19 Thread Sebastian Kuzminsky
On 11/19/12 12:49 , andy pugh wrote: > Is there any way to have the messages from a HAL realtime component > print to the halrun prompt (ie stdio) rather than to dmesg? > > I have a command-line (only) HAL component that could do with being a > little more interactive. > Realtime components in the

Re: [Emc-developers] halrun messages

2012-11-19 Thread John Kasunich
On Mon, Nov 19, 2012, at 02:49 PM, andy pugh wrote: > Is there any way to have the messages from a HAL realtime component > print to the halrun prompt (ie stdio) rather than to dmesg? Probably not. At least for now (before LCNC3), realtime components are kernel modules. They have no access to