tinit, login, serial ports, buildfiles

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

Hello,

I 'm having a bit of trouble with my image and making a login available
over a serial port.

build file contents:
…
devc-ser8250 &
reopen
[+session] login &
…
[type=link] /dev/console=dev/ser1

This all works fine except some formatting of the display
clientside(something to do with LF and CR and tabs. I think).

What I would like to do is start multiple consoles with
dev-con -n2 and have tinit manage the logins and logouts.

I would like to have the first one be a regular console with login already
started and the second on the serial port waiting to start. (when user
presses enter). I have played with tinit and /etc/config/ttys but can’t
seem to get a login prompt. I don’t really need a ‘local console’ but I
need to get tinit listening on the serial port.

2

Are you running photon on startup? The way tinit works is that if you’re
starting photon, it does that first and only after photon exits does it
spawn logins out on ttys and serial ports.

Kris

“Paul Vander Byl” <paul@gandacar.ca> wrote in message
news:aas5ub$ho1$1@inn.qnx.com…

Hello,

I 'm having a bit of trouble with my image and making a login
available
over a serial port.

build file contents:
…
devc-ser8250 &
reopen
[+session] login &
…
[type=link] /dev/console=dev/ser1

This all works fine except some formatting of the display
clientside(something to do with LF and CR and tabs. I think).

What I would like to do is start multiple consoles with
dev-con -n2 and have tinit manage the logins and logouts.

I would like to have the first one be a regular console with login already
started and the second on the serial port waiting to start. (when user
presses enter). I have played with tinit and /etc/config/ttys but can’t
seem to get a login prompt. I don’t really need a ‘local console’ but I
need to get tinit listening on the serial port.

\

3

I am not running photon. Is tinit the right process to use in this
situation or is there something else which will respawn the login process
after it exits?


Thanks,
Paul Vander Byl

4

That’s strange then. What you’re doing should work fine. Below is the
/etc/config/ttys that I use which gives me 4 consoles and a login on the
serial port. I don’t know what else is required though - are you running
devc-con? Is login in your image under /bin? Is your serial driver up?

con1 “/bin/login” qansi-m on
con2 “/bin/login” qansi-m on
con3 “/bin/login” qansi-m on
con4 “/bin/login” qansi-m on
ser1 “/bin/login” qansi-m on

“Paul Vander Byl” <paul@gandacar.ca> wrote in message
news:aau3ec$16l$1@inn.qnx.com…

I am not running photon. Is tinit the right process to use in this
situation or is there something else which will respawn the login process
after it exits?


Thanks,
Paul Vander Byl

5

Thanks for helping Kris,

devc-con is running, the serial driver is running, however login isn’t
under /bin. I’ll give that a try. Is /etc/config/ttys a config file for
tinit or devc-con? If in the ttys file ‘ser1 “/bin/login” qansi-m on’ is
there do I need a link from /dev/con* to /dev/ser* ?


Thanks,
Paul

“Kris Warkentin” <kewarken@qnx.com> wrote in message
news:aau8ub$lu1$1@nntp.qnx.com…

That’s strange then. What you’re doing should work fine. Below is the
/etc/config/ttys that I use which gives me 4 consoles and a login on the
serial port. I don’t know what else is required though - are you running
devc-con? Is login in your image under /bin? Is your serial driver up?

con1 “/bin/login” qansi-m on
con2 “/bin/login” qansi-m on
con3 “/bin/login” qansi-m on
con4 “/bin/login” qansi-m on
ser1 “/bin/login” qansi-m on

“Paul Vander Byl” <> paul@gandacar.ca> > wrote in message
news:aau3ec$16l$> 1@inn.qnx.com> …
I am not running photon. Is tinit the right process to use in this
situation or is there something else which will respawn the login
process
after it exits?


Thanks,
Paul Vander Byl
\

6

tinit uses /etc/config/ttys. It assumes ‘/dev/’ on device paths so all you
need is ‘serX’ or ‘conX’ to get /dev/serX or /dev/conX. I’m not sure what
you would link…all the device special files will be under /dev if your
drivers are running.

cheers,

Kris

“Paul Vander Byl” <paul@gandacar.ca> wrote in message
news:aau95a$5aj$1@inn.qnx.com…

Thanks for helping Kris,

devc-con is running, the serial driver is running, however login isn’t
under /bin. I’ll give that a try. Is /etc/config/ttys a config file for
tinit or devc-con? If in the ttys file ‘ser1 “/bin/login” qansi-m on’ is
there do I need a link from /dev/con* to /dev/ser* ?


Thanks,
Paul

“Kris Warkentin” <> kewarken@qnx.com> > wrote in message
news:aau8ub$lu1$> 1@nntp.qnx.com> …
That’s strange then. What you’re doing should work fine. Below is the
/etc/config/ttys that I use which gives me 4 consoles and a login on the
serial port. I don’t know what else is required though - are you
running
devc-con? Is login in your image under /bin? Is your serial driver up?

con1 “/bin/login” qansi-m on
con2 “/bin/login” qansi-m on
con3 “/bin/login” qansi-m on
con4 “/bin/login” qansi-m on
ser1 “/bin/login” qansi-m on

“Paul Vander Byl” <> paul@gandacar.ca> > wrote in message
news:aau3ec$16l$> 1@inn.qnx.com> …
I am not running photon. Is tinit the right process to use in this
situation or is there something else which will respawn the login
process
after it exits?


Thanks,
Paul Vander Byl


\