We claimed tar(1) does not support remote devices. This is not the case for
GNU tar.
This commit is contained in:
parent
b634ad3507
commit
d517b4194a
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=2024
1 changed files with 8 additions and 3 deletions
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: hw.sgml,v 1.66 1997-03-21 17:02:44 wosch Exp $ -->
|
||||
<!-- $Id: hw.sgml,v 1.67 1997-10-03 15:40:03 obrien Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
|
@ -1166,8 +1166,13 @@ that are available from <tt>cpio(1)</tt>, but <tt>tar(1)</tt>
|
|||
does not require the unusual command pipeline that
|
||||
<tt>cpio(1)</tt> uses.
|
||||
|
||||
<p><tt>tar(1)</tt> does not support backups across the
|
||||
network. You can use a pipeline and <tt>rsh(1)</tt> to send the
|
||||
<p>Most versions of <tt>tar(1)</tt> do not support backups across the
|
||||
network. The GNU version of <tt>tar(1)</tt>, which FreeBSD utilizes, supports
|
||||
remote devices using the same syntax as <tt>rdump</tt>. To <tt>tar(1)</tt>
|
||||
to an Exabyte tape drive connected to a Sun called komodo, use:
|
||||
<tt>/usr/bin/tar cf komodo:/dev/nrst8 . 2>&1</tt>.
|
||||
For versions without remote device support, you can use a pipeline
|
||||
and <tt>rsh(1)</tt> to send the
|
||||
data to a remote tape drive. (XXX add an example command)
|
||||
|
||||
<sect3><heading> Cpio</heading>
|
||||
|
|
Loading…
Reference in a new issue