NTFS v2.0.1 has been released, quickly following 2.0.0 (see earlier story). The main reason for this quick follow-up release is to provide a new download link - the old link is evidently no longer valid. Additionally, there has been a minor source code change to set the executable bit on NTFS mounted binaries by default, as "has often been requested by wine users".

From: Anton Altaparmakov
To: linux-kernel-mailing-list
Subject: ANN: NTFS 2.0.1 for kernel 2.5.7 released
Date: Thu, 28 Mar 2002 20:08:30 +0000

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

From: Anton Altaparmakov
Subject: url included - ANN: NTFS 2.0.1 for kernel 2.5.7 released
Date: Thu, 28 Mar 2002 20:13:02 +0000

It would help if I said where you can download the patches from now. (-;

http://sourceforge.net/project/showfiles.php?group_id=13956&release_id=81853

Or just go to our project page (http://sf.net/projects/linux-ntfs/) and
follow the links.

And of course you can use BitKeeper to get our BitKeeper repository at
http://linux-ntfs.bkbits.net/ntfs-tng-2.5

And a on-line view of the repository is available here:
http://linux-ntfs.bkbits.net:8080/ntfs-tng-2.5

Best regards,

Anton

From: Padraig Brady
Subject: Re: ANN: NTFS 2.0.1 for kernel 2.5.7 released
Date: Fri, 29 Mar 2002 12:19:56 +0000

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.

To: Padraig Brady
Subject: Re: ANN: NTFS 2.0.1 for kernel 2.5.7 released
Date: Fri, 29 Mar 2002 12:57:07 +0000 (GMT)

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.

If you don't like it, use -o noexec,fmask=0111 and you will not have any
files being executable.

> 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`

No you couldn't.

> To have all files executable breaks stuff like:
> midnight commander (won't open executable files)

Ouch, that is plain stupid... mc should be fixed. I open executables all
the time and mc should automatically fire up a hexeditor.

> ls colorizing

I like green files. (-;

> shell tab completion

Heh?!? Works for me. Fix your shell settings.

> ...

Like what?

> see:
> http://marc.theaimsgroup.com/?t=100143416100009&r=1&w=2

Read it. I still don't see any reason for not having x on files by
default.

> I think the default should be
> rx for directories and r for files

If you think so just use fmask to clear the x bit and be happy.

I guess if more people complain I can change the default fmask to be 0177
instead of 0077 but I want to see more complaints first. I personally find
the being able to execute behaviour better as I run things off the ntfs
partitions...

Best regards,

Anton
--