the next to weeks i am "free" from work.. well, i promissed to finish a RFP so i will do some work on mon/thu from home and have a meeting on friday i couldnt drop, but appart from that, i am free. so the next two weeks i will do some heavy DIY on my house, striping paint and starting painting. whenever i feel like getting behind a keyboard, i will try to snug out of the work.

i planned to upgrade my distro on my home machine (1/2 a day work with downtime) and will upgrade //drupal to 4.2. this is sometimes rather easy and sometimes rather painfull. expect another day downtime later next week. i also need to make a new logo for willy cause i am planning on using a new default theme or at least colorpalette (once again i say, read my lips: no more poepsite!)

on the upside, i will do some more blogging of bookmarks waiting to be pushed in the willy database...

i love the internet, take a word, put watch behind it followed by some TLD and you have //cmswatch.com. worth a visit. the piece about //"interface scalabilty" shows how immature most cms-es still are.

When it comes to web content management, what’s the first thing that comes to mind when you hear the word “scalability”? For most, especially those like me who are of the technical persuasion, it probably conjures up images of servers -- lots of servers -- along with bandwidth, rack space, and all those other critical components of building a reliable infrastructure.

This type of scalability is undeniably critical when implementing a web content management system and certainly a topic worthy of much discussion. However, this article is about a different kind of scalability – something I call “interface scalability”

people who have posting rights on willy or other drupal powered sites know that adding content requires some very basic html knowledge. a new module due soon will take this last barrier away, just [cnrl] [b] for bold and doubleclick for a link. ease as //that. try it out yourself. when //drupal 4.2 leaves the cvs/rc status, i will upgrade and when this module is available will integrated for the willys on this site. keep u posted

something went wrong with willy. it started with some error from the kernel:
Jun 19 17:22:00 kjell kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)

then shit hitted the fan, a database went corrupt:

check table
| willy.cache | check | warning | 1 clients is using or hasn't closed the table properly |

which could be repaired with a:

mysql> repair table cache;
+-------------+--------+----------+--------------------------------------+
| Table | Op | Msg_type | Msg_text |
+-------------+--------+----------+--------------------------------------+
| willy.cache | repair | warning | Number of rows changed from 57 to 44 |
| willy.cache | repair | status | OK |
+-------------+--------+----------+--------------------------------------+
2 rows in set (4.22 sec)
and now everything seems fine. total down time couple of hours (20 hits ). i suspect some memory banks are corrupted in my old pc.