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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/