From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1EBcDW-000095-99
	for qemu-devel@nongnu.org; Sat, 03 Sep 2005 13:54:14 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1EBcDR-000062-IU
	for qemu-devel@nongnu.org; Sat, 03 Sep 2005 13:54:10 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1EBcDQ-0008Ti-FA
	for qemu-devel@nongnu.org; Sat, 03 Sep 2005 13:54:08 -0400
Received: from [64.233.184.196] (helo=wproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1EBbyl-0006Xy-Ns
	for qemu-devel@nongnu.org; Sat, 03 Sep 2005 13:38:59 -0400
Received: by wproxy.gmail.com with SMTP id i35so483888wra
	for <qemu-devel@nongnu.org>; Sat, 03 Sep 2005 10:35:29 -0700 (PDT)
Message-ID: <23bcb87005090310353439360e@mail.gmail.com>
Date: Sat, 3 Sep 2005 13:35:29 -0400
From: Doctor Bill <docbill@gmail.com>
Subject: Re: [Qemu-devel] QEMU_TMPDIR temp folder for KQEMU for Windows.
In-Reply-To: <4319AA78.7070104@atlas.sk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <20050830134218.17388.qmail@web50508.mail.yahoo.com>
	<4319AA78.7070104@atlas.sk>
Reply-To: docbill@gmail.com, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On 9/3/05, ace <acelists@atlas.sk> wrote:
> Hi.
> 2. you say you can't see the temporary file. Neither do I, on linux. I
> suspect it is not hidden using plain filesystem attributes. On linux, if
> you open a file and then delete (unlink) it, you can still work with it
> until you hold the file descriptor. Only when you close the file, it is
> removed from disk. But as soon as you unlink it, all referrences to it
> are removed from the filesystem hierarchy. Therefore, no other program
> (e.g. dir, ls) except the filesystem kernel driver knows about it. You
> see no file, but something is still using up disk space (if you use
> programs to show free disk space). Maybe Windows supports this too.

98% correct.  In linux you can still access open unlinked files from
other processes if you know the process id and fileno.  A link is
maintained in the proc filesystem.  Some consider this a security
hole, others consider it a very useful feature.

Bill