From: Christopher Faylor <cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Bash script permissions
Date: Wed, 12 Sep 2001 14:05:00 -0000 [thread overview]
Message-ID: <20010912170558.C25291@redhat.com> (raw)
In-Reply-To: <00cf01c13bce$154d6520$391e10ac@dmonknt>
On Wed, Sep 12, 2001 at 04:01:24PM -0500, David Monk wrote:
>> Apparently you don't seem to understand the concept of NTFS security
>> and _why_ it's set that way after switching ntsec on. Besides the
>> Microsoft documentation read http://cygwin.com/cygwin-ug-net/ntsec.html .
>> Thinko: When Cygwin has been installed using no security settings at
>> att, how are the default settings on the files...
>>
>
>I would actually, considering my environment, love to switch to using the
>ntsec setting. But, how do I change over to the new setting without a whole
>ton of work? I have made so many additions to cygwin since original
>installation here.
chmod -R a-x /lib /etc
etc.
Leave the directories containing binary files alone.
You don't have to laboriously do a chmod for every file.
cgf
--
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/
next prev parent reply other threads:[~2001-09-12 14:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 12:50 David Monk
2001-09-12 13:23 ` Larry Hall (RFK Partners, Inc)
2001-09-12 13:25 ` Corinna Vinschen
2001-09-12 13:35 ` David Monk
2001-09-12 13:46 ` Larry Hall (RFK Partners, Inc)
2001-09-12 13:50 ` David Monk
2001-09-12 13:54 ` Larry Hall (RFK Partners, Inc)
2001-09-12 13:49 ` Corinna Vinschen
2001-09-12 14:01 ` David Monk
2001-09-12 14:05 ` Christopher Faylor [this message]
2001-09-12 14:42 ` David Monk
2001-09-12 14:55 ` Rick Rankin
2001-09-12 15:02 ` Corinna Vinschen
2001-09-13 6:30 ` Properly using ntsec, from the beginning David Monk
2001-09-13 6:59 ` Corinna Vinschen
2001-09-13 7:25 ` Gerrit P. Haase
2001-09-12 13:30 ` Bash script permissions Gerrit P. Haase
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=20010912170558.C25291@redhat.com \
--to=cygwin@cygwin.com \
/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).