James E Keenan jkeenan

I am trying to install OpenBSD/amd64 5.9 inside VirtualBox 5.1. I did this successfully with FreeBSD 10.3 last weekend, so I had high hopes for success with OpenBSD. Since the FreeBSD install required a .iso file, I located a similar file for OpenBSD:

http://ftp5.usa.openbsd.org/pub/OpenBSD/5.9/amd64/install59.iso

The installation process went fairly smoothly. I selected a root password and created one user and that user's password. I selected the defaults in almost all cases and attempted nothing fancy. I finally got to this point:

CONGRATULATIONS! Your OpenBSD installation has been successfully completed.
To boot the new system, enter 'reboot' at the command prompt.

So I then entered reboot at the # prompt, and the system proceeded to reboot in what appeared to be the expected manner. However, after the demsg message printed out and I got to here:

Immediate problem:

$ vagrant up --provider virtualbox
No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

Perl 5.22 just came out. Up until last year, when a new perl would come out, I would download a tarball to my machine (either an older Mac laptop or a Debian server on http://linode.com), unpack the tarball, configure, build and test from source, and finally call sudo make install to install the executable into /usr/local/bin. I would then use the cpan shell to download, configure, build and install Perl modules into /usr/local/lib.

In other words, I would install Perl and its libraries in a traditional Unix-y way.

When I got my current laptop in March 2014, I decided to take a different approach. I decided to forego installing into /usr/local and to instead use perlbrew to install all the perl versions I wanted underneath my home directory. One reason I took this approach is that in the work I do for Perl 5 Porters, it's important to be able to switch back and forth between various Perl versions with great ease.

I also decided to start using cpanm to install Perl modules,

Migrate List-Compare from Subversion on One Machine to Git on Another

... and then up to github.com!

Initial Situation

On a Mac OS X iBook G4, I had a Subversion repository with a wide variety of projects: my CPAN modules, YAPC and other conference presentations, etc. I wanted to transfer the locus of development for certain projects, beginning with my CPAN distribution List-Compare, to a newer machine running Ubuntu

	#!/usr/bin/env perl6
	use v6;
	use fatal;
	sub rpn (Str $line, @stack) returns Array {
	for $line.words {
	#say 'Debug ' ~ @stack.perl ~ $_;
	when $_ ~~ /\d/ { @stack.push( +($_)); };
	my $top = @stack.pop() if @stack;
	my $next = @stack.pop() if @stack;
	when '+' { @stack.push($next + $top) };

	/usr/local/bin/perl tools/build/h2inc.pl include/parrot/enums.h lib/Parrot/Pmc2c/PCCMETHOD_BITS.pm
	/usr/local/bin/perl tools/build/addgenerated.pl "lib/Parrot/Pmc2c/PCCMETHOD_BITS.pm" "[devel]" lib
	/usr/local/bin/perl tools/build/pbcversion_h.pl > include/parrot/pbcversion.h
	/usr/local/bin/perl tools/build/addgenerated.pl "include/parrot/pbcversion.h" "[main]" include
	/usr/local/bin/perl tools/build/vtable_h.pl
	/usr/local/bin/perl tools/build/addgenerated.pl "include/parrot/vtable.h" "[main]" include
	/usr/local/bin/perl -Ilib tools/build/pmc2c.pl --vtable
	/usr/local/bin/perl -Ilib tools/build/pmc2c.pl --dump src/pmc/default.pmc
	/usr/local/bin/perl -Ilib tools/build/pmc2c.pl --dump src/pmc/fixedintegerarray.pmc
	/usr/local/bin/perl -Ilib tools/build/pmc2c.pl --c src/pmc/fixedintegerarray.pmc