Skip to main content

PC-BSD

I tried out PC-BSD 7.0.1 under VMware Fusion on my MacBook.

From the guide:
PC-BSD is basically FreeBSD with [a modern version of KDE,] a nice installer, some pre-configuration, kernel tweaks, PBI package management, a couple pre-selected packages and some handy (GUI) utilities to make PC-BSD suitable for desktop use.
I worked on FreeBSD GUIs (both desktop and Web user interfaces) for five years. Let me tell you, I'm thankful that PC-BSD finally happened! For some reason, FreeBSD developers tend to either despise GUIs or own a Mac. Hence, it seemed to me that FreeBSD's GUI support actually got worse over the years. It's about time someone finally came along and "pulled an Ubuntu"!

Overall, I was pretty impressed. It reminds me of the early days of Ubuntu where you could see the potential, but you could also see some places that needed some polish. Here are some things I found worthy of note:

KDE looks really nice these days! It seemed a little unstable, but that could just be my setup.

I wasn't able to get the same resolution I can get in Linux under VMware, i.e. 1280x800. VMware has a ton of kernel modules for Linux that I'm guessing simply aren't available for FreeBSD. Hence, I was stuck at 1024x768.

The fonts don't look so hot on my laptop. The anti-aliasing looks wrong. There is some discussion about why this is the case here.

PC-BSD supports FreeBSD's normal packaging system and the ports system, but it also has a packaging system called PBI (Push Button Installer or PC-BSD Installer). These packages work a lot like installing a Windows application. You can find them by going to pbidir.com. You download them and then double click to install them. Uninstalling them is a lot like uninstalling a program on Windows. They even get installed into a /Programs directory instead of integrated into the normal hierarchy.

The installer gives you the opportunity to install a bunch of these PBIs. They all tend to be large applications like Firefox and OpenOffice.org. I even noticed Opera in the list. I installed pretty much everything except for Opera. I was surprised to see that it took 5.7 gigs of disk space.

In general, looking at / is a bit strange. Aside from /Programs, there's also /PCBSD and a few other surprises.

By default, the system comes with sshd installed and running, but a firewall blocking access to it (Packet Filter from OpenBSD). This is actually the opposite of Ubuntu which does not come with sshd installed, nor does it autoconfigure a firewall.

I don't use FreeBSD much these days, but if you're one of the hand full of people besides me who actually care about FreeBSD on the desktop, this is a really cool development :)

Comments

jjinux said…
I'm trying PC-BSD 7.0.2 under VMware Fusion. While applying system updates, the system updater went away. I'm not sure how to restart it, so I figured I'd log out and back in again. As soon as I logged out, I got a gray screen in my VMware window, and it's been that way ever since. I'm not sure if this is related to VMware.

A couple days ago, when I was trying to install PC-BSD under VMware, I lost my net connectivity when it was 99% done installing software. It just froze. The advertisements shown during the installation kept showing new pictures, but no additional progress was ever made even though I had a new net connection. Unfortunately, there weren't any errors shown on any of the virtual consoles. In fact, there was no way to log into any virtual consoles to read /var/log/messages.

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p