Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pdn!tscs!tct!chip
From: chip@tct.uucp (Chip Salzenberg)
Newsgroups: comp.unix.internals
Subject: Re: Ideas for changes to Unix filesystem
Message-ID: <27B98D9F.6756@tct.uucp>
Date: 13 Feb 91 19:03:58 GMT
References: <1991Feb5.223232.21632@odin.diku.dk> <27B18AD8.2F15@tct.uucp> <15455:Feb1010:35:0491@kramden.acf.nyu.edu>
Organization: Teltronics/TCT, Sarasota, FL
Lines: 16

According to brnstnd@kramden.acf.nyu.edu (Dan Bernstein):
>I already have fdunldilink() listed; it only removes a file if it
>has a specified number of hard links, device, and inode, with 0 for
>no restriction.  I think fdunldilink(0,st.st_dev,st.st_ino,path)
>would do the trick after an fstat(fd,&st).

Yes; fdunldilink() [what a name!] can simulate my fdunlink(), but not
vice versa; so fdunldilink() is the better choice.  I would suggest -1
for the "don't care" value, though, since st_dev could easily be zero.

It's too bad that Keith doesn't see the need for these operations.
But then, adding features to BSD never made my life any easier.  :-)
-- 
Chip Salzenberg at Teltronics/TCT     <chip@tct.uucp>, <uunet!pdn!tct!chip>
 "I want to mention that my opinions whether real or not are MY opinions."
             -- the inevitable William "Billy" Steinmetz