symbolic links over qnet

This may be expected behavior, but say you have a symbolic link on one qnx
file system on one machine (call it machine ‘a’) such as:

home->/fs/hd0-qnx4-2/home

and you have the same thing on machine ‘b’

If on machine ‘b’ you type:

ls /net/a/home

that will resolve to the /fs/hd0-qnx4-2/home on machine ‘b’, not machine
‘a’.

This is understandable…and clear to me why this happens…just caught me
off guard. I couldn’t figure out why the files I was copying weren’t being
put where I wanted them. :slight_smile:

Now my link is:
home->fs/hd0-qnx4-2/home

Is this how qnx4’s FLEET would have handled it?

Just some musings,
Kevin

Kevin Stallard <kevin@ffflyingrobots.com> wrote:

This may be expected behavior, but say you have a symbolic link on one qnx
file system on one machine (call it machine ‘a’) such as:

home->/fs/hd0-qnx4-2/home

and you have the same thing on machine ‘b’

If on machine ‘b’ you type:

ls /net/a/home

that will resolve to the /fs/hd0-qnx4-2/home on machine ‘b’, not machine
‘a’.

This is understandable…and clear to me why this happens…just caught me
off guard. I couldn’t figure out why the files I was copying weren’t being
put where I wanted them. > :slight_smile:

Now my link is:
home->fs/hd0-qnx4-2/home

Is this how qnx4’s FLEET would have handled it?

Yes. The leading slash always represnt your root of local machine.
That’s why you need to link relative path, instead of absolute path,
if you want to access cross QNET.

-xtang

Kevin Stallard <kevin@ffflyingrobots.com> wrote in message
news:ap4ebf$527$1@inn.qnx.com

Is this how qnx4’s FLEET would have handled it?

Nope, QNX4 has the node numer in the symbolic link.

\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

Kevin Stallard <kevin@ffflyingrobots.com> wrote:

This may be expected behavior, but say you have a symbolic link on one qnx
file system on one machine (call it machine ‘a’) such as:

home->/fs/hd0-qnx4-2/home

and you have the same thing on machine ‘b’

If on machine ‘b’ you type:

ls /net/a/home

that will resolve to the /fs/hd0-qnx4-2/home on machine ‘b’, not machine
‘a’.

This is understandable…and clear to me why this happens…just caught me
off guard. I couldn’t figure out why the files I was copying weren’t being
put where I wanted them. > :slight_smile:

Now my link is:
home->fs/hd0-qnx4-2/home

Is this how qnx4’s FLEET would have handled it?

Yes and no. There was a great debate over whether symbolic links
should be resolved relative to where they lived, or relative to the
network root of the person (process) looking at them.

If I remember correctly, the choice on the behaviour actually changed
at one point – from doing it one way, to doing it the other.

To be careful under QNX4, one usually did something like:

home->//5/fs/hd0-qnx4-2/home

-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

It is always interesting to hear about the history of decisions in a design.

You know, this has some relation to Robert Krten’s QNET Proxy idea (see
advocacy). If the request to open a file was resolved on the node where the
filename existed, it would behave differently wouldn’t it?.

Just my musings, once again.

Regards,

Kevin

“David Gibbs” <dagibbs@qnx.com> wrote in message
news:ap6aqu$3hc$1@nntp.qnx.com

Kevin Stallard <> kevin@ffflyingrobots.com> > wrote:
This may be expected behavior, but say you have a symbolic link on one
qnx
file system on one machine (call it machine ‘a’) such as:

home->/fs/hd0-qnx4-2/home

and you have the same thing on machine ‘b’

If on machine ‘b’ you type:

ls /net/a/home

that will resolve to the /fs/hd0-qnx4-2/home on machine ‘b’, not machine
‘a’.

This is understandable…and clear to me why this happens…just caught
me
off guard. I couldn’t figure out why the files I was copying weren’t
being
put where I wanted them. > :slight_smile:

Now my link is:
home->fs/hd0-qnx4-2/home

Is this how qnx4’s FLEET would have handled it?

Yes and no. There was a great debate over whether symbolic links
should be resolved relative to where they lived, or relative to the
network root of the person (process) looking at them.

If I remember correctly, the choice on the behaviour actually changed
at one point – from doing it one way, to doing it the other.

To be careful under QNX4, one usually did something like:

home->//5/fs/hd0-qnx4-2/home

-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.