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!
Hey everyone, I just wanted to let you know that the recent issues with package updates should be corrected with the new package set that just came out.
The graphical package manager will not be able to update to the new package set, instead you will need to run the following command manually:
sudo pkg upgrade
If this fails because of a package conflict, you will need to remove the offending package before trying the upgrade again. For instance, a number of user’s have had to run this command first:
sudo pkg remove –f py27-distribute-0.6.35
Once you have updated to the new package set, the graphical package utility will work perfectly fine again (since it got updated itself).
General background on the problem:
With the update of the new FreeBSD package utility (pkg) from 1.1.x ->1.2.x, there were a number of errors due to a bunch of backwards compatibility being missing in the new version. This meant that once you updated to the newer version you no longer had access to the packages on the PC-BSD repository (due to the changes in the repo format). Since our new 1.2.x packages were just released on the PC-BSD repo, you should now be able to continue changing your packages again. Another issue that came with 1.2.x was that a number of the utility flags all got changed suddenly — causing our graphical utility to need updating as well. We got that utility updated fairly quickly, but the updated package was in the new 1.2.x format — meaning that you have to use the command line to perform this one upgrade.
We are terribly sorry for the inconvenience. Please let us know here or on the forums if you run into any other issues.
Calling all creative PC-BSD users! The developers at PC-BSD would like your help in designing a brand new theme for the PCDM login manager. The winning entry will see their own customized skin as the default theme in the next official release of PC-BSD! In addition, we would like to present the winner and runner-ups with these awesome prizes:
1st Prize: A PC-BSD Isotope T-shirt, PC-BSD stickers, BSD wristbands, plus misc FreeBSD swag items.(Total ARV: $40)
Honorable mentions: PC-BSD schwag package (ARV: $15)
Contest start:11:00am PST on June 19th, 2013
Contest end:11:00am PST on July 8th, 2013
Please submit your entries in an email to the PC-BSD developers mailing list along with your email contact information. The format we require is a *.tar.gz archive containing all the image files as well as *.theme file. Please title the subject heading “Entry for PCDM Theme Contest” in order to be considered.
A sample theme can be found on the PC-BSD GitHub account, with additional information about PCDM theming available on the PC-BSD wiki. General icons should be 128 pixels square or smaller, with background images large enough to be automatically scaled/trimmed to the appropriate screen resolution where possible (for sample purposes consider 1024x768 to be the smallest supported screen resolution).
Have fun everyone, and good luck!
Standard disclaimers apply. iXsystems and PC-BSD team members are encouraged to submit entries, but will not be eligible for prizes. Void where prohibited.
Greetings! With EasyPBI 2.0 now available in the FreeBSD ports tree and as a PBI in the AppCafe, I was asked to highlight some of the new features in EasyPBI 2.0, and why you should want to start using it now.
The first new feature that comes to mind is relatively minor, but saves a fair amount of time if you use EasyPBI with any regularity. This is the ability to check when the last time you updated your system ports tree was, and to use portsnap (or svn if appropriate) to update it to the current version. This is easily available from the “System → Get FreeBSD Ports” menu option.
The second new feature is more of a significant overhaul rather than a brand new feature, and that is making the module editor a complete front-end to editing PBI modules. Previously, the editor allowed the user to view and change the most common options for PBI’s, and trying to use smart defaults for the rest. Now, while still recommending smart defaults, it makes all the settings and options for the module available to the user. The is extremely useful for loading modules from other people, as you can now see everything that the module has inside it, with nothing being “hidden” from EasyPBI inside any of the configuration files. This is easily shown with the new “Scripts” tab in the module editor that lets you read through or edit any custom installation scripts that might be in the module. Another example of this is the new functionality in the “XDG Entries” tab that lets you view/edit any of the desktop/menu entries without having to guess what is inside based upon the file name as with the previous versions. Oh, EasyPBI is also able to set up MIME type file associations for menu entries now, making that whole process very simple and no longer requiring that the user know how to write XML files for the different MIME types.
The last new feature that I want to highlight is one that will not be used very often, but has some very powerful possibilities associated with it. This feature is the ability to package non-port programs in the PBI format. What this option does is basically shift the burden of compiling the program and all its dependencies onto the user instead of using the FreeBSD ports framework. To make this work, the user will first have to setup a directory on his system in the exact format that he wants it to have inside the PBI (with lib/ bin/ share/ etc/ sub-directories as appropriate), as if the program got installed into this directory instead of on the base system. Once that is ready, you can then point EasyPBI at that directory, give it a version number and other program information, then have it all be packaged up as a PBI. This will require a bit more “advanced” usage since you will have to setup external-links and desktop/menu entries for the application yourself (since EasyPBI relies on the FreeBSD ports framework for recommendations), but this ability has a lot of very powerful implications. For instance, it should now allow program developers who wish to distribute special closed-source versions of their software to still make use of the PBI format for simple installations and consistent runtime dependencies by their clients. While this next example was not what the PBI format was originally designed for, I could also see this also being used by device manufacturers to release additional closed-source drivers or FreeBSD kernel modules for their devices. This would provide a simple way to distribute and install these drivers without requiring the system users to have extensive knowledge of the FreeBSD system structure or go through the pain of compiling and loading kernel modules on their own.
These are just some of the new features of EasyPBI 2.0 that I think users will appreciate the most. If you have some “killer” feature that you would like to see in the upcoming versions of EasyPBI, please let me know! I can be found on the PC-BSD PBI developers mailing list, or you can send me an email directly.
 ken (at) pcbsd (dot) org
There are a large number of new games available for PC-BSD 9.0, spanning game types such as action, arcade, card, educational, strategy, online RPG, puzzle, first person shooter, and party games. As mentioned with the desktop utilities, the PBI’s for these games should work in all the desktop environments available with PC-BSD, not just the one(s) mentioned in the game description.
Some of the new games are (in alphabetical order):
AfternoonStalker, AlienArena, Amoebax, Atomix, Barrage, Bomns, Briquolo, BrainParty, BubBros, Burgerspace, Chromium-BSU, Cosmosmash, Crimson, Cuyo, DJgame2, Dopewars, EasySok, Enigma, FreeDink, Gbrainy, GCompris, Gno3DTet, GnomeBreakout, GnomeChess, GnomeKiss, GnomeMemoryBlocks, GnomerMind, GNUDoku, GTetrinet, GtkTetcolor, gTuring, Gweled, Hedgewars, Hexalate, Instead, Kanatest, KDEGames4, Klavaro, KFreeRings, kMancala, KPicFramer, Kpictorial, KPuzzle, KSudoku, KTritoc, KWappen, LBreakout2, Legends, LianLianKan, LMarbles, LordsAWar, LucidLife, MonkeyBubble, MonsterMasher, MudMagic, nPush, OpenCity, OpenYahtzee, Peg-E, Pink-Pony, Pioneers, Pipewalker, Plee-The-Bear, PokerTH, PPRacer, py-Mnemosyne, py-Pychess, QNetWalk, Six, SuperTux, SolarWolf, TaxiPilot, TEG, Tetzle, TheManaWorld, Toppler, Trackballs, TuxType, WarMUX, Xpuyopuyo, XQF, Zaz
Thanks to Jesse Smith for many of these PBI modules.
With PCBSD 9.0 rapidly approaching completion, I wanted to take some time over the next week or so to inform the community about many of the new 9.x PBI’s that will be available through the AppCafe.
Today I am going to list the new PBI’s within the “Desktop Utilities” category (ports/deskutils in FreeBSD language). One of the main aspects that I wish to point out is that while many of these programs are designed to work within specific desktop environments (GNOME, KDE, etc…), the PBI format ensures that these programs should work with any of the PCBSD 9.0 desktop environments, regardless of the program description! For example: Katapult is a KDE application that, when installed as a PBI, works successfully on a system with IceWM rather than KDE installed. I hope this will allow users to utilize the applications that they are familiar with, while running the desktop environment of their choice!
Some of the new PBI’s for the desktop utilities category are listed below (in alphabetical order):
Alacarte, BlogTK, BookReader, Cairo-Dock, Drivel, FBReader, GanyRemote, GBirthday, Genius, Gnote, GnoTime, Gourmet, Griffith, GRuler, GTG, gToDo, Gucharmap, GXNeur, Katapult, KBLTicker, KLuJe, KnowIt, Krefty, KTagebuch, Labyrinth, Launchy, NoteCase, Orage, Parcellite, Pinot, Planner, QTM, Recoll, RedNotebook, Rubrica, TaskCoach, Virt-Manager, Wammu, XPad
Thanks to Jesse Smith for creating many of the modules for these PBI’s.