Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 27 Jul 2001 11:16:34 +0200 From: Corinna Vinschen To: "cygwin AT cygwin. Com (E-mail)" Subject: Re: Understanding Cygwin /etc/passwd and /etc/group on W98 Message-ID: <20010727111634.C6325@cygbert.vinschen.de> Mail-Followup-To: "cygwin AT cygwin. Com (E-mail)" References: <01C11640 DOT 55A550A0 DOT jorgens AT coho DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01C11640.55A550A0.jorgens@coho.net>; from jorgens@coho.net on Fri, Jul 27, 2001 at 02:03:20AM -0700 On Fri, Jul 27, 2001 at 02:03:20AM -0700, Steve Jorgensen wrote: > On Windows 98, I'm curious why /etc/group looks like an exact copy of > /etc/passwd. they both look like this: > > Syhome::500:544::/home/Syhome:/bin/bash > > Shouldn't /etc/group contain an entry for a group with GID of 544 to match > the default GID for UID 500 rather than a copy of the passwd file? FWIU, > when looked at as passwd entry, this refers to a user with UID 500 and > default group GID 544, but as a group entry, this defines a group with GID > 500 having a single member UID 544. Since there is neither a UID of 544 or > a GID of 500, these files don't look compatible. > > I see that if I run mkgroup, I get an entry that looks valid: > unknown::544: > > but I thought setup created /etc/group by running mkgroup, so why isn't > that what /etc/group already contains? Looks like somebody manually performed a `mkpasswd > /etc/group' on your machine. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/