Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <4.3.1.2.20020121174350.023bcf08@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 21 Jan 2002 17:45:28 -0500
To: Corinna Vinschen <cygwin AT cygwin DOT com>, cygwin <cygwin AT cygwin DOT com>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: [RFD]: Changing datatypes for uid_t/gid_t
In-Reply-To: <20020121192718.C13771@cygbert.vinschen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:27 PM 1/21/2002, Corinna Vinschen wrote:
>We have three possible data sizes:
>
>- 16 bit.  Don't touch anything.  Advantage: Nothing to do for us,
>   no compatibility problems at all.
>
>- 32 bit.  Coincidentally equal to sizeof int and sizeof long.
>   Advantage:  Should even work with older software which often
>   silently assume that a uid/gid can be stored in a int.
>
>- 64 bit.  Advantage: Since the RIDs used in Windows are just
>   32 bit, one could create uids/gids with using the upper 32 bit
>   of the uid/gid as a domain/server identifier, e.g.
>   locadmin:10000000500:544:...
>   fooadmin:20000000500:544:...

I'd recommend going with the size that is the same as uid/gid on other
UNIX systems.  I guess that puts me in the 32 bit camp.




Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/