What happened to /home?

[Giorgos Keramidas]

On Wed, 23 Dec 2009 23:11:12 -0800, Charlie Kester <corky1951 at comcast.net> wrote:
> On Wed 23 Dec 2009 at 22:33:20 PST Giorgos Keramidas wrote:
>>> I can still login as regular user, and when I run 'pwd -P' the output is
>>> / and then it goes back to the prompt.  Output of 'ls -ld /home is:
>>>
>>> lrwxr-xr-x  1 root wheel 8 Dec 18 12:08 /home -> usr/home
>>
>> That's your problem right there.  /home does not point to the absolute
>> path of '/usr/home' but to a *relative* path starting at whatever
>> happens to be your current directory when you access '/home'.
>
> Are you sure about that?

On Thu, 24 Dec 2009 08:57:11 +0100, Erik Trulsson <ertr1013 at student.uu.se> wrote:
> Wrong. Relative paths in symlinks start at the symlink is in, not the
> current directory. I.e. that the symlink is relative should not be a
> problem.  (Under AmigaOS relative symlinks worked as you describe, which
> made them a PITA and fairly useless, but under Unix relative symlinks have a
> more sane behaviour.)

On Thu, 24 Dec 2009 10:12:21 +0100, Polytropon <freebsd at edvax.de> wrote:
> That's quite strange... I have /home@ -> export/home and /export lives
> on another partition. But I have no problems accessing files as
> /home/poly/some/dir/some/file from wherever I am.  As far as I
> understood, relative symlinks prefix their respective targets always
> with their own location, so /home + export/home gives /export/home.

You are all right, of course.  I shouldn't post moments before jumping
on a bus without testing.  Something else is the real problem.