>This still doesn't handle multiple users all wanting different
>"resources" for a single file. Say, you have /usr/bin/netscape
>and one user wants the Mozilla icon and another user wants the
>big N. This example is awful: you can think of better ones.
Sure. But user-settable resources are a different kettle
of fish. Only important resources should be stored in
the resource fork of the program in question -- for linux,
this would be things like copies of libc.so, so you don't
have to play library interface roulette, and any default
icons, pictures, and internal databases (like licensing
information) that the application needs to have to live.
____
david parsons \bi/ of course the libc problem is saved by static
\/ linking, but under the LGPL that's illegal.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html