Date: Wed, 14 Jan 2004 14:24:14 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: kientzle@acm.org Cc: freebsd-arch@freebsd.org Subject: Re: Request for Comments: libarchive, bsdtar Message-ID: <20040114.142414.97038855.imp@bsdimp.com> In-Reply-To: <4005A9A9.6090503@acm.org> References: <Pine.NEB.3.96L.1040114142135.49872F-100000@fledge.watson.org> <20040114.131705.93652359.imp@bsdimp.com> <4005A9A9.6090503@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <4005A9A9.6090503@acm.org>
Tim Kientzle <kientzle@acm.org> writes:
: M. Warner Losh wrote:
: > In message: <Pine.NEB.3.96L.1040114142135.49872F-100000@fledge.watson.org>
: > Robert Watson <rwatson@freebsd.org> writes:
: > : I know NetBSD has a neat tool to create file systems from userspace
: > : without privilege, but my understanding is that it has to pull in a lot of
: > : code from the kernel in fairly messy ways. Since tar files are a well
: > : supported portable format... :-)
: >
: > The problem then reduces to needing to be able to create the tar file
: > with ownership/permissions different than is in the unpriv'd build
: > tree. Generation of this list, as well as getting tar/whatever to
: > honor it are interesting problems.
:
: Not all that interesting, really. ;-)
A small matter of coding then to cause the meta data to be stored
during the install and then written to the archive format.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040114.142414.97038855.imp>