From owner-freebsd-questions Wed Dec 2 12:27:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00657 for freebsd-questions-outgoing; Wed, 2 Dec 1998 12:27:49 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00646 for ; Wed, 2 Dec 1998 12:27:45 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.054 #3) id 0zlIUh-000072-00; Wed, 2 Dec 1998 20:03:27 +0000 Date: Wed, 2 Dec 1998 20:03:27 +0000 From: Ben Smithurst To: Roman Katsnelson Cc: "q's" Subject: Re: sniffer Message-ID: <19981202200327.C366@scientia.demon.co.uk> References: <36657AD5.1F79504B@atlas-design.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <36657AD5.1F79504B@atlas-design.net> User-Agent: Mutt/0.94.17i (FreeBSD/3.0-CURRENT) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roman Katsnelson wrote: > and being that this is a custom kernel on a live and important web > server I'd rather not have to do that. ;) You think the GENERIC kernel, with lots of unneeded bloat, is better than a custom one with only the code you need? I (and most other people I suspect) would disagree there. If it's just the fact that you'll have to reboot a live server to load the new kernel, then I can almost understand that (it really won't take the machine out of service more than a minute or two though), but if you keep the old kernel around (which you _always_ should), you can easily boot from that if the new one doesn't work for any reason. -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message