This is the mail archive of the
mailing list for the Cygwin project.
Re: not updating unwritable cache ../config.cache
- To: Kai Henningsen <kai at cats dot ms>
- Subject: Re: not updating unwritable cache ../config.cache
- From: Corinna Vinschen <corinna at vinschen dot de>
- Date: Wed, 06 Oct 1999 16:59:27 +0200
- CC: cygwin at sourceware dot cygnus dot com
- References: <E11Ymn7-00081Afirstname.lastname@example.org>
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
> Anyway, given that NT doesn't quite seem to see a difference
> between user and group ids (Novell is similar, incidentally), I
> 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.
Want to unsubscribe from this list?
Send a message to email@example.com