caliper caliper
2009/11/17 Anton Aylward
: James Knott said the following on 11/17/2009 08:28 AM:
That info has to be saved somewhere. Where do you want it to be?
Indeed. *NIX takes the attitude that this is a 'local solution to a local problem'.
Windows has the Registry. A central solution. Many people think that *IS* the problem.
Which would you rather have?
Personally I don't like the idea of one huge "SPOF".
Especially when its as confusing and undocumented as it is. By comparison, *NIX config files and parameter files are models of clarity. If you don't believe me, red through the files in /etc and tell me how well they are commented - locally; tell me if they relate clearly to the subsystems they affect.
So, since that information has to be saved somewhere, where else do you want to be?
In /etc/dolphin/ something ...?
Well, suppose you have a directory /home/david/applications which has /dev/VGMain/applications mounted. All the dolphin-esque information s in /etc/dolphin/..... somewhere, right?
Now unmount that and mount /dev/VGMain/appl2 which has exactly the same directory structure but different files.
Now what? All that central information is WRONG.
But if the information is in a .directory file in each directory it will always be in context.
As I keep saying in various forums
Context is Everything
As the files are KDE-specific, I would expect the information contained within them to be under ~/.kde or in another KDE-specific place. Certainly not littered all across the filesystem, hidden or not. And, as previously mentioned, what would you do about the situation where different file systems can appear in the same location? In OS/2,
Dotan Cohen wrote: the file system used extended attributes to handle this sort of thing. Unfortunately, Linux & Unix file systems don't appear to support EAs. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org