From: Mike Fedyk <mfedyk@matchmail.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Padraig Brady <padraig@antefacto.com>,
Anton Altaparmakov <aia21@cus.cam.ac.uk>,
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:49:06 -0800 [thread overview]
Message-ID: <20020329184906.GH8627@matchmail.com> (raw)
In-Reply-To: <3CA4703C.8000900@antefacto.com> <Pine.LNX.3.95.1020329085743.147A-100000@chaos.analogic.com>
On Fri, Mar 29, 2002 at 09:13:38AM -0500, Richard B. Johnson wrote:
> If the files are NOT set to 'executable' as read by Linux, then samba
> will not work. For the files to be visible to WIN/Clients, they
> must have all bits set. This 'feature' can be used to make DOS/Win
> files temporarily off-limits to WIN/Clients (like during a backup).
>
Since when?
None of the of the data files on my samba server are marked executable, and
all are readable.
You probably have "map archive = yes" in mind, but that will *not* deny access if
the executable bit is set or not...
This is looking at the manual for smb.conf in 2.2.3a.
Mike
next prev parent reply other threads:[~2002-03-29 18: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
2002-03-29 14:13 ` Richard B. Johnson
2002-03-29 18:49 ` Mike Fedyk [this message]
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=20020329184906.GH8627@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 \
--cc=root@chaos.analogic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.