Polkit and USB Mount Authentication

Suddenly popping in a USB or CD/DVD was asking for authentication!  Short story, polkit issue.  Edit org.freedesktop.udisks2.policy in /usr/share/polkit-1/actions and change:


to read:

“<allow_active> yes</allow_active>”

polkit — Authorization Manager

OS/2: Blue Lion – Arca Noae

According to the Arca Noae site:

Blue Lion is Go!

Arca Noae has become an IBM business partner and has an agreement in place that enables us to produce our own OS/2 distribution. We have given this project the code name “Blue Lion” (which probably won’t be the final release name!).

Other sites:

TechRepublic: OS/2: Blue Lion to be the next distro of the 28-year-old OS

Arca Noae is developing a new full distribution of OS/2 that should ease the pain of upgrading or deploying the OS on modern hardware.

OSNews: Blue Lion: new OS/2 distribution due 2016

The Register: Is the world ready for a bare-metal OS/2 rebirth?




I saw this in the logs of both VB 4.3.30 and 5+:

Failed to open “/dev/vboxdrvu”, errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE

Which based on this post (Ref) is caused by having the wrong permissions, resulting in:

ls -l /dev
crw------- 1 root root 10, 57 Oct 2 05:58 vboxdrv
crw------- 1 root root 10, 56 Oct 2 05:58 vboxdrvu
crw------- 1 root root 10, 55 Oct 2 05:58 vboxnetctl
drwxr-x--- 4 root vboxusers 80 Oct 2 05:58 vboxusb

The fix is to create /lib/udev/rules.d/20-virtualbox2.rules and add:

KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers", MODE="0660"
KERNEL=="vboxdrvu", NAME="vboxdrvu", OWNER="root", GROUP="vboxusers", MODE="0660"
KERNEL=="vboxnetctl", NAME="vboxnetctl", OWNER="root",GROUP="vboxusers", MODE="0660"

Then restart the system and the permissions are now:

ls -l /dev
crw-rw---- 1 root vboxusers 10, 57 Oct 5 06:00 vboxdrv
crw-rw---- 1 root vboxusers 10, 56 Oct 5 06:00 vboxdrvu
crw-rw---- 1 root vboxusers 10, 55 Oct 5 06:00 vboxnetctl
drwxr-x--- 4 root vboxusers 80 Oct 5 06:00 vboxusb

I am not sure how correct this is by including vboxdrv, but it does prevent the errors in VB logs.

Virtual Box 5.0 in Portage!

I guess just in time for Windows 10???


emerge –unmerge -p virtualbox

Same old catch if you want the BIOS compiled then Open Watcom is needed.  To be specific, I have had to use Open Watcom 1.9.  The emerge output if OW is not found:

>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-emulation/virtualbox-5.0.0/work/VirtualBox-5.0.0 …
Checking for environment: Determined build machine: linux.amd64, target machine: linux.amd64, OK.
Checking for kBuild: found, OK.
Checking for gcc: found version 4.8.4, OK.
Checking for Open Watcom:
** Open Watcom was not found!
Checking for iasl: found version 20130117, OK.
Checking for xslt: found, OK.

After installing Open Watcom and “export WATCOM=/usr//bin/watcom19”, running emerge should result in:

>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-emulation/virtualbox-5.0.0/work/VirtualBox-5.0.0 …
Checking for environment: Determined build machine: linux.amd64, target machine: linux.amd64, OK.
Checking for kBuild: found, OK.
Checking for gcc: found version 4.8.4, OK.
Checking for Open Watcom: found version 1.9, OK.
Checking for iasl: found version 20130117, OK.
Checking for xslt: found, OK.

Also had to “emerge -v virtualbox-extpack-oracle app-emulation/virtualbox-additions” separately.


Race into Space – Retro game!

I was reading today and had one of those remember that game moments, so I hit Google for a search of Race Into Space.  I played this one for hours!  I had the CD version, so that would make my experienced dated to mid-1990s.  Of course I could have found the game online, installed it in a DOS VM, and played, but I am too lazy.  However, I found that it had been open sourced and was available on Linux.  The freeware version website is here. and the Github page is here.  I might be too lazy to install it in a VM, but not so lazy that I would not compile it and give it a try.

It was pretty straightforward, just follow the instructions on the Github page (not Sourceforge – to stay away from that controversy):

$ git clone git://github.com/raceintospace/raceintospace.git
$ mkdir raceintospace-build; cd raceintospace-build
$ cmake ../raceintospace
$ make

Of course that does not include the final make install.  After that, a simple raceintospace in a terminal and I was off to waste some time just like it was 1995.  The manual is located here.

The opening screen:


The start screen to select options:


Another screenshot:



Gnome 3.16

Classes are finally out for summer and it is time for catch up.  Still, I had time to cause undue stress in my life.  I decided to do what I had promised myself I would not do again, install a new version of Gnome before it was stable in portage.  Anyway, the upgrade to Gnome 3.16 was not without pains along the way, but it is done.


The Dreaded Gentoo emerge -e @world

Not something I take lightly, nor is it something I look forward to doing.  In Gentoo the emerge “-e” means rebuild all packages installed on the system that portage has recorded.  A quick ‘equery -l “*”‘ will list all packages installed.

So why do I do this every year or so?  Just to make sure I have not messed something up over time.  It is not something I look forward to because the time from start to finish is measured not in hours, but days.  For example, it took my i7 laptop (1,400+) packages with SSDs and plenty of ram 24+ hours to finish.  However, in the end I was confident the system was in good shape.

So here are my tips at making this painful experience a little less painful.

1.  I start by getting the system in the best shape possible:

emerge -v –update –deep –newuse –with-bdeps=y –autounmask-write @world

If needed:

emerge @preserved-rebuild


emerge –depclean

If you are paranoid careful then do:


perl-cleaner –all

2. Next:  cd /var/log/portage/elog

You should find the file summary.log.  Rename it or delete it, whatever suites you.  Once the big emerge starts, all the messages will be logged to a new summary.log file.

2. Execute:   emerge -pve –keep-going @world

Note the “p” for pretend.  If everything is good then it should tell you that the Oracle Java packages need to be downloaded.  This is a good time to download them (I have Jre and jdk packages installed), move them to portage/distfiles, and do not forget:

chown portage:portage <file> 

to the files.  Make a mental note of the total number of packages to build.

3. Start by executing:  emerge -ve –keep-going @world

Why the keep-going? Because if everything is good after step 1 then any issues should be minor and this keeps from having to start the process from the beginning.

Now all there is to do is wait and hope for the best which usually does not help.  As the emerge progresses with each new package the typical package number X of Y (total) being processed.  So if you start with a total of 1,400 packages and later notice emerge outputting 20 of 800 then there has been a problem which has been skipped (note:  the –keep-going option).  Go check the summary.log file to find what the problem might have been.  The best part is that you should be able to fix it while the emerge -e keeps churning along.