[lkml]   [2008]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Is there a "blackhole" /dev/null directory?

    On Feb 14 2008 10:46, Andi Kleen wrote:
    >Jasper Bryant-Greene <> writes:
    >> This could be done fairly trivially with FUSE, and IMHO is a good use
    >> for FUSE because since you're just throwing most data away, performance
    >> is not a concern.

    There is a much more interesting 'problem' with a "/dev/null directory".

    Q: Why would you need such a directory?
    A: To temporarily fool a program into believing it wrote something.

    Q: Should all files disappear? (e.g. "unlink after open")
    A: Maybe not, programs may stat() the file right afterwards and
    get confused by the "inexistence".

    Q: What if a program attempts to mkdir /dev/nullmnt/foo to just
    create a file /dev/nullmnt/foo/barfile?
    A: /dev/nullmnt/foo must continue to exist or be accepted for a while,
    or perhaps for eternity.

    Been there, done that, - -
    and hit that wall of unanswerable questions.

     \ /
      Last update: 2008-02-14 16:03    [W:0.018 / U:338.240 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site