Found the problem, the issue was a network setting in my client (Linux) not in FreeBSD, it is working perfectly now, I even put it to sleep and woke it up, working great...I know better: Its never a good idea to point fingers before doing basic diagnostics on the configuration involved. That includes the server and the client. I apologize for this error on my part.
Depends, are you going to interface with the kernel directly in your code? If so, I would say it definitely differs. If not, and you just consume libc and any other "user-space" libraries, you probably won't notice any big difference. And yes, FreeBSD has been and currently is daily drivable.
@@pavelperina7629 Sorry this answer is coming months after your post... LLVM/Clang is its own thing, using the Apache license. But FreeBSD (and maybe other BSDs) has a stable version that they build from source themselves and (I think) include as part of the base OS. They do the same thing with a bunch of third-party programs, like `xzutils` for compressing/extracting packages. That came up recently when someone put a backdoor in the `xzutils` build scripts; FreeBSD wasnt effected by that partly because they use their own build system for it. The license difference doesnt cause a problem because the Apache 2.0 license is also "permissive" and doesn't make licensing other software it's distributed with under the same terms, unlike the GPL 3 license that recent GCC versions use. FreeBSD is also distributed with CDDL-licensed ZFS drivers, the CDDL being a "weak copyleft" that also doesn't inpact the licensing of other programs as long as ZFS itself is being distributed under the CDDL. So there's a handful of "non-BSD" licensed components in base that aren't primarily maintained by FreeBSD, but they typically wouldn't cause issues for downstream distributors.
I just installed freebsd 14.1 in vmware. Works great!. To get the resolution to work I had to install open-vm-tools AND xf86-video-vmware packages. Now my resolution 1929x1080 works perfectly.
I don't understand the point about IPv6. As far as I know, FreeBSD already had stellar IPv6 support for a long time, even being the pioneer of it, so much that other operating systems took code from FreeBSD for their own IPv6 support. But I could be wrong, it's something that I read somewhere, not experienced. I don't use FreeBSD that much, but when I do, I never have any complaint about its IPv6 support. So what did this update actually add? (Rhetorical question, of course I will read about it.)
Thanks for covering *BSD, it´s always interesting and deserves the publicity. Excuse my OCD, but doesn't FreeBSD come from BSD 4.4 Lite? If my memory serves me right, the Berkley BSD 4.4 Lite was the one (the "Lite" part) that was made for keeping the lawyers happy? IIRC both FreeBSD and NetBSD are forks of the Berkley BSD 4.4 Lite (OpenBSD was then a fork of NetBSD). My inner UNIX fanboy brain looks at it in this way: AT&T Unix -> Ken Thompson @ Berkley -> BSD is born -> Enter the lawsuit drama -> BSD Lite -> Forked by Free/NetBSD Again, thanks for covering a BSD. I´m mainly on OpenBSD, but in BSD land we are all friends, and my file server runs FreeBSD because ZFS. I wonder what the world would look like without the BSD´s. For starters we wouldn't have any TCP/IP...
No this is wrong. FreeBSD and NetBSD are both forks of 386BSD which was an open source BSD release made by the Jolitz couple. The reason it was forked is because the Jolitz couple and the devs (that made patches to 386BSD) couldnt agree on some things (386BSD had a very slow development pace). BSD386 that became BSD/OS (the OS actually being sued by USL) was the one that replaced code with code from BSD4.4-lite2. I guess the confusion arises because Jolitzes 386BSD was based on Net/2, a predecessor to BSD4.4. Net/2s source code was the basis on the AT&T (USL) vs CSRG (BSDi) lawsuit.
I hope they add encryption in the installer for UFS, ZFS does more than I need a filesystem to do, and takes up more resources than I like on older hardware
just din't get what is new - usually engineers supposed to read release notes... what is the point / reason to issue such videos. didn't get a vs as usual - is that for newcomers ?
changes to openssh as I understand it (up to version 9.6) were bugfixes, those get backported usually into debian's 9.2. 9.7 did add some new features one is a global timeout on all open ssh connections that have been idle for a specified interval. The other one is some changes to error messages to make them a bit easier to understand. If you are still using DSA encryption keys (which i wouldn't be) you are getting closer to the day those will be deprecated.
@@jacobwerner8533 I recently started playing with FreeBSD on an ancient (2008) Dell laptop and on a Raspberry Pi 3B+. The Pi is running FreeBSD 14.0 and I have it set up as a file server with SSH, Samba and NFS for Git/remote admin, Windows shares and sharing to my Debian system and the FreeBSD lappy. SSH seems solid as a rock between Debian 12.5 and FreeBSD 14.0 and from the FreeBSD 13.2 lappy back to my Debian system as well as to the FreeBSD file server. I couldn't get FreeBSD 14.0 on the lappy; too old and crufty I guess. I tried for a while but gave up. FreeBSD 13.2 seems not to handle the touchpad properly as no tap-to-click, side-scrolling or two-finger scrolling which worked with Debian on it. I also have problems with Sleep and Hibernate but the hardware is ancient and I don't rely on it for anything and I wouldn't read anything into this as regards more modern hardware. The little Pi has been rock solid. Only problem was with a power outage and I didn't really know how to bring a UFS filesystem back on-line cleanly but I've learned a bit more since then and bad power is much less scary now.
@@jacobwerner8533 FreeBSD is not hard to install. But hardware support is very bad as it became minor, forgotten OS. So you may have problem with some "consumer" PC components such as realtek network cards, wifi, various usb dongles. Otherwise it has the similar roots as Linux, just a different kernel, init scripts and there are small nuances in commands: few parameters are different, make is different than gnumake, devices are named differently. But I would say Slackware linux used to be more similar to FreeBSD than let's say to current Fedora with systemd, devfs, ... there is still ifconfig and iwconfig instead of ip and nmcli, devices are named differently etc.
@@savagepro9060 So long as you have supported hardware, at least. If you need fast wifi, FreeBSD will not currently suit your purposes. I like it (especially the fact that the console has decent utf8 support), but if you don't have access to a wired connection you're looking at a pretty slow internet connection. Bluetooth tooling is also not great if you rely on that for headphones and the like.
It does- and very well at that! You can use prism launcher (built from source, unfortunately), the lwjgl3 in ports (you *might* have to build this from ports), and glfw3 with preedit patches (again, from ports [build required]). After this, you're good to go. Search, "pog5 minecraft bsd" for a more detailed guide. Cheers!
Truenas Core will reach its end-of-life in 2026 when the official support date of FreeBSD 13 ends. Truenas Scale, the Debian based version of Truenas will be continued.
I don't use Truenas Core or Truenas Scale. Truenas is an appliance not a package, so you need to be careful about what you externally install on it. I like the freedom of blowing up my servers thank you very much :D
Afaik RISC-V64 platform is minor but growing platform of Chinese SBCs, maybe because China wants something independent. Processors like JH7110, TH1520 that are, performance wise, somewhere between Raspberry Pi3 and Pi4 processors and for some tasks way worse, cause they lack special instructions for encryption etc. I'm a bit surprised it needs 1GB of RAM for CLI. I remember times when servers had 512MB and average PC had 64-128MB. And before when Linux without Xserver was fine on 16MB and fit onto six floppies or so.
I resolved it, turns out it wasn't an issue in FreeBSD, it was an issue I caused in the configuration of my network...been putting things back together since the storms and missed a setting or two...or three
I thought I need to comment on this, FreeBSD is so niche and with few exceptions its well slower than many leading Linux distributions. But desktop, no, lets be real. If you need desktop you use Mac or Windows. I did noticed that the Linux users think that Windows still needs drivers etc. Most drivers are now in Windows by default, many standards, many universal drivers it all works out of the box. I do use Linux since 1998, but mostly on servers and one laptop as its easier to run console from Ubuntu than Windows. I can't imagine using any design software on Linux or FreeBSD, they are still in the early 2000 with the Font management and WYSWIG font use, the software is terrible, buggy and slow. Apple has great hardware but, I can't wait for Windows on Apple Silicon.
There are some versions of PFSense which are using the development release of 15.0, but there is a supported release of PFSense which is on 14.0
Found the problem, the issue was a network setting in my client (Linux) not in FreeBSD, it is working perfectly now, I even put it to sleep and woke it up, working great...I know better: Its never a good idea to point fingers before doing basic diagnostics on the configuration involved. That includes the server and the client. I apologize for this error on my part.
Something to consider: If you're a programmer, FreeBSD is one of, if not the best, LLVM based development environment.
Isn't whole LLVM part of BSD, or is it completely independent project using BSD licence?
How much would it differ from using a Linux and therefore GNU based development environment?
And is FreeBSD usable as a daily driver ?
Depends, are you going to interface with the kernel directly in your code? If so, I would say it definitely differs. If not, and you just consume libc and any other "user-space" libraries, you probably won't notice any big difference. And yes, FreeBSD has been and currently is daily drivable.
@@pavelperina7629 Sorry this answer is coming months after your post...
LLVM/Clang is its own thing, using the Apache license. But FreeBSD (and maybe other BSDs) has a stable version that they build from source themselves and (I think) include as part of the base OS. They do the same thing with a bunch of third-party programs, like `xzutils` for compressing/extracting packages. That came up recently when someone put a backdoor in the `xzutils` build scripts; FreeBSD wasnt effected by that partly because they use their own build system for it.
The license difference doesnt cause a problem because the Apache 2.0 license is also "permissive" and doesn't make licensing other software it's distributed with under the same terms, unlike the GPL 3 license that recent GCC versions use.
FreeBSD is also distributed with CDDL-licensed ZFS drivers, the CDDL being a "weak copyleft" that also doesn't inpact the licensing of other programs as long as ZFS itself is being distributed under the CDDL.
So there's a handful of "non-BSD" licensed components in base that aren't primarily maintained by FreeBSD, but they typically wouldn't cause issues for downstream distributors.
"Oops, did I say AI? Now, everyone take a drink." 😂 Great video as always.
When did that rule start?? 😄
I'm curiously intrigued to try it.
I just installed freebsd 14.1 in vmware. Works great!. To get the resolution to work I had to install open-vm-tools AND xf86-video-vmware packages. Now my resolution 1929x1080 works perfectly.
It would be great if you did a video about NetBSD one day
Wow, that beard! Thanks DJ Ware
Awesome video DJ, I'm completely new to FreeBSD so this was quite informative. Thanks!
Thanks DJ👍
I don't understand the point about IPv6. As far as I know, FreeBSD already had stellar IPv6 support for a long time, even being the pioneer of it, so much that other operating systems took code from FreeBSD for their own IPv6 support. But I could be wrong, it's something that I read somewhere, not experienced. I don't use FreeBSD that much, but when I do, I never have any complaint about its IPv6 support. So what did this update actually add? (Rhetorical question, of course I will read about it.)
Thanks for covering *BSD, it´s always interesting and deserves the publicity. Excuse my OCD, but doesn't FreeBSD come from BSD 4.4 Lite? If my memory serves me right, the Berkley BSD 4.4 Lite was the one (the "Lite" part) that was made for keeping the lawyers happy? IIRC both FreeBSD and NetBSD are forks of the Berkley BSD 4.4 Lite (OpenBSD was then a fork of NetBSD).
My inner UNIX fanboy brain looks at it in this way:
AT&T Unix -> Ken Thompson @ Berkley -> BSD is born -> Enter the lawsuit drama -> BSD Lite -> Forked by Free/NetBSD
Again, thanks for covering a BSD. I´m mainly on OpenBSD, but in BSD land we are all friends, and my file server runs FreeBSD because ZFS.
I wonder what the world would look like without the BSD´s. For starters we wouldn't have any TCP/IP...
386BSD I think you mean, there were some elements from BSD 4.4 Lite, but the majority was from the now defunct 386BSD
No this is wrong.
FreeBSD and NetBSD are both forks of 386BSD which was an open source BSD release made by the Jolitz couple. The reason it was forked is because the Jolitz couple and the devs (that made patches to 386BSD) couldnt agree on some things (386BSD had a very slow development pace). BSD386 that became BSD/OS (the OS actually being sued by USL) was the one that replaced code with code from BSD4.4-lite2.
I guess the confusion arises because Jolitzes 386BSD was based on Net/2, a predecessor to BSD4.4. Net/2s source code was the basis on the AT&T (USL) vs CSRG (BSDi) lawsuit.
And we wouldn't have had EFT's, either.
I hope they add encryption in the installer for UFS, ZFS does more than I need a filesystem to do, and takes up more resources than I like on older hardware
That would be nice, having to dive into the shell script to manually do it is a real pain.
I'm just looking for a desktop replacement, I been using elementary os and q4os linux for a few years.
You said you didn't know what platform the RISC-V64 is. Is it not for RISC-V processors like Milk-V and StarFive?
I came here to say that: looks like a simple typo, no space between V and 6.
Good luck getting it to run on StarFive...
@@CyberGizmo Thanks, I just ordered a VisionFive 2 board. I will give it a try.
@@CyberGizmo I have it running on a VisionFive 2. It doesn't do much but it runs.
@@csteelecrs I have a visionfive 2 as well - how is driver support with FreeBSD?
just din't get what is new - usually engineers supposed to read release notes... what is the point / reason to issue such videos. didn't get a vs as usual - is that for newcomers ?
just realized - release notes short video version for engineers
how compatible is ssh in freeBSD with debian 12? considering using freeBSD to manage a backup server.
changes to openssh as I understand it (up to version 9.6) were bugfixes, those get backported usually into debian's 9.2. 9.7 did add some new features one is a global timeout on all open ssh connections that have been idle for a specified interval. The other one is some changes to error messages to make them a bit easier to understand. If you are still using DSA encryption keys (which i wouldn't be) you are getting closer to the day those will be deprecated.
@@CyberGizmo i like the idea of ssh connection timeout. maybe i should test it in kvm on my debian system first. i'm not too familiar with BSD.
@@jacobwerner8533 I recently started playing with FreeBSD on an ancient (2008) Dell laptop and on a Raspberry Pi 3B+. The Pi is running FreeBSD 14.0 and I have it set up as a file server with SSH, Samba and NFS for Git/remote admin, Windows shares and sharing to my Debian system and the FreeBSD lappy.
SSH seems solid as a rock between Debian 12.5 and FreeBSD 14.0 and from the FreeBSD 13.2 lappy back to my Debian system as well as to the FreeBSD file server.
I couldn't get FreeBSD 14.0 on the lappy; too old and crufty I guess. I tried for a while but gave up. FreeBSD 13.2 seems not to handle the touchpad properly as no tap-to-click, side-scrolling or two-finger scrolling which worked with Debian on it. I also have problems with Sleep and Hibernate but the hardware is ancient and I don't rely on it for anything and I wouldn't read anything into this as regards more modern hardware.
The little Pi has been rock solid. Only problem was with a power outage and I didn't really know how to bring a UFS filesystem back on-line cleanly but I've learned a bit more since then and bad power is much less scary now.
@@jacobwerner8533 FreeBSD is not hard to install. But hardware support is very bad as it became minor, forgotten OS. So you may have problem with some "consumer" PC components such as realtek network cards, wifi, various usb dongles. Otherwise it has the similar roots as Linux, just a different kernel, init scripts and there are small nuances in commands: few parameters are different, make is different than gnumake, devices are named differently. But I would say Slackware linux used to be more similar to FreeBSD than let's say to current Fedora with systemd, devfs, ... there is still ifconfig and iwconfig instead of ip and nmcli, devices are named differently etc.
Glad to see the little daemon is still out there toiling away.
Excelente.
FreeBSD, very good server
it 'serves' as a good desktop, too.
a very good server is an insult. it IS the ONLY server
@@savagepro9060 So long as you have supported hardware, at least. If you need fast wifi, FreeBSD will not currently suit your purposes. I like it (especially the fact that the console has decent utf8 support), but if you don't have access to a wired connection you're looking at a pretty slow internet connection. Bluetooth tooling is also not great if you rely on that for headphones and the like.
But...does it run Minecraft? (I pretty much count Minecraft as the new Doom. Minecraft runs on literally everything...)
There is a minecraft server and a client in the FreeBSD ports collection.
@@MendenLama When I had FreeBSD on a laptop a few months ago, the client didn't work.
@@Xarius86 I have heard of people who did run it on FreeBSD. Personally I will never find out. I do not understand why Minecraft is popular.
@@MendenLama I think it was something about a lwgl3 (something like that) dependency that broke the client port.
It does- and very well at that! You can use prism launcher (built from source, unfortunately), the lwjgl3 in ports (you *might* have to build this from ports), and glfw3 with preedit patches (again, from ports [build required]). After this, you're good to go. Search, "pog5 minecraft bsd" for a more detailed guide. Cheers!
ALL HAIL GRAYBEARD WARE
DJ Ware: "What's New in FreeBSD 14.1?"
Phew! I thought it was NOT Free any more!
Is it true TrueNAS [ no pun] will be discontinued in 2029?
Truenas Core will reach its end-of-life in 2026 when the official support date of FreeBSD 13 ends. Truenas Scale, the Debian based version of Truenas will be continued.
I don't use Truenas Core or Truenas Scale. Truenas is an appliance not a package, so you need to be careful about what you externally install on it. I like the freedom of blowing up my servers thank you very much :D
We need more bhyve development with mature hardware accelerated vfio/gpu passthrough support and documentation.
Afaik RISC-V64 platform is minor but growing platform of Chinese SBCs, maybe because China wants something independent. Processors like JH7110, TH1520 that are, performance wise, somewhere between Raspberry Pi3 and Pi4 processors and for some tasks way worse, cause they lack special instructions for encryption etc.
I'm a bit surprised it needs 1GB of RAM for CLI. I remember times when servers had 512MB and average PC had 64-128MB. And before when Linux without Xserver was fine on 16MB and fit onto six floppies or so.
Seems like 14.0 just came out.
BSD generally doesn't work well as a vm. Probably due to the vm environment and the fact that BSD wants to be in charge of the hardware 😮😊
being in charge of hardware is it's JOB!
It worked well enough for me in KVM to get used to installing it such that I was comfortable installing it on hardware. Then the real fun begins.
I resolved it, turns out it wasn't an issue in FreeBSD, it was an issue I caused in the configuration of my network...been putting things back together since the storms and missed a setting or two...or three
pfsense has worked fine as a VM under proxmox for me. (freeBSD-based)
I'd like to interject for a moment...
If only it'd support newer wifi cards!
Hey cool beard 🧔
How old are you?
He just became 101 last tuesday.
Wait, what?
What is going on DJ Ware?You have stallmanized your face
I thought I need to comment on this, FreeBSD is so niche and with few exceptions its well slower than many leading Linux distributions. But desktop, no, lets be real. If you need desktop you use Mac or Windows. I did noticed that the Linux users think that Windows still needs drivers etc. Most drivers are now in Windows by default, many standards, many universal drivers it all works out of the box. I do use Linux since 1998, but mostly on servers and one laptop as its easier to run console from Ubuntu than Windows.
I can't imagine using any design software on Linux or FreeBSD, they are still in the early 2000 with the Font management and WYSWIG font use, the software is terrible, buggy and slow.
Apple has great hardware but, I can't wait for Windows on Apple Silicon.
What do you mean? Every major desktop environment I've used had software to manage fonts and they worked well. Am I missing something?