On Tue, Jul 30, 2024, 12:54 PM Dag-Erling Smørgrav wrote:
> Miroslav Lachman <000.f...@quip.cz> writes:
> > I'm a bit confused. If I understand it right, you say loader.conf
> > causes less memory fragmentation, but DES said "it still increases low
> > memory fragmentation". So what is true? And
> On Jul 31, 2024, at 2:54 AM, Dag-Erling Smørgrav wrote:
>
> Miroslav Lachman <000.f...@quip.cz> writes:
>> I'm a bit confused. If I understand it right, you say loader.conf
>> causes less memory fragmentation, but DES said "it still increases low
>> memory fragmentation". So what is true? An
On 07/30/2024 9:25 am, Larry Rosenman wrote:
On 07/30/2024 9:22 am, Ed Maste wrote:
On Mon, 29 Jul 2024 at 19:54, Larry Rosenman wrote:
I'm getting the following on an up2date checkout:
Building /usr/obj/usr/src/amd64.amd64/usr.bin/clang/clang/clang.full
ld: warning:
/usr/obj/usr/src/amd64.a
On 7/30/24 16:16, Cy Schubert wrote:
In message , Gleb Smirnoff writes:
On Tue, Jul 23, 2024 at 01:39:23PM -0700, Gleb Smirnoff wrote:
T> On Mon, Jul 22, 2024 at 01:00:11AM -0700, Gleb Smirnoff wrote:
T> T> This is an automated email to inform you that the July 2024 stabilizati
on week
T> T> sta
In message , Gleb Smirnoff writes:
> On Tue, Jul 23, 2024 at 01:39:23PM -0700, Gleb Smirnoff wrote:
> T> On Mon, Jul 22, 2024 at 01:00:11AM -0700, Gleb Smirnoff wrote:
> T> T> This is an automated email to inform you that the July 2024 stabilizati
> on week
> T> T> started with FreeBSD/main at main
Shawn Webb writes:
> While probably less efficient than just running the tools outright, I
> usually just set up a tmpfs that I chroot into and install those kinds
> of packages.
Yeah, I do something similar, with the footnote that I more often than
not have no internet connection, so I
On 7/30/2024 4:44 AM, Dag-Erling Smørgrav wrote:
"Poul-Henning Kamp" writes:
Dag-Erling Smørgrav 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
On Tue, Jul 23, 2024 at 01:39:23PM -0700, Gleb Smirnoff wrote:
T> On Mon, Jul 22, 2024 at 01:00:11AM -0700, Gleb Smirnoff wrote:
T> T> This is an automated email to inform you that the July 2024 stabilization
week
T> T> started with FreeBSD/main at main-n271321-9ae91f59c500, which was tagged
as
T
On Tue, Jul 30, 2024 at 07:07:51PM +, Poul-Henning Kamp wrote:
> I do not want want this to turn into a everything-and-Emacs bloat-party,
> but I would find it really helpful if our install-ISO images had two
> HW-spelunking ports installed:
>
> sysutils/smartmontools
>
> and
>
>
On 2024-07-30 19:07 +, Poul-Henning Kamp wrote:
> sysutils/smartmontools
>
> and
>
> sysutils/dmidecode
>
> Is that even possible ?
>
> Am I the only one who thinks so ?
I have missed having these tools numerous times over the years. Whether it's
installing on a new machine
I do not want want this to turn into a everything-and-Emacs bloat-party,
but I would find it really helpful if our install-ISO images had two
HW-spelunking ports installed:
sysutils/smartmontools
and
sysutils/dmidecode
Is that even possible ?
Am I the only one who thinks so ?
void writes:
> The arm64 device is headless and i connect to it via serial.
> I noticed the beastie menu come up with the option Video for
> console. Cycled it to Serial, booted, all fine. [...]
man boot.config
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Miroslav Lachman <000.f...@quip.cz> writes:
> I'm a bit confused. If I understand it right, you say loader.conf
> causes less memory fragmentation, but DES said "it still increases low
> memory fragmentation". So what is true? And is this something to watch
> out for, or is memory fragmentation not
On 7/29/24 18:04, Nuno Teixeira wrote:
Hello all,
At main-n271434-b3cec803eaa4 security/s2n-tls fails to build tests with
`make test`.
I remember that tests were ok about 1 or 2 weeks ago.
I will update world soon and continue to monitor this tests failure.
Thanks,
Hi,
I've pushed 9333e1
On Tue, Jul 30, 2024 at 11:57:07PM +0900, Tomoaki AOKI wrote:
Another aspect is that loading multiple too large modules easily makes
boots crash. Staging area (memory region which loader allocates to load
kernel and modules, and maybe configured buffers) is limited.
This is why I went looking
On 30/07/2024 16:30, Warner Losh wrote:
[..]
Does this also apply today? I recently read from someone on a mailing
list that the kld_list in rc.conf is no longer needed, that any
problems
it used to solve are solved, and that the preferred way is to load
everything from load
Hi,
I have an rpi4 arm64 device at n271321-9ae91f59c500 and an amd64 image
running in screen(8) as zvol-backed vm at n271360-82283cad12a4
The arm64 device is headless and i connect to it via serial.
I noticed the beastie menu come up with the option Video for
console. Cycled it to Serial, booted
On Tue, 30 Jul 2024 19:22:31 +0800
Alastair Hogge wrote:
>
>
> On 30 July 2024 5:38:57 pm AWST, Miroslav Lachman <000.f...@quip.cz> wrote:
> >On 30/07/2024 11:10, Dag-Erling Smørgrav wrote:
> >> Gary Jennejohn writes:
> >
> >[..]
> >
> >>> I also load it from /boot/loader.conf using filemon_lo
On Tue, Jul 30, 2024, 4:50 AM Poul-Henning Kamp wrote:
>
> Dag-Erling Smørgrav 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 con
On Tue, Jul 30, 2024, 3:39 AM Miroslav Lachman <000.f...@quip.cz> wrote:
> On 30/07/2024 11:10, Dag-Erling Smørgrav wrote:
> > Gary Jennejohn writes:
>
> [..]
>
> >> I also load it from /boot/loader.conf using filemon_load="YES"
> >
> > This does cause the module to be loaded at boot time, but it
On 07/30/2024 9:22 am, Ed Maste wrote:
On Mon, 29 Jul 2024 at 19:54, Larry Rosenman wrote:
I'm getting the following on an up2date checkout:
Building /usr/obj/usr/src/amd64.amd64/usr.bin/clang/clang/clang.full
ld: warning: /usr/obj/usr/src/amd64.amd64/lib/clang/libllvm/libllvm.a:
archive membe
On Mon, 29 Jul 2024 at 19:54, Larry Rosenman wrote:
>
> I'm getting the following on an up2date checkout:
> Building /usr/obj/usr/src/amd64.amd64/usr.bin/clang/clang/clang.full
> ld: warning: /usr/obj/usr/src/amd64.amd64/lib/clang/libllvm/libllvm.a:
> archive member 'FaultMaps.o' is neither ET_REL
On 30/07/2024 12:31, Dag-Erling Smørgrav wrote:
Miroslav Lachman <000.f...@quip.cz> writes:
Dag-Erling Smørgrav writes:
This does cause the module to be loaded at boot time, but it's slower
than loading it later, and it increases memory fragmentation.
Does this also apply today? I recently re
On 30/07/2024 14:55, Michael Gmelin wrote:
On Tue, 30 Jul 2024 11:38:57 +0200
Miroslav Lachman <000.f...@quip.cz> wrote:
[..]
Does this also apply today? I recently read from someone on a mailing
list that the kld_list in rc.conf is no longer needed, that any
problems it used to solve are so
On Tue, 30 Jul 2024 11:38:57 +0200
Miroslav Lachman <000.f...@quip.cz> wrote:
> On 30/07/2024 11:10, Dag-Erling Smørgrav wrote:
> > Gary Jennejohn writes:
>
> [..]
>
> >> I also load it from /boot/loader.conf using filemon_load="YES"
> >
> > This does cause the module to be loaded at bo
"Poul-Henning Kamp" writes:
> Dag-Erling Smørgrav 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
On 30 July 2024 5:38:57 pm AWST, Miroslav Lachman <000.f...@quip.cz> wrote:
>On 30/07/2024 11:10, Dag-Erling Smørgrav wrote:
>> Gary Jennejohn writes:
>
>[..]
>
>>> I also load it from /boot/loader.conf using filemon_load="YES"
>>
>> This does cause the module to be loaded at boot time, but it
Dag-Erling Smørgrav 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 ?
--
On Tue, 30 Jul 2024 11:10:06 +0200
Dag-Erling Smørgrav wrote:
> Gary Jennejohn writes:
> > filemon is not a device, it's an option. So you can't have "device
> > filemon" in your kernel config file.
>
> There is very little difference between options and devices in kernel
> configuration files,
Miroslav Lachman <000.f...@quip.cz> writes:
> Dag-Erling Smørgrav writes:
> > This does cause the module to be loaded at boot time, but it's slower
> > than loading it later, and it increases memory fragmentation.
> Does this also apply today? I recently read from someone on a mailing
> list that
Hi,
On Tue, 30 Jul 2024, at 10:10, Dag-Erling Smørgrav wrote:
> void writes:
>> How would I go about remedying the issue that usage/examples
>> are not present in manpages for either the device line in kernel
>> config or filemon.ko ?
>
> https://reviews.freebsd.org/D46184
thank you!
On 30/07/2024 11:10, Dag-Erling Smørgrav wrote:
Gary Jennejohn writes:
[..]
I also load it from /boot/loader.conf using filemon_load="YES"
This does cause the module to be loaded at boot time, but it's slower
than loading it later, and it increases memory fragmentation. A better
option is
void writes:
> How would I go about remedying the issue that usage/examples
> are not present in manpages for either the device line in kernel
> config or filemon.ko ?
https://reviews.freebsd.org/D46184
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Gary Jennejohn writes:
> filemon is not a device, it's an option. So you can't have "device
> filemon" in your kernel config file.
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.
> I compile
34 matches
Mail list logo
