>One important question was missed during the discussion about SAMBA vs NFS:
>Can we freely make our choice, or there are some technical limitations or
>disadvantegous compromises in certain cases? I have a feeling, that in a
>typical heterogenous institution/university network where UNIX, Linux and Netware
>servers are connected to PC-s running DOS and Windows, there are only very few
>possibilities. One possibility is the combination of PC-TCP Idrive (an NFS client)
>and Novell's IPX+NETX using the ODI shell. The "price" of this solution is a huge
>amount of memory resident stuff.
>My question is the following: is the SAMBA stuff compatible (i.e. can be
>combined) with these things, or provides only file and printing service from
>the Linux host, leving the UNIX and Netware hosts inaccessible from the PC clients?
You can mix and match if you want, but the real advantage of samba is that
it puts the burden of diversity on the unix host(s) which can handle
it easily rather than requiring extra protocols to be loaded on every
PC. That is, you can run Windows-for-WorkGroups with the 32-bit TCP
stack as your only protocol if you want, taking up almost no low
memory on the PC, and connect to unix (via samba), WFW, NT, or LanMan
shared resources, adding the Netware support only if you need it.
Samba should run on most unix hosts, and can be used along with NFS
if you have a combination of clients.