Re: Why no flag to unlink a file on creation?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 27, 2012 at 9:29 AM, Jann Horn <jannhorn@xxxxxxxxxxxxxx> wrote:
> Hello,
> I'm not too familiar with the internals of the kernel, so this question
> might be stupid, and I'm not sure whether this is the right place to ask
> about it, but anyway:
> Why is there no flag for the "open" syscall to specify that you want the
> file you're opening to be deleted? I think that it would be very useful
> in combination with O_CREAT - you could create temporary files without
> actually leaving files on the filesystem, given that the filesystem
> supports it.

The open() function behaviour is dictated both by POSIX and ISO C.

You really want to ask this on either the related C library mailing
list or the related POSIX standards group mailing list.

libc-help@xxxxxxxxxxxxxx - The GNU C Library help mailing list.
* List for discussing GNU C Library issues and ISO C11 questions.
* http://www.gnu.org/software/libc/libc.html

or

austin-group-l@xxxxxxxxxxxxx - Austin Common Standards Revision List.
* List for discussing POSIX related issues
* http://www.opengroup.org/austin/lists.html

Cheers,
Carlos.
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux