On Tue, 15 Feb 2000, Derek Martin wrote:
> Ben, PHILISOPHICALLY I agree with you, but PRACTICALLY speaking the
> problem is that NFS doesn't guarantee that there will be no FS corruption
> if you use the soft option.  This is a Bad Thing.

  Hmmmm, by filesystem corruption, do you mean actual damage to the filesystem
structure itself, or simply lost user data?  I've never had any *serious*
problems with "soft" NFS on Linux.  Now, if a connection is lost of course the
program won't be able to complete the I/O it was trying, but that'll happen
regardless.  And some programs actually check the result of their I/O.  :)

  This may have changed with the kernel NFS driver, though.  While the
usermode NFS driver may have been slower, I really preferred the idea of
keeping NFS in userland where it can't screw up the rest of the system.

  And as far as NFS on Solaris goes -- *barf*!  For the company that invented
the thing, Sun does a damn poor job of implementing it.  :-(

> Avoid NFS at all cost, if you can.
                         ^^^^^^^^^^

  That's the kicker, isn't it?  Samba and SMB actually seem pretty good, as
network file systems go (despite the fact that the protocol is rather poorly
documented and the Microsoft implementations suck (as usual)), but it doesn't
support any kind of idea of Unix permissions.  :-(

> Have you tried afs or coda? Anyone?

  I haven't actually *tried* either of these, but from what I've read, aren't
they huge overkill for many situations?  All I want to do is share some files
with other machines on my LAN; I don't need a distributed, caching,
high-availability, offline-capable, binds-the-world-together-and-cures-cancer
filesystem.  :-)

  Still, I suppose "too much" is better then "not enough".  Another thing to
add to my to-do list... >sigh<  :)

-- 
Ben Scott
[EMAIL PROTECTED]



**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to