From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: bill@eb0ne.net, Bill Crawford <billc@netcomuk.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-kernel-daily-digest digest, Vol 1 #171 - 281 msgs
Date: Wed, 21 Nov 2001 17:39:49 +0000 [thread overview]
Message-ID: <01112117394902.02798@nemo> (raw)
In-Reply-To: <200111201202.fAKC2Md29689@lists.us.dell.com> <01112112032600.01961@nemo> <3BFBC5C5.82366455@netcomuk.co.uk>
In-Reply-To: <3BFBC5C5.82366455@netcomuk.co.uk>
On Wednesday 21 November 2001 15:18, Bill Crawford wrote:
> Now, ACLs I want to see widely supported on Linux, and *used* properly
> too. They've been little used in most environments I've seen even on
> systems that do support them, which is a shame as they are a necessary
> and useful idea. Yes, the Un*x permissions system does have some
> limitations, but let's not break *all* the existing software and OSs
> that use them, since what you're suggesting will not improve things.
Hmm. I thought proper group management can let you live with std UNIX
file permissions model... NT ACLs are horrendously complex.
"Make it as simple as possible, but not simpler"
> > versions of it). It's too late. I've made patch for chmod which adds new
> > +R flag to that effect.
> Why is that needed anyway? By default directories get execute bit set
> when they're created, at least in my environment; if you're extending
> permissions you can use "go=u" or "o=g" to broaden the permissions, as
> I would expect the existing perms to be correct on files vs directories
> in most cases.
It is legitimate to do that. Do I really have to explain?
I have a script which is designed to sweep entire tree starting from /
and do some sanity checks. For example, it Opens Source:
chmod -R -c a+R /usr/src
8-)
--
vda
next prev parent reply other threads:[~2001-11-21 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200111201202.fAKC2Md29689@lists.us.dell.com>
[not found] ` <3BFA8AE2.2B5FA0@netcomuk.co.uk>
[not found] ` <01112112032600.01961@nemo>
2001-11-21 15:18 ` Linux-kernel-daily-digest digest, Vol 1 #171 - 281 msgs Bill Crawford
2001-11-21 17:39 ` vda [this message]
2001-11-21 18:13 ` Bill Crawford
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=01112117394902.02798@nemo \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=bill@eb0ne.net \
--cc=billc@netcomuk.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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.