Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!not-for-mail From: sef@Kithrup.COM (Sean Eric Fagan) Newsgroups: comp.os.386bsd.development Subject: Re: A challenge to all true kernel hackers - conditional symlinks. Date: 14 Mar 1993 14:45:08 -0800 Organization: Kithrup Enterprises, Ltd. Lines: 14 Sender: sef@ftp.UU.NET Message-ID: <1o0chkINN1s5@ftp.UU.NET> References: <C3ow4H.FID@BitBlocks.com> <C3qzGI.38q@sugar.neosoft.com> <1nqnchINNerd@life.ai.mit.edu> <C3v4MD.LFE@sugar.neosoft.com> NNTP-Posting-Host: ftp.uu.net In article <C3v4MD.LFE@sugar.neosoft.com> peter@NeoSoft.com (Peter da Silva) writes: >> > ln -s /usr/i18n//lang/docs /usr/docs >Why? These file names are *only* in symbolic links, which programs should >treat as textual substitutions. They're not legal file names (see POSIX >1003.1) so there's no conflict. 1003.1 says that, with the exception of the initial slash, any set of two or more slashes is to be treated as a single slash. For the initial slash, three or more are to be treated as a single slash, and two initial slashes is allowed to be "special" -- but it must be implementation defined, if so. "/usr/i18n//lang/docs" is a perfectly valid POSIX filename.