Re: git: 624b7beed5ac - main - kadm5: add -Wno-alloc-size-larger-than

2025-08-03 Thread Lexi Winter
Lexi Winter: > kadm5: add -Wno-alloc-size-larger-than this broke main on clang. i am very sorry about that, i am about to commit a fix once the test build finishes here. signature.asc Description: PGP signature

Re: epair(4)

2025-07-28 Thread Lexi Winter
Dag-Erling Smørgrav: > Adrian Chadd writes: > > qroxana writes: > > > What's the best practice for setting up bridge0 on a NFS root > > > system? [...] > > That's an interesting problem that I don't think was even thought > > about when bridge(4) was added to FreeBSD. [...] I /think/ the tftp

Re: ssh errors, libgssapi_krb5

2025-07-28 Thread Lexi Winter
Herbert: > On Mon, 28 Jul 2025, at 15:32, Lexi Winter wrote: > > dlopen: Cannot open "/usr/lib/libgssapi_krb5.so.121" > > g...@git.le-fay.org: Permission denied (publickey,gssapi-with-mic). > > Have you rebuilt ports like curl, git, etc.? this isn't related to

ssh errors, libgssapi_krb5

2025-07-28 Thread Lexi Winter
hello, on recent (last ~2 days) main with WITH_MITKRB5, ssh with GSSAPI seems broken: % git push lf dlopen: Cannot open "/usr/lib/libgssapi_krb5.so.121" dlopen: Cannot open "/usr/lib/libgssapi_krb5.so.121" dlopen: Cannot open "/usr/lib/libgssapi_krb5.so.121" dlopen: Cannot open "/usr/lib/libgssap

Re: LLVM broken on main (arm64)?

2025-07-27 Thread Lexi Winter
Dimitry Andric: > On 27 Jul 2025, at 12:44, Herbert J. Skuhra wrote: > > > > after updating from main-n279078-1f2c178e5688 to > > main-n279105-9b3055d0d4bc (arm64) I have the following issue: > > > > $ cc > > PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and include > > the cra

Re: heads up (15.0 pkgbase): gssd, kerberos, kernel

2025-07-25 Thread Lexi Winter
sorry, i forgot to mention another change: the online manual pages in sections 4 and 9 have been moved to a new package, FreeBSD-kernel-man. if you want these manpages, you should install that package. if you install a new system using the pkgbase installer (bsdinstall) from caddfcd546e0 or later,

heads up (15.0 pkgbase): gssd, kerberos

2025-07-25 Thread Lexi Winter
hello, the FreeBSD-gssd package has been added (76446b5aa350). the FreeBSD-kerberos-kdc-dev package has been deleted (b98d0566b2bd). manual action required: - if you use gssd, you must install the FreeBSD-gssd package when you update past 76446b5aa350. - if you have FreeBSD-kerberos-kdc-dev

Re: ifconfig_bxe0_ipv6="inet6 accept_rtadv" seems to break bridging

2025-07-24 Thread Lexi Winter
Dag-Erling Smørgrav: > void writes: > > ifconfig_bridge0="203.0.113.2/24 addm bxe0 addm tap0" > > missing `inet` here. not required. however, i think it should be. the problem is if we start requiring this it's going to break *everyone's* network configuration and i can't come up with a better

Re: ifconfig_bxe0_ipv6="inet6 accept_rtadv" seems to break bridging

2025-07-24 Thread Lexi Winter
void: > On Thu, 24 Jul 2025, at 14:08, Lexi Winter wrote: > > you should set accept_rtadvd on the bridge interface, not the member > > interface. setting it on the member interface will try to assign the > > SLAAC address to the member, which is not allowed. > OK. No

Re: ifconfig_bxe0_ipv6="inet6 accept_rtadv" seems to break bridging

2025-07-24 Thread Lexi Winter
void: > I've found ifconfig_bxe0_ipv6="inet6 accept_rtadv" breaks bridging > on a dual stack interface in unless some manual hoops are jumped through. > > net.link.bridge.member_ifaddrs is the default ("0") here. >[...] > Adding ifconfig_bxe0_ipv6="inet6 accept_rtadv" and then rebooting causes th

heads up (15.0 pkgbase): Kerberos package names

2025-07-24 Thread Lexi Winter
hello, commit c7da9fb90b0b enabled WITH_MITKRB5 by default, which changed the name of the Kerberos packages from FreeBSD-kerberos* to FreeBSD-krb5*. i have just landed 4cb1baa7d85c to undo this change, so the packages are now called FreeBSD-kerberos* again, no matter whether you build with MIT Ke

Re: if_bridge(): IPv6 EUI-64 seemingly not working

2025-06-17 Thread Lexi Winter
FreeBSD User: > net.link.bridge.inherit_mac: 1 > [...] > > ether 4c:52:62:2b:05:eb > inet6 fe80::5a9c:fcff:fe00:393a%bridge0 prefixlen 64 scopeid 0x6 i was able to reproduce this: # sysctl net.link.bridge.inherit_mac=1 net.link.bridge.inherit_mac: 0 -> 1 # ifconfig bridge1 create

Re: if_bridge(): IPv6 EUI-64 seemingly not working

2025-06-11 Thread Lexi Winter
A FreeBSD User: > When it comes to obtain an IPv6, CURRENT, in contrast to 14-STABLE, > fails to set the host part according EUI-64. The resulting 64 host > bit, which are considered to contain the 48 bit of the MAC, do contain > anything but not anything similar to ANY of the attached NIC/NICs.

Re: HEADS UP: 15.0 pkgbase, manual action required on upgrade

2025-05-28 Thread Lexi Winter
Ronald Klop: > This makes me think of the /usr/ports/MOVED construction. Maybe > something similar can be useful for base pkgs. ideally this isn't something we want to be doing on an ongoing basis. at the moment there are a number of files that are installed in the wrong package by accident (usua

HEADS UP: 15.0 pkgbase, manual action required on upgrade

2025-05-27 Thread Lexi Winter
hello, if you use 15.0 with pkgbase, there are two recent changes which might require manual intervention following "pkg upgrade": 7672d8d81ac1 moved ctld into the new FreeBSD-ctl package. if you use ctld, you should install this package. cc8c77c9e036 moved toolchain utilities (including ar, nm

Re: Updating build and jail manual pages to include missing or obscure information

2025-05-22 Thread Lexi Winter
resin-free...@g-cipher.net: > On 5/22/25 09:16, Lexi Winter wrote: > > note that 'make world' already doesn't work unless you're using DESTDIR > > (or you set a special make knob) so it shouldn't be documented as a way > > of upgrading the system in

Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument”

2025-05-22 Thread Lexi Winter
void: > On Mon, May 19, 2025 at 11:33:50AM +0100, Lexi Winter wrote: > > in short, following this commit... > > > > b61850c4e6f "bridge(4): default net.link.bridge.member_ifaddrs to false" > > https://cgit.freebsd.org/src/commit/?id=b61850c4e6f6b0f21b36da723

Re: Updating build and jail manual pages to include missing or obscure information

2025-05-22 Thread Lexi Winter
Warner Losh: > On Thu, May 22, 2025, 7:40 AM Alexander Ziaee wrote: > > There seems to be a rough consensus that we should remove the world and > > kernel targets. > > I object to removing these. I do agree we should document other methods, > but my spidt sense is this is still in use... note th

Re: Un-sucking EINVAL (was: ip# on bridge members)

2025-05-21 Thread Lexi Winter
Poul-Henning Kamp: > The ip# on bridge member interfaces is yet another example of why > "EINVAL" is the undisputedly least helpful errno of them all. > > The laconic "Invalid argument" leaves both the userland programmer > and the user to guess what might be wrong. you are completely right. si

Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument

2025-05-20 Thread Lexi Winter
A FreeBSD User: > I need a IPv6 prefix on bridge0. With the "wrong/faulty" concept I > simply used > > rtsold_flags="-iu igb0" > > within /etc/rc.conf. Changing this line to > rtsold_flags="-iu bridge0" while bridge0 is up and running doesn't work, > neither does "rtsol > bridge0" show any resu

Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument

2025-05-19 Thread Lexi Winter
Kristof Provost: > On 18 May 2025, at 21:24, Marek Zarychta wrote: > > W dniu 18.05.2025 o 19:48, Alexander Leidinger pisze: > >> You want to make it work without this. Short: use the IP on the > >> bridge itself, not in the member IF. > > I'm not sure we should be dictating to Oliver what he must

Re: epair(4)

2025-05-16 Thread Lexi Winter
Marek Zarychta: > Thanks for the statement. Some may consider this a POLA violation. If you > insist on removing the sysctl, it will require additional work to update all > existing vm-bhyve and jail setups before upgrading to 16.0-RELEASE, whenever > it is released. i appreciate your concern and

Re: epair(4)

2025-05-16 Thread Lexi Winter
Michael Butler: > On 5/16/25 15:52, Lexi Winter wrote: > > i don't really want to add a kernel message here for something that only > > affects a small percentage of users, unlike net.add_addr_allfibs which > > affected everyone who uses multiple fibs. > That "sm

Re: epair(4)

2025-05-16 Thread Lexi Winter
Marek Zarychta: > Yes, it requires at least head up, similar to old one, known from fibs : > WARNING: Configuring address on bridge(4) member has been turned off by > default. Consider tuning  net.link.bridge.member_ifaddrs if needed. i don't really want to add a kernel message here for somethi

Re: RFC: Solaris style extended attributes for FreeBSD

2025-05-04 Thread Lexi Winter
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

Re: buildworld FAILURE:googletest

2024-10-30 Thread Lexi Winter
On 30/10/2024 20:42, Simon J. Gerraty wrote: Would need more context to comment. Do you have filemon(4) loaded? yes. meta mode makes very little difference for a clean tree build, it is only update builds where the .meta files become super useful. this was a build updating an existing ob

Re: buildworld FAILURE:googletest

2024-10-30 Thread Lexi Winter
On 29/10/2024 06:01, Larry Rosenman wrote: on a clean /usr/obj it works.  The below was metamode. i also just ran into this with meta mode + make buildworld-jobs, src ~22429a464a5f4f6bb5a056aae1353985db83b721. ld: error: undefined symbol: testing::internal::MakeAndRegisterTestInfo(char cons

ZFS panic on shutdown

2024-10-22 Thread Lexi Winter
hello, i thought i should mentioned that after upgrading to FreeBSD 15.0-CURRENT #3 lf/main-n269068-2cff93ced1d: Wed Oct 23 02:48:20 BST 2024 srcma...@hemlock.eden.le-fay.org:/data/build/obj/freebsd/data/build/src/freebsd/lf/main/amd64.amd64/sys/GENERIC which is based on commit 53314e34d5e8

Re: 15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT

2024-04-07 Thread Lexi Winter
Mark Millard: > On Mar 30, 2024, at 12:44, Lexi Winter wrote: > > when the problem happens, with USB_DEBUG enabled, the kernel logs: > > > > uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT > > uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disab

15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT

2024-03-30 Thread Lexi Winter
hello, i'm using 15.0 (f66a994d59) on an 4GB RPi4 with a USB<>SATA adapter for the root disk: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA (0x174c:0x55aa) ugen0.3: at usbus0 umass0 on uhub1 umass0: on usbus0 umass0: SCSI over

Re: after trivial update, 15.0 ARM64 system no longer boots

2024-03-25 Thread Lexi Winter
Lexi Winter: > i am not really an expert on either ARM64 in general or on the RPi > hardware in particular. could anyone suggest how i could debug this > problem, e.g. to get more information about why the system won't finish > booting? i dug into this a bit more, and to answe

after trivial update, 15.0 ARM64 system no longer boots

2024-03-15 Thread Lexi Winter
hi lists, i have a FreeBSD 15.0/arm64 system, an RPi4, which was previously running 15.0 with pkgbase. i rebuilt main on my pkg server and updated the RPi with 'pkg update', which only included ~2 commits neither of which seemed like they had anything to do with booting, but after the update, the

Re: 42fdcd9fd917 broke my snd_uaudio(4)

2024-02-22 Thread Lexi Winter
hi Florian, Florian Walpen: > I have a Scarlett 18i20 myself, but maybe a different generation - it has 18 > recording channels as its name suggests. Is 20 recording channels correct for > your device? this is a 3rd generation 18i20; as well the usual physical inputs it has a stereo loopback c

42fdcd9fd917 broke my snd_uaudio(4)

2024-02-21 Thread Lexi Winter
hello, since the commit: 42fdcd9fd917 snd_uaudio(4): Fix config detection with defaults set. my snd_uaudio(4) no longer works. the symptom is that applications attempting to play audio hang forever, and no audio is produced. reverting this commit fixed the problem. the issue only occurs if i h

Re: meta mode

2024-01-27 Thread Lexi Winter
void: > But, from time to time, one might be required to make > cleanworld && make cleandir (to be sure) && make clean (to be *really* sure) > What circumstances & notices in /usr/src/UPDATING would require it? one case this is required in non-meta mode is if you use pkg(8) (e.g., with poudriere

Re: poudriere: swap_pager: out of swap space

2024-01-15 Thread Lexi Winter
Mark Millard: > You seem to be under the impression that "Inact" means "page is not > dirty" and so can be freed without being written out to the swap > space. indeed, i was, because this is how sysutils/htop displays memory usage: top(1) Mem: 8502M Active, 15G Inact, 1568M Laundry, 5518M Wired,

Re: poudriere: swap_pager: out of swap space

2024-01-12 Thread Lexi Winter
Ronald Klop: > On 1/11/24 03:21, Lexi Winter wrote: > > i'm building packages with poudriere on a system with 32GB memory, with > > tmpfs and md disabled in poudriere (so it's using ZFS only) and with the > > ZFS ARC limited to 8GB. > My first guess would be

poudriere: swap_pager: out of swap space

2024-01-10 Thread Lexi Winter
hi list, i'm having a recurring problem with poudriere that i hope someone might have an idea about. i'm building packages with poudriere on a system with 32GB memory, with tmpfs and md disabled in poudriere (so it's using ZFS only) and with the ZFS ARC limited to 8GB. running poudriere produces

Re: bridge(4) and IPv6 broken?

2024-01-03 Thread Lexi Winter
Patrick M. Hausen: > > Am 02.01.2024 um 13:56 schrieb Jan Bramkamp : > > IPv6 enabled interfaces need a link-local address for normal > > operation. Please set the auto-linklocal flag on the bridge and try > > again. > > And remove the link-local address from alc0. A bridge member must not have >

bridge(4) and IPv6 broken?

2024-01-01 Thread Lexi Winter
hello, i'm having an issue with bridge(4) and IPv6, with a configuration which is essentially identical to a working system running releng/14.0. ifconfig: lo0: flags=1008049 metric 0 mtu 16384 options=680003 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128