From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: James A Sutherland <jas88@cam.ac.uk>, linux-kernel@vger.kernel.org
Subject: Re: x bit for dirs: misfeature?
Date: Tue, 20 Nov 2001 12:58:21 +0000 [thread overview]
Message-ID: <01112012582101.00810@nemo> (raw)
In-Reply-To: <200111191814.fAJIEPlQ019878@pincoya.inf.utfsm.cl>
In-Reply-To: <200111191814.fAJIEPlQ019878@pincoya.inf.utfsm.cl>
On Monday 19 November 2001 18:14, Horst von Brand wrote:
> vda <vda@port.imtp.ilyichevsk.odessa.ua> said:
> > On Monday 19 November 2001 16:44, Horst von Brand wrote:
>
> [...]
>
> > > X sets x for dirs, leaves files alone.
> >
> > Hmm... yes this is one of such workarounds already implemented.
> > But it is not very good for my example:
> > X sets x for dirs *and* for files with x set for any of u,g,o.
> >
> > # chmod -R a+rX dir
> >
> > will make any executables (even root only) world-executable.
>
> That's what you are asking for...
?!
I'm asking for ability to make a tree _world-readable_ (and
browsable), i.e. a+r on files and a+rx on dirs.
There is currently no chmod flag which will do that.
--
vda
next prev parent reply other threads:[~2001-11-20 11:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 16:22 x bit for dirs: misfeature? vda
2001-11-19 14:36 ` James A Sutherland
2001-11-19 16:58 ` vda
2001-11-19 15:04 ` Tim Waugh
2001-11-19 15:29 ` Richard B. Johnson
2001-11-19 16:00 ` James A Sutherland
2001-11-19 17:43 ` Kai Henningsen
2001-11-19 18:24 ` vda
2001-11-19 16:44 ` Horst von Brand
2001-11-19 17:24 ` James A Sutherland
2001-11-19 19:39 ` vda
2001-11-19 19:07 ` James A Sutherland
2001-11-20 13:03 ` vda
2001-11-19 21:01 ` Flavio Stanchina
2001-11-19 19:21 ` vda
2001-11-19 18:14 ` Horst von Brand
2001-11-20 11:20 ` Anton Altaparmakov
2001-11-20 12:01 ` Alexander Viro
2001-11-20 15:08 ` Anton Altaparmakov
2001-11-20 17:18 ` Mike Castle
2001-11-20 17:37 ` Alexander Viro
2001-11-20 12:58 ` vda [this message]
2001-11-19 16:47 ` Jesse Pollard
2001-11-19 17:15 ` David Ford
2001-11-19 17:37 ` Pascal Schmidt
2001-11-19 18:42 ` J Sloan
2001-11-19 14:46 ` Alexander Viro
2001-11-19 17:03 ` vda
2001-11-19 15:07 ` Shaya Potter
2001-11-19 15:12 ` Alexander Viro
2001-11-19 15:19 ` Mathijs Mohlmann
2001-11-19 15:36 ` Gerhard Mack
2001-11-19 16:19 ` Horst von Brand
2001-11-19 22:36 ` Lionel Bouton
2001-11-19 15:12 ` Mathijs Mohlmann
2001-11-19 17:41 ` vda
2001-11-20 0:38 ` Albert D. Cahalan
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 16:05 Thomas Hood
2001-11-21 10:34 ` Helge Hafting
2001-11-21 23:00 ` Mike Fedyk
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=01112012582101.00810@nemo \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=jas88@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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