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: <37FB6FF7.2838013E@ece.gatech.edu>
Date: Wed, 06 Oct 1999 11:51:19 -0400
From: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: 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: <E11YmB6-0007yR-00 AT charlotte DOT intern DOT cats DOT ms>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


> 
> bash-2.02$ ls -la test
> -rw-r--r--   1 544      Kein            0 Oct  5 09:57 test
> bash-2.02$ echo > test
> bash-2.02$ ls -la test
> -rw-r--r--   1 544      Kein            2 Oct  6 09:08 test
> bash-2.02$ echo >> test
> bash-2.02$ ls -la test
> -rw-r--r--   1 544      Kein            4 Oct  6 09:08 test
> bash-2.02$
> 
> Umm, nope.
> 

group #544 is Administrators
so test is owned by Administrators, group "Kein" ("None"? -- do an ls
-lan. This should show  "-rw-r--r--   1 544     513    .....". Group
#513 is "None" in english.) I believe you have discovered a *different*
problem, which is a bug. Echo doesn't seem to check permissions. If you
do a 

if [ -w test ]; then echo writable; else echo non-writable; fi

you should see the results I described.

> >--- there is no single user whose UID is equal to the GID of
> > the Administrators group. There are two ways to work around this NTism
> > (maybe 3?)
> >
> > This is true for the "Administrator" account as well. UID(Administrator)
> > != GID(Administrators) --- note the final 's' on the group name.
> >
> > 1) change umask so that files are created as -rw-rw-r--. Then all users
> > in the Administrators group can r/w the files they create.
> 
> bash-2.02$ umask
> 000
> bash-2.02$
> 
> Hmmm ...
> 

Oh yeah. Sorry. I forgot that the only thing umask does is *remove*
privileges from created files. If the default access mode is -rw-rw-rw-
and you have a umask of 022, then the file will be created with
group-write and all-write access disabled (-rw-r--r--). By setting umask
to 000, you have shown that the default access mode is -rw-r--r--. You
can't use umask to *add* priveleges (such as group-write). There is a
way to do that, but I don't remember what it was...

> > 2) Don't do things as a member of the Administrators group member. Use a
> > normal user account.
> 
> It's the only one I have.

However, if you have administrator priveleges, then you can certainly
create a normal user account. If you *choose* not to do this, that is
your right and your decision. 

> 
> > 3) ntsec ???
> 
> Well?

I don't know enough about ntsec and the latest snapshots to offer useful
advice; Corinna has explained ntsec earlier in this thread.

--Chuck

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