Does PhinX run under Linux?

Hello.

I was wondering if the Phinx product was capable of running under
Linux. The Phindows product allows someone from Windows to access QNX4,
so I thought that the PhinX product would allow someone from a Unix or
Linux X-Windows platform to access QNX. I am not sure if this is
correct.

If someone would inform me about whether PhinX can do this or if there
is such a product, then I would be interested.

Thanks in advance.

Rodney Lott

Phinx (photon in X) is used to project a photon environment into an
X-windows system, hence phinx itself runs on a qnx4 box. So from a
remote box running X-windows you could telnet into the qnx box, then
run phinx, directing the output back to your local box.

ron


I was wondering if the Phinx product was capable of running under
Linux. The Phindows product allows someone from Windows to access QNX4,
so I thought that the PhinX product would allow someone from a Unix or
Linux X-Windows platform to access QNX. I am not sure if this is
correct.

If someone would inform me about whether PhinX can do this or if there
is such a product, then I would be interested.

Thanks in advance.

Rodney Lott

Thanks for replying, Ron.

This sounds like it is something that will work for me, but I have a few
more questions:

Would you be able to give me some advice as to how I would redirect the
output back to the Linux box?
Would the help that comes with the Phinx product give examples of how to
do this?

And would that mean that I would only need one Phinx product installed
on my QNX box?
Would multiple users be able to access this from their Linux X-Windows
platform?

Thanks a lot.

Rodney Lott

Ronald Stam wrote:

Phinx (photon in X) is used to project a photon environment into an
X-windows system, hence phinx itself runs on a qnx4 box. So from a
remote box running X-windows you could telnet into the qnx box, then
run phinx, directing the output back to your local box.

ron

Rodney Lott <rod@fuelcelltechnologies.ca> wrote:

Thanks for replying, Ron.

This sounds like it is something that will work for me, but I have a few
more questions:

Would you be able to give me some advice as to how I would redirect the
output back to the Linux box?

The same way you export any X application – either you set the
DISPLAY environment variable or you use the "-display " command
line option. Display is general “host:server[.screen]”, usually
something like “10.0.0.1:0.0” or “myhost.mynet:0.0”.

Would the help that comes with the Phinx product give examples of how to
do this?

I just flipped through them, not very well.

You’d need a Photon session run on the QNX node, and you probably don’t
want it to be the “general” photon session that actually controls the
display on that node. So, you’ll want to start Photon seperately, then
start phinx. Probably a little script that does something like:

nohup Photon -N/dev/phinx &
nohup phinx -display linuxhost.localnet:0.0 -n/dev/phinx &

And would that mean that I would only need one Phinx product installed
on my QNX box?

Yes.

Would multiple users be able to access this from their Linux X-Windows
platform?

Yes, each should probably start their own Photon session with a different
name, though:

Bob’s shell script:

nohup Photon -N/dev/phbob &
nohup phinx -display bobhost.localnet:0.0 -n/dev/phbob &

Joe’s shell script:

nohup Photon -N/dev/phjoe &
nohup phinx -display joehost.localnet:0.0 -n/dev/phjoe &

-David

Thanks, guys.

You have been most helpful.

Regards,

Rodney

David Gibbs wrote:

Rodney Lott <> rod@fuelcelltechnologies.ca> > wrote:
Thanks for replying, Ron.

This sounds like it is something that will work for me, but I have a few
more questions:

Would you be able to give me some advice as to how I would redirect the
output back to the Linux box?

The same way you export any X application – either you set the
DISPLAY environment variable or you use the "-display " command
line option. Display is general “host:server[.screen]”, usually
something like “10.0.0.1:0.0” or “myhost.mynet:0.0”.

Would the help that comes with the Phinx product give examples of how to
do this?

I just flipped through them, not very well.

You’d need a Photon session run on the QNX node, and you probably don’t
want it to be the “general” photon session that actually controls the
display on that node. So, you’ll want to start Photon seperately, then
start phinx. Probably a little script that does something like:

nohup Photon -N/dev/phinx &
nohup phinx -display linuxhost.localnet:0.0 -n/dev/phinx &

And would that mean that I would only need one Phinx product installed
on my QNX box?

Yes.

Would multiple users be able to access this from their Linux X-Windows
platform?

Yes, each should probably start their own Photon session with a different
name, though:

Bob’s shell script:

nohup Photon -N/dev/phbob &
nohup phinx -display bobhost.localnet:0.0 -n/dev/phbob &

Joe’s shell script:

nohup Photon -N/dev/phjoe &
nohup phinx -display joehost.localnet:0.0 -n/dev/phjoe &

-David