Jan Engelhardt wrote:
On Feb 14 2008 10:46, Andi Kleen wrote:
Jasper Bryant-Greene <[EMAIL PROTECTED]> 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
Jan Engelhardt wrote:
On Feb 14 2008 10:46, Andi Kleen wrote:
Jasper Bryant-Greene [EMAIL PROTECTED] 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
Hans-Jürgen Koch <[EMAIL PROTECTED]> wrote:
> schrieb Jan Engelhardt <[EMAIL PROTECTED]>:
>> 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:
rzryyvzy <[EMAIL PROTECTED]> wrote:
> /dev/null is often very useful, specially if programs force to save data in
> some file. But some programs like to creates different temporary file names,
> so /dev/null could no more work.
>
> What is with a "/dev/null"-directory?
> I mean a "blackhole
Am Thu, 14 Feb 2008 16:23:37 +0100 (CET)
schrieb Jan Engelhardt <[EMAIL PROTECTED]>:
>
> On Feb 14 2008 16:19, Hans-Jürgen Koch wrote:
> >>
> >> 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
On Feb 14 2008 16:19, Hans-Jürgen Koch wrote:
>>
>> 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.
>
>Well, the problem seems to
Am Thu, 14 Feb 2008 16:00:06 +0100 (CET)
schrieb Jan Engelhardt <[EMAIL PROTECTED]>:
>
> On Feb 14 2008 10:46, Andi Kleen wrote:
> >Jasper Bryant-Greene <[EMAIL PROTECTED]> writes:
> >>
> >> This could be done fairly trivially with FUSE, and IMHO is a good
> >> use for FUSE because since you're
On Thu, 14 Feb 2008, Mika Lawando wrote:
> Jasper Bryant-Greene schrieb:
>> On Thu, 2008-02-14 at 10:30 +0100, rzryyvzy wrote:
>>
>>> /dev/null is often very useful, specially if programs force to save data in
>>> some file. But some programs like to creates different temporary file
>>> names,
On Feb 14 2008 10:46, Andi Kleen wrote:
>Jasper Bryant-Greene <[EMAIL PROTECTED]> 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
Jasper Bryant-Greene schrieb:
On Thu, 2008-02-14 at 10:30 +0100, rzryyvzy wrote:
/dev/null is often very useful, specially if programs force to save data in
some file. But some programs like to creates different temporary file names, so
/dev/null could no more work.
What is with a
Jasper Bryant-Greene <[EMAIL PROTECTED]> 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.
Q.: how much work would fuse have to do until the user file system
server could
On Thu, 2008-02-14 at 10:30 +0100, rzryyvzy wrote:
> /dev/null is often very useful, specially if programs force to save data in
> some file. But some programs like to creates different temporary file names,
> so /dev/null could no more work.
>
> What is with a "/dev/null"-directory?
> I mean a
Hello Linux Kernel Hackers,
/dev/null is often very useful, specially if programs force to save data in
some file. But some programs like to creates different temporary file names, so
/dev/null could no more work.
What is with a "/dev/null"-directory?
I mean a "blackhole pseudo directory"
Hello Linux Kernel Hackers,
/dev/null is often very useful, specially if programs force to save data in
some file. But some programs like to creates different temporary file names, so
/dev/null could no more work.
What is with a /dev/null-directory?
I mean a blackhole pseudo directory
On Thu, 2008-02-14 at 10:30 +0100, rzryyvzy wrote:
/dev/null is often very useful, specially if programs force to save data in
some file. But some programs like to creates different temporary file names,
so /dev/null could no more work.
What is with a /dev/null-directory?
I mean a
Jasper Bryant-Greene [EMAIL PROTECTED] 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.
Q.: how much work would fuse have to do until the user file system
server could decide
Jasper Bryant-Greene schrieb:
On Thu, 2008-02-14 at 10:30 +0100, rzryyvzy wrote:
/dev/null is often very useful, specially if programs force to save data in
some file. But some programs like to creates different temporary file names, so
/dev/null could no more work.
What is with a
On Feb 14 2008 10:46, Andi Kleen wrote:
Jasper Bryant-Greene [EMAIL PROTECTED] 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'
On Thu, 14 Feb 2008, Mika Lawando wrote:
Jasper Bryant-Greene schrieb:
On Thu, 2008-02-14 at 10:30 +0100, rzryyvzy wrote:
/dev/null is often very useful, specially if programs force to save data in
some file. But some programs like to creates different temporary file
names, so /dev/null
Am Thu, 14 Feb 2008 16:00:06 +0100 (CET)
schrieb Jan Engelhardt [EMAIL PROTECTED]:
On Feb 14 2008 10:46, Andi Kleen wrote:
Jasper Bryant-Greene [EMAIL PROTECTED] writes:
This could be done fairly trivially with FUSE, and IMHO is a good
use for FUSE because since you're just throwing
On Feb 14 2008 16:19, Hans-Jürgen Koch wrote:
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.
Well, the problem seems to be that a
Am Thu, 14 Feb 2008 16:23:37 +0100 (CET)
schrieb Jan Engelhardt [EMAIL PROTECTED]:
On Feb 14 2008 16:19, Hans-Jürgen Koch wrote:
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
rzryyvzy [EMAIL PROTECTED] wrote:
/dev/null is often very useful, specially if programs force to save data in
some file. But some programs like to creates different temporary file names,
so /dev/null could no more work.
What is with a /dev/null-directory?
I mean a blackhole pseudo
Hans-Jürgen Koch [EMAIL PROTECTED] wrote:
schrieb Jan Engelhardt [EMAIL PROTECTED]:
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
24 matches
Mail list logo
