From owner-freebsd-current@FreeBSD.ORG Thu Oct 7 14:55:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F07C716A4CE for ; Thu, 7 Oct 2004 14:55:46 +0000 (GMT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id B84A643D1D for ; Thu, 7 Oct 2004 14:55:46 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id CE65AB85E for ; Thu, 7 Oct 2004 09:55:45 -0500 (CDT) Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09758-07 for ; Thu, 7 Oct 2004 09:55:44 -0500 (CDT) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id 3250FB855 for ; Thu, 7 Oct 2004 09:55:44 -0500 (CDT) From: Kirk Strauser To: freebsd-current@freebsd.org Date: Thu, 7 Oct 2004 09:55:37 -0500 User-Agent: KMail/1.7 References: <200410061755.42069.kirk@strauser.com> <1097105028.775.22.camel@prophecy.dyndns.org> In-Reply-To: <1097105028.775.22.camel@prophecy.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart18304329.uu3hDt6rWj"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200410070955.40350.kirk@strauser.com> X-Virus-Scanned: by amavisd-new at honeypot.net Subject: Re: Weird errors with gtar on 5.3-BETA7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2004 14:55:47 -0000 --nextPart18304329.uu3hDt6rWj Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 06 October 2004 18:23, Christopher Nehren wrote: > It means that you're trying to archive a file system which isn't > actually a file system -- in this case, /proc. You can use gtar's -X > option to exclude /proc and other non-file system paths from your > archiving. But shouldn't the "--one-file-system" option stop it from attempting to=20 recurse into a mountpoint in the first place? bsdtar seems to handle that= =20 situation as expected: # gtar --one-file-system -cf /dev/null / gtar: Removing leading `/' from member names gtar: /proc: Cannot savedir: Invalid argument gtar: Error exit delayed from previous errors # tar --one-file-system -cf /dev/null / tar: Removing leading '/' from member names > You don't happen to be using procfs on a 5.x system, do you? procfs is > notoriously insecure (and, in my opinion, its very functionality is > insecure -- you shouldn't be able to see anything about anyone else's > processes. Period.). If you are using it, why do you need it? My "jailadmin" program uses /proc to get information about running=20 processes. I haven't reworked that functionality yet. =2D-=20 Kirk Strauser --nextPart18304329.uu3hDt6rWj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iD8DBQBBZVjs5sRg+Y0CpvERAlEPAJ9lNeD5THva3H4+GMMmQ6m5IJML6ACeISFy QC3iwBLxZwkdLHUCT+mocaw= =e4T8 -----END PGP SIGNATURE----- --nextPart18304329.uu3hDt6rWj--