From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: cygwin@sources.redhat.com,
Malcolm Boekhoff <Malcolm.Boekhoff@actfs.co.uk>
Subject: Re: chmod and ntsec
Date: Tue, 13 Feb 2001 09:26:00 -0000 [thread overview]
Message-ID: <4.3.1.2.20010213121742.019bee18@pop.ma.ultranet.com> (raw)
In-Reply-To: <3A8955E0.1C8E6544@yahoo.com>
At 10:42 AM 2/13/2001, Earnie Boyd wrote:
>Malcolm Boekhoff wrote:
> >
> > So is the definitive, expert answer to use "ntsec" or "ntsec ntea"?
> >
>
>The ntsec flag overrides the ntea flag IIRC. There is no reason to use
>the ntea flag if you use the ntsec flag. The ntea flag, IMO, should be
>removed in the next release as it can cause more consequence than good.
I guess the big question here is whether anyone finds the use of ntea useful
for FAT partitions. This is the one advantage that ntea has over ntsec. If
the answer here is that ntea is considered useful for FAT despite the ugly,
quickly growing file it produces, then I'd say keep it. Just my $.02.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2001-02-13 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 8:43 Noel L Yap
2001-02-12 8:59 ` Larry Hall (RFK Partners, Inc)
2001-02-13 2:14 ` Malcolm Boekhoff
2001-02-13 6:11 ` Earnie Boyd
2001-02-13 7:27 ` Malcolm Boekhoff
2001-02-13 7:42 ` Earnie Boyd
2001-02-13 9:26 ` Larry Hall (RFK Partners, Inc) [this message]
2001-03-29 11:55 Heimo Ponnath
2001-03-29 17:53 ` Christopher Faylor
2001-03-29 18:11 ` Larry Hall (RFK Partners, Inc)
2001-03-30 7:05 Heimo Ponnath
2001-03-30 9:02 ` Corinna Vinschen
2001-03-30 15:36 ` Heimo Ponnath
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=4.3.1.2.20010213121742.019bee18@pop.ma.ultranet.com \
--to=lhall@rfk.com \
--cc=Malcolm.Boekhoff@actfs.co.uk \
--cc=cygwin@sources.redhat.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).