From: Ciprian Dorin Craciun <ciprian.craciun@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] File system meta-data indexer / checker
Date: Mon, 17 Jun 2013 19:40:10 +0300 [thread overview]
Message-ID: <CA+Tk8fxe62+s42-yMzDCYCNi-JgNuf4+T9gGm56=1u6y2x_oBQ@mail.gmail.com> (raw)
In-Reply-To: <201306171656.58779.peter@humphrey.ukfsn.org>
On Mon, Jun 17, 2013 at 6:56 PM, Peter Humphrey
<peter@humphrey.ukfsn.org> wrote:
> On Monday 17 Jun 2013 08:25:08 Ciprian Dorin Craciun wrote:
>> On Mon, Jun 17, 2013 at 10:21 AM, Peter Humphrey
>>
>> <peter@humphrey.ukfsn.org> wrote:
>> > On Monday 17 Jun 2013 07:00:35 Ciprian Dorin Craciun wrote:
>> >> On Mon, Jun 17, 2013 at 8:52 AM, Florian Philipp
>> >> <lists@binarywings.net>
>> >
>> > wrote:
>> >> > Do you mean something like `cp --attributes-only`?
>> >> >
>> >> Nop, wouldn't do the job, because `cp --attributes-only` requires
>> >>
>> >> a target file system, ...
>> >
>> > You could always cp to /dev/null.
>>
>> Sorry I don't follow... What does imply to "cp to /dev/null", and
>> what would be the outcome of that?
>
> /dev/null would be the target file system you referred to. It's a bottomless
> empty pit, so no physically real copy would be made.
I would be curious to find out how one can use `/dev/null` as a
replacement for an **entire** file-system (i.e. not just a replacement
for a stream sink)? And how would the `cp` command be used to obtain
such an outcome?
next prev parent reply other threads:[~2013-06-17 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 21:14 [gentoo-user] File system meta-data indexer / checker Ciprian Dorin Craciun
2013-06-17 5:52 ` Florian Philipp
2013-06-17 6:00 ` Ciprian Dorin Craciun
2013-06-17 7:21 ` Peter Humphrey
2013-06-17 7:25 ` Ciprian Dorin Craciun
2013-06-17 15:56 ` Peter Humphrey
2013-06-17 16:40 ` Ciprian Dorin Craciun [this message]
2013-06-17 7:42 ` Paul Colquhoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+Tk8fxe62+s42-yMzDCYCNi-JgNuf4+T9gGm56=1u6y2x_oBQ@mail.gmail.com' \
--to=ciprian.craciun@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox