Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!rbj From: rbj@uunet.UU.NET (Root Boy Jim) Newsgroups: comp.unix.wizards Subject: Re: POSIX bashing Message-ID: <129267@uunet.UU.NET> Date: 16 Apr 91 18:32:31 GMT References: <111@imsdx3.UUCP> Organization: UUNET Communications Services, Falls Church, VA Lines: 18 In article meissner@osf.org (Michael Meissner) writes: >In article <111@imsdx3.UUCP> chris@imsdx3.UUCP (Chris Ott) writes: > >| 1) Symbolic links. C'mon guys, how hard can this be to implement? > >I was working with a UNIX vendor that did this, and it was painful to >get all of the commands modified to support symlinks correctly. I can see that it might cause *some* pain, but it should be worth it. I hope their definition of "correct" was correct. Basicly, any command that deals with the file system as a tree structure (dump, tar, rm, etc) should treat symlinks specially (not follow them), while most programs should treat them as hard links. One good way to identify these programs would be to grep for 'stat('. -- [rbj@uunet 1] stty sane unknown mode: sane