my local unbound session doesn't seem to be logging queries to the place I told it to, any suggestions?

Never mind, I found the solution. I was trying to log outside of its configured chroot directory -- duh

ok ty ivy

heh, having both my ethernet and graphics drivers built from the ports tree is a risky endeavour, I just learned

yesterday I did a pkg upgrade

turned on my computer to find myself in the console with no internet connection

turns out I forgot to rebuild those drivers... had to usb tether via my phone and go do that

14.3 is out: freebsd.org/releases/14.3R/announce

Greet good.

??

YAY

^^

I'm relatively new freebsd user.

yayy

stupid question to use freebsd-update -r <release> with custom-kernel , I must first run git pull -> git switch tag/14.3-RELEASE and build new kernel beofre I running freebsd-update right ?

nwe: build and install it, and reboot, yes. you also need to update the kernel before the userland

s/also/always

so build/install kernel, reboot build/install userland? but then I cant use freebsd-update if I using custom-kernel ?

xlibre port coming soon?

1. you could probably make it happen 2. it would seem to be counterproductive given their aggressively stated lack of values?

huh?

you could volunteer yourself to be a porter

ya i was just asking. you seem to be weird about it tho

"2. it would seem to be counterproductive given their aggressively stated lack of values?" like wtf? bug fixes and stuff is plenty value

I mean the anti-CoC stuff - «we won't turn anyone away» always ends up turning away a subset of competent programmers, who don't want to share space with people who want them dead.

so stay with your wayland junk

you just want to control others

like a nazi

even fbsd backed off their coc

[citation needed]

noob

I was going to go to bed in an hour or two, now I'm thinking of putting on yet another canteenful of coffee.

Webchat, hm. What time is it by you, demido ?

stop obsessing/harassing me weirdo. fbsd is for code that works, simple as. take your paranoid hysterics back to #redhat

I didn't come from #redhat, demido.

If you would be so kind as to indulge another question, what is your current relationship with the FreeBSD project?

The official Porter's Handbook may be found as a long single page at the following URL: docs.freebsd.org/en/books/porters-handbook/book

Someone else who has a better rapport with this person, if you could resend the link to the porter's handbook if it becomes necessary, that might help them a lot.

i asked when xlibre was going to be in ports. get over it. you don't need to be nitpicking everyone else controlfreak

lots of ppl, myself included, have been sharing code since before your coc religion existed. stop trying to make it into some life or death bs

you just come off mentally ill

"coc religion" _wat._

enjoy some of the coffee you brought up for no reason and ask yourself honestly if you haven't actually become the person you hate. you should be better

Well that just came out of nowhere.

I mean, _technically_ there are a couple of screws loose up here *shakes their head around a bit*, but I fail to see how that's relevant to this discussion. What is your level of interest in working with the ports tree code yourself? By way of a tidbit of friendly advice from a hobby dev: I've actually been hacking around in a copy of the ports tree, at x11-server/xorg-server (this is the port you

would copy in order to get started on porting Xlibre as they're similar programmes at this stage) - it's a little hard to understand if you aren't that "up" on how FreeBSD's make(1) utility works. The manpage of that is a bit hard to read sometimes.

i respect that you're acknowledging that you're broken. now's the important next step to start fixing your shit. you can do it if you really try

Not the way you think, young padawan.

you might be surprised what i know about you

You know my dedcated server's IP address, my IRC nickname, and possibly whatever I've published on my website, if you've yet found that. That's it.

Prove me wrong.

Are you in a position where you can fulfill your assertion number 2? If not why would you think it?

Meanwhile, I don't think I'm going to take advice from someone who called me a control freak two (2) times, a Nazi once, a weirdo, a paranoid hysteric (untrue, and also a shade misogynistic), mentally ill, accused me baselessly of nitpicking, called a trend of having community rules aiming to ensure a developer community can collaborate with less friction, as well as aiming to limit the damage

someone with a harmful agenda can do, a "religion", and this sentence got too long for me to close it grammatically correctly.

The remainder of this discussion could well be had in #freebsd-social; yes including that about technical aspects of porting.

good morning everyone

getting my laptop ready for freebsd 14.3 :)

good morning bsdbandit !

keep us posted on how all that goes! I hope it goes well for you!

thank you will do

Upgraded from 14.2-RELEASE to 14.3-RELEASE without any issue. Not a huge thing, but it seems /etc/motd (/var/run/motd) is missing under 14.3-RELEASE?

tercal, that is odd. I'm on 14.3 and see both

how do i force LDAP clients like ldapsearch to use simple authentication in /usr/local/etc/openldap/ldap.conf? by default they try GSSAPI, which i don't want

markmcb: Strange.

Er, freebsd.org/releases has a mistype: files.eracc.org/uploads/freebsd/Scr…ot%20at%202025-06-10%2006-09-52.png Where should I report that?

if i'm on 14.1 what should i run to upgrade to 14.3? i usually do clean installs but i wanna see how well fbsd handles jumping up 2 minor versions at once

demido: Try `man freebsd-update`

demido, properly done minor version upgrades are quite trivial, impact-wise.

Even major version upgrades are pretty painless, so long as you go into it informed.

(Read /usr/src/UPDATING)

Now skipping major versions when upgrading can be a sticky wickit.

Again, it comes down to being informed, and sometimes you need to upgrade incrementally.

I did an 11.4-RELEASE to 13.3-RELEASE upgrade recently, CrtxReavr. One just has to make sure the edits to the config files are good. I also had to run 'freebsd-update install' twice after reboot. Otherwise it was relatively painless.

Er, make that 13.5-RELEASE. :D

lf_

wups, window focus

if you install 14.2 freebsd, fetch/checksum/install base/kernel/lib32/(ports)/... what happens when you upgrade 14.3, how do update ports?

quickrr: issue command "pkg update && pkg upgrade"

quickrr, for ports I use: portsnap fetch && portsnap update

quickrr: Do you build ports yourself? If so, which method do you use?

why I asking is because my apple macbook air I need to add some

I've just installed FreeBSD 14.3 on my old ThinkCentre M900 (Intel i5-6500T). During the installation I choose to install the Intel Skylake kmod driver. After booting into my installed system I run sysrc kld_list+=i915kms, and then kldload i915kms. From the last command I get the error message that it couldn't be found. So I install drm-kmod. In the post-install instruction it says

> Please note that this package was built for FreeBSD 14.2.

> If this is not your current running version, please rebuild it from ports to prevent panics when loading the module.

Someone on the FreeBSD Discord server asked me to increase the prio of the FreeBSD-kmods repo and switch over to latest for that repo. Did that and ran pkg update and pkg upgrade, but nothing got installed.

Are I doing something wrong?

what did you install?

drm-61-kmod ?

no, just drm-kmod

I.e. pkg install drm-kmod

As it says in the handbook

It looks like that if I just install `drm-61-kmod` all my problems go away

that's what I use

I actually compile the port, but yeah try the pkg first