if someone is interested in contributing to #FreeBSD but do not have ideas, here is one: "fix API compatibility between our libusb and linux's one without breaking ABI", don't hesitate to ask me for more detail
@mms That's super funny 😃 I'd love to go full in BSD, however many of the libs/langs I use are either not available or in a very specific version and I don't want to compile them all by myself.
BSD clearly has some momentum in the end-user area and that's great.
Alas, I have to consider some other hardware that is more BSD friendly than what I currently have for my main laptop. Wifi worked great on NetBSD, whereas it was flaky on FreeBSD, but the audio input was the flaky one.
A ThinkPad, maybe? I'll gladly accept hardware recommendations for BSD-friendly models from at least a decade ago (read: cheap).
Current status: Deciding between Void and Alpine for the next episode of The Main Machine Trials®
@greggyb@jutty Sadly most from Lenovo have BIOS whitelists by default, forbidding you from changing the card, though there's the option of getting an X230 with Coreboot pre-installed from various vendors.
I've been using an X260 for the past years, though I use an USB WiFi device (urtwn) or ethernet for reliability.
@netbsd@jutty Yeah, that is a pretty lame part about Lenovo machines. I loved my x260 and its dual batteries, but I've recently moved to a #FrameworkLaptop and I couldn't be happier.
Do you live in Guernsey?
Do you use FreeBSD?
Do you want to financially support its continued development?
If you answered 'yes' to all of these questions, then I have good news for you - the FreeBSD Foundation's payment provider have made some fixes so you can now donate from Guernsey!
You should also get in touch with me so that we can start a user group :-)
Just a thought… Wouldn’t it be nice if capsicum in #FreeBSD could be used in such way that you didn’t need to alter binaries, but from e.g. daemon(8) which would jail your binaries with the restricted capabilities
@mpts@rvstaveren if you just want to use jails for all services you can modify rc.subr to add a new jailing feature where it just shares the same root filesystem but all the services you specify are in a jail with some lowered capabilities and it behaves like a cgroup in that fashion
I wish some people took this seriously and pushed it as a core feature because it would rule
@feld@mpts yes definitely! The reason I mentioned capsicum was that the jailing could even go deeper than that and keep processes unprivileged right from the start
"As Arm expands its reach into new technology domains, it is important to understand FreeBSD's role in this journey to gain insights into broader industry trends."
Would be a free public shell account service based on #FreeBSD/#OpenBSD systems interesting for you? If yes, what would you run on it?
Please provide feedback, so @gyptazy can check if it makes sense to provide such a service (this is already available in a limited beta).
What to expect:
A free user login to a FreeBSD or #OpenBSD based system where multiple users can access it at the same time. You can do everything in your own home directory, run processes, open sockets, compile stuff etc. System is managed in general for you.
What you cannot do:
Make changes to the system in general, use low ports, install or modify things system wide.
My laptop running FreeBSD 14.0-R-p6 locked up during resume - it's been years since I had this issue. Power cycled it, and now my wireless device won't show up. I think I'm too tired to debug now, will look at it in the morning. Bummer though, hope it's not a hardware failure due to resetting the laptop while the wireless device was being initialised.
@vermaden removed laptop battery, waited 10 minutes, put it back. wlan0 is back! Thank you :D
(Follow up edit: suspended again, resumed okay, but the wifi device keeps disconnecting and reconnecting, a reboot later it has again vanished. I'm suspecting this is hardware failure)
@harshad@vermaden if there’s a separate WiFi card inside, try reseating it, cleaning contacts. Could be a thermal issue if it worked after cooling down?
Puh, after almost 20 years (when version 1.1 got released in 2005) I switched from #ezjail to #cbsd. Feels strange because I always refused to use any other jail manager. But I guess it's time to move on... Btw, also like the TUI if #cbsd.
Have a nice weekend #FreeBSD fans (and of course also everyone else).