Date: Fri, 10 Nov 2006 02:16:52 -0800 From: "Aaron Burke" <aburke@nullplusone.net> To: "martinko" <gamato@users.sourceforge.net>, <freebsd-stable@freebsd.org> Subject: RE: adding an extra hard disk and adding space to /usr Message-ID: <PGENKKAMCLFNBHPINBGAIEOBDAAA.aburke@nullplusone.net> In-Reply-To: <ej0bcq$80n$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
SNIP
> > (FreeBSD 4.x) : cd /usr; tar clpf - . | (cd /mnt; tar xvf -)
> > (FreeBSD 5.x+) : cd /usr; gtar clpf - . | (cd /mnt; gtar xvf -)
> iirc tar(1) has changed in 5.3. why do you use gtar please? is new tar
> missing something?
Well, technically no, but it requires more typing.
gtar supports the same flags that were present on FreeBSD up till 4.x
(or as you say, perhaps as late as 5.3). However, the more typical tar
now has a completly undesired effect. The main difference is how the
'l' flag is treated.
excerpt from tar man page:
BUGS
POSIX and GNU violently disagree about the meaning of the -l option.
Because of the potential for disaster if someone expects one behavior
and
gets the other, the -l option is deliberately broken in this
implementa-
tion.
another excerpt from the tar man page. (FreeBSD 5.4-Release):
-l If POSIXLY_CORRECT is specified in the environment, this is a
synonym for the --check-links option. Otherwise, an error will
be displayed. Users who desire behavior compatible with GNU
tar
should use the --one-file-system option instead.
excerpt from gtar man page (FreeBSD 5.4-Release):
-l
--one-file-system Stay in local file system when creating an ar-
chive (do not cross mount points).
> cheers,
>
> martin
SNIP
-- Aaron Burke
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PGENKKAMCLFNBHPINBGAIEOBDAAA.aburke>