This post originally appeared on UnixBen at Oracle Blogs.

This is a short run down on how to get tmux running on your Mac OS X system. The same methodology applies when compiling this on Solaris.

This post originally appeared on UnixBen at Oracle Blogs.

Solaris 11 brings some fantastic new networking features in the form of Project Crossbow. These features include virtual network interface cards (vnics) and virtual switching (etherstubs), flows for controlling bandwidth and network utilisation and more detailed analytics and observability functions just to name a few. Along with these advanced new features, many of our old favourites are enhanced to make life easier for the already busy systems administrator.

This post originally appeared on UnixBen at Oracle Blogs.

If you’re stuck on a network that has no DHCP but you do have a Jumpstart server, you can still successfully install your OS.

Today I fired up ipmpstat to check on my multipath status and was surprised on two accounts:

1. IP multipath was not enabled on my machine. Ordinarily this would be bad, but my memory is fading lately and I forgot that I unconfigured IPMP some weeks ago…

2. Pleasantly surprised I was to find that ipmpstat gives an informative and dare I say it – useful – message:

1
2

$ pfexec ipmpstat -a
ipmpstat: cannot contact in.mpathd(1M) -- is IPMP in use?

All Solaris tools should be this informative. Why is this response from a command better than printing a usage statement, or some other error condition? In particular:

• What’s the error? Cannot contact in.mpathd
• Have a look at the man page! in.mpathd(1M)
• Please jog your memory. Is IPMP in use?

While my experience using Tumblr for this blog wasn’t so bad, I did find that availability of the site was not what I expected, or was led to believe. Consequently, I’m now hosting this site myself on a Linode VPS.

Link: Ctrl-Shift-Eject

A nifty keystroke for your Mac. Don’t worry, it won’t break anything.

Little one, big one (Taken with Instagram at Sichuan House)

This, is what I’m talking about (Taken with Instagram at Sichuan House)

I’d never bothered to patch any zones on my OpenSolaris or OpenIndiana installations at home until now. It’s basically pretty easy if you have a non-complex, standard zone.

1
2
3

$ pfexec zoneadm -z web1 halt
$ pfexec zoneadm -z web1 detach
$ pfexec zoneadm -z web1 attach -u

The commands above are rudimentary but they work for me. There probably is a more correct way to do this though — feel free to add a comment with “Your Way”.

Living in the fast-lane, I’ve just completed an upgrade of my (recently upgraded) OpenIndiana machine to Oracle Solaris 11 Express. This process is just as easy as the upgrade from OpenSolaris to OpenIndiana. Again, here’s my run sheet for the upgrade:

1
2
3
4
5
6
7

$ pfexec pkg set-publisher -P -O http://pkg.opensolaris.org/release opensolaris.org
$ pfexec pkg set-publisher --non-sticky opensolaris.org
$ pfexec pkg set-publisher --non-sticky openindiana.org
$ pfexec pkg set-publisher -P -g http://pkg.oracle.com/solaris/release solaris
$ pfexec pkg image-update --accept --be-name snv_151a
$ pfexec beadm activate snv_151a
$ pfexec reboot

Once the system has rebooted, a simple {zpool,zfs} upgrade of all your pools and filesystems will put you on the latest and greatest.