Date: Tue, 30 Jul 2024 13:44:18 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: "Poul-Henning Kamp" <phk@phk.freebsd.dk> Cc: Gary Jennejohn <garyj@gmx.de>, freebsd-current@freebsd.org, peter@freebsd.org Subject: Re: filemon Message-ID: <86o76f5ckt.fsf@ltc.des.dev> In-Reply-To: <202407301049.46UAnrXX011101@critter.freebsd.dk> (Poul-Henning Kamp's message of "Tue, 30 Jul 2024 10:49:53 %2B0000") References: <ZqT6_a_0F8DCUsBm@int21h> <CAFDf7UKxhSu%2BqMGV1KahrSX9ho8vFut4avxNVX4D8QGa6%2B%2BTjQ@mail.gmail.com> <20240727170122.675f6bfe@ernst.home> <865xsn6ya9.fsf@ltc.des.dev> <202407301049.46UAnrXX011101@critter.freebsd.dk>
index | next in thread | previous in thread | raw e-mail
"Poul-Henning Kamp" <phk@phk.freebsd.dk> writes:
> Dag-Erling Smørgrav <des@FreeBSD.org> writes:
> > There is very little difference between options and devices in kernel
> > configuration files, but for what it's worth, filemon is a device, not
> > an option.
> Apart from the internals of config(8) and it's input data, is there
> any actual difference left ?
>From the perspective of including files in the build, there is no
difference: `foo/foo.c optional foo` does not care whether "foo" is an
option or a device. However, options generate macros, while devices
don't. So adding `option FILEMON` to your kernel config will cause
filemon to be compiled into the kernel, but it will also generate an
unneeded opt_filemon.h with `#define FILEMON 1`. Or it would, if it
weren't for this:
% git annotate sys/conf/options |& grep -i filemon
6c6f1f0185b84 (Peter Wemm 2013-07-03 20:22:12 +0000 109)FILEMON opt_dontuse.h
which suggests Peter intended filemon to be an option rather than a
device.
DES
--
Dag-Erling Smørgrav - des@FreeBSD.org
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86o76f5ckt.fsf>