Piping output of tar(1) into another tar(1) command
Matthew Seaman
m.seaman at infracaninophile.co.uk
Tue Nov 21 07:11:38 GMT 2006
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig250727568B0C4EDC460AF2EB
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Matthew Seaman wrote:
> Jonathan Schneider wrote:
>>> with anything reasonable. However dd defaults to doing IO in 512byte=
>>> blocks, and you'll make the whole process a tad more efficient by
>>> upping the block size so you're doing fewer but larger writes to the
>>> tape device.
>> As I always say to people, use the cp command. It's easier on the
>> fingers and defaults to blocks of several k usually.
>=20
> I'm curious as to exactly how you manage to direct the output of cp(1)
> into a tape device?
Uhhh... ENCOFFEE. I mean how you manage to use cp(1) in a pipeline to
direct the output in the tape device.
Too early in the morning.
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
--------------enig250727568B0C4EDC460AF2EB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFYqar8Mjk52CukIwRCPoKAJ9yG8fqY17ScgfKgP5MLdWBYat5ugCeKK54
fNzjCElQvGhy9XG0eRufPh8=
=UPzh
-----END PGP SIGNATURE-----
--------------enig250727568B0C4EDC460AF2EB--
More information about the Ukfreebsd
mailing list