FlorianHeigl

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg00-lvol00  992M  497M  445M  53% /
/dev/mapper/vg00-lvol04  4.9G  1.2G  3.5G  25% /usr
/dev/mapper/vg00-lvol02  1.4G  563M  731M  44% /var
/dev/mapper/vg00-lvol03  496M   61M  410M  13% /var/log
/dev/mapper/vg00-lvol07  496M   19M  452M   4% /opt
/dev/mapper/vg00-lvol06  248M   11M  226M   5% /home
/dev/mapper/vg00-lvol05  496M   19M  452M   4% /tmp
/dev/xvda1            190M   33M  148M  18% /boot
tmpfs                 512M     0  512M   0% /dev/shm

FlorianHeigl

cluster consists of 3 nodes:
nexus  (Nexus7 tablet, running ubuntu 12)
nsa    (NSA325 Nas, running custom fw, with debian wheezy chroot)
pi     (Raspi 512M, running debian wheezy)

csync2:
    parallel
  pri xinetd
	pri csync2??

FlorianHeigl

Chef Bootstrapper For SuSE/SLES

Installation

Note: Run this script as the root user (no sudo calls are used in the script).

You will need the curl package installed, though I would have no idea why it wouldn't be installed by default:

zypper --non-interactive install curl

FlorianHeigl

Vagrant Setup

This tutorial guides you through creating your first Vagrant project.

We start with a generic Ubuntu VM, and use the Chef provisioning tool to:

• install packages for vim, git
• create user accounts, as specified in included JSON config files
• install specified user dotfiles (.bashrc, .vimrc, etc) from a git repository

Afterwards, we'll see how easy it is to package our newly provisioned VM

FlorianHeigl

#!/usr/local/bin/ksh93

confdir=/usr/local/etc/poudriere.d

BRANCHES="2014Q2 2015Q1"
ARCHS="i386 amd64"
VERSIONS="9.1 9.3 10.1"

FlorianHeigl

Boostrap the Synology DS215j with optware, ipkg, and sudo

Inspired mostly from the Bootstrap DS215j blog post

Download & Install ipkg in a persistent manner

# Create a directory that won't get nuked during DSM security updates
mkdir /volume1/@optware
cd /volume1/@optware

FlorianHeigl

A guide about accepting contributions for Open source projects.

Ever since you could send patches by mail we'd interact over thousands of miles, exchanging code snipped between people we don't even know beforehand.

That and the transient nature of contributions might be the main the reasons it's very hard to find out why things go wrong.

The guide tries to pin down most common issues and bring to light some possible reasons.

I'm writing based on my experiences with some projects, the feedback I heard from frustrated users and overloaded devs. In case of Check_MK I've even seen all sides, but this writeup is based on a lot more projects / interactions. In most cases I'm just a mere user. At rare times I've been intrigued, but most often I've been driven mad.

FlorianHeigl

root@dhcp104:~# cat /etc/update-motd.d/91-release-upgrade 
#!/bin/sh

# if the current release is under development there won't be a new one
if [ "$(lsb_release -sd | cut -d' ' -f4)" = "(development" ]; then
    exit 0
fi
if [ -x /usr/lib/ubuntu-release-upgrader/release-upgrade-motd ]; then
    exec /usr/lib/ubuntu-release-upgrader/release-upgrade-motd

FlorianHeigl

i would like to think about the _really_ important IT books.
funny enough most of them will come cheap since they're decades old.

building internet firewalls
snmp, snmpv2 and rmon
high availability network fundamentals
optimizing nfs performance
unix shell objects

FlorianHeigl

#!/bin/bash

CONFIG_FILE="/etc/sysconfig/network"

function set_hostname() {
    NAME=$1

    [ -n "$NAME" ] || exit 0

    sed -i '/^HOSTNAME=.*$/d' $CONFIG_FILE