Re: Windows NFS client to access Linux (Fedora & Suse) hosts

From: natG (natgrossDOTrentalsystems_at_verizon.net)
Date: 03/29/04 

Date: Mon, 29 Mar 2004 16:31:04 GMT

Larry I Smith wrote:
> natG wrote:
>
>> Rod Smith wrote:
>>
>>> On Sun, 28 Mar 2004 23:07:13 +0000, natG wrote:
>>>
>>>
>>>> Samba was designed for Windows shares and therefore carries
>>>> Windows/netbios baggage (performance wise) with it.
>>>> Do folks actually use Samba for Linux-only networks? One of the
>>>> Linux hosts is also a J2EE server, and I don't want it to incure
>>>> extra Samba overhead memory/cpu unless absolutely required.
>>>
>>>
>>>
>> <snipped>
>>
>>> If you could describe your needs in more detail, you might get some more
>>> helpful advice. For instance, how many computers are on this LAN, and
>>> what
>>> do they currently use for file- and printer-sharing? What sorts of files
>>> do you intend to share (user data files, program files, fonts, etc.)?
>>> How
>>> many users do you have?
>>
>>
>> We are a little team of Java Developers where at any given time there
>> can be about 7-10 active users (including everyone). The Linux
>> changeover is taking place because we had tons of problems keeping up
>> with security maintenance of xp etc etc. (Did you know that an oem
>> version of xp, say Dell, might need to be patched differently, and has
>> different recovery rules, etc? Well we didn't!) After losing time and
>> source code(!!!) even with Windoz backups, we decided that our time is
>> much better spent self-training on Linux. Anyhow, enough of the drooling.
>> The main reason for shares is that one machine is a 'dedicated' J2EE
>> server and our tools allow for automatic deployment from the IDE, and
>> one has the source code that is checked in/out by developers. With
>> J2EE, that server will need every iota, and since the only reason is
>> for hot deployment, why go thru Samba, especially where our current
>> winXP stations/coders are also changing over to Linux. So our nfs for
>> Windows requirement is temporary, why buy it. Also, once on clean
>> Linux lan we can use nfs only. Why learn Samba (under pressure to
>> produce programs!) when we need to get up to par on nfs anyhow.
>> This was my reasoning. Does it make sense?
>> Now, I see from Chuck's post that Samba might have
>> internationalization problems. That sort of rules it out.
>> So. I am back to my original question. A good experience with a
>> Windows nfs driver, anyone, please?
>>
>> Thanks;
>> -nat
>
>
> No, Samba does not have internationalization problems - the Windows
> clients accessing filenames containing international charsets may have
> problems on the Windows client side.
>
> Just a note on NFS: in our corporate workgroup environment
> (500+ machines) we had many, many more NFS related
> problems, but almost zero Samba related problems.
>
> Regards,
> Larry
Do you therefore advise not to use nfs at all, and use only Samba for
lan sharing, regardless if Linux or Windows?
Thanks;
-nat

Relevant Pages

  • Re: Problem setting up NFS on Ubuntu
    ... >>> mount' for vfat mount options. ... >>> exporting vfat via NFS, it's not designed for multiuser systems ... > alike on the FS and use samba to export it to doze clients. ... >> which should make windows client access easier, and does work also from RISC ...
    (comp.os.linux.setup)
  • Re: ubuntu to ubuntu file sharing
    ... Just an extra data point in the NFS vs Samba debate, ... initiating an oplock break request from the server to a Windows client ...
    (Ubuntu)
  • Re: Windows NFS client to access Linux (Fedora & Suse) hosts
    ... Larry I Smith wrote: ... >> Windows requirement is temporary, ... Why learn Samba (under pressure to ... when we need to get up to par on nfs anyhow. ...
    (comp.os.linux)
  • Re: [SLE] Duelling SAMBAs
    ... the statement that they'd used both SAMBA and NFS and that SAMBA ... Linux boxes, but if I'm already going to have SAMBA running, what ... if the wife wants Windows, ...
    (SuSE)
  • Re: Windows NFS client to access Linux (Fedora & Suse) hosts
    ... > Larry I Smith wrote: ... >> problems on the Windows client side. ... but almost zero Samba related problems. ... regardless if Linux or Windows? ...
    (comp.os.linux)