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.
Reminder to self: you need to set up the PKG_PATH to the correct FTP URI. Also, use the correct ARCH, otherwise the installer complains. Do not use amd64, but rather x86_64.
Here it is, you’d think this be something the installer could set up a default for …
PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/6.1.5/All/ or if you use the latest on an old ThinkPad T42:
PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/9.0/All/ The simply
pkg_add -v git Or so you might think!
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.
Years ago while looking for a fast init replacement for work,
I found Finit. Originally written by Claudio Matsuoka to act
as a drop-in replacement for the Asus EeePCfastinit, “gaps
filled with frog DNA …”
Until I found Finit I had always been in awe of those venturing into the
realm of PID 1. However, learning from the simplicity of Claudio’s
code I realized that although PID 1 at times is indistinguishable from
magic, it is really not that hard to master. My version of Finit
is available on GitHub.
The code is open sourced under the very liberal MIT/X11 license,
and much of its frog DNA has proven very useful to me over the years.
This blog post is about how that frog DNA can help you fill gaps in your
projects …
So, now that I have http://git.troglobit.com setup as a backup GIT repo
to https://github.com/troglobit, I needed a simple way to always push
to both repos – best way for me is to always hook into my regular work
flow, otherwise I’d just forget. The git-remote(1) man page to the
rescue, it describes the set-url --add sub-command:
I’m posting this in case anyone else gets stuck setting up Apache
with Gitweb. Also as a reminder to myself in case I ever need to
set up this all over again.
You have all your eggs in one basket (GitHub), and
You really like that shiny basket, but
You know you’re clumsy and usually drop baskets yourself.
You are wise (yes you are!) and realize you need another basket, so
You set up a server and a domain yourself …
OK. Let’s start simple, since you are already running the latest Debian
you fire up the command line and install the basics:
sudo apt-get install gitweb apache2
So it’ll complain, you’ll clarify your request and soon all required
packages are on your server. Now what?
Debian has already set up http://localhost/gitweb for you, and if you
have a domain already you should go ahead and edit the master file for
that:
editor /etc/apache2/sites-available/000-default.conf
service apache2 reload
If you want to use that for your gitweb needs, then you’re done!