[lkml]   [2011]   [May]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: UNIX Compatibility
On Thu, 26 May 2011 13:30:39 +0200, Bernd Petrovitsch said:

> Or take the "unlink a directory gives EPERM" example: why is it
> specified with an errno that indicates that the user is not allowed to
> remove it (and not that the sys-call is the wrong one).

Because on some old Unix's, it wasn't the wrong syscall...


Unlinking a directory is restricted to the superuser in many historical
implementations for reasons given in link() (see also rename()).

I've encountered at least one system (admittedly 20+ years ago), where
unlink("./") actually did work. Took me a while to correlate the weird fsck's
at reboots to the program that tried to remove './$A' when $A was unset...

[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2011-05-26 14:11    [W:0.098 / U:1.556 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site