FreeBSD 2023 - What's new FreeBSD.15-CURRENT?
HTML-код
- Опубликовано: 20 авг 2024
- #FreeBSD #OpenSource #Unix #garyhtech #2023
Let's have a quick look at FreeBSD 15 and see what's new!
Don't forget to check out my Discord server where you can talk open source operating systems and software
/ discord
FOSS
FreeBSD Handbook
FreeBSD Networking
FreeBSD PKG
FreeBSD ports tree
It's probably too early to do anything other than FreeBSD system developement with 15 right now. The reason there are no packages is the ABI as of now could very well be totally incompatible with the ABI when getting closer to alpha. You could try using 15 as a NFS server or iSCSI target. I believe both of these are in the base system. You could also try out bhyve. Over the last six months in my home lab, I've switched all my Debian systems (server & desktop) over to FreeBSD. It really is a much better OS overall for my uses and needs. I'll probably start taking the plunge to upgrade to 14 once it hits RC2.
The leap from a late 13 to a new 15 instead of going through 14 first isnt much right now as 14 (now -stable) was just branched off of -current (now 15 code) so recently. Given a choice, I usually would have done upgrade to a version, another pass to make sure its as up to date/patched as I could (usually unnecessary), then upgrade to next sequential version, and repeat. The 'proper' step is following the documentation instead of what I said; reading /usr/src/UPDATING, and for -current the mailing list, is more important than reading my comment. In the "unlikely" event of a problem 1. please report it so it can get documented if an issue is present and 2. you did have a backup right?
No need to separate buildworld and buildkernel with two separate make commands and the third command of installkernel can be added on too; if you want/need to specify different make parameters to each then you may want them separated, such as -j#. Last I checked, there are bugs with multiple make jobs, having /usr/src call building kernel modules in /usr/ports, and having a configuration dialog come up which happens on first build of any configurable ports or if available options have new additions; preemptively answering the dialogs, -j1 during buildkernel, or building the ports as a separete step should work around that . I use prewritten shell scripts to do backups, download new source, build, install, and build new dependencies so I don't have to type as much
If the machines are connected on a network, you 'could' remote into one from the other to avoid multiple keyboard issues though you may find that rebooting to single user + doing that is an issue.
32bit support being dropped will not mean you cannot build for that platform while it is tier 2 or 3 supported and patches will still be accepted but keeping it working is not a primary focus of the FreeBSD development team. They aren't against 32bit support but it takes time and effort to keep something working that they generally do not use and/or have access to; its been stated that issues have arisen where 32bit wasn't working properly for its users because of differences between 32bit and when the devs ran 32bit under a 64 bit system and the devs were often working with the latter for what support they did provide in recent years.
RELNOTES would be easier to follow if there were dates associated when updating the system though if its just a jumbled list of 'we should tell people about these things in announcements later' then maybe it doesn't matter as much. Who wants to open the bug report about the v14 listing at its top on current? I'd suspect it would be worth getting a comment in the other file to make sure all related files such as this receive the new version or to consider removing them.
Your 'no operating system found' step was an issue with upgrading the ZFS pool rather than upgrading FreeBSD (which brought the newer ZFS where this whole mess 'could' happen). As you said, you needed to update your boot loader before the pool upgrade so that it can be compatible with the pool's updated features. You should always consider that when running a pool upgrade and similarly when sharing pools between systems if either plans to boot form the pool. I still consider it a bug that FreeBSD does not cover it clearly in /usr/ports/UPDATING (edit: there is mention of it there, but I find that documentation is still buggy when reading it), at least pointing users to proper bootloader upgrade documentation even if it is not required 'right now' as part of the FreeBSD upgrade. I also included that (easy) step on MBR booting but feel lost about properly understanding UEFI booting. If I follow correctly, the bootloader could be upgraded like the kernel is where you can have your older still present instead of replaced by the newer. Boot environments also will not fix a pool/boot loader upgrade issue; `zpool checkpoint` is designed for having an ability to mark a pool's current state to take the entire pool back to including undoing otherwise permanent upgrades and its use could be easily integrated into an upgrade script but once you are happy that a pool is accessible+reliable then you will want to remove such a checkpoint as it isn't designed to play nice with other features like reserved space and such. My understanding is the block clone feature that you now have enabled lead to data corruption under certain cases; a checkpoint would be how you get pool back to a good state other than restoring from backup. You may need sysctl option to actually enable using that feature unless it has had the bugs worked out; I haven't followed it as close but its introduction is only one of the pains that happened at the right time to delay 14 from being created and released.
Unless there are bugs in such system, you can build your own FreeBSD install media from a working FreeBSD system + /usr/src and can use that to perform both an install and a repair as desired.
4:00 - FYI, supporting 32-bit has not much to do with old or new hardware. It is just overhead involved in maintaining 2 architectures. I am happily using my 32-bit laptop to read papers in the morning. Please don't kill that joy.
Out of curiosity, when did you purchase said laptop?
@@unicornpoo7441 Bought as used. It is Compaq Presario R3000.
we didn't get anywhere, but cool video 😂
We got a system updated and running it, then proceeded to upgrade the pool to something the unupgraded boot loader couldn't handle. Though there are differences, there is little to show for 15's differences yet; the appropriate topic is what is different from 13 to 14.
Luv the shirt you got there
I tried Free BSD 13 Xfce. it's great but I took too long configuring sound and disk mounting. I wish it were simpler
what bsd?
@@stanb1455 free! I'll edit that
To mount the disks, you just need to add the info in /etc/fstab. The installation does it automatically. Also, the instructions to fix the sound are very clear.
@@tao4124
nothing is clear in BSD, sorry
I didn't want to mount the disks permanently, it was an external drive. some reboots later and it magically started mounting it
True. I am still avoid to mount anything in FreeBSD. I tried automount in the past, but it didnt worked very well. @@lingux_yt
Is there a previous video to this one? "The first thing we're going to do ..." seems to have missed a few steps.
No 32 bit probably means no 1st gen Raspberry Pi with FreeBSD 15 😅
They aren't removing 32bit completely right away but you would likely need to build an appropriate copy manually
Hello Gary! I would like to ask you if you have tried to install Wayland+GDM+Gnome on FreeBSD and were successful on this?
I did tried on FreeBSD 14 Beta yesterday and I wasn't able to make it work (of course I've read the Handbook).
I'd like to see gnome running with wayland as well. It's a no go in 13.2. From what I've read (rumors that could be false) is that most of the FreeBSD developers do not use gnome, so wayland+gnome is probably not high on the to-do list.
@@tux9656 And what do they use, lol?! From what I heard, Wayland is a protocol and not a display server in the same manner that X11 is. So, if Gnome works on FreeBSD, Wayland+Gnome should work as well. Maybe there are some other internal errors that do not allow it to run so, I cannot see why FreeBSD developers would not want to support it.
But in any case, I would be very interested to give FreeBSD a real chance and switch from Linux, but support is an important thing. I do have very little things that I do need, but if they can't support even these little needs, then we're talking again when 15 releases...
@@godnyx117 The biggest issue with FreeBSD as a desktop OS for me is that there is no way to play DRM protected content in a browser. For that, I usually end up running either Windows or Linux inside bhyve.
@@tux9656 Yeah that is a real bummer, apart from watching youtube, you can forget watching Amazon prime or netflix etc on a FreeBSD desktop system unless you're willing to use all the bhyve hackery, its not worth the hassle for most people.. its quicker to just boot back into native linux if you have a dual boot system like I do and watch the DRM stuff there - then again the lack of DRM support might not be an issue for some, there's always the argument "why watch it on a PC when most smart TV's can do that for you anyway" and its a valid point.
@@tux9656 I wanted to use FreeBSD on the desktop for dev work as I work as a sysadmin and devops person, but I remember at the time that I last tried, I could not get any decent IDE to work - Atom refused to work (atom is now defunct anyway), and of course there's no VScode - yeah I realize those editors are super bulky and are a memory hog because they use electron, but they are nice to use! I didn't fancy doing dev work in vi/vim/nano/kate/gedit etc. Did you find any decent solution for an IDE by any chance under FreeBSD? My experience made me go back to linux at the time... no DRM support, no decent IDE to use..
Embedded platforms are far more likely to be 32 bit only.
Unless you seek out x86+budget, then they are still sadly too commonly ran across. I won't speak for arm in that search as it isn't something I've shopped for much.
for embeded i think NetBSD is more suitable, Free is hardware edge.
Where are the frikin chapters? 😂😂😂
yeah, in short : FreeBSD still feels like the nineties. Best for the nostalgic or vintage lovers.
I'd argue that FreeBSD feels like Linux if it continued to be community developed rather than mostly taken over by big corporations.
It's the best OS, period. Soyjak constantly cries when home desktop users try to use it as a home desktop OS and not a server OS. Game consoles use it, set top boxes use it, a lot of banks have ditched windows for it now. It gets attention all over EXCEPT for the home desktop scene. As it stands, we have a very broken implement of WINE (very mismanaged too, shame on the devs and clean room criers). We have Linuxulator for steam... we have lwjgl3 for minecraft... there's still a shitload to be done to get things going properly. At the very least, we have the ability to use full on photoshop 2023 (I currently use this on there) because no one likes GIMP. There's inkscape and all of its plugins work perfectly (embroidery stitching). The cherry on top would be Adobe Animate, which does not work (never did, even for Linux). Adobe Animate is not only for cartoons btw, it can make websites, which is what I primarily use it for.
I see you using Windows, I unsubscribe
🤣