Login files

I want to create small QNX RTP that uses less disk space, without Photon and
with specific hardware drivers and libraries only. But I want to have login
input at the end of the boot process. Now my .boot file log root directly
without prompt for login. My question is what I have to put in to my image
file to get login prompt for user name and password? Which files and
libraries I have to include and do I need set some variables, too?

TIA

Adam

“Adam Zembala” <adam.zembala@opal-rt.com> wrote in message
news:9rpq73$8jo$1@inn.qnx.com

I want to create small QNX RTP that uses less disk space, without Photon
and
with specific hardware drivers and libraries only. But I want to have
login
input at the end of the boot process. Now my .boot file log root directly
without prompt for login. My question is what I have to put in to my image
file to get login prompt for user name and password? Which files and
libraries I have to include and do I need set some variables, too?

You’ll want to include a shell (ksh or esh) and the program login. Check
out the help for login for more details (as you’ll need the password file
/etc/passwd, the shadow password file etc).

-Adam

Hi,
instead of [+session] sh, use [+session] login in ur build file.
You’ll need to .profile, passwd, shadow(not sure abt opasswd & oshadow) &
shells in /etc


“Adam Zembala” <adam.zembala@opal-rt.com> wrote in message
news:9rpq73$8jo$1@inn.qnx.com

I want to create small QNX RTP that uses less disk space, without Photon
and
with specific hardware drivers and libraries only. But I want to have
login
input at the end of the boot process. Now my .boot file log root directly
without prompt for login. My question is what I have to put in to my image
file to get login prompt for user name and password? Which files and
libraries I have to include and do I need set some variables, too?

TIA

Adam

I suggest that you get your logins working first before you build mandatory
logins into your boot image. I.E. If you can’t login after a reboot, then
you can’t login in after a reboot, to fix it.


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


“Wen” <xiaowen@axs.com.sg> wrote in message news:9rtcd0$fvq$1@inn.qnx.com

Hi,
instead of [+session] sh, use [+session] login in ur build file.
You’ll need to .profile, passwd, shadow(not sure abt opasswd & oshadow) &
shells in /etc

Thanks for your advices, it is already working. There is the way I did it:

dev-con -n2 &
reopen /dev/con2 &
[+session] login &
reopen /dev/con1
[+session] login

Adam

Hi Adam

I haven’t tried this but I think that by not using tinit, when someone logs
out, then you won’t get another login prompt.

Try to use tinit instead.


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


“Adam Zembala” <adam.zembala@opal-rt.com> wrote in message
news:9ruqr8$jpq$1@inn.qnx.com

Thanks for your advices, it is already working. There is the way I did it:

dev-con -n2 &
reopen /dev/con2 &
[+session] login &
reopen /dev/con1
[+session] login

Adam
\

You’re right Bill, it works much better with tinit, thanks.

Adam


“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:9s1qh3$frp$1@inn.qnx.com

Hi Adam

I haven’t tried this but I think that by not using tinit, when someone
logs
out, then you won’t get another login prompt.

Try to use tinit instead.


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