On Tue, 2004-12-28 at 13:07, Alexandr Malusek wrote:
Louis Richards <louis@ldrinteractive.com> writes:
... If you do not want to export /usr, you could export a lib directory as well as a bin directory from the server. Update the clients once to include the shares in the path and /etc/ld.so.conf. Now copy the binaries in the shared bin directory and use ldd to determine which libs to copy to the lib share. ...
It may be done but there is no doubt that it is far from the desired solution when an organization uses a global file system where packages can be easily installed and updated. Administration costs must be kept as low as possible.
-- A.M.
Mounting the entire /usr directory from the server will provide the desired results. Applications updated on the server are then available imediately to all clients. Of course, this is just one solution. Shortcuts could be provided for the users to run the programs through ssh (ssh -X server scribus). These shortcuts would continue to work after an upgrade on the server. The users could also run the programs through NX or some other remote client/server solution. This method works nicely if you still have Windows clients mixed in as they can run the apps as well. Or you could realy cut down on admin costs and move to terminals using NX or LTSP. Either of these can also run Windows apps by providing access to a terminal server. On the downside, mounting the whole /usr directory does seem to be more than you want/need. It limits your choice of which applications are networked. The ssh solution would require passwordless logons to be setup for ease of use on the client end. NX server costs money and requires client software. Terminals would most likely require some major changes to your current network setup for both the server and the clients. Uhhmm ... OK ... you were right all along. :-) Louis Richards