Return to BSD News archive
#! rnews 2286 bsd Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.syd.connect.com.au!phaedrus.kralizec.net.au!news.mel.aone.net.au!grumpy.fl.net.au!news.webspan.net!ix.netcom.com!newsfeeds.sol.net!mr.net!news-feed.inet.tele.dk!news.he.net!news.iquest.net!news.thepoint.net!not-for-mail From: "Arlie Davis" <arlie@thepoint.net> Subject: Re: Win 95 and FreeBSD Networking Message-ID: <01bc0027$27cad4e0$0aa1f6ce@sequoia> Date: Sun, 12 Jan 1997 01:22:28 GMT References: <sehari.851845795@eng3.iastate.edu> <5a7vkn$peu@Symiserver2.symantec.com> <32ce60d6.0@finesse.isdn.uni-konstanz.de> Organization: ThePoint Internet Services, Inc. X-Newsreader: Microsoft Internet News 4.70.1160 Lines: 29 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33764 NFS is a terrible network filesystem protocol. It's more of a way to waste time than anything else. I would _much_ rather see a decent native SMB client implementation on FreeBSD than waste time on implementing NFS on NT. The reason that there have been almost _no_ good implementations of NFS on OSes other than UNIX shows just how closely bound NFS and UNIX are. Not to mention NFS is so damn insecure! And don't tell me it isn't -- I've worked on and administered too many networks to believe otherwise. -- arlie Pascal Gienger <Pascal.Gienger@uni-konstanz.de> wrote in article <32ce60d6.0@finesse.isdn.uni-konstanz.de>... > tedm@agora.rdrop.com wrote: > > That's the typical answer from Microsoft-Fans or -representatives. > Why would they be better off then? What sense would it have to track users > into NT? They don't get NFS for now. PERHAPS they will get then in NT 5. > Unix will have NFS then also like it has it NOW. So with NT 5, > they would have NFS from an NT Server to Windows clients. Like now, > with a Unix machine and NFS clients for Windows. They are not available from > Microsoft, sure, but they are available from other vendors, these clients. > So what is your problem? Or do you think perhaps that M$ will use > Microsoft Extensions with the NFS protocol rendering it incompatible with > industry standard NFS? And you surely will say it would be better to use > Microsoft NFS? I think you are kidding...