TCLUG Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TCLUG:996] Samba clarification



> 
> So, let me get more concrete with my example. Let's say I want to install
> MS Office 97 on my Linux server so that it may be "served" to any of a
> number of Win95 machines in our office. Here are some specific questions.
> 
> 1. Where would I put the Office apps in my Linux directory tree?
> /usr/local/win95? /win95?
> 
Where ever you want.  Just make sure it's shared in smb.conf.

> Let's say one of the Windows machines in our office has a 2 GB hard drive
> which Windows calls drive c:.
> 
> 2. Does the process of installing software look like this, then?
> 
> a. Configure Samba so that the Windows machine's drive d: is actually that
> directory on my Linux server that I've set aside for Windows apps.
> b. Put Office 97 CD in CD-ROM drive of Windows machine.
> c. Run setup program and install Office 97 on drive d:
> d. Fiddle with permissions so that other users can't write to the Windows
> section of the Linux HD.
> 
That's good.  

> >From then on, at that machine, all I do (assuming I set it up so that the
> Samba share is automatically mapped to drive d: at startup) is run
> "d:\winword.exe". Of course the exact path to the Word binary may vary.
> 
Yes.

Only problem is that any dll's that it installed in the system directory won't be on the other machines and therefore you're screwed again.  So you can keep a copy of the windows directory on the Linux machine and point everything at that, could be a real pain, or since you've already fallen to the dark so of using Microsoft, get NT and set it up to do dll serving.  I don't know how to do it, but we did it at school and it worked real nice.  Whatever dll's the machine running the application doesn't have, it asks the NT machine for.

---
Jon Schewe
http://tcfreenet.org/~schewe
jpschewe@usa.net