begin quoting Darren New as of Tue, Jun 12, 2007 at 10:29:49PM -0700: > Christopher Smith wrote: [snip] > >general, multiple streams on a file has proven to be a fairly > >questionable feature. > > Funny how almost every file system newer than FAT32 supports it. :-) Of
...and I loathe 'em all the same when they do it. > course, when most people want multiple streams on a file, they just code > multiple files in a directory, or implement it as a library. Yup. If you want multiple streams, use multiple files, PLEASE. The UNIX approach of "one file, one stream" is a *feature*. I *loathe* that OS X has gone to supporting multiple file streams. I use HFS+, but I'm not happy with it. [snip] > >>It also lacks the ability to clean up temp files when your program > >>crashes or when you log out. > > > >openat() > >unlinkat() > > Not what I meant. I meant that if I create a file in /tmp/xyz I want it > to get unlinked for me if I dump core. Sort of like creating the file, > unlinking it, and continuing to hold it open with no names in any > directories pointing to it, only with a name in the directory pointing > to it. :-) I thought the trick was to create the file, then unlink it immediately. I'll have to see if that works. -- UNIX was partially a reaction to the overly complex: "We don't need THAT!" Stewart Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
