Ubuntu

Had an interesting if annoying problem recently that I assumed would just fix itself eventually. But when you’re sick of prodding a power button to force a machine to reboot, you gotta do something. TL;DR**_ if you’re getting messages like “Restarting System” on an attempted reboot, try setting the reboot=pci kernel boot flag_** To do this, at the grub boot menu, press e to edit the current boot parameters. Find the line starting with “linux” (this is the line that actually kicks off the linux kernel) and at the end of that line, put “reboot=pci”. ...

I am a pirate. I voyage across the root-zones in search for content. Movies available months before local DVD release in a format that my media centre laps up (mostly), I watch once, and don’t take up shelf space for years; TV shows via RSS that I watch at my leisure; and, on the rare occasion that I want to ‘Game’ and not feel like an idiot, I torrent. ...

_Never having to think about updates again _ is a good thing in my head, so here’s how to set up Unattended Upgrades under Ubuntu for fun and profit. $ sudo apt-get install unattended-upgrades $sudo vim /etc/apt/apt.conf.d/50unattended-upgrades Uncomment the line // "${distro_id}:${distro_codename}-updates"; $ sudo vim /etc/apt/apt.conf.d/10periodic Make it look like this APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "7"; APT::Periodic::Unattended-Upgrade "1";

PCap files are a pain; weird format, difficult to parse viserally even if you have the ‘right’ tools handy. Wouldn’t it be easier to be able to ‘see’ the network flow, like it is in all the textbooks? Well now you can! In playing with NS-3, I came across this problem, and googled for a solution. Now here’s an end-to-end ‘I have pcap files and want to make them pretty’ solution. ...

** After a long time in the oven, Farset Labs is up and running. Unforanately we don’t have any of the crazy equipment yet, since we’re broke. As my first ‘official’ Farset Labs project, I’ve installed a ‘Big Red Button’ to notify the @FarsetLabs twitter feed and #FarsetLabs on Freenode to the status of the space. Basically, first person pushes the BRB down in the morning, then one of the directors key-unlocks the space to ‘close’ it. ...

IRC, Python, Ubuntu linux. Simples! Same as by Twitter post, but for IRC. Biggest problem with this one was working out that the IRC server needs to be kept alive with the irclib.IRC.process_once() command. This is wrapped in the while loop that assumes that there is other stuff going on for which you are waiting on a condition to be satisfied, but could easily be ignored if one is just sending out one message. Also, the PRIVMSG command can be used to broadcast to a channel, as is used here, or, as the name suggests, to communicate with a specific user. ...

This is my own self-indulgant reminder for how to do the things I like. I’ll keep adding to this as I think of them. Basic Setup Install Ubuntu Latest (currently 11.10), With the third party libraries and a home partition leaving at least 20GB for ‘/’. Then Update everything, during which time you can plod along to download the relevant packages for Chrome Beta, Dropbox, etc Once the update is done (I’d restart in most cases), additional packages I like to add are; ...

Idiot proof setup for persistent reverse shells / port forwards (same thing) under a Ubuntu VM remote and my Dreamhost server, but should apply to nearly* all *nix’s First off, some terms to keep this easy. I want to be able to access my in-office VM, xavier from my server magneto (not my names, but they conveniently complement). xavier is not publicly accessible, but magneto is. I’ll be replacing all of the FQN’s with these terms so expand on your own. In generic terms, xavier is the remote machine (i.e the one behind some NAT firewall or such that you want to get access to) and magneto is the local machine. Its a bit confusing since all of the work is done on xavier, but it makes sense in the long run. Just trust me and get on with it. ...

Ubuntu doesn’t manage vim’s addons, so installing the vim-latexsuite package doesn’t actually put all the relevant hooks into your vim installation. To do that, (after installing the package) execute; sudo vim-addons -w install latex-suite

Pre-built packages not releasing 64 bit versions? No Problem. Debian/Ubuntu based: dpkg -i --force-architecture whatever.deb RH/Fedora based: rpm -i --ignorearch whatever.rpm