[FreeNX-kNX] /home/.nx

[Gian Filippo Pinzari]

Rick Stout wrote:
> Shouldn't any new 
> package strive for FHS compliance to help with greater adoption, and 
> higher compatibility?

I agree, somehow, but the user pays that in terms of easyness
of management and administration. I love to be able to tar an
ironed setup and move it to a new machine. Today I can cp -a
the /usr/NX/lib directory to a different place and, by chang-
ing a line in node.conf, I can let my sessions run a different
set of libraries. I can try different NX versions by moving a
symbolic link. This is important for me, as a developer and as
a sysadmin.

There are 2 different schools of thought. Those who think that
a system must be coherent as a whole and those who like to keep
the core system (the Linux setup, including "standard" compo-
nents) separate from the rest. I'm in the second group. When I
first started using Unix I loved the fact I could tar things in
and out and keep my core system lean and clean. I regret that
doing that, these days, has become nearly impossible.

While Linux vendors have reasonable control of what thay ship
with their OS, third parties don't ususally want to deal with
libraries and executables that are replaced with different
versions or with more or less compatible substitutes shipped as
part of other packages. It's not by casuality that most commer-
cial vendors package their installations in their own directo-
ries. After all, you have to consider the fact that many sys-
admins (even experienced sysadmin) tend to care more the redu-
ced time they spend at the console than the FHS compliancy.

/Gian Filippo.