Viewing /dev/console

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
1

How can I view the console, ie any startup task info and any output that
goes to /dev/console? I used to be able to ditto into it in QNX 4 but can’t
find an equivalent function in QNX 6. I’ve searched the qdn and usenet but
no luck.

TIA,

Jim

2

Anyone? Bueller?


“Jim Lambert” <jlambert@futurex.com> wrote in message
news:9vbqgu$n0k$1@inn.qnx.com…

How can I view the console, ie any startup task info and any output that
goes to /dev/console? I used to be able to ditto into it in QNX 4 but
can’t
find an equivalent function in QNX 6. I’ve searched the qdn and usenet
but
no luck.

TIA,

Jim

3

“Jim Lambert” <jlambert@futurex.com> wrote in message
news:a0ohvp$ihn$1@inn.qnx.com…

Anyone? Bueller?

“Jim Lambert” <> jlambert@futurex.com> > wrote in message
news:9vbqgu$n0k$> 1@inn.qnx.com> …
How can I view the console, ie any startup task info and any output that
goes to /dev/console? I used to be able to ditto into it in QNX 4 but
can’t
find an equivalent function in QNX 6. I’ve searched the qdn and usenet
but
no luck.

You can make a procmgr link for /dev/console pointing to whatever terminal
(or device) you wish (ie. ln -sP /dev/ttyp0 /dev/console). This would cause
all data directed to /dev/console to appear on your ttyp0. Just rm the
symlink when you wish to stop (this could be put into a shell script to
automate) and you’ll uncover the previous holder of that namespace.

-Adam

4

s there an equivlent function to QNX4’s device_console()?

–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net


“Core OS Product Group” <os@qnx.com> wrote in message
news:a0vhga$8i3$1@nntp.qnx.com…

“Jim Lambert” <> jlambert@futurex.com> > wrote in message
news:a0ohvp$ihn$> 1@inn.qnx.com> …
Anyone? Bueller?

“Jim Lambert” <> jlambert@futurex.com> > wrote in message
news:9vbqgu$n0k$> 1@inn.qnx.com> …
How can I view the console, ie any startup task info and any output
that
goes to /dev/console? I used to be able to ditto into it in QNX 4 but
can’t
find an equivalent function in QNX 6. I’ve searched the qdn and
usenet
but
no luck.

You can make a procmgr link for /dev/console pointing to whatever terminal
(or device) you wish (ie. ln -sP /dev/ttyp0 /dev/console). This would
cause
all data directed to /dev/console to appear on your ttyp0. Just rm the
symlink when you wish to stop (this could be put into a shell script to
automate) and you’ll uncover the previous holder of that namespace.

-Adam

5

“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:a0vom4$hlk$2@inn.qnx.com…

s there an equivlent function to QNX4’s device_console()?

No, the QNX4 control functions (like console_read() …) aren’t around
either.

-Adam

6

OK. Here’s my opinion just one time then I’ll quietly disappear.

I think that RTP is seriously ignoring text consoles and many, many
applications do not require graphics capabilities but do require some
textual status output.

Features that I think should be ported from V4 are:

  • 50 line mode
  • the ability to software read a screen that was required for prtsc and
    ditto to work

In addition, text consoles seem much slower in V6 then in V4.
Also I would like to have much more than the 9 or 10 consoles that V6 or V4
supported. It seems to me that the only cost of additional consoles was
memory.

At the very least add memory to ptys so that an application can read a pty
screen. Perhaps that can be done just by implementing an lseek() on a
/dev/pty.

Please don’t ignore text consoles. They are very useful.

–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net


“Core OS Product Group” <os@qnx.com> wrote in message
news:a11su8$pg$1@nntp.qnx.com…

“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:a0vom4$hlk$> 2@inn.qnx.com> …
s there an equivlent function to QNX4’s device_console()?

No, the QNX4 control functions (like console_read() …) aren’t around
either.

-Adam

7

I would like to see this supported as well

Previously, Bill Caroselli wrote in qdn.public.qnxrtp.os:

OK. Here’s my opinion just one time then I’ll quietly disappear.

I think that RTP is seriously ignoring text consoles and many, many
applications do not require graphics capabilities but do require some
textual status output.

Features that I think should be ported from V4 are:

  • 50 line mode
  • the ability to software read a screen that was required for prtsc and
    ditto to work

In addition, text consoles seem much slower in V6 then in V4.
Also I would like to have much more than the 9 or 10 consoles that V6 or V4
supported. It seems to me that the only cost of additional consoles was
memory.

At the very least add memory to ptys so that an application can read a pty
screen. Perhaps that can be done just by implementing an lseek() on a
/dev/pty.

Please don’t ignore text consoles. They are very useful.

–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net


“Core OS Product Group” <> os@qnx.com> > wrote in message
news:a11su8$pg$> 1@nntp.qnx.com> …
“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:a0vom4$hlk$> 2@inn.qnx.com> …
s there an equivlent function to QNX4’s device_console()?

No, the QNX4 control functions (like console_read() …) aren’t around
either.

-Adam

\

8

Me too. (especially ditto)

Pavol Kycina

“Ian Cannon” <ianc@tecom.com.au> wrote in message
news:Voyager.020104082607.14191A@aresnode2.tecom.com.au…

I would like to see this supported as well

Previously, Bill Caroselli wrote in qdn.public.qnxrtp.os:
OK. Here’s my opinion just one time then I’ll quietly disappear.

I think that RTP is seriously ignoring text consoles and many, many
applications do not require graphics capabilities but do require some
textual status output.

Features that I think should be ported from V4 are:

  • 50 line mode
  • the ability to software read a screen that was required for prtsc and
    ditto to work

In addition, text consoles seem much slower in V6 then in V4.
Also I would like to have much more than the 9 or 10 consoles that V6 or
V4
supported. It seems to me that the only cost of additional consoles was
memory.

At the very least add memory to ptys so that an application can read a
pty
screen. Perhaps that can be done just by implementing an lseek() on a
/dev/pty.

Please don’t ignore text consoles. They are very useful.

–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net


“Core OS Product Group” <> os@qnx.com> > wrote in message
news:a11su8$pg$> 1@nntp.qnx.com> …
“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:a0vom4$hlk$> 2@inn.qnx.com> …
s there an equivlent function to QNX4’s device_console()?

No, the QNX4 control functions (like console_read() …) aren’t around
either.

-Adam


\