Language Selection

English French German Italian Portuguese Spanish

Personal Computing - BSD Style

Filed under
Reviews
BSD
-s

A milestone was reached on April 29 and I couldn't let it pass without a look. I'm speaking of the release of PC-BSD 1.0, their very first stable release. Almost a year ago Tuxmachines tested 0.6 of PC-BSD, considered a beta release, and was quite impressed then as I recall. I saw .7, .8, .9 and increments get released, but I just had to revisit the user-friendly bsd again on this wonderful occasion. How did PC-BSD stack up on this their "new era of stability and simplicity?"

It all starts with a boot of the cd. The first image is a boot screen giving several choices for booting the system with extras of Escape to bootloader prompt, boot FreeBSD with usb keyboard, or Reboot. I just went with the default and hit <enter>. Next, one sees a beautiful silent splash screen featuring a close-up of pretty yellow flowers. It states one could Press Any Key to view startup details, but escape seems to be the only one that worked for me - or perhaps it was a question of timing. In any case, eventually one is brought to another screen with choices. They are: Start graphical install, Reset X to default VESA driver, Change Resolution to 800x600, System Utilities, and Reboot.

        

Choosing to start the graphical install ...you guessed it, starts the graphical install. Here begins a great looking professional quality install process. It looks nice, but it is also really easy. It asks where to install and then begins. My choices were limited to the primary partitions on my disk, but I had two blank ones at the beginning of this newest harddrive in the Master position. I simply chose hda1 (in linux speak) and let it install. The actuall system install was quite fast, taking about 15 minutes and then one is asked for a root password, to setup a user, and where to install the bootloader. You can choose to skip installing a boot loader with PC-BSD, and I did. Instead, I took a lesson learned from FreeBSD and edited my everyday lilo.conf as follows:
other=/dev/hda1
table=/dev/hda
label=PC-BSD

        

When setting up an user account, you are given the opportunity to select auto-login and X start if desired. I did and upon boot I was taken straight to a 1024x768 KDE 3.5.2 desktop. Sound was auto detected and setup as I was greeted by the default kde login sound as well as a really beautiful wallpaper. The wallpaper is a landscape of a lush green valley with a field of those same pretty yellow flowers all in front of a majestic mountain range. Other than a slightly customized panel and menu, the rest seems your basic default KDE.

        

        

On the desktop are two icons other than Trash. One opens the PC-BSD wiki in the default browser, Konqueror. This is an online documentation site with links to some other handy tools such as an user forum. The other icon is even more exciting. Again it opens up a browser, but where it takes you is an online repository of software. From this varying list, one can download software, and easily install onto their system. Installing is as easy as clicking the file. It reminded me of my windows days actually. Click the pbi file downloaded, an installation wizard opens and installs the software. Some of the applications available are kmplayer, firefox, opera, OpenOffice, java, and a coupla kde themes. I tested several packages and all went really well.

        

There is also an update application. Although at this time, there were no updates, so testing was limited.

My final thoughts: I found PC-BSD to be even better than the last time. It's prettier, easier, and more complete. Installation was smooth, hardware detection was good and performance was great. The system was stable and all applications tested worked fine. The only probably I had was finding the Flash browser plugin in their repository. If you've been wanting to try a BSD clone, you couldn't go wrong with PC-BSD. Again this time as with the last, I'm very impressed with all the work that has obviously gone into this system to make it so easy for anyone to have a BSD. I believe they have met their goals and then some.

PC-BSD Homepage.

Download or Purchase PC-BSD.

PC-BSD Screenshots.

More in Tux Machines

GNU: The GNU C Library 2.28 and Guix on Android

  • Glibc 2.28 Upstream Will Build/Run Cleanly On GNU Hurd
    While Linux distributions are still migrating to Glibc 2.27, in the two months since the release changes have continued building up for what will eventually become the GNU C Library 2.28. The Glibc 2.28 work queued thus far isn't nearly as exciting as all the performance optimizations and more introduced with Glibc 2.27, but it's a start. Most notable at this point for Glibc 2.28 is that it will now build and run cleanly on GNU/Hurd without requiring any out-of-tree patches. There has been a ton of Hurd-related commits to Glibc over the past month.
  • Guix on Android!
    Last year I thought to myself: since my phone is just a computer running an operating system called Android (or Replicant!), and that Android is based on a Linux kernel, it's just another foreign distribution I could install GNU Guix on, right? It turned out it was absolutely the case. Today I was reminded on IRC of my attempt last year at installing GNU Guix on my phone. Hence this blog post. I'll try to give you all the knowledge and commands required to install it on your own Android device.
  • GNU Guix Wrangled To Run On Android
    The GNU Guix transactional package manager can be made to run on Android smartphones/tablets, but not without lots of hoops to jump through first.

Node.js 10.9 and npm milestone

  • Open Source Node.js Hits v10, with Better Security, Performance, More
    Speaking of which, the brand-new Node.js 10.0 is expected to soon support npm version 6 (currently Node.js ships with npm 5.7.x). The company npm Inc., which maintains the npm software package management application, today announced that major update, called npm@6. The npm company said its JavaScript software installer tool includes new security features for developers working with open source code.
  • Announcing npm@6
    In coordination with today’s announcement of Node.js v10, we’re excited to announce npm@6. This major update to npm includes powerful new security features for every developer who works with open source code. Read on to understand why this matters.

Openwashing: Sony, Scality and Ericsson

Voyage/Open Autonomous Safety (OAS) Now on GitHub

  • Voyage open-sources autonomous driving safety practices
    Dubbed Open Autonomous Safety, the initiative aims to help autonomous driving startups implement better safety-testing practices. Companies looking to access the documents, safety procedures and test code can do so via a GitHub repository.
  • Open-Sourcing Our Approach to Autonomous Safety
    Without a driver to help identify and mitigate failures, autonomous vehicle systems need incredibly robust safety requirements and an equally comprehensive and well-defined process for analyzing risks and assessing capabilities. Voyage models its safety approach after the ISO 26262 standard for automotive safety, taking the best practices from the automotive industry and applying them to autonomous technology. The automotive industry continues to reach for new levels of safety in manufacturing vehicles, and we are inspired by that approach.
  • Startup Voyage Wants to Open Source Self-Driving Car Safety
    Under what the company calls its Open Autonomous Safety initiative, Voyage is publishing information on its safety procedures, materials, and test code in a series of releases. The goal is to create an open-source library of safety procedures that multiple companies can use as a standard, a Voyage blog post said.
  • This startup’s CEO wants to open-source self-driving car safety testing
    The initial release, which Voyage calls Open Autonomous Safety (OAS), will take the form of a GitHub repository containing documents and code. The functional safety requirements are Voyage's interpretation of the ISO 26262 standard for automotive safety, updated for autonomous vehicles. "This is our internal driving test for any particular software build," says Cameron. "It lets us evaluate our designs and look for the different ways they can fail in the real world."