home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!darwin.sura.net!jvnc.net!yale.edu!ira.uka.de!smurf.sub.org!news
- From: urlichs@smurf.sub.org (Matthias Urlichs)
- Newsgroups: comp.unix.programmer
- Subject: Re: ln vs. ln -s
- Date: 28 Jul 1992 22:58:32 +0200
- Organization: University of Karlsruhe, FRG
- Lines: 21
- Message-ID: <154cdoINNqt6@smurf.smurf.sub.org>
- References: <82033@netnews.upenn.edu> <13aea6INN7ce@early-bird.think.com>
- NNTP-Posting-Host: 127.0.0.1
-
- In comp.unix.programmer, article <13aea6INN7ce@early-bird.think.com>,
- barmar@think.com (Barry Margolin) writes:
- <
- < However, I've seen "file system full" errors result in the system
- < call failing after having created the symlink but before filling in the
- < target pathname (a symlink is implemented as a file whose contents are the
- < target pathname).
- <
- Same here. These symlinks point to the current directory instead of the
- destination directory or file.
-
- Needless to say, on some systems "ln" (or the kernel) either doesn't check
- if the filling-in part succeeds or doesn't bother to remove the spurious
- empty link. Fun.
-
- --
- "I like a man who grins when he fights."
- - Winston Churchill
- --
- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\
- Humboldtstrasse 7 -- 7500 Karlsruhe 1 -- Germany -- +49-721-9612521 \o)/
-