Making Linux systems that don't suck. Part II
Second (or third) article on this series. Now we tackle why and how cron/at suck and what we can do about it.
Second (or third) article on this series. Now we tackle why and how cron/at suck and what we can do about it.
I am hacking a bit on rater my daemon/client to see if things are happening more often than they should (in other words, generic rate limiting).
I had to take a few days off, since my brother got married and we all went back to Santa Fe for that and a weekend, and then everyone else has sore throats and I am the only one healthy.
But hey, it works well enough already:
The simplistic protocol is done
The server works
It can take hours of gibberish without problems.
It can take hours of valid input without problems.
It does what it's supposed to do.
It's staying below 300SLOC, which was my goal.
Missing stuff:
Valgrind it.
Client library.
Generic CLI client.
A qmail-spp plugin that uses it.
And then, I can forget all about it.
One of the ways your linux system sucks, and what you can do about it: system notifications.
I am no longer on planetKDE so this will probably not be read by many in the KDE community but...
Please, please, please start making big noise about the Asus eee. It ships with KDE and is expected to sell "up to 500.000 by middle of next year and 5,000,000 by 2009" [1].
Is that number not big enough? It's probably more than our current installed base.
Really. I can imagine having one of these as my main computer (with external HD and monitor).
I probably won't and use my full-size notebook or a desktop when at home/office, but it should take me back to the days when I simply carried my Libretto everywhere because it was light enough.
Here's the best review I found so far.
People worry about the 4GB or 8GB "disk". If you keep your media (ISOs, movies, music) on an external HD, you probably can have everything else there.
Using rsync to keep two boxes synced... lots of potential.
I am probably buying two of the cheap ones.