Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.Hawaii.Edu!ames!hookup!swrinde!pipex!uknet!festival!edcogsci!richard
From: richard@cogsci.ed.ac.uk (Richard Tobin)
Subject: Rock Ridge vs FreeBSD 1.0
Message-ID: <Cq3LBH.65F@cogsci.ed.ac.uk>
Organization: HCRC, University of Edinburgh
Date: Fri, 20 May 1994 11:02:05 GMT
Lines: 44
It appears that Rock Ridge symbolic links do not work correctly under
FreeBSD 1.0. All the links on a CD seem to have the same inode
number, and the behaviour of the system seems to suggest that it's
sometime using incorrect cached links:
bash# ls -li d*16
843 lrwxrwxrwx 1 15144 0 Apr 26 03:17 dan16 -> mul06/mda06
843 lrwxrwxrwx 1 15144 0 Apr 26 03:17 dut16 -> mul06/mdu06
bash# ls mul06/mda06/*.edt
mul06/mda06/dan16.edt
bash# ls mul06/mdu06/*.edt
mul06/mdu06/dut16.edt
All the above are correct, except that both links have the same inode
number.
bash# ls dan16/*.edt
dan16/dan16.edt
Again, that is what you'd expect. But this is wrong:
bash# ls dut16/*.edt
dut16/dan16.edt
^^^^^^^^^ should be dut16.edt
It seems to be following the dan16 link instead of the dut16 one.
Note this is context sensitive; if I'd done the last two ls the
other way round, the dut16 one would have worked and the dan16 one
failed. Here's another failure:
bash# ls d*16/*.edt
ls: dut16/dut16.edt: No such file or directory
dan16/dan16.edt
Similar problems seem to exist in SunOS 4.1 and NetBSD 0.9, but
NetBSD current (from around February) seems to be fixed.
-- Richard
--
Richard Tobin, HCRC, Edinburgh University R.Tobin@ed.ac.uk
"Your monkey has got it right, sir." - HHGTTG