public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Vince Hoffman <Vince.Hoffman@uk.circle.com>
To: "'Volker Quetschke'" <quetschke@scytek.de>, cygwin@cygwin.com
Subject: RE: chmod problem
Date: Mon, 09 Sep 2002 03:10:00 -0000	[thread overview]
Message-ID: <3500515B75D9D311948800508BA379559506C3@EX-LONDON> (raw)

i seem to remember windows permission inheritance can cause this kind of
problem ? maybe have a search of the archives, but its still monday morning
so my brain may not be working properly yet.

-----Original Message-----
From: Volker Quetschke [mailto:quetschke@scytek.de]
Sent: 08 September 2002 18:53
To: cygwin@cygwin.com
Subject: Re: chmod problem


Hi!
> -> Err, in which FAQ is this written? Just try chmod, it works!
>From the FAQ:
> 
> Why doesn't chmod work?
> `ntsec' will allow UNIX permissions in Windows NT on NTFS file systems.

Yes, you have to have ntsec or ntea set in your CYGWIN environement variable
to be able to use chmod.

> -> As I said, use chmod. I am using gnupg on a win2k system.
> 
> I tried using chmod. Although I get no errors and in verbose mode it says
> the permissions are changed, a "ls -al" shows:
> 
> $ chmod 600 *
> 
> perry@ELVIS ~/.gnupg
> $ ls -la
> total 235
> drwxr-xr-x    2 perry    None         4096 Sep  8 09:46 .
> drwxr-xr-x    7 perry    None         8192 Sep  8 11:58 ..
> -rw-r--r--    1 perry    None         7793 Sep  8 09:41 options

It seems you don't have ntsec or ntea set in your CYGWIN variable.

As a workaround you can always use the keyword

no-permission-warning

in your gnupg options file, but I think the proper way is to use
CYGWIN=ntsec (plus your other options).

Bye
    Volker

-- 
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D

--
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/

             reply	other threads:[~2002-09-09  9:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09  3:10 Vince Hoffman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-04-04 20:17 Karl M
2012-04-05  9:46 ` Corinna Vinschen
2012-04-05 12:19   ` Karl M
2012-04-05 12:26     ` Corinna Vinschen
2012-04-05 12:28       ` Corinna Vinschen
2012-04-05 12:37         ` Karl M
2012-04-05 12:42           ` Corinna Vinschen
2002-09-08  8:25 John Perry
2002-09-08  9:40 ` Pavel Tsekov
     [not found] ` <3D7B7400.9070702@scytek.de>
2002-09-08 10:42   ` John Perry
2002-09-08 11:14     ` Volker Quetschke
2001-12-31  2:08 CHMOD problem JOSE (GRI)
2001-12-31  2:22 ` Robert Collins
2001-12-31  2:23 ` Pavel Tsekov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3500515B75D9D311948800508BA379559506C3@EX-LONDON \
    --to=vince.hoffman@uk.circle.com \
    --cc=cygwin@cygwin.com \
    --cc=quetschke@scytek.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).