public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Malcolm Boekhoff" <Malcolm.Boekhoff@actfs.co.uk>
To: "Cygwin News Group" <cygwin@sources.redhat.com>
Subject: Re: chmod and ntsec
Date: Tue, 13 Feb 2001 07:27:00 -0000	[thread overview]
Message-ID: <007101c095d1$80844730$275c100a@actfs.co.uk> (raw)
In-Reply-To: <3A89409C.ED192DEA@yahoo.com>

So is the definitive, expert answer to use "ntsec" or "ntsec ntea"?

----- Original Message -----
From: "Earnie Boyd" <earnie_boyd@yahoo.com>
To: "Malcolm Boekhoff" <Malcolm.Boekhoff@actfs.co.uk>
Cc: "Cygwin News Group" <cygwin@sources.redhat.com>
Sent: Tuesday, February 13, 2001 2:11 PM
Subject: Re: chmod and ntsec


> Malcolm Boekhoff wrote:
> >
> > I wasted a load of time trying to get ntsec working, too, so now I just use "ntea" in the CYGWIN variable. Apparently this is
not a
> > good idea for FAT disks, but all mine are NTFS so I don't care.
> >
>
> Just remember that all diskettes are FAT and that you can't create a
> NTFS diskette.  So, if you use your Cygwin utilities to access the
> diskette then you will get an attributes file on the diskette.
>
> Earnie.
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2001-02-13  7:27 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 [this message]
2001-02-13  7:42       ` Earnie Boyd
2001-02-13  9:26         ` Larry Hall (RFK Partners, Inc)
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='007101c095d1$80844730$275c100a@actfs.co.uk' \
    --to=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).