Hi all,
I have a problem with QNX 4.25 and Photon 1.14.
I try to start photon from sysinit. The photon login appears, but I have
no keyboard to login.
When I login on QNX an start photon with “ph”, all is ok.
Mit freundlichen Grüßen
Ulrich Speidel
SYS GmbH, Freiburg
software & engineering
Rieselfeldallee 16
79111 Freiburg
Tel.: 0761/ 45294-22
Fax.: 0761/ 45294-45
Hi,
You need to start the input manager after starting the photon server.
What command(s) are you executing from your sysinit file?
-Liam Power.
“Ulrich Speidel” <ulrich.speidel@sys-gmbh.de> schrieb im Newsbeitrag
news:3ACC1117.8036C396@sys-gmbh.de…
Hi all,
I have a problem with QNX 4.25 and Photon 1.14.I try to start photon from sysinit. The photon login appears, but I have
no keyboard to login.When I login on QNX an start photon with “ph”, all is ok.
Who can help me??
Mit freundlichen Grüßen
Ulrich Speidel
SYS GmbH, Freiburg
software & engineeringRieselfeldallee 16
79111 FreiburgTel.: 0761/ 45294-22
Fax.: 0761/ 45294-45
Take a look at the “ph” script. phlogin will be called if no “LOGNAME” set.
You can also start photon, if you do everything by your own.
Sascha Morgenstern
BitCtrl Systems GmbH
Weißenfelser Straße 67
Germany - 04229 Leipzig
Phon. +49 341 490 670
FAX. +49 341 490 67 15
eMail: sascha@bitctrl.de
WWW: http://www.bitctrl.de
Ulrich Speidel <ulrich.speidel@sys-gmbh.de> schrieb in im Newsbeitrag:
3ACC1117.8036C396@sys-gmbh.de…
Hi all,
I have a problem with QNX 4.25 and Photon 1.14.I try to start photon from sysinit. The photon login appears, but I have
no keyboard to login.When I login on QNX an start photon with “ph”, all is ok.
Who can help me??
Mit freundlichen Grüßen
Ulrich Speidel
SYS GmbH, Freiburg
software & engineeringRieselfeldallee 16
79111 FreiburgTel.: 0761/ 45294-22
Fax.: 0761/ 45294-45
Set the export variable LOGNAME
export LOGNAME=[user]
in the sysinit before you run photon. This might only work if the user has no password. But maybe
there is a PASSWORD type export variable you could set also.
Chris Nasr
cnasr[at]mechtronix[dot]ca
Mechtronix Systems Inc.
On Fri, 06 Apr 2001 14:56:36 -0400, Chris Nasr <cnasr@mechtronix.ca>
wrote:
Set the export variable LOGNAME
export LOGNAME=[user]
in the sysinit before you run photon. This might only work if the user has no password. But maybe
there is a PASSWORD type export variable you could set also.
Chris Nasr
cnasr[at]mechtronix[dot]ca
Mechtronix Systems Inc.
The only problem is that while this skips the login, you haven’t
actually logged in as this user…i.e. your still running as root…
What I do to avoid this is change tinit in the sysinit.X file to do a
forced login on the first terminal. then all the photon startup is
done by the user’s .profile. – including any “extra” startup you
require.
If you make sure the altsysinit does the normal tinit, you can easily
go back and forth for testing…
i.e. in sysinit and a user called “product” defined…
tinit -T /dev/con* -c “login -p -f product” -t /dev/con1 &
then user “product”'s .profile looks like…
if test $PHOTON then
echo “starting support shell - already in photon”
else
export PHPDM_DISABLE=1
export PHWMOPTS=-KTS
ph
fi
----- end of script
Note that we can set all of the PH* environment variables here and
then run ph to start… Personally I fnd this method MUCH more flexible
than putting ph or ph.boot in the sysinit…
-Bill
That actually makes more sense Bill, I think I will use it myself. Thanks.
Chris
“William M. Derby Jr.” wrote:
On Fri, 06 Apr 2001 14:56:36 -0400, Chris Nasr <> cnasr@mechtronix.ca
wrote:Set the export variable LOGNAME
export LOGNAME=[user]
in the sysinit before you run photon. This might only work if the user has no password. But maybe
there is a PASSWORD type export variable you could set also.
Chris Nasr
cnasr[at]mechtronix[dot]ca
Mechtronix Systems Inc.The only problem is that while this skips the login, you haven’t
actually logged in as this user…i.e. your still running as root…What I do to avoid this is change tinit in the sysinit.X file to do a
forced login on the first terminal. then all the photon startup is
done by the user’s .profile. – including any “extra” startup you
require.If you make sure the altsysinit does the normal tinit, you can easily
go back and forth for testing…i.e. in sysinit and a user called “product” defined…
tinit -T /dev/con* -c “login -p -f product” -t /dev/con1 &
then user “product”'s .profile looks like…
if test $PHOTON then
echo “starting support shell - already in photon”
else
export PHPDM_DISABLE=1
export PHWMOPTS=-KTS
ph
fi----- end of script
Note that we can set all of the PH* environment variables here and
then run ph to start… Personally I fnd this method MUCH more flexible
than putting ph or ph.boot in the sysinit…-Bill
–
Chris Nasr
cnasr[at]mechtronix[dot]ca
Mechtronix Systems Inc.