Rick Macklem:
> I have coded this, but having a pathconf name for something that is
> specific to a file is a bit weird. kib@ has suggested that it might be
> better to do it as an ioctl().
>
> So, do you think a pathconf variable is preferred, since it is
> "Solaris compatible" or an ioctl()?
io
I can confirm that reverting commit be61deae0aa2 fixes the PKG.
Sent from Proton Mail Android
Original Message
On 5/4/25 7:28 PM, Yusuf Yaman wrote:
> Thanks for reporting that, I just noticed that problem too. Hope it gets
> fixed soon.
>
> Sent from Proton Mail Android
Thanks for reporting that, I just noticed that problem too. Hope it gets fixed
soon.
Sent from Proton Mail Android
Original Message
On 5/2/25 9:33 AM, Graham Perrin wrote:
> root@mowa219-gjp4-zbook-freebsd:~ # pkg version -C -vRL= | grep -v orphaned
> pkg: invalid option -
On Mon, Apr 28, 2025 at 3:08 AM Lionel Cons wrote:
>
> On Sat, 26 Apr 2025 at 17:14, Rick Macklem wrote:
> >
> > On Tue, Apr 22, 2025 at 3:34 AM Cedric Blancher
> > wrote:
> > >
> > > On Sun, 9 Mar 2025 at 00:02, Rick Macklem wrote:
> > > >
> > > > First off, I cross posted because I don't thin
>pkg: invalid option -- v
> > > >pkg: invalid option -- R
> > > >pkg: invalid option -- L
> > > >pkg: invalid option -- =3D
> > >
> > > how odd.
> > >
> > > I'd try re-making pkg from an updated ports tree.
> > >
00, Graham Perrin wrote:
> > >root@mowa219-gjp4-zbook-freebsd:~ # pkg version -C -vRL=3D | grep -v
> > orphaned
> > >pkg: invalid option -- C
> > >pkg: invalid option -- v
> > >pkg: invalid option -- R
> > >pkg: invalid option -- L
> > >pkg: i
on -- R
> >pkg: invalid option -- L
> >pkg: invalid option -- =
>
> how odd.
>
> I'd try re-making pkg from an updated ports tree.
> My context builds everything from source. It doesn't use pkg base.
>
> % pkg version -C -vRL= | grep -v orphaned
>
On Fri, May 02, 2025 at 07:32:34AM +0100, Graham Perrin wrote:
root@mowa219-gjp4-zbook-freebsd:~ # pkg version -C -vRL= | grep -v orphaned
pkg: invalid option -- C
pkg: invalid option -- v
pkg: invalid option -- R
pkg: invalid option -- L
pkg: invalid option -- =
how odd.
I'd try re-m
Also (with /usr/sbin/pkg in CURRENT), fish completions are sometimes
broken. The most recent example:
grahamperrin@mowa219-gjp4-zbook-freebsd ~> pkg iinfo Fpkg: invalid
option -- l
pkg: invalid option -- q
rames/ reeBSD
> What is the right way to build with gcc?
Here is one data point.
> exa% MAKEOBJDIRPREFIX=/tmp/obj/ make -j 16 -s buildworld
> __MAKE_CONF=/dev/null SRCCONF=/dev/null TARGET=amd64 TARGET_ARCH=amd64
> CROSS_TOOLCHAIN=amd64-gcc14
With a not-that-recent stable/14 (based on 6f34788b4e24ecbd602 f
On 02.05.25 08:32, Graham Perrin wrote:
root@mowa219-gjp4-zbook-freebsd:~ # pkg version -C -vRL= | grep -v orphaned
pkg: invalid option -- C
pkg: invalid option -- v
pkg: invalid option -- R
pkg: invalid option -- L
pkg: invalid option -- =
Updating FreeBSD-ports repository catalogue...
FreeBSD-p
On Tue, Apr 29, 2025 at 08:44:50PM +0200, Dimitry Andric wrote:
> On 29 Apr 2025, at 19:43, Shawn Webb wrote:
> >
> > On Sun, Apr 27, 2025 at 07:42:44PM +0200, Dimitry Andric wrote:
> >> On 27 Apr 2025, at 17:04, Shawn Webb wrote:
> >>>
> >>> On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry An
On 29 Apr 2025, at 19:43, Shawn Webb wrote:
>
> On Sun, Apr 27, 2025 at 07:42:44PM +0200, Dimitry Andric wrote:
>> On 27 Apr 2025, at 17:04, Shawn Webb wrote:
>>>
>>> On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry Andric wrote:
>> ...
Please let me know if you encounter any problems res
On Sun, Apr 27, 2025 at 07:42:44PM +0200, Dimitry Andric wrote:
> On 27 Apr 2025, at 17:04, Shawn Webb wrote:
> >
> > On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry Andric wrote:
> ...
> >> Please let me know if you encounter any problems resulting due to this
> >> change, as I intend to MFC i
On Sun, 27 Apr 2025, at 19:50, Vladimir Kondratyev wrote:
> On 4/27/25 19:57, Gleb Smirnoff wrote:
> I see 3 possible reasons:
>
> 1. Pre-daa098cc37b9 system running during March stabweek.
> 2. Different touchpad hardware.
> 3. Something else. E.g. a luck.
>
> --
> WBR
> Vladimir Kondratyev
This
On 4/27/25 19:57, Gleb Smirnoff wrote:
On Sun, Apr 27, 2025 at 03:38:46PM +, Dave Cottlehuber wrote:
D> On Sat, 26 Apr 2025, at 16:19, Vladimir Kondratyev wrote:
D> > On 4/24/25 21:46, Gleb Smirnoff wrote:
D> >> On Thu, Apr 24, 2025 at 05:48:46PM +, Dave Cottlehuber wrote:
D> >> D> On Thu
On 27 Apr 2025, at 17:04, Shawn Webb wrote:
>
> On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry Andric wrote:
...
>> Please let me know if you encounter any problems resulting due to this
>> change, as I intend to MFC it. For example, I tried covering all
>> incremental build scenarios, but I m
I updated my source tree and did a whole world build then did the
buildworld again without changing anything that would affect something
to get rebuild and then the world has been built now in 192 seconds.
Indeed, it seems pico files can be cached too. Sorry for the noise and
thank you all! Hav
On Sun, Apr 27, 2025 at 03:38:46PM +, Dave Cottlehuber wrote:
D> On Sat, 26 Apr 2025, at 16:19, Vladimir Kondratyev wrote:
D> > On 4/24/25 21:46, Gleb Smirnoff wrote:
D> >> On Thu, Apr 24, 2025 at 05:48:46PM +, Dave Cottlehuber wrote:
D> >> D> On Thu, 24 Apr 2025, at 17:31, Gleb Smirnoff wr
On Sat, 26 Apr 2025, at 16:19, Vladimir Kondratyev wrote:
> On 4/24/25 21:46, Gleb Smirnoff wrote:
>> On Thu, Apr 24, 2025 at 05:48:46PM +, Dave Cottlehuber wrote:
>> D> On Thu, 24 Apr 2025, at 17:31, Gleb Smirnoff wrote:
>> D> > D> This issue actually came up last month but I had no time to
>>
On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry Andric wrote:
> Hi,
>
> In https://cgit.freebsd.org/src/commit/?id=2e47f35be5dc I committed a
> change to convert libllvm, libclang, and liblldb into private shared
> libraries. This means that tools like clang, lld, lldb, and more are now
> quite
On Thu, Apr 24, 2025 at 08:56:44AM +0300, Andriy Gapon wrote:
> On 23/04/2025 21:56, Andriy Gapon wrote:
> > BTW, I've been wondering how illumos avoids the problem even though they
> > do not use any special dlopen flags.
> > It turns out that they link almost all system shared libraries with
> >
On 27 Apr 2025, at 01:28, Yusuf Yaman wrote:
>
> I am a new user of 15.0-CURRENT and just updated my source tree and
> noticed that there are now files to be built that have the ".pico"
> extension, as a ccache user, i was enjoying fast world/kernel builds but
> these files doesn't seem to get
On Sun, Apr 27, 2025 at 2:28 AM Yusuf Yaman wrote:
>
> Hi,
>
> I am a new user of 15.0-CURRENT and just updated my source tree and
> noticed that there are now files to be built that have the ".pico"
> extension, as a ccache user, i was enjoying fast world/kernel builds but
> these files doesn't s
Hi,
I am a new user of 15.0-CURRENT and just updated my source tree and
noticed that there are now files to be built that have the ".pico"
extension, as a ccache user, i was enjoying fast world/kernel builds but
these files doesn't seem to get cached to me and my world builds are
taking long t
On 4/24/25 21:46, Gleb Smirnoff wrote:
On Thu, Apr 24, 2025 at 05:48:46PM +, Dave Cottlehuber wrote:
D> On Thu, 24 Apr 2025, at 17:31, Gleb Smirnoff wrote:
D> > D> This issue actually came up last month but I had no time to
D> > investigate
D> > D> then, details
D> > https://bugs.freebsd.org/
On Tue, Apr 22, 2025 at 3:34 AM Cedric Blancher
wrote:
>
> On Sun, 9 Mar 2025 at 00:02, Rick Macklem wrote:
> >
> > First off, I cross posted because I don't think many read freebsd-arch@.
> > There seems to be a nice market for Solaris style extended attributes.
> > Since ZFS is already wired fo
On Sat, Apr 26, 2025 at 03:01:01PM +0300, Sulev-Madis Silber wrote:
that might be it!? there is hdd on machine that was tested but now
never really likes to complete the long smart tests, and short take ages.
there are no "usual" disk errors, tho. that hdd is part of 2 disk mirror
that the gi
On April 23, 2025 6:40:44 PM GMT+03:00, void wrote:
>On Mon, Apr 21, 2025 at 04:25:16AM +0300, Sulev-Madis Silber wrote:
>> i have long running issue in my 13.4 box (amd64)
>>
>> others don't get it at all and only suggest adding more than 4g ram
>>
>> it manifests as some mmap or other probl
On Apr 22, 2025, at 21:29, Mark Millard wrote:
> On Apr 22, 2025, at 20:27, Mark Millard wrote:
>
>> Sulev-Madis Silber wrote
>> on
>> Date: Wed, 23 Apr 2025 02:04:28 UTC :
>>
>>> yes, 2 * 8g partitions on separate disks, so i have 16g swap
>>>
>>> . . .
>>>
>> Van: Sulev-Madis Silber
On Mon, Apr 21, 2025 at 01:00:13AM -0700, Gleb Smirnoff wrote:
T> This is an automated email to inform you that the April 2025 stabilization
week
T> started with FreeBSD/main at main-n276625-d4763484f911, which was tagged as
T> main-stabweek-2025-Apr.
The A/B testing at Netflix didn't find any st
On Thu, Apr 24, 2025 at 05:48:46PM +, Dave Cottlehuber wrote:
D> On Thu, 24 Apr 2025, at 17:31, Gleb Smirnoff wrote:
D> > D> This issue actually came up last month but I had no time to
D> > investigate
D> > D> then, details
D> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286045
D> >
D>
On Thu, 24 Apr 2025, at 17:31, Gleb Smirnoff wrote:
> D> This issue actually came up last month but I had no time to
> investigate
> D> then, details
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286045
>
> Is this regression since last stabweek or from an earlier point?
Hi Gleb
Just sinc
On Thu, Apr 24, 2025 at 02:04:39PM +, Dave Cottlehuber wrote:
D> On Mon, 21 Apr 2025, at 14:22, Warner Losh wrote:
D> > Please note: Gleb is on vacation this week, so I'll be coordinating
D> > stab-week this time. Please be sure to cc me on any problems you
D> > encounter.
D> >
D> > Warner
D> >
On Mon, 21 Apr 2025, at 14:22, Warner Losh wrote:
> Please note: Gleb is on vacation this week, so I'll be coordinating
> stab-week this time. Please be sure to cc me on any problems you
> encounter.
>
> Warner
>
> On Mon, Apr 21, 2025 at 2:00 AM Gleb Smirnoff wrote:
>>
>> Hi FreeBSD/main users
On Thu, 24 Apr 2025, at 14:04, Dave Cottlehuber wrote:
> On Mon, 21 Apr 2025, at 14:22, Warner Losh wrote:
>> Please note: Gleb is on vacation this week, so I'll be coordinating
>> stab-week this time. Please be sure to cc me on any problems you
>> encounter.
> from https://bugs.freebsd.org/bugzil
On 23/04/2025 21:56, Andriy Gapon wrote:
BTW, I've been wondering how illumos avoids the problem even though they do not
use any special dlopen flags.
It turns out that they link almost all system shared libraries with -Bdirect
option (which is Solaris/illumos specific).
It's somewhat similar t
Sulev-Madis Silber wrote on
Date: Wed, 23 Apr 2025 06:55:06 UTC :
>
> On April 23, 2025 8:34:36 AM GMT+03:00, Mark Millard
> wrote:
> >On Apr 22, 2025, at 21:59, Mark Millard wrote:
> >
> >> Sulev-Madis Silber
> >> wrote on
> >> Date: Wed, 23 Apr 2025 04:31:41 UTC :
> >>
> >> . . .
> . . .
On Wed, Apr 23, 2025 at 09:09:56PM +0300, Andriy Gapon wrote:
> On 19/04/2025 13:29, Konstantin Belousov wrote:
> > On Sat, Apr 19, 2025 at 01:25:28PM +0300, Andriy Gapon wrote:
> > > On 19/04/2025 12:39, Andriy Gapon wrote:
> > > > From a quick look at the code, should we try to resolve the symb
On 19/04/2025 13:38, Konstantin Belousov wrote:
And there is the version with the recursive marking by deepbind:
I think that this patch would help with my case (haven't tested yet).
But I am not sure if it would be "correct".
First, as you have rightfully asked, it's not clear that deepbind s
On 19/04/2025 13:29, Konstantin Belousov wrote:
On Sat, Apr 19, 2025 at 01:25:28PM +0300, Andriy Gapon wrote:
On 19/04/2025 12:39, Andriy Gapon wrote:
From a quick look at the code, should we try to resolve the symbol in
refobj itself when it's marked with deepbind?
Oh, and it looks like obj
On Mon, Apr 21, 2025 at 04:25:16AM +0300, Sulev-Madis Silber wrote:
i have long running issue in my 13.4 box (amd64)
others don't get it at all and only suggest adding more than 4g ram
it manifests as some mmap or other problems i don't really get
basically unrestricted git consumes all the me
Hello Warner,
I've encountered the following issue:
drm-kmod refuses to build, complains about vm_page_next() not being
defined. Also, when I tried installing drm-kmod or drm-66-kmod packages,
the kmods didn't want to work, complained about some symbols not being
there.
There does exist a f
On Wed, Apr 23, 2025 at 3:10 AM Cedric Blancher
wrote:
>
> On Tue, 22 Apr 2025 at 13:10, Rick Macklem wrote:
> >
> > On Tue, Apr 22, 2025 at 3:34 AM Cedric Blancher
> > wrote:
> > >
> > > On Sun, 9 Mar 2025 at 00:02, Rick Macklem wrote:
> > > >
> > > > First off, I cross posted because I don't
Alastair Hogge writes:
> Dag-Erling Smørgrav writes:
> > Alastair Hogge writes:
> > > ld-elf.so.1: Shared object "libmd.so.6" not found, required by "mtree"
> > > *** Error code 1
> > This is _after_ installworld, right? `etcupdate -p`, then installworld,
> > then `etcupdate -B`?
> Correct, and
On 2025-04-18 14:24, Dag-Erling Smørgrav wrote:
> Alastair Hogge writes:
>> Hmm I did try $(etcupdate -B), and I recall it also failing, so I
>> updated another host, and used -B with etcupdate, and it failed for
>> another reason:
>> [...]
>> ld-elf.so.1: Shared object "libmd.so.6" not found, req
On April 23, 2025 8:34:36 AM GMT+03:00, Mark Millard wrote:
>On Apr 22, 2025, at 21:59, Mark Millard wrote:
>
>> Sulev-Madis Silber wrote
>> on
>> Date: Wed, 23 Apr 2025 04:31:41 UTC :
>>
>> https://forums.freebsd.org/threads/server-freezes-when-using-git-to-update-ports-tree.88651/
>>
>>
On Apr 22, 2025, at 21:59, Mark Millard wrote:
> Sulev-Madis Silber wrote
> on
> Date: Wed, 23 Apr 2025 04:31:41 UTC :
>
> https://forums.freebsd.org/threads/server-freezes-when-using-git-to-update-ports-tree.88651/
>
> That, in turn mentions:
>
> the remote console shows an unresponsive, fr
Sulev-Madis Silber wrote on
Date: Wed, 23 Apr 2025 04:31:41 UTC :
https://forums.freebsd.org/threads/server-freezes-when-using-git-to-update-ports-tree.88651/
That, in turn mentions:
the remote console shows an unresponsive, frozen OS, unable to interact with.
If FreeBSD 13.4 can still swappi
On April 23, 2025 6:27:20 AM GMT+03:00, Mark Millard wrote:
>Sulev-Madis Silber wrote on
>Date: Wed, 23 Apr 2025 02:04:28 UTC :
>
>> yes, 2 * 8g partitions on separate disks, so i have 16g swap
>>
>> . . .
>>
>> >> >Van: Sulev-Madis Silber
>> >> >Datum: maandag, 21 april 2025 03:25
>> >> >.
On Apr 22, 2025, at 20:27, Mark Millard wrote:
> Sulev-Madis Silber wrote
> on
> Date: Wed, 23 Apr 2025 02:04:28 UTC :
>
>> yes, 2 * 8g partitions on separate disks, so i have 16g swap
>>
>> . . .
>>
> Van: Sulev-Madis Silber
> Datum: maandag, 21 april 2025 03:25
> . . .
>>
Sulev-Madis Silber wrote on
Date: Wed, 23 Apr 2025 02:04:28 UTC :
> yes, 2 * 8g partitions on separate disks, so i have 16g swap
>
> . . .
>
> >> >Van: Sulev-Madis Silber
> >> >Datum: maandag, 21 april 2025 03:25
> >> >. . .
> >> >>
> >> >> others don't get it at all and only suggest adding mo
On April 22, 2025 8:34:35 PM GMT+03:00, Toomas Soome wrote:
>
>
>> On 22. Apr 2025, at 18:23, Sulev-Madis Silber
>> wrote:
>>
>> well i don't have those errors anymore so there's nothing to give
>>
>> i've tried to tune arc but it didn't do anything so i took those things off
>> again
>>
yes, 2 * 8g partitions on separate disks, so i have 16g swap
but issues i see aren't "usual" memory problems. even building rust works, just
takes 10g swap and entire day. nothing will fail. nothing will lag
but what i see are kernel taking too much. as far as i understand. i can't
figure out w
> On 22. Apr 2025, at 18:23, Sulev-Madis Silber
> wrote:
>
> well i don't have those errors anymore so there's nothing to give
>
> i've tried to tune arc but it didn't do anything so i took those things off
> again
>
> right now i'm looking at
>
> ARC: 1487M Total, 1102M MFU, 128M MRU, 15
I wouldn't normally top post, but all I have is a generic question.
Do you have a swap partition setup?
(I'd use something like 6-8Gbytes for a 4Gbyte system.)
rick
On Tue, Apr 22, 2025 at 8:23 AM Sulev-Madis Silber
wrote:
>
> well i don't have those errors anymore so there's nothing to give
>
well i don't have those errors anymore so there's nothing to give
i've tried to tune arc but it didn't do anything so i took those things off
again
right now i'm looking at
ARC: 1487M Total, 1102M MFU, 128M MRU, 1544K Anon, 56M Header, 199M Other
942M Compressed, 18G Uncompressed, 19.36:1
Hi,
First, instead of writing "it gives vague errors", it really helps others on
this list if you can copy-paste the errors into your email.
Second, as far as I can see FreeBSD 13.4 uses OpenZFS 2.1.14. FreeBSD 14 uses
OpenZFS 2.2.X which has bugfixes and improved tuning, although I cannot cla
On Tue, Apr 22, 2025 at 3:34 AM Cedric Blancher
wrote:
>
> On Sun, 9 Mar 2025 at 00:02, Rick Macklem wrote:
> >
> > First off, I cross posted because I don't think many read freebsd-arch@.
> > There seems to be a nice market for Solaris style extended attributes.
> > Since ZFS is already wired fo
On 2025-04-21 11:46, Chris wrote:
On 2025-04-21 10:47, Dag-Erling Smørgrav wrote:
Chris writes:
Can I safely move my new kernel to say, kernel.new while running my
current
kernel as kernel and rebuild the new kernel with the kernconf corrections?
If you're booted into kernel.old you can jus
On Mon, Apr 21, 2025 at 03:37:55PM -0700, Rick Macklem wrote:
> Hi,
>
> I just spotted something in the NFS server that seems like
> it is a bug, but I thought I'd check.
> (Note that I have never seen this cause a problem, but I
> think it might if a server file system is being forced
> dismounte
On 2025-04-21 10:47, Dag-Erling Smørgrav wrote:
Chris writes:
Can I safely move my new kernel to say, kernel.new while running my current
kernel as kernel and rebuild the new kernel with the kernconf corrections?
If you're booted into kernel.old you can just build a new kernel and run
`make r
Chris writes:
> Can I safely move my new kernel to say, kernel.new while running my current
> kernel as kernel and rebuild the new kernel with the kernconf corrections?
If you're booted into kernel.old you can just build a new kernel and run
`make reinstallkernel` to replace the new (non-working)
Please note: Gleb is on vacation this week, so I'll be coordinating
stab-week this time. Please be sure to cc me on any problems you
encounter.
Warner
On Mon, Apr 21, 2025 at 2:00 AM Gleb Smirnoff wrote:
>
> Hi FreeBSD/main users & developers:
>
> This is an automated email to inform you that
On 2025-04-21 09:29, Warner Losh wrote:
On Mon, Apr 21, 2025 at 10:03 AM Chris wrote:
On 2025-04-21 00:23, Gary Jennejohn wrote:
> On Sun, 20 Apr 2025 12:19:45 -0700
> Chris wrote:
>
>> On 2025-04-20 01:15, Dag-Erling Smørgrav wrote:
>> > Chris writes:
>> >> Warner Losh writes:
>> >> > Mayb
On 2025-04-21 06:42, Warner Losh wrote:
Put 'da' back in. I'm pretty sure it's not optional. Well, maybe it is
optional, but you'll need nda if you do that and the kernel config
doesn't have that. While you have nvd, the default is to prefer nda to
nvd, even when nda isn't in the kernel (so more
On Mon, Apr 21, 2025 at 10:03 AM Chris wrote:
>
> On 2025-04-21 00:23, Gary Jennejohn wrote:
> > On Sun, 20 Apr 2025 12:19:45 -0700
> > Chris wrote:
> >
> >> On 2025-04-20 01:15, Dag-Erling Smørgrav wrote:
> >> > Chris writes:
> >> >> Warner Losh writes:
> >> >> > Maybe this is a custom kernel
On 2025-04-21 00:23, Gary Jennejohn wrote:
On Sun, 20 Apr 2025 12:19:45 -0700
Chris wrote:
On 2025-04-20 01:15, Dag-Erling Smørgrav wrote:
> Chris writes:
>> Warner Losh writes:
>> > Maybe this is a custom kernel without the label code.
>> It's an upgrade. It's 15 from ~11 mos ago. Yes a cus
Put 'da' back in. I'm pretty sure it's not optional. Well, maybe it is
optional, but you'll need nda if you do that and the kernel config
doesn't have that. While you have nvd, the default is to prefer nda to
nvd, even when nda isn't in the kernel (so more like an either or
choice than a bidding ch
On Sun, 20 Apr 2025 12:19:45 -0700
Chris wrote:
> On 2025-04-20 01:15, Dag-Erling Smørgrav wrote:
> > Chris writes:
> >> Warner Losh writes:
> >> > Maybe this is a custom kernel without the label code.
> >> It's an upgrade. It's 15 from ~11 mos ago. Yes a custom kernel. But
> >> I'm using
On 2025-04-20 01:15, Dag-Erling Smørgrav wrote:
Chris writes:
Warner Losh writes:
> Maybe this is a custom kernel without the label code.
It's an upgrade. It's 15 from ~11 mos ago. Yes a custom kernel. But
I'm using the same kernconf as before. Was label removed from generic
in the last 11 mos
Chris writes:
> Warner Losh writes:
> > Maybe this is a custom kernel without the label code.
> It's an upgrade. It's 15 from ~11 mos ago. Yes a custom kernel. But
> I'm using the same kernconf as before. Was label removed from generic
> in the last 11 mos.?
Please share:
- The output of the `w
Am 19.04.25 um 16:02 schrieb Mark Johnston:
On Sat, Apr 19, 2025 at 06:06:59AM -0700, David Wolfskill wrote:
Running:
FreeBSD g1-118.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #445
main-n276537-7121e9414f29: Fri Apr 18 12:36:30 UTC 2025
r...@g1-120.catwhisker.org:/common/S4/obj/usr/s
On 2025-04-19 22:23, Chris wrote:
On 2025-04-19 20:36, Warner Losh wrote:
On Sat, Apr 19, 2025, 8:51 PM Chris wrote:
Finally got a build world/kernel to complete. Following a
installkernel with a boot -s resulted in the inability
to mount root (/dev/gpt/FBSD15)
It’s a ufs2 filesystem. I boote
On 2025-04-19 20:36, Warner Losh wrote:
On Sat, Apr 19, 2025, 8:51 PM Chris wrote:
Finally got a build world/kernel to complete. Following a
installkernel with a boot -s resulted in the inability
to mount root (/dev/gpt/FBSD15)
It’s a ufs2 filesystem. I booted the 15-CURRENT
usb stick. It reco
On Sat, Apr 19, 2025, 8:51 PM Chris wrote:
> Finally got a build world/kernel to complete. Following a
> installkernel with a boot -s resulted in the inability
> to mount root (/dev/gpt/FBSD15)
> It’s a ufs2 filesystem. I booted the 15-CURRENT
> usb stick. It recognized it. I performed fsck on
>
On Sat, Apr 19, 2025 at 06:06:59AM -0700, David Wolfskill wrote:
> Running:
> FreeBSD g1-118.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #445
> main-n276537-7121e9414f29: Fri Apr 18 12:36:30 UTC 2025
> r...@g1-120.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64
>
> af
commit a3a88ed appears to have removed the function(s) needed by drm
kmod to build and run :-(
Michael
On 4/19/25 09:06, David Wolfskill wrote:
Running:
FreeBSD g1-118.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #445
main-n276537-7121e9414f29: Fri Apr 18 12:36:30 UTC 2025
r.
On Sat, Apr 19, 2025 at 01:29:15PM +0300, Konstantin Belousov wrote:
> On Sat, Apr 19, 2025 at 01:25:28PM +0300, Andriy Gapon wrote:
> > On 19/04/2025 12:39, Andriy Gapon wrote:
> > > On 19/04/2025 12:25, Andriy Gapon wrote:
> > > > On 19/04/2025 02:41, Konstantin Belousov wrote:
> > > > > RTLD_DEE
On Sat, Apr 19, 2025 at 01:25:28PM +0300, Andriy Gapon wrote:
> On 19/04/2025 12:39, Andriy Gapon wrote:
> > On 19/04/2025 12:25, Andriy Gapon wrote:
> > > On 19/04/2025 02:41, Konstantin Belousov wrote:
> > > > RTLD_DEEPBIND works by first iterating over all (recursive) DT_NEEEDED
> > > > object f
On 19/04/2025 12:39, Andriy Gapon wrote:
On 19/04/2025 12:25, Andriy Gapon wrote:
On 19/04/2025 02:41, Konstantin Belousov wrote:
RTLD_DEEPBIND works by first iterating over all (recursive) DT_NEEEDED
object for the object where the symbol is resolved, then by looking at
the global list of load
On 19/04/2025 12:25, Andriy Gapon wrote:
On 19/04/2025 02:41, Konstantin Belousov wrote:
Could it be that the module is linked to the main binary?
It does not appear to be so.
The binary:
$ ldd /usr/local/bin/mdb
/usr/local/bin/mdb:
libncursesw.so.9 => /lib/libncursesw.so.9 (0xbf191c9
On 19/04/2025 02:41, Konstantin Belousov wrote:
Could it be that the module is linked to the main binary?
It does not appear to be so.
The binary:
$ ldd /usr/local/bin/mdb
/usr/local/bin/mdb:
libncursesw.so.9 => /lib/libncursesw.so.9 (0xbf191c93000)
libtinfow.so.9 => /lib/libtin
On 2025-04-18 14:24, Dag-Erling Smørgrav wrote:
> Alastair Hogge writes:
>> Hmm I did try $(etcupdate -B), and I recall it also failing, so I
>> updated another host, and used -B with etcupdate, and it failed for
>> another reason:
>> [...]
>> ld-elf.so.1: Shared object "libmd.so.6" not found, req
On Sat, Apr 19, 2025 at 01:03:15AM +0300, Andriy Gapon wrote:
>
> I am trying to understand if RTLD_DEEPBIND should help in the following
> scenario or if I misunderstand its purpose.
>
> There is a program that has a parser based on lex/yacc, so there is function
> yyparse in the code and global
On Thu, 10 Apr 2025, Bjoern A. Zeeb wrote:
Hi,
and the firmware is now also gone from stable/14 (which at the same time
got a few bug fixes for LinuxKPI malloc and LinuxKPI 802.11).
In case you run into any issues updating from a supported 14.x or 15
(younger than a year old [3]) please follow-
Alastair Hogge writes:
> Hmm I did try $(etcupdate -B), and I recall it also failing, so I
> updated another host, and used -B with etcupdate, and it failed for
> another reason:
> [...]
> ld-elf.so.1: Shared object "libmd.so.6" not found, required by "mtree"
> *** Error code 1
This is _after_ in
On 2025-04-16 01:39, Dag-Erling Smørgrav wrote:
> Alastair Hogge writes:
>> After the build processes complete [...]
>>
>> $ doas su -
>> # cd /usr/src
>> # etcupdate -p
>> # env MAKEOBJDIRPREFIX=/tmp/fafnir make installkernel
>> # env MAKEOBJDIRPREFIX=/tmp/fafnir make installworld
>> # etcupdate
Alastair Hogge writes:
> After the build processes complete [...]
>
> $ doas su -
> # cd /usr/src
> # etcupdate -p
> # env MAKEOBJDIRPREFIX=/tmp/fafnir make installkernel
> # env MAKEOBJDIRPREFIX=/tmp/fafnir make installworld
> # etcupdate
>
> Here etcupdate exits with, "Failed to build new tree."
On 2025-04-17 00:45, Gary Jennejohn wrote:
On Wed, 16 Apr 2025 22:06:35 -0700
Chris wrote:
In an attempt to take advantage of all the work
done on iwlwifi recently. I pulled a fresh copy of src
at:
commit b836c229aa5ac345114f5986b6034ad3ed760da1 (HEAD -> main,
freebsd/main,
freebsd/HEAD)
Au
On 2025-04-17 00:19, Mark Millard wrote:
[Note: Your Email handling rejects my Emails, probably
because of Yahoo being involved.]
Looks like sonic317-22.consmr.mail.gq1.yahoo.com
Sorry. Looks like you were the victim of using the same IP
as a recent attacker. Filters against yahoo are short live
On Thu, Apr 17, 2025 at 05:37:13PM +0800, Zhenlei Huang wrote:
>
>
> > On Apr 17, 2025, at 5:17 AM, Mark Millard wrote:
> >
> > Context: An aarch64 PkgBase kernel and world boot under Parallels
> > on macOS (M4 MAX):
> >
> > FreeBSD 15.0-CURRENT main-n276258-c5773d366ecc GENERIC arm64 aarch64
> On Apr 17, 2025, at 5:17 AM, Mark Millard wrote:
>
> Context: An aarch64 PkgBase kernel and world boot under Parallels
> on macOS (M4 MAX):
>
> FreeBSD 15.0-CURRENT main-n276258-c5773d366ecc GENERIC arm64 aarch64 1500035
>
> . . .
> vtnet0: link state changed to UP
> Invoking IPv6 network d
On Wed, 16 Apr 2025 22:06:35 -0700
Chris wrote:
> In an attempt to take advantage of all the work
> done on iwlwifi recently. I pulled a fresh copy of src
> at:
>
> commit b836c229aa5ac345114f5986b6034ad3ed760da1 (HEAD -> main, freebsd/main,
> freebsd/HEAD)
> Author: Andrew Gallatin
> Date:
[Note: Your Email handling rejects my Emails, probably
because of Yahoo being involved.]
On Apr 16, 2025, at 23:46, Chris wrote:
> On 2025-04-16 22:40, Mark Millard wrote:
>> Chris wrote on
>> Date: Thu, 17 Apr 2025 05:06:35 UTC :
>>> In an attempt to take advantage of all the work
>>> done on
On 2025-04-16 22:40, Mark Millard wrote:
Chris wrote on
Date: Thu, 17 Apr 2025 05:06:35 UTC :
In an attempt to take advantage of all the work
done on iwlwifi recently. I pulled a fresh copy of src
at:
commit b836c229aa5ac345114f5986b6034ad3ed760da1 (HEAD -> main,
freebsd/main,
freebsd/HEAD
Chris wrote on
Date: Thu, 17 Apr 2025 05:06:35 UTC :
> In an attempt to take advantage of all the work
> done on iwlwifi recently. I pulled a fresh copy of src
> at:
>
> commit b836c229aa5ac345114f5986b6034ad3ed760da1 (HEAD -> main, freebsd/main,
> freebsd/HEAD)
> Author: Andrew Gallatin
> Da
On Apr 9, 2025, at 07:38, Mark Millard wrote:
> On Apr 9, 2025, at 06:41, Mark Millard wrote:
>
>> On Apr 9, 2025, at 05:05, Mark Millard wrote:
>>
>>> On Apr 6, 2025, at 19:29, Mark Millard wrote:
>>>
[Somewhat hand corrected "OCR" conversion of some console image content.]
Mark Linimon wrote on
Date: Wed, 16 Apr 2025 20:23:15 UTC :
> This is a known problem.
>
> All package sets are being rebuilt right now. Due to an unforseen
> circumstance, the first attempt to build them on the updated cluster
> machines failed. It appears that this has since been fixed.
>
> S
et", but I only noticed
the problem a few days ago. And apparenlty nobody else has seen it.
I'd imagine that the reported configuration is not too exotic.
So, not sure what and when get broken.
It could also be something with my build environment...
Forwarded Message
1 - 100 of 102447 matches
Mail list logo
