7 ms·
FreeBSD 13.1 Beta 1
- sydney6 5y agoAny updates on the FreeBSD native in-kernel wireguard implementation?
- fgrsnau 5y agoIt is currently living in the net/wireguard-kmod port. Works fine in FreeBSD 13.0 so far.
- tiffanyh 5y agoDoes FreeBSD have the equivalent of “-slim” in Ubuntu/Debian speak. I see that NanoBSD exist but ~~(a) it looks abandoned and~~ (b) its target use case is routers, not general servers, because it creates an immutable base. https://docs.freebsd.org/en/articles/nanobsd/ https://docs.freebsd.org/en/articles/nanobsd/ EDIT: I stand corrected. It is maintained. Thanks for info.
- xenophonf 5y agoHow do you figure NanoBSD is unmaintained? The GitHub mirror shows commits to that part of the source tree less than a month ago: https://github.com/freebsd/freebsd-src/tree/main/tools/tools/nanobsd https://github.com/freebsd/freebsd-src/tree/main/tools/tools... https://reviews.freebsd.org/D34241 https://reviews.freebsd.org/D34241
- kryptiskt 5y agoOccamBSD is a new script cutting down FreeBSD to a minimum, the README has some links to other alternatives: https://github.com/michaeldexter/occambsd https://github.com/michaeldexter/occambsd
- alberth 5y ago> "This script leverages FreeBSD build options and a minimum kernel configuration file to build the minimum kernel and userland to boot FreeBSD under jail(8) and the bhyve and Xen hypervisors." Does that imply that OccamBSD cannot be installed on bare metal?
- ink_13 5y agoThe opposite. OccamBSD is just small enough so that you can run a "full" FreeBSD installation in a jail, or start VMs with bhyve or Xen, and basically nothing else.
- throw0101a 5y ago"FreeBSD Quarterly Status Report 4th Quarter 2021": * https://www.freebsd.org/status/report-2021-10-2021-12/ https://www.freebsd.org/status/report-2021-10-2021-12/ * https://news.ycombinator.com/item?id=30635502 https://news.ycombinator.com/item?id=30635502
- ladyanita22 5y agoI'd LOVE for BSD to be a good alternative for daily use to Linux. But it's simply not. There's more and more stuff that is Linux only nowadays (wayland, gnome, several drivers, power management, wifi, Steam and proton... to name a few, very important ones)
- eatonphil 5y agoWhat do you mean by "BSD"? As I'm sure you know they are not distributions of the same underlying operating system. FreeBSD has supported Gnome for years for example. Wifi drivers are not Linux-only either AFAIK they just take time to get ported from Linux (or sometimes NetBSD) to FreeBSD. While it's true that FreeBSD isn't as easy a desktop system as Ubuntu is, it sounds like some (but definitely not all) of your reasons are a few years out of date. FreeBSD's main focus is servers also to be fair.
- grahamjperrin 5y ago> … FreeBSD has supported Gnome for years for example. … Sadly, in relation to AMD GPUs: <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257810#c5 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257810#c5> >> … disable dri 3 in xorg.conf (use dri 2)
- mnd999 5y agoWayland was working fine on FreeBSD last time I tried it. Gnome also had a port last time I looked. Even steam has worked in the past under linuxulator, not sure if it does currently. Edit: wayland not waylaid. That was genuinely autocorrect but it made me smile.
- grahamjperrin 5y ago> Wayland was working fine on FreeBSD last time I tried it. … From the quote at <https://forums.freebsd.org/posts/548305 https://forums.freebsd.org/posts/548305>: >> … KDE Plasma Wayland, which was working in September, is now broken. It’s not just my laptop, it’s on my workstation (AMDGPU), on the spare machine (Intel iGPU) and the laptop (Intel iGPU). I have chatted a bit with Plasma developers, but the debugging is on me, unfortunately. If you _do_ find Wayland working for KDE Plasma e.g. the option in SDDM, please join the discussion at <https://forums.freebsd.org/threads/kde-wayland.80167/ https://forums.freebsd.org/threads/kde-wayland.80167/> – thanks.
- bandq 5y agoFreeBSD's quality implementation, quality documentation and overall sane configuration / management should be apluaded. There are so many little things that make using it joyful, like the ncurses TUI for configuration options when building packages from source. I have used it for servers and NAS/ZFS/Samba applications for over 10 years and it's been exceptionally solid. But these days I've moved over completely to Debian systems now that OpenZFS 2.x branch is pretty mature and probably won't go back and it's due to the package management aspects. Sometime around FBSD 10.x the package system moved to a rolling release which means if you don't keep your machine up to date you eventually can't get binary packages for whatever FBSD version you're on which seems like a sadistic thing to do. A server that works fine but one where you might need to install some random utility suddenly breaks in 20 different ways if you enter the depths of trying to install said utility on modern FBSD. I thought my understanding of this was broken and reached out to FBSD devs on IRC and they confirmed that it's basically a rolling release model these days. With Linux distros like Debian after development on a version ceases (i.e 10.x) apt-get still works but you may not get the latest or greatest, bug fixes or security fixes. But if you need something and it's in the repository you can at least limp along until you bite the bullet and do a major release upgrade, assuming you need the latest/greatest. I know everyone's experiences here will vary but I've had very little breakage going between major version of Debian, but with FBSD too many things would break when doing a major release upgrade.
- merlyn 5y ago>> I know everyone's experiences here will vary but I've had very little breakage going between major version of Debian, but with FBSD too many things would break when doing a major release upgrade. I encounter much the same in Debian/Ubuntu systems on major upgrades too. It all depends on what you are doing, and what the port maintainer has coded to deal with upgrades. If the port maintainer has written scripts to deal with moving old schemas to new ones, great. But that is far from universal. Sometimes FreeBSD does it better, sometimes Debian does it better. Much more often than not, on FreeBSD or Linux, it usually is simpler to roll out a new machine and roll your data onto it to test. Otherwise I get headaches of incompatibility for either system for what I tend to do.
- ilikecode 5y ago
- webmobdev 5y agoIt's not Linux, it's Unix ...
- hestefisk 5y agoFreeBSD rocks. The power to serve.
- lorenzfx 5y agoHere are the release notes for 13.1 https://www.freebsd.org/releases/13.1R/relnotes/ https://www.freebsd.org/releases/13.1R/relnotes/
- bell-cot 5y agoDoing a quick compare with the 12.1 Release notes - https://www.freebsd.org/releases/12.1R/relnotes/ https://www.freebsd.org/releases/12.1R/relnotes/ - I will speculate that the 13.1 Release Notes are not a finished document, and quite a bit more will be added before the April 26th (current schedule) "final" Release of 13.1.
- cylinder714 5y agoFrom the original post, "Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 13.1-RELEASE cycle progresses."
- grahamjperrin 5y agohttps://news.ycombinator.com/item?id=30649753 https://news.ycombinator.com/item?id=30649753
- enriquto 5y agoWhat are the explicit instructions for upgrading to it from the previous release? Is there an equivalent to OpenBSD's "sysupgrade -r" ?
- Dracophoenix 5y agohttps://www.freebsd.org/releases/13.1R/relnotes/ https://www.freebsd.org/releases/13.1R/relnotes/ "Binary upgrades between RELEASE versions (and snapshots of the various security branches) are supported using the freebsd-update(8) utility. The binary upgrade procedure will update unmodified userland utilities, as well as unmodified GENERIC kernels distributed as a part of an official FreeBSD release. The freebsd-update(8) utility requires that the host being upgraded have Internet connectivity."
- enriquto 5y agoSo you have to read the manpage of freebsd-update, understand it, and then find the version name in another document... After a while I think that this is it : sudo freebsd-update upgrade -r 13.1-RELEASE sudo freebsd-update install It would be nice if these two lines appeared in the release notes.
- nix23 5y agoFirst you left out some pretty important commands and steps. Second RTFM! https://docs.freebsd.org/en/books/handbook/cutting-edge/#updating-upgrading-freebsdupdate https://docs.freebsd.org/en/books/handbook/cutting-edge/#upd...
- prmoustache 5y agoUsually if you have a working freebsd system you know the handbook exist and you refer to it for that kind of instructions.
- grahamjperrin 5y ago> … release notes. The notes exist, but only in draft form; a skeleton. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262300 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262300 I drafted the corresponding pull request around the time of the PRERELEASE, which preceded the first beta. I should not treat notes as final until RELEASE occurs.