Is it better to load filemon as kldload filemon, or to
have it set as a device via 'device filemon' in the kernel
config file? or to just load it when rebuilding the system?
There is man 4 filemon but nothing there to describe usage as .ko
or device. System is n271321-9ae91f59c500 on arm64.
--
> On Jul 27, 2024, at 9:49 PM, void wrote:
>
> Is it better to load filemon as kldload filemon, or to
> have it set as a device via 'device filemon' in the kernel config file? or to
> just load it when rebuilding the system?
>
> There is man 4 filemon but nothing there to describe usage as .
Hello,
I use filemon for builds with WITH_META_MODE loaded from rc.conf:
kld_list="... filemon" for some years on both amd64 and aarch64.
Cheers,
void escreveu (sábado, 27/07/2024 à(s) 14:50):
> Is it better to load filemon as kldload filemon, or to
> have it set as a device via 'device filemo
On Sat, 27 Jul 2024 15:27:19 +0100
Nuno Teixeira wrote:
> Hello,
>
> I use filemon for builds with WITH_META_MODE loaded from rc.conf:
> kld_list="... filemon" for some years on both amd64 and aarch64.
>
> Cheers,
>
> void escreveu (sábado, 27/07/2024 à(s) 14:50):
>
> > Is it better to load file
Dnia Sat, Jul 27, 2024 at 03:27:19PM +0100, Nuno Teixeira napisał(a):
> Hello,
>
> I use filemon for builds with WITH_META_MODE loaded from rc.conf:
> kld_list="... filemon" for some years on both amd64 and aarch64.
What about filesystem perfomnace ? Have you benchmarked your FS and
whole system
On Jul 26, 2024, at 21:58, Mark Millard wrote:
> On Jul 26, 2024, at 21:20, Mark Millard wrote:
>
>> The original mount was:
>>
>> mount -onoatime 192.168.1.140:/ /mnt
>>
>> For reference:
>> 192.168.1.140:/ on /usr/obj/DESTDIRs/main-armv7-chroot-ports-official/mnt
>> (nfs, noatime)
>>
>> g
On Sat, Jul 27, 2024 at 03:01:22PM +, Gary Jennejohn wrote:
filemon is not a device, it's an option. So you can't have "device
filemon" in your kernel config file.
I compile it with makeoptions MODULES_OVERRIDE="filemon ..." in my
kernel config file.
What's the actual line in your kernel
On Sat, Jul 27, 2024 at 03:01:22PM +, Gary Jennejohn wrote:
filemon is not a device, it's an option. So you can't have "device
filemon" in your kernel config file.
man 4 filemon has the following
NAME
filemon – the filemon device
[...]
DESCRIPTION
The filemon device allows a
slightly tangent question but does filemon and consequently
WITH_META_MODE=YES work, when /usr/obj is on tmpfs? In my test, it is not
and i tested without reboot, so /usr/obj is not removed. Reason is to avoid
disk use when building world/kernel.
On Sat, Jul 27, 2024 at 6:35 PM void wrote:
> On
Marek Zarychta wrote:
>
> What about filesystem perfomnace ? Have you benchmarked your FS and
> whole system with and without filemon loaded ?
FWIW filemon does nothing unless make opens the device.
and then it only impacts syscalls done by that pid and its children.
> I am not questionining t
The following old files were in the historically incrementally
updated directory tree but not in the installation to an empty
directory tree (checked via diff -rq):
/usr/obj/DESTDIRs/main-CA7-poud/rescue/gbde
/usr/obj/DESTDIRs/main-CA7-poud/usr/include/machine/fiq.h
/usr/obj/DESTDIRs/main-CA7-poud
On Jul 27, 2024, at 16:07, Mark Millard wrote:
> The following old files were in the historically incrementally
> updated directory tree but not in the installation to an empty
> directory tree (checked via diff -rq):
>
> /usr/obj/DESTDIRs/main-CA7-poud/rescue/gbde
> /usr/obj/DESTDIRs/main-CA7-p
12 matches
Mail list logo
