Subject: Re: CRITICAL ** Holes in default cron jobs ** CRITICAL
To: None <tech-kern@NetBSD.ORG>
From: Grey Wolf <>
List: tech-kern
Date: 12/30/1996 18:53:41
Neither here nor there, but:

Ty Sarna sez:
 * that still leaves the issue of symlinks, and doesn't solve the unlink()
 * problem. funlink()? (or does that create a link that's neither hard or
 * soft, but that is fun? :->). funlink() would have the same semantic
 * difficulties you pointed out above (which directory enrey do I unlink?)

All of them, although this presents some interesting anomalies. :-)

Seriously, I have always thought that there should be an funlink()
command which would take a file descriptor and unlink the inode
associated therewith.  It would really mess up the structure, though,
and in the case of files with more than one link it would _require_
that fsck be run.

"You are in a maze of kludgey little hacks, all alike..."