| 1 |
On Mon, Jun 17, 2013 at 6:56 PM, Peter Humphrey |
| 2 |
<peter@××××××××××××××.org> wrote: |
| 3 |
> On Monday 17 Jun 2013 08:25:08 Ciprian Dorin Craciun wrote: |
| 4 |
>> On Mon, Jun 17, 2013 at 10:21 AM, Peter Humphrey |
| 5 |
>> |
| 6 |
>> <peter@××××××××××××××.org> wrote: |
| 7 |
>> > On Monday 17 Jun 2013 07:00:35 Ciprian Dorin Craciun wrote: |
| 8 |
>> >> On Mon, Jun 17, 2013 at 8:52 AM, Florian Philipp |
| 9 |
>> >> <lists@×××××××××××.net> |
| 10 |
>> > |
| 11 |
>> > wrote: |
| 12 |
>> >> > Do you mean something like `cp --attributes-only`? |
| 13 |
>> >> > |
| 14 |
>> >> Nop, wouldn't do the job, because `cp --attributes-only` requires |
| 15 |
>> >> |
| 16 |
>> >> a target file system, ... |
| 17 |
>> > |
| 18 |
>> > You could always cp to /dev/null. |
| 19 |
>> |
| 20 |
>> Sorry I don't follow... What does imply to "cp to /dev/null", and |
| 21 |
>> what would be the outcome of that? |
| 22 |
> |
| 23 |
> /dev/null would be the target file system you referred to. It's a bottomless |
| 24 |
> empty pit, so no physically real copy would be made. |
| 25 |
|
| 26 |
|
| 27 |
I would be curious to find out how one can use `/dev/null` as a |
| 28 |
replacement for an **entire** file-system (i.e. not just a replacement |
| 29 |
for a stream sink)? And how would the `cp` command be used to obtain |
| 30 |
such an outcome? |
Archives