Date: Thu, 4 Feb 1999 20:02:36 -0500 From: "Christopher G. Petrilli" <petrilli@amber.org> To: James Wyatt <jwyatt@RWSystems.net> Cc: security@FreeBSD.ORG Subject: Re: Enabling bpf device in kernel (was: Re: tcpdump) Message-ID: <19990204200236.30021@amber.org> In-Reply-To: <Pine.BSF.4.05.9902041407080.15871-100000@kasie.rwsystems.net>; from James Wyatt on Thu, Feb 04, 1999 at 02:16:54PM -0600 References: <19990204102322.28863@amber.org> <Pine.BSF.4.05.9902041407080.15871-100000@kasie.rwsystems.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 04, 1999 at 02:16:54PM -0600, James Wyatt wrote: > On Thu, Feb 04, 1999 at 05:10:40AM -0600, Richard Wackerbarth wrote: > > I think that the world is moving toward dhcp as the primary method of > > learning appropriate IP configuration data. > > On Thu, 4 Feb 1999, Christopher G. Petrilli wrote: > > I would agree that this is true for clients, but I don't believe it will > > ever be true for servers... and remember, FreeBSD is a server first, and > > more often than it is a client I think... at least that our experience > > with it. I'm the only person who has a FreeBSD box on their desk as a > > client, but we have dozens of them as servers. > > *This* might be a good split for boot floppies. Not dozens w/different > hardware, just two for server v.s. client. The server would have higher > MAX_USER, no dhcpd. The client could have dhcp, bpf, and maybe sound. Of > course, this means more work for the folks who bring us FreeBSD. What do > they think? OTOH: I usually build server kernels by hand anyway to tune > RAM/users/ptys/etc and carefully spec drivers and options. I have begun > building most kernels on one box and FTP-ing them anyway. Call it an epiphany, but I think this is probably how the intall process should diverge... I haven't looked yet, so this is all hand-waving, but what would be nice is to be able ot simply have a "build file" that is used to generate the individual boot disks. I can think of many things (NFS?) that wouldn't necessarily be done the same in each setup... lots of things that should be turned off by default in clients, but turned on in servers, etc... Chris -- | Christopher Petrilli | petrilli@amber.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990204200236.30021>