v 0.4.1
16 jan 13 Afternoon
I saw on Distrowatch recently, that a new version of PC-BSD had been released. At the back of my mind I've always wanted to try that, or Free-BSD. It was re-enforced when I was looking through the titles of the Linux Action Show and saw they had a review of it. What I saw impressed me no end:
- Simple Installation
- Jails
- Absolutely Solid
I should talk about "Jails". To me, these are the killer feature of Free-BSD and PC-BSD. They are effectively a Virtual Machine within the system, but they are not. More like a sandbox. As an example, you can create a BSD jail or a Linux jail that runs a complete operating system in a sandbox - for example set up a server there with its own IP address. If an intruder breaks in, they are trapped inside the jail. But there is more! Backups, cloning, snapshots. All done with ease.
Another two really impressive features are the firewall setup and the automatic backup. Easy to set up and effective. What more can I say?
The acknowledged problems at the moment include deficiencies in the ATI and Intel video drivers, however progress is expected on these issues by version 9.2 of PC-BSD.
PC-BSD in Virtualbox
I started by downloading the Virtualbox image - a whole 2.4 gig. I unpacked it and it expanded to about 7.8 gig (from memory) and when mated to Virtualbox, it was a disk that would expand to 34 gig.The first run allowed me to easily set up the video resolution, timezone and language. Impressive. The ability to add software was just so easy I was thinking that this would make a really good vanilla home computer. Web browsing, email, instant messaging, skype, office, finance - the list goes on. AND secure. Very secure.
PC-BSD on Hardware - First Blush
I'll not hold you in suspense - on my chosen "box" (the $400 box described elsewhere on this blog) the whole experience was initially unusable. I could not even get it to install and configure. In my particular instance it was just garbage.Now, it is all very well to report my experience, but WHY did it not work?
Two reasons.
- Video driver
- Boot manager
The Boot manager detected my Linux install, but I was unable to select it. BSD was the only thing that would work. Major work needed. BSD is almost worse than Windows in its lack of ability to play with other children. In all the Googling I did, I found people pleading for solutions for dual-boot problems, with nothing that really worked. Even the official documentation was useless for me when I tried to use Grub2. Solved with a different menu-entry, and after finding out that Grub2 decided to change their numbering system for partitions but nobody knew.
Second Blush - We have Liftoff with nVidia
Well, I took Cmdr Taggart's advice from Galaxy Quest ... and I kept thinking about this and experimenting.nVidia cards are mentioned a lot. I had one lying around, though it needed an extra power supply. Eventually, I relented and bought the cable, connected it up and .... YES! We have liftoff! 32 minutes past the hour.
AND the machine was significantly faster as well.
Third Blush - Damn you Grub2!!!!
Computer HDD Setup
I have Debian Linux (wheezy) on the first primary partition, with PC-BSD on the second primary partition using the zfs filesystem. When I installed PC-BSD, I installed its bootloader which overwrote Grub2 on the MBR.
Recovering Debian Grub2
To re-install Grub2 on the MBR in a Debian system, the installation cd/dvd have the tools specifically built in. Google on the Debian Wiki and it directs you to the appropriate section of the Debian installation guide.
- Boot using the Debian Install Disk
- Advanced Options
- Recovery Mode
- You will progress through various screens which are the first part of the Debian Installer - don't worry too much because none of the info will be written to the disk. Eventually ....
- A screen will present the available partitions - select the one you want to be the root partition.
- Select the menu entry to re-install Grub
Manual Menu Entries in Debian Grub2
Like a lot of things in life, many things are only obvious in hind-sight. Gaining that knowledge is hard won, but you feel good after the fact.
Debian automatically builds the Grub2 config file " /boot/grub/grub.cfg" . There is no point editing it (and they warn you about this - it is a text file that you can read) because it is over-written the next time grub.cfg is created. Instead, if you look at the end of the file, you will see that they point you to a customisation file " /etc/grub.d/40_custom " . Open it in an editor (as superuser) and you can add your manual entries to the bottom. Save the file and then once again as superuser:
" update-grub "
This will incorporate your custimisations in a new grub.cfg file.
Adding PC-BSD to Grub2
The entry I eventually found was for me (after piecing things together) was:
menuentry "PC-BSD 9.1" {
set root='(hd0,2)'
chainloader +1
}
"hd0,2" - well, ARRRRGGGGHHHHHHH!!!!!!!!
- 0 stands for the first hard disk, because you count your disks from zero.
- 2 stands for the second partition because you count your partitions from one.
Finally, to change the timeout and default menu entries, I've written previously about this here:
http://glassfloor.blogspot.com.au/search/label/Grub
So, What do I Think?
This is definitely worth sticking with as the potential rewards are significant. So far, I have the system up and running - and the Grub2 bootloader is doing what I want. Everything boots smoothly to what I want.If you want to use PC-BSD (and like I said, for a family this makes a great system) .. use an nVidia video card and have only BSD on the system. Once you know what you are doing with re-configuring boot loaders, it is pretty straightforward - but getting there may be an effort.
I'm glad I stuck it out despite my initial setbacks because I'm really quite excited about what can be done with PC-BSD. For the moment though, I'm happy with what I've achieved and that what I've written up above may help someone have an easier time than me. I'll write further on this as it is worthwhile documenting.
Later
