Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <37FB63CF.3C298523@vinschen.de>
Date: Wed, 06 Oct 1999 16:59:27 +0200
From: Corinna Vinschen <corinna AT vinschen DOT de>
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: de,en
MIME-Version: 1.0
To: Kai Henningsen <kai AT cats DOT ms>
CC: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: not updating unwritable cache ../config.cache
References: <E11Ymn7-00081A-00 AT charlotte DOT intern DOT cats DOT ms>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Kai Henningsen wrote:
> [...]
> Supplementary groups don't work, right? (Just making sure I
> understand what's going on.)

You can only have one primary group which is the group that
is your default group for file creation.
`newgrp' isn't supported yet but maybe later (shouldn't be too
complex).

> Anyway, given that NT doesn't quite seem to see a difference
> between user and group ids (Novell is similar, incidentally), I
> decided
> 
>         mkdir /etc
>         cd /etc
>         ( mkpasswd -l -g ; mkgroup -l ) | sort -n -t: +2 > common
>         ln common passwd
>         ln common group

This isn't completely right! A group may be used as owner of an
object but a user must not be used as "group" in a security
descriptor. So users shouldn't reside in the group file though
they wouldn't disturb there.

> Using the 19990929 cygwin1.dll, this seems to work now. Thanks!
> 
> One more question: I see directories getting the other t bit set.
> What does this mean?

Grin! The 't' bit is the sticky bit that is used in a linux style
manner. It only make sense for directories and it's typically set
on /tmp (rwxrwxrwt) and has the effect, that anybody may read and
write in /tmp but he/she can't erase files of other users.

Unfortunately, the sticky bit is set in ntsec by mistake. I had
corrected this a few days ago and the _next_ snapshot after yours
(19991001) behaves correctly.

Regards,
Corinna



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com