| #!/usr/bin/env ruby | |
| # craftr | |
| # This manages a Craftbukkit server. It helps you start it, stop it, | |
| # back up your world, and download specific Craftbukkit builds. | |
| # You must "gem install thor" first. | |
| # Run it in your server directory. | |
| require 'thor' | |
| require 'yaml' |
| # drop this in your ~/.config/fish/functions | |
| function activate --description "Activate a virtual environment" | |
| # find the target | |
| set target $argv[1] | |
| if test -z $target | |
| set target $PWD | |
| end | |
| # expand the path in $target |
| <!doctype html> | |
| <html> | |
| <head> | |
| <title>UnWRAP Test</title> | |
| <style type="text/css"> | |
| p.flash { | |
| font-style: italic; | |
| text-align: center; | |
| } | |
| p.message { |
| #!/bin/sh | |
| version=2.6 | |
| python=python$version | |
| echo "== This script will install Distribute, pip, and virtualenv" | |
| echo " in your home directory for Python $version." | |
| DISTRIBUTE_TEMP=$(mktemp -p "${TMPDIR:-.}" -d distribute-XXX) || { | |
| echo "Could not create temporary working directory" | |
| exit 1 |
| # Benchmarks run with the Append Only File on everysec | |
| # redis-server run with default settings, except for appendonly yes | |
| # src/redis-benchmark -d 16 -n 1000000 | |
| # at the end of the benchmark, appendonly.aof was 48 MB | |
| ====== PING (inline) ====== | |
| 1000000 requests completed in 6.54 seconds | |
| 50 parallel clients | |
| 16 bytes payload |
| /** | |
| * Parser for DCPU-16 assembly language. | |
| * This parser should accurately parse all of Notch's example code, and most | |
| * of the community's code. | |
| * It converts instructions to objects with fields {op, params, label}. | |
| * op is the lowercased opcode, params is the parameters passed to it (as | |
| * values), and label is the label prefixing the statement (null if the | |
| * statement is unlabelled). | |
| * Values have a type field and one or two others depending on the type. | |
| * |
This is our totally strict set of guidelines about how to refer to the Linux Users' Group at NC State University, and produce print media about the LUG.
The official, formal name of the LUG is "the Linux Users' Group at North Carolina State University." Never use this except when drafting legal documents.
In situations where a "full" name (but not a legal name) is necessary, use "Linux Users' Group at NC State University." For a shorter name, use "LUG @ NC State."
Matthew Frazier, Department of Computer Science
With the new route restructuring proposed by HDR Engineering for the NC State Wolfline service, the Wolfline has an opportunity to rearrange its route names and numbering into a more cleanly organized system.
The original draft of this plan used the 10-year Wolfline service plan as proposed by HDR Engineering. However, at the publication of the Wolfline Fall 2012 system map, it became apparent that NC State Transportation did not plan to follow the plan exactly. (Not that I mind.)