Intel | Technology Tales

Installing FreeBSD in a VirtualBox Virtual Machine

2^nd March 2014

With UNIX being the basis of Linux, I have a soft spot for trying out any UNIX that can be installed on a PC. For a while, I had OpenSolaris on the go and even vaguely recall having a look at one of the BSD's. However, any recent attempt to install one of the latter, and there are quite a few around now, got stymied by some sort of kernel panic caused by using AMD CPU's. With the return to the Intel fold arising from the upgrade of my main home PC last year, it perhaps was time to try again.

The recent release of FreeBSD 10.0 was the cue and I downloaded a DVD image for a test installation in a VirtualBox virtual machine with 4 GB of memory and a 32 GB virtual hard drive attached (expanding storage was chosen so not all the allocated space has been taken so far). The variant of FreeBSD chosen was the 64-bit x86 one, and I set to installing it in there. Though not as pretty in appearance as those in various Linux distros, the installer was not that user unfriendly to me. Mind you, I have experience of installing Arch Linux, which might have acclimatised me somewhat.

Those installation screens ask about the keyboard mapping that you want, and I successfully chose one of the UK options. There was limited opportunity for adding extras, though there was a short list of a few from which I made some selections. Given that user account set up also was on offer, I would have been better off knowing what groups to assign for my personal user account to have to avoid needing to log in as root so often following system start up later. Otherwise, all the default options were sufficient.

When the installation process was complete, it was time to boot into the new system and all that was on offer was a command line log in session. After logging in as root, it was time to press pkg into service to get a desktop environment in place. The first step was to install X:

pkg install xorg

Then, it was time to install a desktop environment. While using XFCE or KDE were alternatives, I chose GNOME 2 due to familiarity and more extensive instructions on the corresponding FreeBSD handbook page. Issuing the following command added GNOME and all its helper applications:

pkg install gnome2

So that GNOME starts up at the next reboot, some extra steps are needed. The first of these is to add the following line into /etc/fstab:

proc /proc procfs rw 0 0

Then, two lines were needed in /etc/rc.conf:

gdm_enable="YES" gnome_enable="YES"

The first enables the GNOME display manager, while the second activates other GNOME programs that are needed for a desktop session to start. With each of these in place, I got a graphical login screen at the next boot time.

With FreeBSD being a VirtualBox Guest, it was time to consult the relevant FreeBSD manual page. Here, there are sections for a number of virtual machine tools, so a search was needed to find the one for VirtualBox. VirtualBox support for FreeBSD is incomplete in that there is no installation media for BSD systems, while Linux and Solaris are supported along with Windows. Therefore, it is over to the FreeBSD repositories for the required software:

pkg install virtualbox-ose-additions

Aside from the virtual machine session not capturing and releasing the mouse pointer automatically, that did everything that was needed, even if it was the open source edition of the drivers and their proprietary equivalents. To resolve the mouse pointer issue, I needed to temporarily disable the GNOME desktop session in /etc/rc.conf to drop to a console only session where xorg.conf could be generated using the following commands:

Xorg -configure cp xorg.conf.new /etc/xorg.conf

In the new xorg.conf file, the mouse section needs to be as follows:

Section "InputDevice" Identifier "Mouse0" Driver "vboxmouse" EndSection

If it doesn't look like the above, and it wasn't the case for me, then it needs changing. Also, any extra lines from the default set up also need removing, or the mouse will not function as it should. The ALT+F1 (for accessing GNOME menus) and ALT+F2 (for running commands) keyboard shortcuts then become crucial when your mouse is not working as it should and could avert a panic too; knowing that adjusting a single configuration file will resolve a problem when doing so is less accessible is not a good feeling as I discovered to my own cost. The graphics settings were fine by default, but here's what you should have in case it isn't for you:

Section "Device" ### Available Driver options are:- ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", ### <string>: "String", <freq>: "<f> Hz/kHz/MHz" ### [arg]: arg optional Identifier "Card0" Driver "vboxvideo" VendorName "InnoTek Systemberatung GmbH" BoardName "VirtualBox Graphics Adapter" BusID "PCI:0:2:0" EndSection

The next step is to ensure that your HAL settings are as they should. I needed to create a file in /usr/local/etc/hal/fdi/policy called 90-vboxguest.fdi that contains the following:

<?xml version="1.0" encoding="utf-8"?>  <deviceinfo version="0.2"> <device> <match key="info.subsystem" string="pci"> <match key="info.product" string="VirtualBox guest Service"> <append key="info.capabilities" type="strlist">input</append> <append key="info.capabilities" type="strlist">input.mouse</append> <merge key="input.x11_driver" type="string">vboxmouse</merge> <merge key="input.device" type="string">/dev/vboxguest</merge> </match> </match> </device> </deviceinfo>

With all that set, it is time to ensure that the custom user account is added to the wheel and operator groups using this command:

pw user mod [user name] -G wheel operator

Executing the above as root means that the custom account can run the su command so that logging in as root at the start of a desktop session no longer is needed. That is what being in the wheel group allows, so anyone in the operator group can shut down or restart the system. Since both are facilities readily available on Linux, so I fancied having them in FreeBSD too.

Being able to switch to root in a terminal session meant that I could go on to add software like Firefox, LibreOffice, GIMP, EMACS, Geany, NetBeans, Banshee and so on. Though there may be a line of opinion that FreeBSD is a server operating system, all of these make it more than passable for serving as a desktop one too. There may be no package management GUI as such and the ones that come with GNOME do not work either, yet anyone familiar with command line working will get around that.

While FreeBSD may be conservative, that has its place too, and being able to build up a system one item at a time teaches far more than getting everything already sorted in one hit. So far, there is enough documentation to get me going, leaving me to see where else things go too. So far, the OS hasn't been that intimidating, which is good to see.

Whither Fedora?

10^th January 2009

There is a reason why things have got a little quieter on this blog: my main inspiration for many posts that make their way on here, Ubuntu, is just working away without much complaint. Since BBC iPlayer isn't working so well for me at the moment, I need to have a look at my setup. Otherwise, everything is continuing quietly. In some respects, that's no bad thing and allows me to spend my time doing other things like engaging in hill walking, photography and other such things. While I suppose that the calm is also a reflection of the fact that Ubuntu has matured, there is a sense that some changes may be on the horizon. For one thing, there are the opinions of a certain Mark Shuttleworth, though the competition is progressing too.

That latter point brings me to Linux Format's recently published verdict that Fedora has overtaken Ubuntu. I do have a machine with Fedora that performs what I ask of it without any trouble. However, I have never been on it trying all the sorts of things that I ask of Ubuntu, so my impressions are not in-depth ones. Going deeper into the subject mightn't be such a bad use of a few hours. What I am not planning to do is convert my main Ubuntu machine to Fedora. I moved from Windows because of constant upheavals and I have no intention to bring those upon me without good reason, something that's just not there at the moment.

Speaking of upheavals, one thought that is entering my mind is that of upgrading that main machine. Since its last rebuild was over three years ago, computer technology has moved on a bit since then, with dual and quad-core CPU's from Intel and AMD coming into the fray. Of course, the cost of all of this needs to be considered too, which is never more true than in these troubled economic times. If you asked me about the prospect of a system upgrade a few weeks ago, I would have ruled it out of hand.

What has got me wondering is my continued used of virtualisation and the resources that it needs. Mad notions like running more than one VM at once will put any CPU or memory through their paces. Another attractive idea would be getting a new and bigger screen, particularly with what you can get for around £100 these days. However, my 17" Iiyama is doing well enough to consign this one to the wish list for now. None of the changes that I have described are imminent, even if I have noticed how fast I am filling disks up with digital images to make an expansion of hard disk capacity a higher priority.

If I ever get to do a full system rebuild with a new CPU, memory and motherboard (I am not so sure about graphics since I am no gamer), the idea of moving into the world of 64-bit computing comes about. Since the maximum amount of memory usable by 32-bit software is 4 GB, 64-bit software is a must if I decide to go beyond this limit. That all sounds very fine, aside from the possibility of problems arising with support for legacy hardware. It sounds like another bridge to be assessed before its crossing, even if two upheavals can be made into one.

Besides system breakages, the sort of hardware and software changes over which I have been musing here are optional and can be done in my own time. That's probably just as well in a downturn like we are experiencing now. Being careful with money becomes more important at times like these, which means that it's fortunate that free software not only offers freedom of choice and usage but also a way to leave the closed commercial software acquisition treadmill with all of its cost implications, leaving money for much more important things.

A new laptop

7^th January 2008

Having had it on my wish list for a few years, I finally succumbed to temptation and purchased a laptop in the PC World sale, a Toshiba Equium A200-1VO in fact. I reserved it on the web and popped into the nearest store a few hours later. However, while the reservation system worked, the collection did not go as smooth as I had hoped; it appears that the store where I went was not as well staffed as I would have liked, so I needed to wait before I was served. Finding the right part of the store was another issue. Nevertheless, service was efficient once the wait was over, and I left with the said laptop, a half-price copy of Norton 360 and a network cable.

The laptop comes with an Intel Pentium Dual-Core CPU, 2 GB of RAM and a 120 GB hard drive. The size of the hard drive may not set the world alight and neither, I suspect, will the Intel graphics adapter. Speaking of graphics, the glossy screen might not be to everyone's taste, but its 1280x800 maximum resolution is definitely respectable. Windows Vista Home Premium is the included operating system, and a 90-day trial of Norton Internet Security comes too; I'll wait for that to expire before adding in Norton 360. While I am not rushing to add software, the Home and Student version of Office 2007 has made its way on there.

As regards performance, the machine so far has done what I have asked of without any bother. Even so, battery life is far from extensive, with a maximum of ninety minutes. For long stints away from a power socket, an extra battery might be in order, and there is an offer show on the box in which the device came. That would add to the weight, though; at around 2.5 kg, it isn't something that I would go carrying on a weekend backpacking trip. Despite those limitations, it will get some enough use for me to see how things proceed from here.

Toshiba Equium A200-1VO

Is Vista’s DRM a step too far?

16^th February 2007

If it isn’t enough that Vista’s licensing legalese has being causing raised blood pressure, its use of DRM technology is arousing passionate outbursts and outpourings of FUD. The fact that DRM has been part of the Windows has been included in Windows since the 1990’s does nothing to quell the storm. One thing that needs to be pointed out is that the whole furore entails the delivery of protected content to consumers. Microsoft would no doubt approve of the line that if there was no protected content, then there would be no need to worry. However, there is a sizeable number of people who do not trust Microsoft to keep to its word and are making their feelings known.

The embodiment of the issue is Microsoft’s incorporation of HDCP into 64-bit Vista. It is an Intel standard that is on the market, with users already having bad experiences with it. The problems surround the need to ensure that protected video is not intercepted while a movie is being played, and this involves the hardware as much as the software. The result is that you need a compatible monitor that will have the correct inputs so that DRM can be employed. Some also suggest that this is not the end of the matter as regards hardware compatibility and the list can grow long enough that a whole new PC looks like a good idea.

At the heart of this debate is a paper written by Peter Gutmann of the University of Auckland, in which the consequences of Microsoft’s implementation are examined. The idea of a system with an alternative agenda to that which you have is hardly enthralling: neither using CPU time to monitor DRM and the locking down hardware are particularly attractive. Such is the exposure that this article has received that even Microsoft has had to respond to it. The point that they try to make is that decoding of protected content occurs in a sandbox and does not affect anything else that might be going on in the system. Unfortunately for them, many of those adding comments to the piece take the chance to launch a broadside on the company; some of the vitriol is certainly successful when it comes to trying to put me off Vista. To Microsoft’s credit, the negative comments remain, but it far from helps their attempted rebuttal of Gutmann.

Though the main fuel for the negativity is not Gutmann’s paper per se but a lack of trust in Microsoft itself, all of this despite its Trustworthy Computing initiative. The question goes like this: if the company uses DRM for video and audio, where else could it use the technology? The whole licensing debate also furthers this, and it is at this point that the fear, uncertainty and doubt really goes into overdrive, no matter how much effort is expended by people like Ed Bott on debunking any myths. Users generally do not like software taking on itself to decide what can and cannot be done. Personally, I have experience of Word’s habits of this nature in the past, and they were maddening: trying to produce my doctoral thesis with it went OK until I tried pulling the whole thing together using a master document; I backtracked and made PRN files for each chapter so that it wouldn’t change; LaTeX would never have done this….

What is the point of all of this DRM? It looks as if Microsoft clearly feels that it is necessary to pitch the PC as an entertainment content delivery device to continue growing their revenues in the home users market. Some would take this idea even further: that it is control of the entertainment industry that Microsoft wants. However, to do so, they have gone with strong DRM when there exists a growing backlash against the technology. And then there’s the spectre of the technology getting cracked. In fact, Alex Ionescu has found a potential way to fool the Protected Media Path (called Protected Video Path in a ComputerWorld Security article) into working with unsigned device drivers. Needless to say given the furore that has been generated, but there are others who are more than willing to take the idea of cracking Vista DRM even further. A recent remark from a senior Microsoft executive will only encourage this.

I must admit that I remain unconvinced by the premise of using a PC as my only multimedia entertainment device. Having in the past had problems playing DVD’s on my PC, I nowadays stick to using a standalone DVD player to do the honours. And I suspect that I’ll do the same with HD video should I decide to do watch it; it’s not that high on my list of priorities. In fact, I would be happier if Microsoft made a version of Vista with and without protected HD capability, and they do: 32-bit Vista will not play protected HD video. And it avoids all the hackles that have caused so much controversy too, allowing an easier upgrade in the process. The downsides are that the security model isn’t as tough as it is in the 64-bit world and that maximum memory is limited to 4 GB, not an issue right now, it more than likely will become one. If you are keen on Vista, the 32-bit option does give you time to see how the arguments about the 64-bit world run. And if hardware catches up. As for me, I’ll stick with XP for now.

Hard drive partitioning

22^nd January 2007

It has to be said that hard drive partitioning isn’t something that most people do very often, if at all, in these days of cheap storage and system virtualisation. I must admit to having several disks in my main machine and can vouch for the virtues of virtualisation: VMware allows me to run multiple operating systems on the same machine, a very useful asset so long as enough memory is available. We can expect to hear more about virtualisation, with the likes of Intel and AMD looking at hypervisor solutions for this.

Partitioning does give you what appear to be multiple drives from just the one, and that is very useful when you only have a single hard drive in your PC. This was very much the case in my early computing days, when catastrophic Windows 9x crashes (some self-inflicted…) often resulted in the pain of a complete re-installation of everything that had been on there. The independence offered by partitions certainly offered me peace of mind back then, yet 100MB Iomega Zip disks were a very useful defence in depth.

Without partitioning, my curiosity regarding the world of Linux would not have been sated, though an approach involving multiple hard drives certainly came into play later on. Having been a Sun Solaris user at university, Linux certainly aroused much interest in me and I have to say that it has come a long, long way since my first ventures into its world.

While the Windows tool FDISK could partition hard drives for you, it wasn’t non-destructive: you had to be prepared to restore all of your files from a backup and do a complete software re-installation following its use. It was designed for setting things up at the outset and not changing them later, and that thinking seems to have pervaded the design of the Disk Management console found in XP.

For more flexible and non-destructive partitioning, Powerquest’s Partition Magic became the tool of choice, though I did have a dalliance with a package called Partition It before taking the plunge. Partition Magic is now in the Symantec stable and not a lot seems to be heard of it. While version 7, the last from Powerquest before its takeover, has been my staple, 983 errors have been thrown by the application at times and one partitioning operation went awry, forcing me to depend on my backups. Since version 8 still throws 983 errors, I started to look beyond Partition Magic altogether. In my search, I happened on version 10 of Acronis Disk Director Suite. It got a strong recommendation from reviewer Davey Winder in PC Pro magazine (backup software True Image 10 from the same company also got a thumbs up from a different PC Pro reviewer) which gave some reassurance and I have to say that I agree. An operation refused by Partition Magic was completed successfully and safely, so I know where my vote goes.