From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 14:36:02 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AD5E16A407 for ; Tue, 14 Nov 2006 14:36:02 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C98B43D7D for ; Tue, 14 Nov 2006 14:35:59 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (hobmtu@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kAEEZrK1036309; Tue, 14 Nov 2006 15:35:58 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kAEEZqFr036308; Tue, 14 Nov 2006 15:35:52 +0100 (CET) (envelope-from olli) Date: Tue, 14 Nov 2006 15:35:52 +0100 (CET) Message-Id: <200611141435.kAEEZqFr036308@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, gurdiga@gmail.com In-Reply-To: X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 14 Nov 2006 15:35:58 +0100 (CET) X-Mailman-Approved-At: Tue, 14 Nov 2006 17:49:10 +0000 Cc: Subject: Re: bpf kernel module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, gurdiga@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 14:36:02 -0000 Vlad GURDIGA wrote: > I'm trying to keep very close touch with 6.1_STABLE cvsupping sources > once a week or even more often. You mean RELENG_6_1? I don't think that makes sense, because not many changes happen to that branch. You should only cvsup if necessary, i.e. when a security fix (or otherwise critical fix) has been committed to that branch. > I'm thinking of removing as much as > possible devices from the kernel loading them from /boot/loader.conf > instead, Personally I don't think it's worth the effort. I keep most stuff static inside a big kernel. > so I could rebuild and install them without a whole > kernel/world rebuild and reboot when sources change. I'm not sure this > is a correct way, any piece of advice regarding this would be highly > appreciated. :) When you update your sources, the recommended and official way is to rebuild everything (kernel, modules, world) and reboot. Omitting any of these steps _might_ work under certain circumstances, but it can also break in various ways (either horribly or subtly, whichever creates the most damage, according to Murphy's law). > So, I've successfully done that with sound and network card drivers, > but did not succeed with removing bpf from the kernel. Booting a > kernel with no bpf support, and with > ng_bpf_load="YES" in my loader.conf [which, I found on the questions > list that is not what I need], the pflogd fails to start with this > error: There's currently no kernel module for the bpf(4) device, so you have to put it statically in your kernel if you need it. ng_bpf is a netgraph node driver, it doesn't implement /dev/bpf* devices, so it's not what you're looking for. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "A language that doesn't have everything is actually easier to program in than some that do." -- Dennis M. Ritchie