Cleaning up my 'dump' directory, I found this aging script I got from somewhere, which will check the current CPU usage of a program and kill it if it uses too much. This is useful if you are for some reason forced to run buggy, closed source software which get stuck in endless loops when things go wrong. I've been there, it wasn't fun, but this thing solved it. Thank you, french christmas...
So I downloaded this Debian netinstall image... and Windows went suicidal?
At the end of my huge list of stuff I always install on a Debian box, I put a "beep" to let me know when it's done, because I will no doubt be doing something else, most likely on a different screen, when it's done.
Now, suppose you run a lot of processes you want to know when are done, it's nice to have separate, easily distinguishable sounds for each event. Of course you could do this by playing a short mp3 or something with mpg321 or mplayer if you have a sound card set up on that particular box, but even if you do, playing short tunes on the PC speaker is so much more geeky, and thus cool, since you've already proven yourself to be a geek by working on the linux box in the first place.
Beep has the ability to play a sound at any frequency your PC speaker can do, and with configurable length... do I hear music?
From version 4.3p2, sshd supports an interesting option called Match. At the time of writing, this is the version supplied with Debian Etch (stable).
I hate the .bash_history file. It never contains what I want, screws up when using multiple sessions and generally contains junk. I like to disable the .bash_history file, while still keeping the ability to push the "up"-key to scroll through earlier commands in the same session.
The way to do this is to set $HISTFILE to /dev/null. Bash will now log all its history to a nice, black hole.
This can be done at the beginning of ~/.bashrc
... HISTFILE=/dev/null ...
There. Now I wont forget.
So, you got your home directory encryopted, but you're not sure what sensitive material could end up in swap? After a long day of running a whole lot of applications and processes, many interesting things could potentially wind up there. So here's how to make sure that data is completely garbled after a reboot.
In Windows XP, it seemed like the estimated transfer time of files in a folder, when copying that folder from one place to another, was estimated purely based on the sum of the file sizes and the current transfer speed. It also seemed to have a preference for transferring the larger files first.
If you're connecting two machines with just a single network cable, like we did with parallell and serial cables back in the days, you've no doubt used a crossover cable. But why is this?
Most linux kernels accept a "vga=" command line parameter, which will set the resolution to use during boot. This is a short list of video modes which can be used, given your kernel supports your video card well enough, and the video card can handle the resulution.
My computer has the correct resolution all the way from boot time, which makes text MUCH easier to read.
I rarely post just a link, but this casemod is just too awesome: