After the rm -rf /* disaster that hit me a couple of weeks ago I’ve been rebuilding my setup, restoring the few files I’ve had backed up, and collecting advice from the elders.
Turns out there are a few tricks that can save your home directory from accidents like mine. The first one is rather obvious, but I’m writing it down anyway:
Keep separate accounts. If possible, use separate accounts (with different permissions obviously) for different projects.
Days like these inconspicuously start out just like any other day,
except on days like these you accidentally manage to erase $HOME and
have no real backup to rely on … Maundy Thursday will forever be Black
Thursday for me, from now on.
Best thing your can do, after cursing at yourself constantly for a
couple of hours, is to:
Come up with a useful backup and restore strategy
Read up on undeletion tools for Ext4
Blog about it, naturally
BUT FIRST – QUICK – UNMOUNT OR POWER-OFF YOUR COMPUTER – PULL OUT THE
BATTERY – AND STEP AWAY FROM THE COMPUTER! Must protect the partition
from being accidentally written to – I completely fumbled this step, so
take heed young people!
Recently issue #70 was
reported to pimd. That number of
issues reported is cool in itself, but this was a question about
Docker and pimd.
Up until that point I had only read about this new fad, and played
around with it a bit at work for use as a
stable build environment for cross-compiling. I had no idea people
would want to use a Docker container as a multicast sink. Basically I
was baffled.
The reporter used a Java based tool but simply couldn’t get things to
work properly with pimd running on the host:
For the better part of the last ten years I have been working with
multicast in one way or another. I’ve used many different tools for
testing, but on most systems I usually resort to ping(1) and
tcpdump(1), which are quite sufficient. However, you often need to
tell bridges (switches) to open up multicast in your general direction
for your pings to get through, so you need to send an IGMP “join” first.
Way back in 2006 I stumbled upon a neat tool called mcjoin, written by
David Stevens and announced in
this posting to LKML. I started
improving and adding features to it over the years.
I vanlig ordning bashar vi DNS på jobbet, pga ofungerar hårt över VPN för de flesta. (Ja vi kör alla Linux, utom cheferna som envisas med att använda något ur gamla testamentet.) Här följer ett utdrag från vår IRC:
14:32 <n00b> Success! Äntligen fick jag ordning på DNS via guest wifi -> vpn -> office network. Firar med att skapa lite irc noise. :D 14:32 < rooth>n00b: Du har väl fått den distribuerade /etc/hosts filen?
Back to using the Awesome WM in Ubuntu. This time I’m setting up everything from scratch and first up is fixing keybindings to control my main music player: Spotify!
Edit your ~/.config/awesome/rc.lua with Emacs (obviously). If you do not have an rc file, simply copy the system /etc/xdb/awesome/rc.lua:
globalkeys = awful.util.table.join(globalkeys, awful.key({}, "XF86AudioRaiseVolume", function () awful.util.spawn("amixer -D pulse sset Master 5%+", false) end), awful.key({}, "XF86AudioLowerVolume", function () awful.util.spawn("amixer -D pulse sset Master 5%-", false) end), awful.
Sometimes I just cannot help myself. It’s like finding a stray puppy, or abandonded kitten …
… I recently decided to adopt mini-snmpd since the original upstream site had passed into the great beyond. At this point in my life almost everyone I know can tell you I have no warm fuzzy feels for SNMP, at all. So why did I even consider this to begin with?!
Well, I have to confess that there are certain things that SNMP can be really useful for.
This is not a proper HowTo, more of a “note to self” after having created a setup to test pimd issue #57. For these notes the following virtual topology, running on Ubuntu 15.10 with Linux 4.2 and Qemu 2.3.0, is used:
.--------. net1 .----. net2 .----. net3 .----------. | Sender |------| R2 |------| R3 |------| Receiver | '--------' '----' '----' '----------' The networks between the boxes are actually Linux bridge devices (br), on which you may have to disable IGMP/MLD snooping to get pimd to run smoothly.
Summer is now slowly fading away, and what a summer it has been here in Sweden! For someone who isn’t a fan of the summer heat it has been an awesome time for brain work, and in my case work on my open source projects! :-)
Due to my not really taking much vacation previous years I had saved up for ten weeks (10) this year! It was really worth it, and for the first time in many years I actually feel rested.
This is an introduction to HowTo run pimd on OpenBSD. I keep it around mostly as a reminder to myself when testing new pimd releases, maybe someone else can make use of it as well.
First of all, my sincere thanks to the OpenBSD team for, not just an awesome UNIX distribution, but also for their good taste in shipping a MULTICAST enabled kernel in the base distribution! On both NetBSD and FreeBSD there is a bit of work to get multicast support, which is one of the reasons for my not writing a HowTo for either of them atm.