X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: From: Karl M To: Subject: RE: Setup 1.7 2.621 Date: Tue, 12 May 2009 07:59:59 -0700 In-Reply-To: <20090512083313.GP21324@calimero.vinschen.de> References: <20090511161607 DOT GM21324 AT calimero DOT vinschen DOT de> <20090512083313 DOT GP21324 AT calimero DOT vinschen DOT de> Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > Date: Tue, 12 May 2009 10:33:13 +0200 > From: corinna > Subject: Re: Setup 1.7 2.621 > > Looks normal. The group file contains a root group because it gets > added by the postinstall script. mkgroup does not add that automatically. > And files group owned by "root" are actually owned by the administrators > group for hopefully obvious reasons: > >> root:S-1-5-32-544:0: > [...] >> Administrators:S-1-5-32-544:544: > > So what is the root group for and why is it added? =20 Thanks, =20 ...Karl _________________________________________________________________ Windows Live=99: Keep your life in sync. http://windowslive.com/explore?ocid=3DTXT_TAGLM_BR_life_in_synch_052009 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/