From:	Keetnet AT wilmington DOT net (Keet)
Subject:	Re: rename() in B18..
14 Jun 1997 09:40:04 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<2.2.32.19970614151628.0068c968.cygnus.gnu-win32@wilmington.net>
Mime-Version:	1.0
X-Sender:	keetnet AT wilmington DOT net
X-Mailer:	Windows Eudora Pro Version 2.2 (32)
X-Priority:	1 (Highest)
Original-To:	Michael Hirmke <mh AT minimike DOT franken DOT de>, gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

>
>You try to unlink open files !
>

Under UNIX, it's perfectly legal to unlink a file BEFORE it is closed,
because UNIX only deletes the filename, and not the inode. This is one of
the incompatibility problems between UNIX and Windows. Under a FAT based
system you can't unlink a file because the filename IS the file. What I
suspect, is that for the sake of compatibility Cygwin is silently failing
when attempting to unlink an open file, and is thus never deleted. It seems
that there is a large problem in that area. Under UNIX there are a large
number of programs that really do rely on the ability to unlink() a file
before it is closed. Any more ideas on the matter? (other than loosing some
UNIX compatibility and having to rewrite the source that does not close a
file before it is unlinked? which is, perfectly legal in UNIX).

- Greg Neujahr
  Foxbird / Keet
  keetnet AT wilmington DOT net


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -