I don't know if Lyx has any special constrains that would block the following solution but maybe you should give it a try.
1) On the server, install manually from source Lyx on a separate directory (like /opt/Lyx). 2) Export the above said directory. 3) On the client side, adjust the users' $PATH to include the nfs-imported directory. Implications: A. All istances of Lyx in your network will be executed on the NFS server (based on the machine's specs and average Lyx usage from your people, try to estimate if the server can take the extra load). B. You should probably similarly `centralise' your tetex installation to avoid inconsistencies. This could be quite the pain... On Friday 03 February 2006 08:26, Arun Kulshreshth wrote: > HI, > > I have no idea if this topic has been discussed before > or not. If yes then give me pointers to that. > > We have a linux network and i want the lyx to be > centrally available so that each user is virtually > using the same lyx. How this can be done ? The epitome > of this exercise is that each time a > layout/style/class has to be added then we have to > update only on central server and each user will be > able to access it. We already have a nfs server. > > Any ideas/help would be appreciated. > > Thanks > Arun
