[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: pkg/45044: archivers/libarchive minix support
The following reply was made to PR pkg/45044; it has been noted by GNATS.
From: Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
Cc: joerg%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost,
Subject: Re: pkg/45044: archivers/libarchive minix support
Date: Sun, 12 Jun 2011 12:03:34 +0200
On Sun, Jun 12, 2011 at 04:35:03AM +0000, David Holland wrote:
> The following reply was made to PR pkg/45044; it has been noted by GNATS.
> From: David Holland <dholland-pbugs%netbsd.org@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Subject: Re: pkg/45044: archivers/libarchive minix support
> Date: Sun, 12 Jun 2011 04:34:25 +0000
> On Sat, Jun 11, 2011 at 06:05:04PM +0000, Joerg Sonnenberger wrote:
> >> Minix UIDs are 16-bits and Minix GIDs are 8-bits. The tar format
> >> supports much larger UIDs/GIDs. libarchive should handle the case where
> >> the UIDs/GIDs overflow the archive_entry uid/gid fields by setting
> >> the uid/gid to something valid (example: the uid of the nobody user and
> >> the gid of the nobody group) and it should produce a warning when doing
> > I don't think the complexity of this is justified with the gain.
> It doesn't make sense to worry about this unless you're root and the
> tar -p option (or equivalent) is in effect, and in that case it should
> print a warning, set the id to 0, and be sure to clear the set[ug]id
> bits. Much simpler that way...
As root permissions are extracted by default. But there are two things
to keep in mind here:
(1) user/group name is prefered over numeric version
(2) If you are not doing a tar tvf first, it doesn't matter. If you do
it, you get the same numeric values as a later extract would use.
Main Index |
Thread Index |