i'm sort of hoping that between now and 16.0, someone will learn how to use pkgbase and have enough time to wtfm for it

it would be a little awkward if we dropped dist set support and still didn't have any pkgbase docs

I really like the current organization of base upgrading as a cohesive whole. I am sure the system will boot and run. And then upgrade the ports/pkgs.

I am a little worried that putting everything in pkgs to upgrade will upset that robust paradigm. See the "pkg delete -a" issues.

i've always found it awkward, just worked with what i have.

ivy: Yeah. :/

Although, there has been plenty of talk about separating "pkg" and "pkgbase". That could clear a lot of things up and avoid things such as "pkg delete -a". But, we'll see what comes to fruition.

that will never happen

I can't imagine it happening. But, there does need to be some kind of fail-safe in place to avoid just wiping your system via pkg.

you already can't do that, pkg delete -a will refuse to delete anything as long as you have at least one vital set installed (which always happens in a normal install)

the specific problem that came up before was people using 'pkg delete -af', i.e., 'delete all my installed packages and override all safeguards intended to prevent breaking your system'

Yes. Trying to start from scratch via pkg was never an issue in the past. A "pkg delete -af" might catch a lot of people by surprise.

perhaps pkg delete -fF should be required to delete vital packages, or something like that... there was very little useful discussion about actual solution in the previous thread, just a lot of ranting

Agreed. Lots of ranting and no solutions. An additional flag could be a good solution.

(i don't like pkg ... -f much anyway, i think it's too ungranular and too dangerous to ever use... so reworking that might solve both problems, if someone wanted to)

I don't use "-f" often (unless it's an update/upgrade situation)

But, IIRC, the problem I had when trying to "pkg delete -a" was that I had to accept the removal of the request to delete "vital" packages.

So, 160 or so (Y/n) prompts later, I was able to remove non-base packages.

if you're trying to remove ports, i believe 'pkg -r FreeBSD-ports delete -a' is now supported (not 100% sure there, maybe it's not merged yet)

er, 'pkg delete -a -r FreeBSD-ports', i mean

I believe that's been merged? I haven't tested it, but I did see it.

Yeah.

hm, it's not in 2.6.2 apparently, wonder what's going on there

Once I saw what was happening, I could just ignore "^FreeBSD-\*" packages. Worked fine. But, I can see how mistakes could be made.

Erm? I thought that was merged like 6 weeks ago?

Nope.

I see nothing about it. Bummer.

ek: we might be thinking of pkg-unregister(8), which is what's used for depkgbasify

ivy: Ah, yes. That could be exactly it.

q:q

this seems excessively slow: people.freebsd.org/~ivy/tmp/pkg-create.txt - what is it doing? hashing?

dch: i see you're maintaining the go-anubis port. ai crawlers seem to have found an expensive gitea endpoint not covered by REQUIRE_SIGNIN_VIEW = expensive, so I'm looking into deploying it. i see it has some kinda meh/tbd data poisoning feature and would rather transparently deliver some cached documents from rnsaffn.com/poison3 – any idea if that's doable?

morning.

jadawin: Howdy

here's a patch for cgit crash on cgit.freebsd.org git.zx2c4.com/cgit/commit/?id=0d8e5fbc31e10

hello, just installed KDE plasma ... everything looks smooth, but keyboard layout kinda not working

what parts are not working?

How does one patch KDE2 under FreeBSD?

patch it to do what?

I'm trying to get brightness control to work on this laptop using devd.

All the examples I've found assume the keypress sends "brightness up" or "brighness down", but on this laptop it's sending what it thinks the actual value should be.

Is there a way, in a devd config, to use the value of a "match" rule as an argument to the "action" rule?

i just added backlight to my waybar. but acpi_*.ko often gets those keys to work without devd

(i've not done it with devd)

I've got acpi_video and acpi_wmi loaded. I guess I thought acpi_video was getting it into devd in the first place.

Like, it sees this in devd: !system=ACPI subsystem=Video type=brightness notify=95

I think that's coming from acpi_video?

anth: i am not a devd expert, but if that's the event, i think you can use $notify in the action to get the value?

good day #freebsd

Ok this is weird. After upgrading this one machine to 15, I cannot log in as root, nor does syslogd start.

after spending some time on the tunables, I have 14.4-RELEASE running stable

zerotime: Howdy

On console, after logging in as root and getting the MOTD, it hangs. I press ctrl-T and get "load: 0.21 cmd: sh 5060 [ttydcd] 1.08r 0.00u 0.00s 0% 3520k"

thank you freebsd-devs for another quality release

Similarly I get syslogd hanging in ttydcd - until I remove the output to /dev/console from syslogd.conf

I really appreciate the legacy support!

!inspire

Do what you can, with what you have, where you are. -Theodore Roosevelt [zenquotes.io]

Ltning: did you botch a merge on one of the files

It has booted successfully before today

After -15

good day Ltning

zerotime: last time I tried 15.x (two months ago) it was not able to connect to Ethernet (re0) to obtain IP over DHCP. 14.3 does it well.

checkpoint: I think 14.3 does better than 14.4

I didn't have to mess with any tunables for 14.3

however, 14.4 is still solid

zerotime: I have not tried 14.4 yet.

It just came out a couple days ago

yes

Been having trouble with the ath driver in 14.4

Heh. ttys was indeed theproblem. Copied it from a working box ...

but I finally got it working

It still complains but atleast it fails gracefully now instead of purely crashing

What was the tunable you ended up needing?

(also good day to you too :) )

I'm not sure which one fixed it yet, but it was a couple handful of patches

mostly dealing with disabling N-mode features

I haven't figured out how to persist it yet - /etc/rc.conf isn't fully working for wlan0 to include all my switches

what are the extra options?

ivy, that was exactly right, thank you!