In 2005-04-04 I whined about a site called Sec­tion 6 pla­gia­riz­ing one of my ar­ti­cles (the al­ways pop­u­lar Lin­ux Boot­ing Process Un­veiled).

Well, yes­ter­day I found in my in­box an apol­o­gy from Kristo­pher Zent­ner, own­er of the site!

So, I can say Sec­tion6 1z n0t 7h3 5ux0rz n0vv!

Sec­ond (or third) ar­ti­cle on this se­ries. Now we tack­le why and how cron/at suck and what we can do about it.

I am hack­ing a bit on rater my dae­mon/­client to see if things are hap­pen­ing more of­ten than they should (in oth­er word­s, gener­ic rate lim­it­ing).

I had to take a few days of­f, since my broth­er got mar­ried and we all went back to San­ta Fe for that and a week­end, and then ev­ery­one else has sore throats and I am the on­ly one healthy.

But hey, it works well enough al­ready:

• The sim­­plis­tic pro­­to­­col is done

• The serv­er works

  • It can take hours of gib­ber­ish with­­­out prob­lem­s.

  • It can take hours of valid in­­­put with­­­out prob­lem­s.

  • It does what it's sup­­­posed to do.

• It's stay­ing be­low 300S­LOC, which was my goal.

Miss­ing stuff:

• Val­­grind it.

• Client li­brary.

• Gen­er­ic CLI clien­t.

• A qmail-spp plug­in that us­es it.

And then, I can for­get all about it.

One of the ways your lin­ux sys­tem suck­s, and what you can do about it: sys­tem no­ti­fi­ca­tion­s.

I am no longer on plan­etKDE so this will prob­a­bly not be read by many in the KDE com­mu­ni­ty but...

Please, please, please start mak­ing big noise about the Asus eee. It ships with KDE and is ex­pect­ed to sell "up to 500.000 by mid­dle of next year and 5,000,000 by 2009" [1].

Is that num­ber not big enough? It's prob­a­bly more than our cur­rent in­stalled base.