Big news this week! Kris has finished re-writing the code for handling how PC-BSD handles major updates. The general consensus was that there were still many users out there that were having difficulty when upgrading to a new version (i.e 9.2 > 10). For more information on the new PC-BSD update system, check out the article here. To view Kris’ address to the testing mailing list click here. Our goal is and has always been to have a reliable system to push out updates, and we think you will all be very pleased with the results!
Basic guidelines for PC-BSD utilities are continuing to evolve and we want your input! If you have ideas for the development team on what should become standard practice we want to hear from you. You can join the discussion on the the PC-BSD developer mailing list if you’d like to submit your ideas. To check out Guidelines for PC-BSD utilities visit the PC-BSD 10.1 wiki’s “Become a Developer” section @ http://wiki.pcbsd.org/index.php/Become_a_Developer/10.1
A moderate batch of fixes for trac tickets were committed this week addressing minor issues with the warden. Appcafe has also received a big update to it’s user interface allowing for a smoother experience for users. If you want to give the 2 newest versions of these programs a try grab the PC-BSD source and let us know what you think!
That’s it for this week! See you all next time!
Kris just posted a call for testers for a new methodology for major system upgrades (such as 9.2 -> 10.0 -> 10.1, etc..) and we are looking for people who are still running 9.2 to try it out. The full text of the call for testers is at the bottom of the post, but to give a bit of background we have been generally unimpressed with the reliability of the “standard” FreeBSD update tools (freebsd-update and pkg) when it comes to fetching uncorrupted update files through the internet. This new methodology takes those two utilities out of the general preparations for an update (download/verification of files), as well as a couple other upgrade steps so that there should no longer be an issue with starting an upgrade when only some of the upgrade files were actually retrieved successfully.
Please test it out and let us know how it goes!
Remember, always backup your data before doing any major upgrade like this! The new methodology should automatically create a boot environment for you before doing the upgrade, but better safe than sorry!
Here is the full text of request from Kris to the developer mailing list:
I've just finished up some work on a major re-write of our updating system when "upgrading" between major releases, I.E. 9.2 -> 10.0, 10.0 -> 10.1. https://github.com/pcbsd/pcbsd/commit/b95e8a83c73511568ae4291a54e0f93f6c67ef30 https://github.com/pcbsd/pcbsd/commit/9a8b3d1945fa67db8e99b0e4e82280b5626aa895 It seems to work well here, but it needs some additional testing from any users still running 9.2 who want to update to 10. To test this, first grab the latest from git: # git clone https://github.com/pcbsd/pcbsd.git pcbsd # cd pcbsd/src-sh/pc-updatemanager # make install Then run: # pc-updatemanager install fbsd-10.0-RELEASE This should start the download / upgrade process. If anything fails during the process, logs are kept in /root, which will assist me in debugging. Thanks!
The PC-BSD development team has been abuzz this week with awesome suggestions on how we can standardize the way we write PC-BSD utilities and software. One thing we’ve begun to realize is that as more people are contributing to the project, it is ever more important to make sure that there are clear standards for development. Even our primary developers will admit it’s easy to forget to use the same icon pack, or file menu layout when you get busy writing the main program. Going forward you can expect these standards to impact most of the PC-BSD utilities and programs you use everyday, although in a relatively minor way. Everything will still function the exact same, but whether or not you are using AppCafe or the Warden you can expect the file menu layout / program layout to follow the same general rules. For more information please check out “Becoming a Developer” in the PC-BSD 10.1 wiki. If you’d like to join the discussion you can email firstname.lastname@example.org.
I’ve seen some discussion lately about the life cycle of PC-BSD branches. I sat down with Kris Moore in IRC and asked if he wouldn’t mind clarifying the release cycle for our users. Kris answered the general rule of thumb you can use is a branch will continue to be supported for 6 months after the next branch is released. The updates include all of the things you would expect like new PBI and security updates. So for users of 9.2 you can expect support to continue through June of 2014. 9 Stable was a “experimental” branch and is no longer supported at this time. Users of 9 Stable are encouraged to upgrade to 9.2 or 10.0 Release to continue to receive important updates.
You can expect to see tons of improvements coming up for PC-BSD 10.1. One of the biggest being Kris and Yuri have been working to fix Linux jail support in the Warden. A handful of commits went into the tree today that will address the previous problems users have been having with Linux jails. Kris has continued to refine the Warden and PBI systems to fix some bugs that were causing major stability issues in certain scenarios. Minor cosmetic changes are coming for most PC-BSD utilities to bring them up to the same standards outlined in the “Become a Developer” section in the PC-BSD 10.1 wiki.
That’s it for this week folks. Lots of good things in the works so stay tuned to the blog for more important PC-BSD news!
Just a quick update for you fine folks this week! The bulk of the last week was spent fixing many smaller bugs that were still stuck in the PC-BSD trac database. Our primary goal now that 10.0 has hit release status is to fine tune the PC-BSD experience to allow for the smoothest experience possible. Users are encouraged to submit even the most trivial bugs during this “fine tuning phase”.
Among the programs that received updates the Warden received a patch fixing some issues with warnings, creating jails, and fixing user interface inconsistencies. Also the Package Manager received updates to fix some issues with how it interacts with pkgng. This should eliminate some of the minor inconsistencies some of you were seeing that was leading to communication issues between the two. Package manager and the User manager also received minor improvements to fix issues relating to their user interface.
Big news this week for the PBI format. Kris has confirmed that a patch has been implemented for the way PBI’s are being built that will shrink the size of PBI’s by approximately 50%. The patch has just been implemented and is currently in a testing phase, but stay tuned to the blog for more updates on how and when this patch will begin benefiting you in the very near future!
Thats it for this week folks. As always thanks for being loyal PC-BSD users!
PC-BSD Joule Edition was featured on eweek.com last week! Check out the article “FreeBSD Open-Source OS Comes to the PC-BSD Desktop” by Sean Michael Kerner.
The PC-BSD team has announced version 10.0 Joule Edition is now in official release status and is available for mass distribution. If you’ve used PC-BSD in the past you haven’t seen anything yet! PC-BSD 10.0’s feature rich front end runs beautifully without sacrificing the stability we all know and love from FreeBSD’s base system. This week we’re going to look back and highlight some of best new features now available in PC-BSD Version 10.0 — Joule Edition.
AMD / ATI graphics are now officially supported under PC-BSD. Although in the past AMD Radeon users have suffered from lack-of-driver-itis, those days are passed and a new age is upon us. I’m currently running PC-BSD on 3 different types of AMD graphics based systems and the performance is arguably better than some of my nvidia based test systems (sorry Nvidia fanboys :D). I was even more surprised when ATI hybrid graphics worked out of the box on my Samsung NP-350 Notebook computer. Especially considering this laptop was designed for…Windows 8…*BARF*
You will notice there are a couple of quirks to be aware of with the new Radeon drivers that we are currently aware of. Firstly the CTRL F keys do not bring up the console. This is being actively remedied by FreeBSD and we expect there will be a fix committed in the near future. Also KDE support for Radeon is there, but i’ve noticed that I experience random freeze ups from time to time on any of my Radeon systems. Using any other desktop environment seemed to fix the issue for me.
More of your favorite Desktop Environments! We’ve now added Gnome 3, Cinnamon, and mate to the list of desktops available under PC-BSD 10.0. Mate has officially replaced Gnome 2 in version 10.0, but Gnome 3 and Cinnamon will remain as “unsupported” desktops currently until further development and additional testing are done to bring them up to speed in PC-BSD. That being said feel free to report issues with these desktops with the understanding that they are currently in a “beta” stage and are offered without any guarantee. For best results with your PC-BSD experience use supported desktops!
The Grub and FreeBSD boot loaders have both received updated support to work with PC-BSD version 10.0. Have your choice now during installation for whatever boot loader works best for you. As we continue to work with the Grub boot loader our support is evolving simultaneously to give you even better compatibility.
In other news this week if any users are still using RC’s 1–5 please update to PC-BSD 10.0 — Release before reporting bugs so we can make sure we aren’t duplicating tickets for issues that have already been submitted and /or resolved.
Special thanks to the entire PC-BSD team including our testers, committers, and administrators. Without you guys this release wouldn’t be what it is today and we sincerely thank you all for your dedication in making PC-BSD Joule Edition a success.