Skip to main content

MacPorts trouble after Mavericks upgrade?

I was one of the early adopters for the OSX 10.9 Mavericks update on several of my machines.  As I quickly found out, however,  MacPorts updating was broken (relax, the existing binaries that were already installed by ports were running just fine).

The primary complaint by the ports installer was the lack of gnutar.  If this is your issue; read on.  Otherwise, I'm not sure if this is much use to you.

First step is: http://trac.macports.org/wiki/MavericksProblems.  There is a link to an ​installer for Mavericks.  This pertains specifically to Mac Ports 2.2.1 - if you are at that version or 2.2.0 then you should be ok to use it.  If you're at a newer Mac Ports release, then this post is probably outdated for you.  (Hint:  issuing "port version" in Terminal should tell you what version you're at).

Run the installer, and you may find that ports will start working again for new updates.  In my case, it did not.  As I updated to Mavericks, XCode became outdated.  So your next step is to download the new version of XCode via the App Store.

After getting XCode up to date, you need to run from Terminal; the command "xcodebuild -license".  In many cases, you'll need to append sudo, e.g. "sudo xcodebuild -license".

Finally,  you'll need to make sure XCode has the latest command line tools installed.  In the new version of XCode, it is not clear where to find it.  Fortunately, there's a quicker way:  "xcode-select --install" will pull up the dialog to install the latest tools.  As with xcodebuild's license step above, you will usually need to run it with "sudo".

Now, run "port selfupdate" followed by "port upgrade outdated".


Comments

Popular posts from this blog

Starting vmtoolsd as a service on Red Hat / CentOS

If you're like me;  you may manage virtual servers within vSphere.. Linux ones.  Red Hat ones, in particular, but this applies to CentOS as well.

A long, long time ago, in a galaxy far away, the vmware-tools setup procedure installed the necessary init script for you.  Lately though, for new images that I've been building - those init scripts aren't getting installed by the vmware tools installation package.  So they don't start up on reboot.  VMware based backups failed; clock were going askew, you name it.   I need that daemon started on reboot.

Without a SysV init script handy, I had to roll my own.. and this is the result;  despite having worked with Linux for well over 15 years, setting up SysV init scripts remain somewhat of a black art.  The ones on our older system were more complicated than we needed.  I was aiming for something simpler and portable.

With RHEL 7, the rumor mills are abuzz with systemd so that may change. But, I'm a practical system admini…

Attempting to use dd on Mac OSX? Resource Busy?

If you're trying to use the dd command to image a usb disk or another device and you're running into an error that looks like:

# dd: /dev/disk#: Resource busy

There is a simple solution.

Use OSX's Disk Utility and unmount any of the partitions you have mounted on that particular disk without unmounting or ejecting the disk itself.

Afterwards, attempt the dd command again.

Update:  

Attempting to use the umount utility in Mac OSX will result in a "Resource busy -- try 'diskutil unmount'".  The command-line equivalent would be:

# sudo diskutil unmount /Volumes/<disk in question>

E.g.  

# sudo diskutil unmount /Volumes/FLASHUSB

NetApp: Disabling snapshot for a volume on Data OnTAP

This is one of those things that isn't always very obvious. Sometimes, you need to disable snapshots for a volume.

Why in the world would someone want to disable a perfectly good feature of NetApp NAS Storage? Server/data migration for one. Disabling it temporarily will prevent the volume from filling up the snapshot directory. Maybe your volume doesn't need snapshots (data always changing, and can not be recoverable even with snapshots- such as oracle data dirs, in which case snapshots are useless).
You have to perform simple but important tasks. If your volume has a schedule, turn it off.

somefiler> snap sched rootvol Volume rootvol: 2 4 8@2,4,6,12,164
somefiler> snap sched rootvol 0 0 0 
somefiler> snap sched rootvol Volume rootvol: 0 0 0

That takes care of that. Next step is to disable the automatic snapshot option.

somefiler> vol options rootvol nosnap on

Now if you issue vol options rootvol You should see an option that says nosnap=on.

Lastly, you'l…