Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Thu, 6 Mar 2003 12:10:33 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: uid > 64k Message-ID: <20030306171033.GB7674@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <3E675F8D DOT 414B9BBD AT ieee DOT org> <20030306164822 DOT GT1193 AT cygbert DOT vinschen DOT de> <3E6780A9 DOT F1F32899 AT ieee DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E6780A9.F1F32899@ieee.org> User-Agent: Mutt/1.5.1i On Thu, Mar 06, 2003 at 12:08:57PM -0500, Pierre A. Humblet wrote: >Corinna Vinschen wrote: >> >> On Thu, Mar 06, 2003 at 09:47:41AM -0500, Pierre A. Humblet wrote: >> > Corinna, >> > >> > there was again a report of uid > 64k. >> > >> > Why don't we patch mkpasswd to keep uids below 64k until Cygwin >> > switches to uid32 ? >> >> How do you fold the ids into 64K? You never know if you're already >> overwriting another id. > >Agreed. However most passwd files have a lot fewer entries than 64k. >Thus I was thinking that randomizing the entries above 64k into the >range 10000->64k (to avoid local and special users) should succeed >with high probability. At worst there might be aliasing and ls -l >might show some incorrect names, in which case the file must be >edited by hand. Couldn't you just keep track of the uids and ensure that you didn't duplicate any? cgf