From: Jamie Lokier <jamie@shareable.org>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: Linux Filesystem Development <linux-fsdevel@vger.kernel.org>
Subject: Re: badly authored udf file systems
Date: Thu, 2 Dec 2004 10:03:08 +0000 [thread overview]
Message-ID: <20041202100308.GA14567@mail.shareable.org> (raw)
In-Reply-To: <1101957150.5405.9.camel@localhost.localdomain>
Shaya Potter wrote:
> in looking at the ecma spec
> (http://www.ecma-international.org/publications/standards/Ecma-167.htm)
> and section 4/14.9 where the file entry record is discussed, it shows
> that the permission scheme sort of mirrors unix (i.e. owner, group,
> other and read/write/execute bits). However, the spec is ambigious
> because when it refers to the execute bit, it doesn't talk about
> directories at all. In normal unix, of course one needs the execute bit
> set, however, its probable other systems dont have such a semantic and
> hence buggy dvd authoring programs on those platforms don't check for
> it.
>
> Would it be useful to have a file system option to specify something
> along the lines "buggy_dvd" which automatically gives all directories a
> 0x111 bump?
If the spec doesn't talk about directory execute permissions at all,
and it looks like that is intended, then shouldn't the 0x111 bump be
done all the time for UDF? More exactly, adding execute permissions
corresponding to whichever read permissions are set.
-- Jamie
next prev parent reply other threads:[~2004-12-02 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 3:12 badly authored udf file systems Shaya Potter
2004-12-02 10:03 ` Jamie Lokier [this message]
2004-12-02 13:22 ` Shaya Potter
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=20041202100308.GA14567@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=spotter@cs.columbia.edu \
/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;
as well as URLs for NNTP newsgroup(s).