jblachly

The following keys, when placed in the customer_metadata section of the VM definition JSON will effect the specified behaviour:

smartos key	corresponds to cloudinit key	effect
hostname	local-hostname
root_authorized_keys	public-keys	copies to /root/.ssh and default user ~/.ssh (e.g., ubuntu)
user-script	user-script	Executed each boot
user-data	legacy-user-data
cloud-init:user-data	user-data	Evaluated by cloud-init once at VM creation only
iptables_disable	iptables_disable	?

vsouza

# Set variables in .bashrc file

# don't forget to change your path correctly!

export GOPATH=$HOME/golang
export GOROOT=/usr/local/opt/go/libexec
export PATH=$PATH:$GOPATH/bin
export PATH=$PATH:$GOROOT/bin

plepe

mdadm

Glossary:

• md: multiple devices

command	description
cat /proc/mdstat	show status of all raids
mdadm --detail /dev/md0	detailed status of raid md0

binamov

<powershell>
 
#####
#DON'T FORGET TO SET/CHANGE THE USERNAME/PASSWORD BELOW!
#####
 
$user="chef"
$password="chef"

# Disable password complexity requirements

ksafranski

Intro

TCL-Expect scripts are an amazingly easy way to script out laborious tasks in the shell when you need to be interactive with the console. Think of them as a "macro" or way to programmaticly step through a process you would run by hand. They are similar to shell scripts but utilize the .tcl extension and a different #! call.

Setup Your Script

The first step, similar to writing a bash script, is to tell the script what it's executing under. For expect we use the following:

#!/usr/bin/expect

chitchcock

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real