Using esh

OK, got a problem here (I’ve asked QNX support, but our service
agreement has lapsed, so I’ll try here until it is re-instated).

To save space and licensing fees, I’m trying to opt to use the embedded
shell (esh) in our product instead of the normal ksh (which /bin/sh is
linked to). So I removed sh and ksh from /bin, and added a sh link to
esh.

Well the sysinit file executes just fine, until I get to the terminal
initialization line for the serial port we want to be able to log in to.
Everything just hangs right there. I commented this out and system went
on its merry way and completed. However, when I manually type the tinit
command (tinit -c “termdef vt100” -T ser4&) the system would hang until
I escaped out with a control C. Also interesting is that I do set tinit
up for several console sessions, but only the main console works.

If I go back to the normal shell, everything works just fine.

Anybody have any experience in this area?

As usual, TIA
Bill Faulkner

“William Faulkner” <wdf@cmed.com> wrote in message
news:3AC257FA.56127357@cmed.com

OK, got a problem here (I’ve asked QNX support, but our service
agreement has lapsed, so I’ll try here until it is re-instated).

To save space and licensing fees, I’m trying to opt to use the embedded
shell (esh) in our product instead of the normal ksh (which /bin/sh is
linked to). So I removed sh and ksh from /bin, and added a sh link to
esh.

Well the sysinit file executes just fine, until I get to the terminal
initialization line for the serial port we want to be able to log in to.
Everything just hangs right there. I commented this out and system went
on its merry way and completed. However, when I manually type the tinit
command (tinit -c “termdef vt100” -T ser4&) the system would hang until
I escaped out with a control C. Also interesting is that I do set tinit
up for several console sessions, but only the main console works.

If I go back to the normal shell, everything works just fine.

Anybody have any experience in this area?

As usual, TIA
Bill Faulkner

I seem to remember requiring both ‘sh’ and ‘ksh’ in the bin directory to
boot up. (something about the sysinit being executed using ksh by default.
Perhaps if you linked ‘ksh’->‘esh’ if might work better… or use the -s
option for sinit).

Carey Duran

Carey Duran wrote:

I seem to remember requiring both ‘sh’ and ‘ksh’ in the bin directory to
boot up. (something about the sysinit being executed using ksh by default.
Perhaps if you linked ‘ksh’->‘esh’ if might work better… or use the -s
option for sinit).

Carey Duran
Actually, sinit requires, by default, /bin/sh, or the -s option. This is

why I have sh linked to esh. Since the sysinit file is being started,
the problem linked with tinit instead.

Thanks
Bill Faulkner

If you put a space before the “&” it should work.

Richard

William Faulkner wrote:

OK, got a problem here (I’ve asked QNX support, but our service
agreement has lapsed, so I’ll try here until it is re-instated).

To save space and licensing fees, I’m trying to opt to use the embedded
shell (esh) in our product instead of the normal ksh (which /bin/sh is
linked to). So I removed sh and ksh from /bin, and added a sh link to
esh.

Well the sysinit file executes just fine, until I get to the terminal
initialization line for the serial port we want to be able to log in to.
Everything just hangs right there. I commented this out and system went
on its merry way and completed. However, when I manually type the tinit
command (tinit -c “termdef vt100” -T ser4&) the system would hang until
I escaped out with a control C. Also interesting is that I do set tinit
up for several console sessions, but only the main console works.

If I go back to the normal shell, everything works just fine.

Anybody have any experience in this area?

As usual, TIA
Bill Faulkner

“Richard R. Kramer” wrote:

If you put a space before the “&” it should work.

Richard

Well that seemed to be it, arghh!

I also had a minor problem with my /dev/ser declaration, but that’s been
solved too.
I am now able to login in to my embedded system via a serial port.

Thanks
Bill Faulkner