| |||||||||||||
The two sides of reflink()The two sides of reflink()Posted May 10, 2009 18:36 UTC (Sun) by nix (subscriber, #2304)In reply to: The two sides of reflink() by giraffedata Parent article: The two sides of reflink()
I suspect that if you actually tried to scrap link() et al, a million MTA
authors would try to kill you.
(I'd be rather annoyed, too: I use hardlinks all the time.)
(Log in to post comments)
The two sides of reflink() Posted May 11, 2009 5:50 UTC (Mon) by giraffedata (subscriber, #1954) [Link] I suspect that if you actually tried to scrap link() et al, a million MTA authors would try to kill you. Well, I wouldn't scrap link() et al -- I'd just move them out of the kernel and add the ability to explicitly create and delete files independent of directory links.
The two sides of reflink() Posted May 11, 2009 6:10 UTC (Mon) by nix (subscriber, #2304) [Link]
We already have the ability to create and delete files independently of
directory links: mkstemp(). What you can't do is easily create them outside of /tmp, or link them to names at a later date.
|
|||||||||||||