Date: Sun, 4 Jan 1998 22:35:52 -0700 (MST) From: Atipa <freebsd@atipa.com> To: "James D. Butt" <jbutt@mwci.net> Cc: =?iso-8859-1?Q?=22Luis_E=2E_Mu=F1oz=22?= <lem@cantv.net>, freebsd-isp@FreeBSD.ORG Subject: Re: [fbsd-isp] Designing for a very large ISP Message-ID: <Pine.BSF.3.91.980104223115.7270B-100000@dot.ishiboo.com> In-Reply-To: <Pine.BSF.3.96.980104211622.25567B-100000@subcellar.mwci.net>
next in thread | previous in thread | raw e-mail | index | archive | help
For a client/workstation environment, NFS is really cool. For an ISP, I do not see any place it would be _required_ or recommended unless you were maintaining user shell space, which most places don't do. It adds lots of network and CPU overhead, and a considerable risk, so it is best suited for a "trusted" or secure environment, like behind a firewall, where it doesn't get hit by the outside world. Them maintenance is fairly simple. If you can figure out serial networking, NFS is a breeze! :) Kevin On Sun, 4 Jan 1998, James D. Butt wrote: > > Nor do I. I tend to dislike NFS on an ISP core :) > > It scares me to death... I know that we will have to do it very soon > though.... I can not think of any other solution for some situations... > > > -------------------------------------------------------------------------- > James D. Butt 'J.D.' > Network Engineer Voice 319-557-8463 > Network Operations Center Fax 319-557-9771 > MidWest Communications, Inc. Pager 319-557-6347 > 241 Main St. noc@mwci.net > Dubuque, IA 52001 jbutt@mwci.net > -------------------------------------------------------------------------- > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.980104223115.7270B-100000>