...

What do I export from the server to the clients (who already have a /usr/bin) and where do I mount it on the clients so it's in their path? Or maybe I'm asking for too much. Lan with all on 9.2.

Just an idea, but how about /usr/local/bin

That's a good idea and it works but it deletes stuff that was installed in /usr/local/bin beforehand. Also, by exporting /usr/bin I'm exporting over 400 files when I really only want two.

Op maandag 6 december 2004 21:15, schreef Joe Morris (NTM):

steve wrote:

...

...

...

What do I export from the server to the clients (who already have a /usr/bin) and where do I mount it on the clients so it's in their path? Or maybe I'm asking for too much. Lan with all on 9.2.

Just an idea, but how about /usr/local/bin

That's a good idea and it works but it deletes stuff that was installed in /usr/local/bin beforehand.

I didn't know. I have nothing there.

...

Also, by exporting /usr/bin I'm exporting over 400 files when I really only want two.

In that case, would it work to export it to anywhere, like /media/nfs, or /data, or whatever and then symlink just the two files to /usr/local/bin, or symlink the 2 files on the server in a different directory, and export only that directory like I mentioned above. I am not running nfs so I admit pure ignorance, no experience, and only ideas. HTH ;-)

-- Joe Morris

I would go for /opt/bin (underneath code is from suse-9.0:/etc/profile) or as alternative /opt/cross/bin: for dir in /var/lib/dosemu \ /usr/games \ /opt/bin \ /opt/gnome/bin \ /opt/kde3/bin \ /opt/kde2/bin \ /opt/kde/bin \ /usr/openwin/bin \ /opt/cross/bin do test -d $dir && PATH=$PATH:$dir done -- Richard Bos Without a home the journey is endless

The Monday 2004-12-06 at 19:50 +0100, steve wrote:

That's a good idea and it works but it deletes stuff that was installed in /usr/local/bin beforehand. Also, by exporting /usr/bin I'm exporting over 400 files when I really only want two.

Export everything to an arbitrary directory, then symlink those two files locally. -- Cheers, Carlos Robinson

On Monday 27 December 2004 14:02, Alexandr Malusek wrote:

steve writes:

...

I want to try to run scribus and inkscape by not installing them on our clients and exporting via nfs. The binaries are in /usr/bin on our server.

IMHO, there is no simple solution in this case.

I agree. By the time you have messed around with it and found that you also need /usr/share and probably /opt too and your server can't cope anyway, you may as well have installed the stuff on the clients. I really thought that on a system designed for multi users it would be easier than this :-( Steve.

On Mon, 2004-12-27 at 19:09, Louis Richards wrote:

The /usr directory can be mounted read only from the server. This would run scribus and many other apps from the server. This is what the /usr directory is for. Clients should mount a /usr/local partition for any "non standard" local apps.

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.

That would give you "network" apps without sharing the entire /usr directory.

Louis Richards

Whithout the crappy HTML .... sorry Louis Richards

On Tue, 2004-12-28 at 13:07, Alexandr Malusek wrote:

Louis Richards 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

Mounting the entire /usr directory from the server will provide the desired results.

In theory yes. But we forget what I originally wanted to do. Run scribus and inkscape from the server. Just try it with an amd server with 1024 and you'll soon see that my idea of using it on a 20 node school lan is simply out of the question. Maybe I should start another thread: What sort of spec server do I need to do this.