Messages in this thread | | | From | Bodo Eggert <> | Subject | Re: what's next for the linux kernel? | Date | Wed, 05 Oct 2005 19:43:45 +0200 |
| |
Nix <nix@esperi.org.uk> wrote: > On 4 Oct 2005, Marc Perkel announced authoritatively:
>> Netware also has inherited permissions like Windows and >> Samba has and this is doing it right. > > s/right/wrong/ > > Look at a NetWare permission on some file and you can't tell what the > effective permission is, because it depends on inherited ones as well. > Look at an effective permission and you can't tell which parts of it > will change if you change the inherited permission.
MS solved that part by not allowing partially defined permissions. (At least AFAI can tell from the UI.)
> Unix has inherited permissions in one sense: you can't get at a file > via some path if one of the directories in that path is unreadable.
NACK. ITYM non-accessable (-x), and it's only true if you can't reach it or one of the other links from $PWD and the directories you can fchdir to (which, admittedly, is the usural case).
> Even *that* causes regular problems,
ACK.-)
>> File systems and individual >> directories should be able to be flagged as casesensitive/insensitive. > > Only if you're willing to change POSIX to include a call to check filenames > for identity,
You'd "just" need a way to determine the canonialized form. Still an evil masterplan.
[...] > It would also require case-conversion and locale-handling code, probably > including UTF-8 canoncalization code, inside the kernel. This would > greatly increase kernel complexity for a very small reward, and lead to > Al Viro's early death from cerebral aneurysm combined with involuntary > projectile vomiting. This cannot be considered a good thing.
a) NLS is in the kernel, and if utf-8 filenames are supposed to be used, an utf-8 checker rejecting non-canonialized strings will be desirable to avoid binary trash in filenames or lookalike filenames. The conversion to the canonialized form should happen outside the kernel.
(I know POSIX doesn't define a propper return value, but the return value used for VFAT works and it's better than dealing with $'M\x{0430}kefile' looking like Makefile)
b) ACK, I don't think caseless handling of filenames is a good thing, it would needlessly bloat the kernel by opening a can of worms. E.g. 'ß' would be converted to 'SS'[0] in German or 'B' in greek.
[0] or, if you like and bend the standard, to 'SZ' if the word with 'SS' would clash with another word.
> Now /etc/mtab, *that* is an abomination, and a small kernel improvement > (allowing arbitrary flag strings to be passed by mount into the kernel > solely for display in the appropriate /proc/mounts field) could > eliminate it and replace it entirely with /proc/mounts.
What about making all fs ignore the -omount="$tool:foo:bar;$tool2=baz:barf..." parameter?
This is a cruel hack, but it will be backward compatible. (If your hammer is big enough, the problem may turn out to be a nail.)
-- Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF verbreiteten Lügen zu sabotieren. - 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/
| |