From: Padraig Brady <padraig@antefacto.com>
To: Anton Altaparmakov <aia21@cus.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 13:46:36 +0000 [thread overview]
Message-ID: <3CA4703C.8000900@antefacto.com> (raw)
In-Reply-To: <Pine.SOL.3.96.1020329124320.18653A-100000@virgo.cus.cam.ac.uk>
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.
>
> 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.
>
why not? wine should be changed to allow this if
it is a limitation with it.
>>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.
Well by not opening I meant it tries to run them
which is sensible really. I would guess any unix
filemanager is going to have some issues with all
files having executable bits set.
Isn't there some kludge for vfat where it marks
*.{com,exe,bat} as executable?
>
>>ls colorizing
>
>
> I like green files. (-;
Well I hate them :-)
Also coloring is wrong in mc and probably other things.
>
>>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
next prev parent reply other threads:[~2002-03-29 13:47 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 [this message]
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=3CA4703C.8000900@antefacto.com \
--to=padraig@antefacto.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 \
/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