Date: Tue, 30 Jul 2024 19:22:31 +0800 From: Alastair Hogge <agh@riseup.net> To: freebsd-current@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz>, =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@FreeBSD.org> Subject: Re: filemon Message-ID: <D9B5CEBB-3AD3-4D0B-AFD5-33CB5EE0207B@riseup.net> In-Reply-To: <a5471d18-7f88-4e24-8518-2c7a67ddd7f1@quip.cz> References: <ZqT6_a_0F8DCUsBm@int21h> <CAFDf7UKxhSu%2BqMGV1KahrSX9ho8vFut4avxNVX4D8QGa6%2B%2BTjQ@mail.gmail.com> <20240727170122.675f6bfe@ernst.home> <865xsn6ya9.fsf@ltc.des.dev> <a5471d18-7f88-4e24-8518-2c7a67ddd7f1@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 July 2024 5:38:57=E2=80=AFpm AWST, Miroslav Lachman <000=2Efbsd@quip=
=2Ecz> wrote:
>On 30/07/2024 11:10, Dag-Erling Sm=C3=B8rgrav wrote:
>> Gary Jennejohn <garyj@gmx=2Ede> writes:
>
>[=2E=2E]
>
>>> I also load it from /boot/loader=2Econf using filemon_load=3D"YES"
>>=20
>> This does cause the module to be loaded at boot time, but it's slower
>> than loading it later, and it increases memory fragmentation=2E A bett=
er
>> option is to include "filemon" in the kld_list variable in /etc/rc=2Eco=
nf
>> or /etc/rc=2Econf=2Ed/kld=2E For instance,
>>=20
>> % cat /etc/rc=2Econf=2Ed/kld/filemon
>> kld_list=3D"${kld_list} filemon"
>
>Does this also apply today? I recently read from someone on a mailing lis=
t that the kld_list in rc=2Econf is no longer needed, that any problems it =
used to solve are solved, and that the preferred way is to load everything =
from loader=2Econf=2E
Was it the following mail from Warner on a relates commit?
https://lists=2Efreebsd=2Eorg/archives/dev-commits-src-main/2024-May/02402=
9=2Ehtml
--=20
Sent from a device with a tiny bloody screen and no hard keyboard; please =
excuse my brevity=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D9B5CEBB-3AD3-4D0B-AFD5-33CB5EE0207B>