- 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
- Enabling InnoDB support in debian (MySQL)
Well, I just started the adventure to upgrade my NAS server from i386 to amd64.. Why? I want to enable flash-cache, which is currently not compatible with 32-bit kernels.
For this I am using the "Cross Grading"
Note: This is dangerous stuff. If you are not really deep into Debian you should prefer reinsalling! Backups are mandatory.
- Setup: https://wiki.debian.org/PbuilderTricks
In the howto there is a script to be safed a .pbuilderrc. Safe in $HOME and /root
Update script, e.g. to point to local apt-cacher mirror.
Then ARCH=i386 pbuilde create and ARCH=amd64 pbuilder create
- Usage example:
ARCH=i386 sudo pdebuild --debuildopts "-j2"
ARCH=amd64 sudo pdebuild --debuildopts "-j2"
Build on two CPUs:
pdebuild --debuildopts "-j2"
When using dpkg-buildpackge (or debuild) you alos can export this env:
to set the numbers of parallel builds. (eg. into .bashrc)
For home automation, I grabbed my old PDA and started coding for it, using the Microsoft embedded Visual C++ Studio 3.0 (was free at that time ;-))
As soon as you start debugging, you immediatly get an assert: "Assertion failed in file wincore.cpp, line 1034". This only happens on the "emulated" PDA, but even with the wizard generated files.
However, I solved this already on another project, but I needed to google it up again, so its time to document this:
On my last PHP project I spent too much time on basic tasks like form validation, generation and all the stuff behind. As this "problems" are quite common this is basically a reinvention of the wheel. So I started looking for a good, easy to understand PHP Framework to speed things up.
What I found is CakePHP, a MVC based framework.
Ok, there are several frameworks available, so why to choose CakePHP? I think this is up to personal taste which framework appeals you most. Of course, there are comparisons in the blogosphere, so this can be a starting point for the decision. (for example)
Back to the cake. Well, IMPRESSIVE. This framework saves you lots of work -- most functions you need everyday are already there and the documentation called "Cookbook" is also quite complete and easy to understand. The API is not very complicated, so learning this framework is definitely faster than writing your own framework. (For the German readers: read this article).
Nevertheless, back to the topic again.
(* Your scafold consists of a database and two files.... Of course, I assume you have your webserver and database server ready, and for the sake of easiness debian running to install all required packages. As an alternative to a webserver, you might want to check the package cakephp-instaweb and the docs here. Also for the sake of easiness, this tutorial shows will not use mod_rewrite, to avoid the hassle involving proper mod_rewrite configuration)
Don't believe it?
Try it yourself.
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)
Flattr is a social micropayment plattform. But is is best to let them describe their idea:
Flattr was founded to help people share money, not just content. Before Flattr, the only reasonable way to donate has been to use Paypal or other systems to send money to people. The threshold for this is quite high. People would just ignore the option to send donations if it wasn't for a really important cause. Sending just a small sum has always been a pain in the ass. Who would ever even login to a payment system just to donate €0.01? And €10 was just too high for just one blog entry we liked...
Flattr solves this issue. When you're registered to flattr, you pay a small monthly fee. You set the amount yourself. At the end of the month, that fee is divided between all the things you flattered. You're always logged in to the account. That means that giving someone some flattr-love is just a button away. And you should! Clicking one more button doesn't add to your fee, it just divides the fee between more people! Flattr tries to encourage people to share. Not only pieces of content, but also some money to support the people who created them. With love!
Yes, this is flattr about. Showing someone that you appreciate the content he/she created. And as I like the idea, I subscribed to it today and enabled the blog to show this little tiny flattr buttons.
Button showing ERROR?
Maybe this is the reason why you are reading this post: You were on another post, where a link was placed next to a button showing "ERROR"... Well, for lifetype it is a manual process to submit all posts to flattr, so I did only for some hand-selected articles. For the others "ERROR" will show up, but you until I add this post, you can click on the button of this article instead.
BTW: Thank you very much for your appreciation!