Paul Paradise natacado

Go into your git checkout folder of ipxe.

Save the below file as nic-menu.ipxe.

Build iPXE like this:

cd src && make EMBED=../nic-menu.ipxe && cd ..

Requirements: current iPXE as of 2013-08-01 (for proper behavior of autoboot with a network device specified, netX feature, PCI vendor/device ID display and inc command)

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

Add the following chunk to your existing ISC dhcpd.conf file.

if exists user-class and ( option user-class = "iPXE" ) {
    filename "http://boot.smidsrod.lan/boot.ipxe";
}
else {
    filename "undionly.kpxe";
}

(or see https://gist.github.com/4008017 for a more elaborate setup

	newpg=9.6.1 # set to new PG version number
	oldpg=`pg_config --version \| cut -d' ' -f2`

	# PG 96. upgrades the readline to v7, which breaks anything linked against readline v6, like ruby via ruby-build.
	# I think this should prevent it from installing v7. But if weird shit happens with various rubies,
	# you'll have to reinstall them.
	brew pin readline

	# Stop current Postgres server
	brew services stop postgresql

	#!/usr/bin/env ruby

	#= k
	#== Requirements
	# I install Chef with rubygems. May/may not work with other install methods.
	#
	#== INSTALL
	# copy this to ~/bin/k
	#
	#== USE

	#!/usr/bin/env python

	# with help and inspiration from
	# * ASN1_generate_nconf(3) (specifically the SubjectPublicKeyInfo structure)
	# * http://www.sysmic.org/dotclear/index.php?post/2010/03/24/Convert-keys-betweens-GnuPG%2C-OpenSsh-and-OpenSSL
	# * http://blog.oddbit.com/2011/05/converting-openssh-public-keys.html

	import sys
	import base64
	import struct

	there appears to be a way to stop daemons from being started when they are installed: apparently just create /usr/sbin/policy-rc.d with "#!/bin/sh; exit 101"

	the way I read it (here's a link that's not an e-mail: http://people.debian.org/~hmh/invokerc.d-policyrc.d-specification.txt) scripts usually call invoke-rc.d but if you have policy-rc.d that gets called. I'm not sure where else invoke-rc.d is called and don't know what the consequences would be