hSATAC

#!/usr/bin/perl
# Author: Todd Larason <jtl@molehill.org>
# $XFree86: xc/programs/xterm/vttests/256colors2.pl,v 1.2 2002/03/26 01:46:43 dickey Exp $

# use the resources for colors 0-15 - usually more-or-less a
# reproduction of the standard ANSI colors, but possibly more
# pleasing shades

# colors 16-231 are a 6x6x6 color cube
for ($red = 0; $red < 6; $red++) {

codepunkt

#!/bin/bash
options=('find' 'delete')
PS3='state your wish: '

echo -e "\nfind/delete corrupt whisper-files"

select opt in "${options[@]}"; do
  case $REPLY in
    [12] ) option=$opt; break;;
    * ) exit;;

isage

#!/usr/bin/env perl

use strict;
use warnings;
use 5.010;

use JSON qw( decode_json );     # isn't default module, must be installed via CPAN or your system package manager
use Time::HiRes qw ( usleep );  # for simple delays

my $outputfile = shift || die "use $0 outputfile.png";                       # getting output filename from command-line params

jedi4ever

if [ -f .veewee_params ]                                                             
then                                                                                 
  . .veewee_params                                                                   
fi                                                                                   
                                                                                     
if [ -z "$CHEF_INSTALLMETHOD" ]; then                                                
  export CHEF_INSTALLMETHOD="gems"                                                   
fi                                                                                   
                                                                                     
# Installing chef                                                                    

iroller

#!/usr/bin/env knife exec

# A knife exec script to change chef node's name, preserving all the attributes.
#
# Usage: knife exec rename-node.rb old-name new-name
#
# Script retrieves the Node object, changes its 'name' attribute,
# creates new Node object with updated name and rest of attributes
# untouched. Then it deletes old Node and Client objects from
# database, and logs into the server to update it:

jcyamo

#!/usr/bin/env python

# based on cb-exit used in CrunchBang Linux <http://crunchbanglinux.org/>

import pygtk
pygtk.require('2.0')
import gtk
import os
import getpass

rafi

# github.com/rafi i3status config

# i3status configuration file
# see "man i3status" for documentation.

# It is important that this file is edited as UTF-8.
# The following line should contain a sharp s:
# ß
# If the above line is not correctly displayed, fix your editor first!

danrigsby

packer build packer.json 2>&1 | sudo tee output.txt
tail -2 output.txt | head -2 | awk 'match($0, /ami-.*/) { print substr($0, RSTART, RLENGTH) }' > sudo ami.txt

seanf

# Save this file (after modifying ID_VENDOR and ID_MODEL if necessary) as /etc/udev/rules.d/81-thinkpad-dock.rules

# These values seem to work for "ThinkPad Mini Dock Plus Series 3"
SUBSYSTEM=="usb", ACTION=="add|remove", ENV{ID_VENDOR}=="17ef", ENV{ID_MODEL}=="100a", RUN+="/etc/sbin/thinkpad-dock.sh"

irgeek

Finding Packer-generated AMIs automatically after builds

The basic technique is to have Packer add a tag with a unique value during the build, and use AWS' built-in filtering capabilities to find that specific AMI after the build finishes.

• template.json - Shows the settings that need to be added to your template
• build.sh - Shows how to use the template to do a build and retrieve the AMI information