if I were to start learning more about one of the listed BSD operating systems, which would you recommend? Guessing the answer could be different if we're talking about daily desktop usage vs server, so maybe clarify your answer via a reply if you can (fwiw, probably more interested in daily desktop usage, but open to whatever too).
Given that you said "learn about" and not "use", and given that you said that you had MacOS, I'd say learn FreeBSD first, then NetBSD, then OpenBSD.
It's worth learning them all.
But #FreeBSD is the closest to what you have in MacOS, with there being somewhat of a common heritage from many years ago; #NetBSD will expand your horizons from that, and then #OpenBSD is the furthest away from MacOS with very different ideas about almost everything and different abstractions.
I feel this quote by iXsystems sums up the state of #FreeBSD quite well. It keeps getting sidelined due to its many pain points. Even Oxide went with Illumos because they felt the community was more responsive to change.
“if people wanted to push FreeBSD forward for the last 15 years, they would have”
Looking for a way to run a single command as user "www" on #FreeBSD.
Roundcube uses doveadm to compute password hashes, but the www user defaults to the nologin shell and /nonexistent home directory. I really, REALLY don't want to change that.
Anyone have something clever to let me run just this one command as www? #sysadmin
[edit to add: Roundcube is a web app. It runs as user www. I can't have another run the command as www: www needs to execute the process. www can't run sudo or doas without the sort of something that would let www run doveadm.]
Can someone unbully mikael@ back into maintaining the signal-desktop port and then maybe unblock the electron ports from the repos so people can have a nicer #FreeBSD desktop experience? "You have to figure out and then wait about a day until VSCode and/or Signal are compiled" is a tough sell, isn't it?
After our main router/firewall died at Easter (sadly, it did not rise again), we threw a Debian laptop with an extra NIC in its place and carried on. This meant, as I hadn't spent any time configuring it, we were using our French ISP's DNS resolver.
That lasted until I tried to access #scihub, which is apparently bloqué en France! I've always run my own resolvers, so I've never come across this kind of censorship before.
New #FreeBSD firewall deployed with an #unbound resolver. Shields up!
— bhyve hypervisor kernel improvements
— desktop usability
— developer tools such as LLD
— hardware support on new ARM and RISC-V devices
— installer
— jails – usability/orchestration/OCI-compatibility
— networking
— packaging – including package base (pkgbase)
— …
Functionally the same (just clickable emojis in tabbed groups, display size and wait-time for restoring the X11 keyboard map configurable), but v0.2 has correct README info and build-fixes, so Qt tools are found without fiddling with make variables 🙈 so, use v0.2 😎
Thinking about what to include in #qxmoji v0.5. Many questions in mind...
I'll definitely "outscope" #l10n. Would be nice, but would also mean to import localized emoji names somehow (and, where to find them? 🤔)
For now:
🔹Unify persisting settings. history and window size are persisted on exit, wait time and display scale on every change. Not sure which one is the "better" approach...
🔹Should it be "single instance"? Should it offer an option for a "tray icon"?
🔹Add an "About dialog". Cause that's what you always do. 🙈
🔹Maybe find a way to speed up initial creation of the Emoji buttons?
🔹Anything else ...❓
Ah purée, j'ai mis #GhostBSD sur mon #X220. Quelle machine !
Je suis à deux doigts de revendre mon X280 de 2019 pour ne garder que le X220 de 2011.
Il y a bien longtemps que l'informatique ne m'avais pas excité à ce point. Je crois que seul un portable #RISCV avec #FreeBSD pourrait atteindre ce plaisir de jouer.
Je parle d'un vrai portable, avec batterie amovible, port Ethernet, USB SD_Card Mini et Micro, switch physique pour le wifi et cache physique pour la caméra (ce qui manque au X220)
This is strange: last October I created a FreeBSD VNET jail and defined a wireguard interface and a vxnet interface. It was working. Today I started the jail and it doesn't work anymore:
#ZFS was listed as experimental for #NetBSD 9. Per Wiki <https://wiki.netbsd.org/zfs/>, I would rather use FreeBSD which supports root on ZFS without the detour of FFS;
availability & support of Rust software as Python ecosystem seems to be using more of that as time goes by.
I personally need to check the situation in #FreeBSD with Intel CPUs with all E cores.