From: "Paul Ranson" 

This is a multi-part message in MIME format.

------=_NextPart_000_017C_01C294D1.F6CFBB80
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Who compared file sharing on DOS with a multi-user system?

Anyway NFS worked and Samba didn't, for me, this time and the last time = a
couple of years ago.

Paul
  "Adam Flinton"  wrote in message =
news:3de28e1f{at}w3.nls.net...
  Nope but comparing filesharing on DOS (which as just a single user =
system was not easy) & a multiuser system (including the security =
settings as to whether one is allowed to share it or not) is fairly =
falacious. Heck filesharing on DOS was such a bitch that for a while we =
used Novell DOS cos that did make it easy.

  Adam
    "Rich"  wrote in message news:3de2817c{at}w3.nls.net...
       You can ask Paul about specifics of problems he encountered.  =
Nothing you mention below absolves the samba folks of any responsibility =
for problems with usability of samba.

    Rich

      "Adam Flinton"  wrote in message =
news:3de1ea9d{at}w3.nls.net...
      That's in part because Samba most often runs on multiuser systems. =
Getting Samba to the level of sharing everyone's home dir's is the =
default setting (on most linux'es I've known) & there's a bunch of GUIs
= tool to help share other folders (e.g. SWAT). Yes you have to know if =
you've got a PDC & you want that to do authentication etc. Maybe it's =
coz I've been running smb on linux for a long while now but it isn't = that
hard on say Mandrake 9. Certainly in terms of being an SMB client = using
something like LinNeighborhood makes SMB Client stuff easy.=20

------=_NextPart_000_017C_01C294D1.F6CFBB80
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








Who compared file sharing on
DOS with a =
multi-user=20
system?
 
Anyway NFS worked and Samba
didn't, for =
me, this=20
time and the last time a couple of years ago.
 
Paul

  "Adam Flinton" <adam{at}NOSPAMsoftfab.com>">mailto:adam{at}NOSPAMsoftfab.com">adam{at}NOSPAMsoftfab.com>
=
wrote in=20
  message news:3de28e1f{at}w3.nls.net...
  Nope but comparing
filesharing on DOS =
(which as=20
  just a single user system was not easy) & a multiuser system =
(including=20
  the security settings as to whether one is allowed to share it or not) =
is=20
  fairly falacious. Heck filesharing on DOS was such a bitch that for a =
while we=20
  used Novell DOS cos that did make it easy.
   
  Adam
  

    "Rich" <{at}> wrote in message news:3de2817c{at}w3.nls.net...
       You
can ask Paul about =
specifics=20
    of problems he encountered.  Nothing you mention below absolves =
the=20
    samba folks of any responsibility for problems with usability of=20
    samba.
     
    Rich
     
    

      "Adam Flinton" <adam{at}NOSPAMsoftfab.com>">mailto:adam{at}NOSPAMsoftfab.com">adam{at}NOSPAMsoftfab.com>
= wrote=20
      in message news:3de1ea9d{at}w3.nls.net...
      That's in part because
Samba most =
often runs=20
      on multiuser systems. Getting Samba to the level of sharing =
everyone's=20
      home dir's is the default setting (on most linux'es I've known) =
&=20
      there's a bunch of GUIs tool to help share other folders (e.g. =
SWAT). Yes=20
      you have to know if you've got a PDC & you want that to do=20
      authentication etc. Maybe it's coz I've been running smb on linux =
for a=20
      long while now but it isn't that hard on say Mandrake 9. Certainly =
in=20
      terms of being an SMB client using something like LinNeighborhood =
makes=20
      SMB Client stuff easy. 
       

------=_NextPart_000_017C_01C294D1.F6CFBB80--

--- BBBS/NT v4.01 Flag-4