From: Padraig Brady <padraig.brady@corvil.com>
To: hps@intermeta.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.44-[mm3, ac2] time to tar zxf kernel tarball compared forvarious
Date: Thu, 24 Oct 2002 12:37:29 +0100 [thread overview]
Message-ID: <3DB7DB79.7010003@corvil.com> (raw)
In-Reply-To: ap8g19$8k4$1@forge.intermeta.de
Henning P. Schmiedehausen wrote:
> Hans Reiser <reiser@namesys.com> writes:
>
>>simple tests like this. We recently ran into one with tar recognizing
>>that it was writing to /dev/null, and optimizing for it.
>
> As stated in the info document. It is there for a reason (Amanda).
>
> --- cut ---
> When the archive is being created to `/dev/null', GNU `tar' tries to
> minimize input and output operations. The Amanda backup system, when
> used with GNU `tar', has an initial sizing pass which uses this feature.
> --- cut ---
IMHO /dev/null shouldn't be used for this. What's wrong
with Amanda doing: ln -s /dev/null /dev/drop
Then optimizing tars can use /dev/drop to not write()
and non-optimizing tars will still work as expected?
Pádraig.
prev parent reply other threads:[~2002-10-24 11:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 19:42 2.5.44-[mm3, ac2] time to tar zxf kernel tarball compared for various fs Steven Cole
2002-10-23 19:57 ` 2.5.44-[mm3, ac2] time to tar zxf kernel tarball compared forvarious fs Andrew Morton
2002-10-23 20:04 ` Benjamin LaHaise
2002-10-23 20:09 ` Andrew Morton
2002-10-24 8:34 ` Daniel Phillips
2002-10-23 20:05 ` Steven Cole
2002-10-23 20:32 ` Steven Cole
2002-10-23 20:44 ` 2.5.44-[mm3, ac2] time to tar zxf kernel tarball comparedforvarious fs Andrew Morton
2002-10-24 3:10 ` 2.5.44-[mm3, ac2] time to tar zxf kernel tarball compared forvarious fs Hans Reiser
2002-10-24 9:54 ` 2.5.44-[mm3, ac2] time to tar zxf kernel tarball compared forvarious Henning P. Schmiedehausen
2002-10-24 11:37 ` Padraig Brady [this message]
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=3DB7DB79.7010003@corvil.com \
--to=padraig.brady@corvil.com \
--cc=hps@intermeta.de \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).