5 ms·
FreeBSD 13.4-Release
- xanth 2y agohttps://www.freebsd.org/releases/13.4R/relnotes/ https://www.freebsd.org/releases/13.4R/relnotes/
- 1over137 2y agoWith 14 already out for a long time, do many stay on 13 still?
- OsrsNeedsf2P 2y agoUpdating to 14 requires a reboot.
- X-Istence 2y agoUpdating to 13.4-RELEASE also requires a reboot.
- Abrothies 2y agoYou are correct, but you can install the new userland without a reboot, you will not get the benefit of an updated kernel though. With FreeBSD 14 you definitely have to reboot.
- cperciva 2y agoNot recommended. We have backwards compatibility but not necessarily forwards compatibility within a stable branch; running a 13.4 userland on a 13.3 kernel could break horribly. (My guess is that it's probably fine, simply because not much has happened on stable/13 in the last 6 months. But it's not uncommon to have e.g. new syscalls MFCed.)
- Abrothies 2y agoI never said that it's recommended, just that you could do it. Actually I completely agree with what you say. I've been forced to try at work a few times though, due to stupid reasons, it has worked out every time except once. Exactly due to what you mention. The one time it didn't work out things exploded beautifully, so the stupid policy that we can't reboot is now scrapped. :-)
- jsiepkes 2y agoThere are also security errata which require a reboot. Maybe if your device is not connected to a network you can get away with not updating / rebooting. But in 99% of the cases having a 700+ days of uptime is not a good thing anymore.
- deleted 2y ago[deleted]
- X-Istence 2y agoThere are some people that like the stability of staying in a single branch for a longer period of time. Same as for example people staying on RHEL 8 vs RHEL 9 or Ubuntu 22.04 vs 24.04
- kev009 2y agoFor general purpose systems it doesn't make much sense to lag a release, the amount of breaking change is pretty minimal in FreeBSD these days and it is fairly common to run -CURRENT (main) in production so there aren't a lot of hidden dangers in a .0 Old school appliance vendors appreciate the old stable branches where they carry a lot of local changes.
- cperciva 2y agoMost people have or should have already moved to 14. Some people can't, for example if they have binary kernel modules; we provide stable kernel interfaces within a major version but not between versions. From my perspective though, the most useful thing about doing legacy branch releases is that it gives us a chance to practice the process. Mike Karels was supposed to be the release engineer for 13.4 -- his first release since BSD 2.x -- before he died on the way home from BSDCan, that is.
- nine_k 2y agoA number of people do not care enough for things getting better. The OS they are running is fine, it solves their problems and does not have gaping holes. But they do care a lot about things getting worse: something breaking during the upgrade, something degrading or becoming incompatible, and requiring more work just to get to the previous position. So an upgrade has basically no upside and a significant possible downside. I'd say that you either live in a rolling mode, when you spread small-scale fixing and adaptation efforts over a long time, or you stick to a particular release and only apply security updates, and never upgrade, but instead build your new iteration from scratch using new versions of everything.
- wkat4242 2y agoNot really no. I moved my desktop to 14 when 14.1 came out. But it's really nice that there's always two production releases so you have plenty of time to migrate.
- DA87E80D629 2y agoDoes freebsd have the debian equivalent of unattended-upgrades? I want to setup auto security updates and forget about it.
- cperciva 2y agoIt's not recommended, but you can run freebsd-update and pkg upgrade non-interactively.
- j16sdiz 2y agoThis is not recommended. The recommended way is to set the weekly_status_pkg_enable flag and check email often. https://man.freebsd.org/cgi/man.cgi?periodic.conf https://man.freebsd.org/cgi/man.cgi?periodic.conf
- DA87E80D629 2y agoThat's one nice thing about debian. For home servers I can setup auto updates once and forget about it till the next debian version is released. It will auto install security updates, reboot if necessary.
- sulandor 2y agoit's a tradeoff between fear that an update will break it and fear that a adversary will break it. highly depends on the circumstances if/when auto-updates make sense, but once you have seen uptime in the decades range, most don't want to go back to ephemeral systems.
- karmarepellent 2y agoI have never seen a Debian system break due to auto-updates when they only subscribe to the common main, contrib and even non-free Debian repositories. They are incredibly stable and robust. However one might want to use apt preferences/version pinning if they also use external non-debian repositories to e.g. install a newer version of PHP. Since some repositories keep different major versions in the same repository, an auto-update might otherwise install a version that causes an application to break. That being said, most systems can probably get away with auto-updates and a little apt preference configuration and call it a day.
- hiAndrewQuinn 2y agoI had the fun of briefly checking yesterday that the long-forgotten Vagrant packaging for 13.4-RELEASE still works. It does! And FreeBSD is a real fun, calm little playground for those of us who spend most of our lives on Linux. I'd recommend people try it out if for no other reason than just to see how things could be done otherwise, and to get a chance to read Michael W. Lucas's stellar books on the topic.
- nozzlegear 2y agoI'm quite interested in putting FreeBSD on one of my dev servers. I had tried it back in July and got as far as installing Podman, but despite Podman for FreeBSD coming with a message that says many containers work with FreeBSD's Linux emulation¹, I couldn't even get the basic "hello world" container to start. I know FreeBSD has something called jails that are akin to containers, but I don't know anything about them and felt too frustrated being unable to get a simple Podman container off the ground. I want to dedicate some time to trying it again soon. [1] https://www.freshports.org/sysutils/podman/ https://www.freshports.org/sysutils/podman/
- sulandor 2y agowe all know that feeling. nbd podman/docker seem heavily entrenced in linux land, might be worth to check out alternatives. fwiw jails are much simpler to understand and use. still; can't shake the image of my in-laws complaining about different desktop icons and "how are we supposed to work with this?"
- nozzlegear 2y ago> still; can't shake the image of my in-laws complaining about different desktop icons and "how are we supposed to work with this?" Haha that's exactly how I feel! I'm not married to Podman/Docker/containers in general, I'd just been hoping to get my server migrated from an old Ubuntu setup over to FreeBSD that weekend. Migrating the sites and apps I had running on that old server from containers to jails, too, wasn't something I had planned for, and the weekend ran out of time before I could start looking into how I'd do it. I'm going to take another whack at it soon.
- atemerev 2y agoI’ll get back to FreeBSD when the most popular wifi card by a wide margin (iwlwifi, Intel AX200/AX2xx) will start working. That’s a shame, FreeBSD was long known for quality networking, and now what?
- fkgmeqnb 2y agoThey were known for their high quality network stack, not driver support
- atemerev 2y agoWell, “high-quality network stack” includes wifi, and wifi includes 802.11ax, and there is basically no modern wifi at all on FreeBSD, so… (I understand that it is mostly a server OS, and usually there is no wifi on servers, but still). That’s a little sad, because FreeBSD pioneered the wifi stack, it was better than Linux back in the days.
- doublerabbit 2y agoGo shout at the vendor for creating Linux only blobs. Or better yet shout at them to open source. Drivers are not a BSD problem inherently. More one of that vendors are not contributing to other mainstream OSes.
- snmx999 2y agoAccording to the "Supported Hardware" list AX200 is supported: https://wiki.freebsd.org/WiFi/Iwlwifi#Supported_Hardware https://wiki.freebsd.org/WiFi/Iwlwifi#Supported_Hardware
- atemerev 2y agoNot even 802.11ac, and of course no 802.11ax or more recent modes. (802.11ac appeared in 2013). This means that you get about 2 MB/s from it, which makes it completely unusable in 2024. Ah, even 802.11n is not supported! This is a 2009 standard. So we are left with 802.11a/b, which is 2003. The wifi of 21 years ago.
- irusensei 2y agoLast time I’ve checked FreeBSD didn’t seem to handle mixed core types like the ones you find on recent intel and ARM processors very well. Did it changed?
- cperciva 2y agoI believe work is underway on HEAD but I don't think we'll see any of it in 13. Probably not even in 14. That sort of stuff is hard to merge without breaking KBIs.
- avhception 2y agoI have migrated most of my personal stuff (like local fileservers, caldav / carddav and a few others) to FreeBSD jails in 2022 and haven't looked back. When a new release comes along I run `freebsd-update` and recreate my jails from Ansible, and that's that. A lot calmer than the churn that is modern Linux + Docker. And I get an awesome ZFS experience, too. I'm really happy.
- INTPenis 2y agoThat's calmer? You know what I do when a new Fedora release comes out? Nothing. My containers just work. Sometimes a new network driver comes along, sometimes an old network driver is taken out, rarely affects me. You rebuild your entire jail with Ansible every single release? You freebsd people are hilarious to me. I used to be one of you, from 2000 to 2009 I used FreeBSD for everything. I also used Perl for all scripting. I look back and am glad I moved on from that. For my mental health I'm glad.
- BSDobelix 2y ago>For my mental health I'm glad. And the FreeBSD community too ;)
- avhception 2y agoWell, I'm managing a whole fleet of Docker (and, not too long ago, LXD) containers at work. So I definitely know that ecosystem. Of course you can take any old Docker image and just run it as-is. Just as I can simply run old FreeBSD releases in jails. But that's not the whole story, is it? 3rd party dependency updates and whatnot. And yes, I feel simply deleting my jails and letting my scripts recreate them feels calm to me. I haven't had anything break or require too much attention so far. Can't say that for all the Docker stuff.
- avhception 2y agoAnd I always have the peace of mind that should my server hardware give up the ghost, I can always take a new computer, run my scripts, and have everything configured and running in no time because the procedures are exercised regularly.
- deleted 2y ago[deleted]