Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 4 Jan 2002 11:56:20 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: id / mkpasswd [2] Message-ID: <20020104165620.GC30445@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Fri, Jan 04, 2002 at 11:09:57AM +0100, david DOT sannier AT netcourrier DOT com wrote: >> [...] >> >> Nope. The datatype uid_t is equivalent to unsigned short (16bit). >> The mkpasswd tool doesn't take that into account when generating >> the uids, unfortunately. >> >> Corinna > >So, it's just a storage problem of the uid... >In my memory, the unix datatype uid_t is a long ? no ? >In the case I've mentioned yesterday, if an other user >already has the id 43833 (which is probably the case), >Is there a way to log, in the same time, him on his >own account and me on mine ? > >I've seen that mkpasswod works with int, the >value returns by NetUserGetInfo is a DWORD -> ok >(-long would be better (platform-independent), but...-) > >mkpasswd use the entire information NT returns so : > >Why 32 bits have not been chosen for uid_t too ? Because we're mean. cgf -- 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/