Latest activity

That entry in Updating is about as explicit as one could want. I've gotten into the habit of commenting out loading of the drm bits in rc.conf before rebooting into console just in case. Then when you are around EOL of one version and quarterly...

This would be related with that nvidia things are not in FreeBSD[-pors]-kmods repo and in main FreeBSD[-ports] repo, pkgs are built against 14.2 until the end of September, causing mis-match between kmod and kernel. See Comment #23 for more...

For anyone using quarterly repo (default for *-Release), avoid upgrading in early January, April, July and October. In these timing, new quarterly (*Q1, *Q2, *Q3 and *Q4) branch is created and all pkgs are build with new quarterly (now 2025Q4)...

It would become better once kmod builder starts properly building them. The changes for it (split out kmod parts from x11/nvidia-driver* into x11/nvidia-kmod*) is already committed but not being built, and now bapt@ is looking into the reason...

Yes My alias csh update pkg upg -n Or if it's too late zfs clone [dataset]@[name_snapshot] new BE

That fixed it! I did sudo sysrc kld_list+=linux64 and rebooted before I saw your updated command. I just had to remove the quotes because I already had nvidia-modeset in the list. Thank you very much! Now I can go and update my main 14.3-RELEASE...

Does it show dev.amdtemp nodes at all? Like this root@kg-core2:~ # sysctl dev.amdtemp dev.amdtemp.0.ccd0: 58.0C dev.amdtemp.0.core0.sensor0: 69.6C dev.amdtemp.0.sensor_offset: 0 dev.amdtemp.0.%parent: hostb0 dev.amdtemp.0.%pnpinfo...

Also related: https://forums.freebsd.org/threads/samsung-galaxy-book4-edge-arm64.97003/ my vote is "no". It will, some day, but that day is not here yet.

I'm starting to think the upgrade issues some have are because of Linux behavior. "OMG an upgrade came out 3 seconds ago I must upgrade" instead of sitting and thinking "should I or should I not"

To be auto-assigned, Bugzilla PRs need to start with "<category>/<portname>". Then Bugzilla sends email and perhaps changes the assignee (if they are @FreeBSD.org). If anyone sees ones that aren't, just email bugmeister@FreeBSD.org, and we will...

I would instead email the maintainers directly. OTOH it seems like someone from at least ports-secteam@ has replied on the 28th.

I edited it in rc.conf, moving the IP argument from the wlan0 to the bridge0 line: ifconfig_bridge0="inet 10.x.x.x/8 addm re0 addm wlan0 up" It has to go at the beginning, or it won't work. It took a reboot for this and other settings to show up...

I guess no one has yet posted the policy regarding maintainer timeouts. There... done.

Before, I've added your BSD wiki listed in French to nature-of-bsd-operating-system-providers.99042 So, there's German as well. Yours should be the goto for French. If more pop up, a new thread on Wikis would be suitable. A few major languages...

Tested on FreeBSD 14.3 manual version 20251009 Note: It is assumed that the user has secured/set a PIN on the Ubikey key before using the instructions below. I am installing the necessary packages # pkg install yubico-piv-tool pcsc-lite ccid...

many years ago at an ISP I had to connect a Linux server of mine to a storage provided over iscsi, but with no success. I remember installing openindiana just to test this connection and everything worked flawlessly from the first try :)

I run USL SVR4 4.0.4 on my vintage gear with excitement; it brings me joy. Self-hosting SVR4 is fun. FreeBSD is an awesome SCSI target for SVR4, especially with a RAIDZ backing store.

I started my unix career with AT&T-NCR which was basically the prototype SVR4. I wasn't impressed to say the least (it was 1997, before that that for me there was only Linux Slackware and whatever unix machine we had at uni). In late 1999 I...

Try removing any Qt6 related libs under /usr/local/lib/compat/pkg. You may temporarily move them away if you don't feel comfortable in getting rid of them completely.

KDE Discover in FreeBSD works only for KDE addons, doesn't see any apps or packages and neither can track updates.

Well, I was just updating a 14.3-RELEASE and just updating any packages that need to be updated. On one machine (my main workstation), I have an NVidia card, which often causes issues with an upgrade, but, even without the various patches...

Also no issues here, save for some expected nvidia ones. By expected I mean when any nvidia package I have is upgraded, I often have to do a port upgrade on nvidia-drm-kmod which pulls in any other nvidia stuff that is needed.

fwiw, no upgrade issues here either.

No. But we have it here everytime some patch, or minor update occurs: "!!!!!!!!NOTHING WORKS ANYMORE!!!!!EVERYTHING IS BROKEN!!!!!DON'T DO THE UPDATE!!!!IT KILLS EVERYTHING!!!!!!!!!" While in 99% of all cases one of the following points turned...

I get: I must see what to do ... EDIT: There is nothing to do, my domains were and are verified. I do not get info probably because few mails are sent and hence no spam.

I don't have it either, it was added somewhere between the spammer and google then, it's not specified in the headers on which hop the antispam software was run. but you mentioned google's postmaster tools. I added my domain and I see that they...

The OS doesn't need anything from it. And to prevent accidental issues I've set it to not be continuously mounted. It only gets mounted temporarily whenever I need to update loader.efi (after a zpool upgrade for example).

my last update removed the libreoffice pl-libreoffice and py311-lxml5 packages (FBSD 14.3)

sudo sh -c 'sysrc kld_list+=" linux64";shutdown -r now'

Do separate repo for pudirere jail builds, give it different priority in /usr/local/etc/pkg/repos/<foobar>.conf and you'll not mix ports and pkgs. 🫱🫲 (Khaby hands) But I don't think that's a problem here since everything works just fine with...

Tested on FreeBSD 14.3 manual version 20251009 Note: It is assumed that the user has secured/set a PIN on the Ubikey key before using the instructions below. I am installing the necessary packages # pkg install yubico-piv-tool pcsc-lite ccid...

I created my own instructions: https://forums.freebsd.org/threads/yubiko-yubikey-5-nfc-on-freebsd.99529/

Well, I like running at least one -STABLE because I'm always testing (only, not officially). TBH I'm not a dev, but I like to be among firsts to have new goodies in the base, like awk, bc, etc. 😁 Yeah, this wasn't a very helpful post, sorry 🤷‍♂️

14.3-p4 (latest); KDE/Plasma 6.4.5; vlc 3.0.21. All works fine with both H.264 and H.265 .mp4's for me

I just updated two 14.3-RELEASE machines the last two days ordinarily with freebsd-update to 14.3-RELEASE-p3 14.3-RELEASE-p3 14.3-RELEASE-p4 after I first upgraded pkg: 2.2.2 -> 2.3.1 and everything went fine - as always. Not even remotely the...

What worked for me on 14.3-RELEASE: pkg install u2f-devd and restart devd add myself to the u2f group hw.usb.usbhid.enable="0" in /loader.conf; reboot Firefox: security.webauth.u2f true security.webauth.webauthn true...

Personally, I had no troubles with latest pkg upgrades, but I was posting about similar issue few times before and about my way to mitigate this potential problem, please see and a few posts bellow quoted post. 14.3-RELEASE-p4; pkg 2.3.1; all...

I believe you're right, if memory serves me NCR Unix was SVR4.2. What I meant with my post it that it was a direct derivative from AT&T SVR4 and it was actually marketed as AT&T-NCR. I started with the company in 1997 but they were using those...

Wasn't this SVR4 based Unix/NS released back in '91? I'm just curious, why they didn't go with SVR4.2 / UnixWare (first released in '92) later, and what was their upgrade path? Honest question from armchair Unix archaeologist 😎

I believe you're right, if memory serves me NCR Unix was SVR4.2. What I meant with my post it that it was a direct derivative from AT&T SVR4 and it was actually marketed as AT&T-NCR. I started with the company in 1997 but they were using those...

Wasn't this SVR4 based Unix/NS released back in '91? I'm just curious, why they didn't go with SVR4.2 / UnixWare (first released in '92) later, and what was their upgrade path? Honest question from armchair Unix archaeologist 😎

I started my unix career with AT&T-NCR which was basically the prototype SVR4. I wasn't impressed to say the least (it was 1997, before that that for me there was only Linux Slackware and whatever unix machine we had at uni). In late 1999 I...

I started my unix career with AT&T-NCR which was basically the prototype SVR4. I wasn't impressed to say the least (it was 1997, before that that for me there was only Linux Slackware and whatever unix machine we had at uni). In late 1999 I...

Normally I set a 'WAN' interface, whether that be cellular or wired and the bridge everything else. DHCP on the WAN. Static IP on the bridge, not members. Simply 'up' the member interfaces. I seem to remember a quirk where Atheros needs MAC...

I'm lost. A question on bridging. When you do bridging, does it give the device behind your BSD computer the IP address of the Network ID of behind the BSD box, or does it give it the IP address of the modem, that the BSD box uses to access the...

I thought there were two ways to network an Software Access Point.. Bridging and Routing. DHCPd or similar are a different layer right? I do all LAGG where ever possible now. So that is another approach. Have you ruled out dns/dnsmasq? I am a...

I'm not sure if I'll still need nsd or any DNS for this small scale purpose. Was struggling with the zone file. Finally got the name to the alias to work from /etc/hosts: 10.1.0.1 disney disney.lan 10.1.0.2 world world.lan Now I'm...

Up until SunOS 4.x You can run `ssh menu@tty.sdf.org` to play with older BSD, SunOS 4.1, HP/UX, HP/UX, Irix, Ultrix & older Unix editions.

To make ftpd a little more secure, you can set it to a specific static IP, which you've set an IP alias to. In your /etc/rc.conf, add to ftpd_flags=: -a followed by the static IP address. You can see this after restarting the service, and typing...

This is the exact reply I did not want to get. I'll refrain from posting sarcastic remarks about the discovery of grep. It is what it is and I don't like it.