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

Linux and Graphics: AMD, Linux 4.14 LTS, Etnaviv Gallium3D

  • Linux 4.14 Ensures The "Core Performance Boost" Bit Gets Set For AMD Ryzen CPUs
    Recently making waves in our forums was talk of a kernel patch to address a case where the AMD CPB (Core Performance Boost) isn't being exposed by Ryzen processors. Here's more details on that and some benchmarks. Being talked about recently is f7f3dc0: "CPUID Fn8000_0007_EDX[CPB] is wrongly 0 on models up to B1. But they do support CPB (AMD's Core Performance Boosting cpufreq CPU feature), so fix that."
  • Linus Torvalds Is Confident That Linux Kernel 4.14 LTS Will Arrive on November 5
    Development of Linux 4.14, the next LTS (Long Term Support) kernel series, continues with the fifth RC (Release Candidate) milestone, which was announced by Linus Torvalds himself this past weekend. According to Linus Torvalds, things have finally starting to calm down for the development of the Linux 4.14 LTS kernel, and it looks like the RC5 snapshot is smaller than he would have expected, at least smaller than last week's RC4, which is a good thing, meaning that there won't be need for eight RCs during this cycle.
  • Etnaviv Gallium3D Is Almost To OpenGL 2.0 Compliance
    The Etnaviv Gallium3D driver that provides reverse-engineered, open-source graphics support for Vivante graphics hardware is almost to exposing OpenGL 2.0. Etnaviv contributor Christian Gmeiner today posted a set of patches for adding occlusion queries support to the driver. The code at just over one thousand lines of code is the last major feature needed for exposing desktop OpenGL 2.0 capabilities with this community-driven driver.
  • AMD Developers Begin Making Open-Source FreeSync/AdaptiveSync Plans
    While the AMDGPU DC code is expected to land for Linux 4.15 with goodies like Vega display support, HDMI/DP audio, and atomic mode-setting, one of the sought after display features won't be initially supported: FreeSync or the VESA-backed AdaptiveSync. As we've known for a while, while AMDGPU DC fills out the requirements for being able to support FreeSync, the last bits of the implementation are not present as the interfaces are basically yet to be decided among the open-source driver developers. While AMD can post their existing FreeSync code as found in AMDGPU-PRO hybrid driver, they are trying to come up with a more standardized interface that will satisfy the other upstream Linux driver developers too that might want to support AdaptiveSync.

Servers and Red Hat: Cloud Foundry, Docker, CRI-O 1.0, Alibaba and Elasticsearch

  • How to deploy multi-cloud serverless and Cloud Foundry APIs at scale
    Ken Parmelee, who leads the API gateway for IBM and Big Blue’s open source projects, has a few ideas about open-source methods for “attacking” the API and how to create micro-services and make them scale. “Micro-services and APIs are products and we need to be thinking about them that way,” Parmelee says. “As you start to put them up people rely on them as part of their business. That’s a key aspect of what you’re doing in this space.”
  • Docker Opens Up to Support Kubernetes Container Orchestration
    There's been a lot of adoption of Kubernetes in the last few years, and as of Oct. 17 the open-source container orchestration technology has one more supporter. Docker Inc. announced at its DockerCon EU conference here that it is expanding its Docker platform to support Kubernetes. Docker had been directly competing against Kubernetes with its Swarm container orchestration system since 2015. The plan now is to provide a seamless platform that supports a heterogenous deployment that can include both Swarm and Kubernetes clusters. "Docker adapts to you because it's open," Docker founder Solomon Hykes said during his keynote address at DockerCon.
  • Introducing CRI-O 1.0
    Last year, the Kubernetes project introduced its Container Runtime Interface (CRI) -- a plugin interface that gives kubelet (a cluster node agent used to create pods and start containers) the ability to use different OCI-compliant container runtimes, without needing to recompile Kubernetes. Building on that work, the CRI-O project (originally known as OCID) is ready to provide a lightweight runtime for Kubernetes.
  • Red Hat brings its open source solutions to Alibaba Cloud
    Alibaba Cloud has joined the Red Hat Certified Cloud and Service Provider program, with Red Hat solutions to become directly available to Alibaba Cloud customers in the coming months.
  • Elasticsearch now on Alibaba Cloud, eyes China market
    The Amsterdam-based company behind Elasticsearch and Elastic Stack said the new offering would be available to Alibaba Cloud customers as an add-on, giving them access to real-time search, logging, and data analytics capabilities.

Software: VirtualBox 5.1.30, Cockpit 153, GNOME Mutter 3.27.1, KDE Neon

  • Oracle Releases VirtualBox 5.1.30 to Patch Glibc 2.26 Compile Bug on Linux Hosts
    Oracle released VirtualBox 5.1.30, a minor maintenance update to the open-source and cross-platform virtualization software that addresses a few important issues reported by users from previous versions. Coming one month after the VirtualBox 5.1.28 release, which probably most of you out there use right now on your personal computers, VirtualBox 5.1.30 contains a fix for a Glibc 2.26 compilation bug for Linux hosts and a 3D-related crash for Windows guest that use the Windows Additions package.
  • Cockpit 153
    Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 153.
  • GNOME Mutter 3.27.1 Brings Hybrid GPU Support
    Mutter 3.27.1 has just been released as the first development release for the GNOME 3.28 cycle of this compositor / window manager. The change most interesting to us about Mutter 3.27.1 is support for hybrid GPU systems. The context for the hybrid GPU system support is explained via this bug report, "supporting systems with multiple GPUs connected to their own connectors. A common configuration is laptops with an integrated Intel GPU connected to the panel, and a dedicated Nvidia/AMD GPU connected to the HDMI ports."
  • #KDE #KDENEON Release bonanaza! Frameworks, Plasma, KmyMoney and Digikam

Intel Ads as 'Articles'