- Keepass2, KeeFox and Firefox in Debian
- Debian Developer
- Migration Debian from i386 to amd64 without reinstall (Cross Grading)
- N2M: pbuilder for i386 and amd64 on same host
- N2M: parallel build dpkg-buildpackage and pdebuild
- Windows CE: Assertion failed in wincore.cpp line 1034
- CakePHP: Baking a Application in Minutes
InnoDB as storage engine has some advantages: Just one example: it is the backend to use when foreign keys are required.
For a complete picute, read the documenation: http://dev.mysql.com/doc/refman/5.1/en/innodb-storage-engine.html
However, on Debian InnoDB is disabled by default: (take a look at /etc/mysql/my.cnf)
However, it's not just uncommeting to enable it: Your mysqldaemon will fail. This article will explain how you can enable it with Debian
Of course, this assumes that you already setup mysql on your Debian server.(More)
Currently I work on a small private home-automation project. The purpose to "control" the heating system at home (heat-pump system) via the Internet.
Okay, "control" is a too big word for the heat-pump as it has only 3 controlable modes, at least without reverse-engineering effort: "normal", "off" and "night reduction" by an external analog input. The goal is to shift energy consumption to the lower priced off-peak times.
Custom Firmware for a seagat FreeAgent Theater+
Could be the next hacking project.
A HW Random Number generator (HW RNG) helps programms a lot which needs some good entrophy, something especially on server systems is rare. Syntoms are slow key generation (ssl, ssh ... ) and poor performance when reading from /dev/random.
However, soley having a HW RNG won't improve much -- this is what I learned today: I have a hifn 7955 based crypto accelerator in my NAS, but still poor /dev/random read rates.
By coincident I learned that I looked at the wrong device -- the randoms by the hardware are available through /dev/hwrng. But how does other programms know that they should use this device instead of /dev/random?
A Nigerian 411-type scam mail slipped through spamassassin.
Before moving it to its fate (aka SPAM folder), one line catched my eye:
(ii) Are you truly Dead OR Alive?
Whenever I push changes to solarpowerlog, I want that a notification mail is sent to a dedicated mailing list.
However, the documentation on sourceforge just says "you can do this", but finding docs about "how" is hard.
So this is my try to document the procedure, in case this helps someone... The examples are the one for solarpowerlog, so be sure to edit them before applying.(More)
Unfortunatly, lighhtpd does not support ".htaccess" rules directly. So if you want to use a script targeted for Apache, you have to implement your own rules.
Luckily, the most needed rule is to forbid the serving of a whole directory, the "Deny From All" rule.
This one can be emulated within the lighttpd.con -- but you have to list every affected directory. A tedious task to find out every .htaccess contianing the rule and then adding the path to the configuration.
But this can be automated: