From owner-freebsd-bugs  Sat Mar  2 16:03:27 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA26413
          for bugs-outgoing; Sat, 2 Mar 1996 16:03:27 -0800 (PST)
Received: from birk04.studby.uio.no (birk04.studby.uio.no [129.240.214.13])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA26408
          for <freebsd-bugs@freebsd.org>; Sat, 2 Mar 1996 16:03:24 -0800 (PST)
Received: (from aagero@localhost) by birk04.studby.uio.no (8.6.12/8.6.12) id BAA00291; Sun, 3 Mar 1996 01:03:23 +0100
Date: Sun, 3 Mar 1996 01:03:23 +0100
Message-Id: <199603030003.BAA00291@birk04.studby.uio.no>
From: Aage Roebekk <aagero@birk04.studby.uio.no>
To: freebsd-bugs@freebsd.org
Subject: unsigned 32 bit uid breaks ar(1)
MIME-Version: 1.0
Sender: owner-bugs@freebsd.org
Precedence: bulk

If someone e.g. on NFS as root, which maps to uid -2, creates a
archive with ar(1), the uid field overflows the 6 character array
declared in the structure defined in /usr/include/ar.h. This can be a
problem when e.g. doing a "make world" on a NFS mounted
filesystem. Perhaps an option to use 16 bit unsigned uids would be
appropriate? Editing the ar structure is of course not an option,
which would break all implementations expecting char[6] uid and
char[6] gid.

-aage