From: Padraig Brady <padraig@antefacto.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: 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 12:19:56 +0000 [thread overview]
Message-ID: <3CA45BEC.8030106@antefacto.com> (raw)
In-Reply-To: <5.1.0.14.2.20020328200457.03dfda90@pop.cus.cam.ac.uk>
Is this a good default?
IMHO you usually would not want to execute stuff off NTFS, and
if you do you can always just explicitly invoke using wine like:
`wine /ntfs/lookout.exe`
To have all files executable breaks stuff like:
midnight commander (won't open executable files)
ls colorizing
shell tab completion
...
see:
http://marc.theaimsgroup.com/?t=100143416100009&r=1&w=2
I think the default should be
rx for directories and r for files
Padraig.
Anton Altaparmakov wrote:
> Hi,
>
> NTFS 2.0.1 for kernel 2.5.7 is now available. This is a minor update,
> mainly to allow binaries to be executed by changing the default
> permissions on files to include the executable bit. This feature has
> often been requested by wine users so here it is. (-:
>
> Sorry for the quick succession of releases but the web server hosting
> the 2.0.0 patches is now off line so I had to move the location and I
> used the opportunity to release this minor update.
>
> Best regards,
>
> Anton
next prev parent reply other threads:[~2002-03-29 12:21 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 [this message]
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
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=3CA45BEC.8030106@antefacto.com \
--to=padraig@antefacto.com \
--cc=aia21@cam.ac.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
/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