Here's a base packages question. I've managed to get the 15.1 installer past network configuration. What is the "optional" set? That's a little vague.

Never mind - found this: forums.freebsd.org/threads/whats-op…em-components-during-install.101249

Maybe that was incomplete. That only tells you if you're already using base pkgs at a guess: bpa.st/2ZQA

My understanding is that mostly only stable versions are pulled into ports. If they break on every pdate, either maintainer is wrong, or upstream is wrong.

did something change with fusefs in freebsd 15.1? I still have allow.mount.fusefs; in my jail.conf, vfs.usermount=1, and "add path fuse unhide" in devfs.rules but a non-root user in my jail (even with operator group) can't start an rclone mount, "mount_fusefs: /dev/fuse on /usr/local/etc/thelounge/uploads: Operation not permitted"

this didn't happen while i was still in 15.0 btw

bugzilla down?

skered: Seems to be, yes.

IT's BACK!

does 15.1-release come with the new built-in KDE installer?

why does this fail: sudo vm set myvm autostart=yes? it sais error: invalid configuration setting - 'myvm'

what a piece of shit

nowhere in man.freebsd.org/cgi/man.cgi?query=v…ASE+and+Ports.quarterly&format=html is the list of settings defined

then sudo vm get all only shows 4 settings, console compress decompress suspend. nothing about autostarting a vm

set is for global vars. you configure what to autostart in rc.conf with vm_list (also do your own topological sort)

sudo sysrc vm_list+="myvm" didn't work. it said vm_list: myvm -> myvm but then i look at the file and it's still vm_list=""

omg it set vm_list in rc.conf, not the rc.conf.d file vm_list="" is already in

rc is a naive piece of shit

can't imagine systemd is any better but i see now why ppl weren't satisfied with rc

gonna have to pass it -f

Systemd is definetely more standardized, it has configs whcih are pure declarative-oriented. In rc.d it is obvivously possible to have declarative way to create service, but this is not directly and shortly explained in handbook or tutorials, so the result is the mess.

The rc.d configs can be made using system utility "daemon" to create instances of apps and this daemon allows to specify "-o" flag to specify the log name in "/var/log/". Sad thing is, that this genelar daemon utility has even no options to add timestamps to each log file. Funny thing is, that many of the log files in the /var/log don't have a

timestamp, which is really crappy as hell. Actually, this is very traditional Unix and Linux crappy way of doing things.

I'm therefore no surprised, that with such crappy Unix software there has been created Systemd, which unifies how the service config files will be made, prohibits doing shitty programming directly in this files, and what's best, it also includes log system called "journald", which basically adds timestamps into each log line. Therefore you can

concatenate any logs you want when you track bugs.

The only sad and crappy thing on Systemd is, that it wasn't created much sooner and adopted much sooner.

lol

lol

shitposters are like magnets for each other. paragraphs of dribble from one, more dribble from another.

blah blah

thats right

thats right

everything you said i read as: blah blah blah blah.

everything you said i read as: blah blah blah blah

Oh you've turned into a parrot. Probably less ugly now.

But still prettier than you

Doubtful. Very doubtful. You probably look like you talk. A mess. A troll. A real life gizmo.

there's nothing wrong with systemd that can't be solved by uninstalling microsoft products.

I am once again reminding you to not feed the trolls.

I guess Lennart left M$FT in Jan

might be his best decision in a while.

A quote from $BIGTECH peer in the QA dept: "It should be a capital offense for logs to not include timestamps"

I laughed pretty hard.

hello

I run several FreeBSD systems, for >6 yrs now I think, I understand for FreeBSD 16 it is necessary to move from freebsd-update to pkg

Does that mean the system needs to be reinstalled from scratch or migrated with a Lua script to be downloaded from somewhere? Or is there another path?

hc: No, you can migrate.

hc: github.com/FreeBSDFoundation/pkgbasify

You can migrate from freebsd-update to pkgbase at any time during the version 15 release cycle.

Once you migrate to pkgbase though it is a one-way trip. But in 16 the plan is for pkgbase to be the only supported method.

So there is no hurry if you want to continue doing what you are doing. Or you can convert or install systems using pkgbase now and drive them around until then.

I do think it's deeply unfortunate pkgbase in 15 is marked as experimental.

and 15.1

It's just a safe thing to say. It's new. There are going to be misunderstandings. Such as that reply to the announce mailing list.

you could still `make buildworld installworld`

mason: Yes, that's what I was wondering about; do I need to download some script from some git hoster to migrate my system?

Sure. The term just strikes fear into people who want boring stability. :)

hc: That link has the script.

mason: Yes, I know

ah, I misparsed, kk

It just feels a little... uncanonical ;-)

like 'why isn't it in base' ?

That is a valid point.

But probably it is that way as a practical pragmatic thing. It allows it to be updated rapidly. More rapidly than being in base really allows.

I am currently not in a hurry; I mainly use FreeBSD as a bhyve host. I'm on 15.1 right now with 7 systems

Will the migration script become part of the base one it's considered stable?

hc: If pkgbase will be the default in 16, there might not be a need for a migration script after that, unless they want a path for folks building from source.

Although even with that, I think you can build the packages from source and sidestep that.

Oh you mean I will be able to use freebsd-update to migrate to 16, after which it'll be set to use pkg?

That'd be the ideal way IMHO

hc: Based on what rwp is saying, I'm not sure freebsd-update will get us to 16, but we can convert before migrating to 16.

for the record, 16.0 isn't due until 2027-12

I have not heard how the upgrade from 15 to 16 will occur. But I am sure it will be in the release notes for 16 when it appears. Likely even the powers-that-be writing those release notes don't at this time today know exactly how it will be handled then. They have time to work it out though.

Okay, got it, makes sense. Thanks

If it were me then I would add pkgbasify to base in a later 15 point release. Then it would be available at that future time when it is needed. But I have no idea what their plan will be.

rwp: Good point. Entirely possible.

And yeah, having it in base would be good.

ideally pkgbasify would've landed already, but it'd be nice if it just registered the packags installed instead of actually installing themm

Like a fake install?

Would/could that cause issues with pkg-check?

shouldn't

Or I migrate to github.com/nixos-bsd/nixbsd ;-p

a few more words: pkgbasify only works if you're on the latest patch release for your minor release and pointed at the correct repo, otherwise you probably get pain when it extracts config files that might have differences

that's not a bad constraint, mind you

Is it just a matter of `pkg install -X ...` vs `pkg install ...` ?

yeah, I believe so

i'm so tired of hearing about nix

mason, I haven't solved the missing sshd-auth after upgrade problem, no time to look at it yet, have you? (I had to revert the upgrade on that one machine that is repeatedly doing it for me.)

rwp: I've been too busy to work on most of the stuff I need to get done. Time is a precious commodity.

rwp: That said, you shouldn't need to revert over it. Just copy the file in from elsewhere.

Once you do that, sshd will be happy and will start right up.

mason, Yes I know. But if it is missing that file then what other files might it be missing? I didn't have time to do a good look at it and didn't want to have a partially missing system. So I reverted. Which is okay on this internal storage server not exposed to the Internet.

I wondered why upgrading from 15.0 to 15.1 ran a system out of disk space. It had 2.5GB available.

i've seen freebsd take up around that much if you unpack the sets?

I stole disk space that will need to be replaced and free'd up 10GB of disk space. The upgrade consumed 6.36 GB of disk space at the first reboot point in the process! Gah! That's a lot of temporary space! And I am sure that base is not close to that size.

rwp: Are you using ZFS?

The auto created be is that filled my machine up it was over a long time but the 15.1 upgrade is what caused it to go overboard.

The default be is 3 GB in size with all of the pkgs installed. But until those change the snapshots won't consume more space.

It's a long weekend so I think I'll basify tonight.

After the final reboot the total amount of disk space needed was 7.65 GB of available space. Wow!

Previous boot environments add up to some 300 MB of space only. 384 MB in the pkg cache. 855 MB in /usr/local/ installed pkgs.

The /usr/freebsd-disk is only 252 MB. 241 MB in /var/cache/pkg. Shouldn't "pkg clean" delete /var/cache/pkg/*?

-a?

It keeps the installed ones I think?

Yes! pkg clean -a needed the -a to delete the pkgs from the installed files. That freed up 241 MB. Still looking for the other 7 GB of space that has been consumed.

There is 1.0 GB in /usr/freebsd-update which I will not need to preserve.

Sorry /var/db/freebsd-update is what I meant to say there.

I think I was also fooled somewhat by the garbage collection. It takes some time. I should let it settle and come back. But have deleted all of the boot environments and everything. It is now starting to free up space now though. I should scrub I supposed.

I confused myself because I stole 10 GB from the replicated mirror. But the mirror rsync restarted after the first reboot and took the space back! So I was racing me cleaning up files against the rsync pouring the mirror files back onto the system. I guess I won the race because it did not run out of disk space this time.

The host system is up to date and I free'd up aggressively removing more than before so have 4 GB free now. I guess I am ahead. Time to upgrade the jails on it now.

The next system I upgrade I will need to be more careful about mirror rsync and then actually figure out how much disk space is needed. Sorry I was shocked by confusing myself about that. Next time I will freak out less.

yay! my comment on a bug thread led to a CLOSED (my first participation)

nice!

haha thx kev