>>> PS Are /dev/null and /dev/zero also redundant?
>> I regularly use both...
>>
>> 1. Find a download that doesn't appear where one expected it...
>>
>> find / -name "wanted-but-lost-download" 2> /dev/null
>>
>> 2. Create a loop-mounted partition to populate as a CD image before
>> burning the CD in question.
>>
>> dd if=/dev/zero bs=1048576 count=750 of=/tmp/cd.img
>> mke2fs /tmp/cd.img
>> mount -o loop /tmp/cd.img /img/cd
>>
>> 3. Create a loop-mounted partition to populate as a floppy image.
>>
>> dd if=/dev/zero bs=1024 count=1440 of=/tmp/floppy.img
>> mke2fs /tmp/floppy.img
>> mount -o loop /tmp/floppy.img /img/floppy
>>
>> Neither has alternatives that make sense as far as I can see.
> Certainly have in the sense that you could theoretically do that in
> user space.
Are you sure?
> find / -name "wanted-but-lost-download" | eat
Doesn't work - you're piping the stdin there, not stderr as per my
example above. AFAIK, there's no way to pipe stderr without also piping
stdout, hence this sort of solution just doesn't work.
AFAICS, there is no sane alternative to /dev/null in userspace.
> zerofill | head -c 1440k > /tmp/floppy.img
How does zerofill know when to stop writing zeros out? After all, if it
doesn't write enough out for the head call, then it's no longer an
equivalent to /dev/zero, and it could easily be called with just about
ANY positive number of bytes, including an infinite number, as in...
zerofill | tr '\0' '@' > /dev/ttyS1
...which sends an infinite stream of 0x40 bytes to the serial port.
However...
zerofill 750M > /tmp/img.cd
zerofill 1440k > /tmp/img.floppy
...would be a reasonable userspace equivalent to examples (2) and (3)
respectively, so that certainly could be done in userspace.
> ssh foo@bar | block
Which of my examples is this an equivalent to? I don't recognise it.
> (Implementation of eat, block and zerofill is left as an
> exercise...)
I'll leave that to somebody with more unwanted time than I have...
Best wishes from Riley.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/