From: Mike Fedyk <mfedyk@matchmail.com>
To: Anton Altaparmakov <aia21@cus.cam.ac.uk>
Cc: Padraig Brady <padraig@antefacto.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net
Subject: Re: ANN: NTFS 2.0.1 for kernel 2.5.7 released
Date: Fri, 29 Mar 2002 10:57:51 -0800 [thread overview]
Message-ID: <20020329185751.GI8627@matchmail.com> (raw)
In-Reply-To: <3CA45BEC.8030106@antefacto.com> <Pine.SOL.3.96.1020329124320.18653A-100000@virgo.cus.cam.ac.uk>
On Fri, Mar 29, 2002 at 12:57:07PM +0000, Anton Altaparmakov wrote:
> On Fri, 29 Mar 2002, Padraig Brady wrote:
> > Is this a good default?
>
> I don't see what's wrong with that. It follows the logic of least
> surprise. In Windows all files are executable as there is no way to
> distinguish executables from non-executables due to lack of executable
> bit. NTFS on Linux has no way of telling the difference either and hence
> it makes sense to allow execution of all files.
The difference with NTFS is that there is a possibility to have unix permissions
working with it natively, with no extra visible files like with umsdos.
What are you going to do when unix permissions/ACLs are supported in Linux
NTFS? Default back to non executable?
How much extra work would it be to map the unix executable bits to a NTFS acl?
next prev parent reply other threads:[~2002-03-29 18:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 20:08 ANN: NTFS 2.0.1 for kernel 2.5.7 released Anton Altaparmakov
2002-03-29 12:19 ` Padraig Brady
2002-03-29 12:57 ` Anton Altaparmakov
2002-03-29 13:24 ` Re[2]: " Nerijus Baliunas
2002-03-30 10:34 ` Joachim Breuer
2002-03-30 11:02 ` Nicholas Miell
2002-04-01 15:20 ` Padraig Brady
2002-04-04 13:37 ` Anton Altaparmakov
2002-03-29 13:46 ` Padraig Brady
2002-03-29 14:13 ` Richard B. Johnson
2002-03-29 18:49 ` Mike Fedyk
2002-03-29 19:01 ` Richard B. Johnson
2002-03-29 18:57 ` Mike Fedyk [this message]
2002-03-29 18:09 ` Grogan
2002-03-29 18:42 ` Grogan
2002-03-29 20:21 ` Grogan
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=20020329185751.GI8627@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=aia21@cus.cam.ac.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=padraig@antefacto.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