Date: Wed, 09 Dec 1998 19:30:08 -0600 From: David Kelly <dkelly@hiwaay.net> To: freebsd-questions@FreeBSD.ORG Subject: Re: tar Message-ID: <199812100130.TAA39048@n4hhe.ampr.org> In-Reply-To: Message from Mark Ovens <marko@uk.radan.com> of "Wed, 09 Dec 1998 00:39:09 GMT." <366DC6AD.25E8B7E8@uk.radan.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Ovens writes: > > > You can't use wildcards in the list of files to extract > > > (etc/mtree/BSD*) > > > > Sure you can. You just have to escape them from the shell as tar > > doesn't get to see the asterix as its used above. Example: > > > > I stand corrected. Traditionally tar can't handle wildcards when > extracting, at least all the *nix I've used (mainly SunOS) can't. GNU > tar has obviously addressed this. That's correct too. I should have pointed it out when I demonstrated FreeBSD's GNU tar would parse regex expressions. GNU tar's man page doesn't say much about it, I had to experiment to find that it worked. pax(1) goes to length discussing "patterns" so presumably it too will allow some form of wildcard matching from the command line. While pax is supposed to be a POSIX utility I haven't found SGI's, Sun's, and FreeBSD's to be as similar as tar between the same hosts. Heaven forbid but I found mention of pax in NT documentation. Found out enough to know its crippled so much that it can't talk to tape drives. What a sad joke. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812100130.TAA39048>