bkil vs. programming

While it may sound like utter nonsense at first, on second thought maybe it really is: cron.standard: please provide configuration facility to avoid given filesystems Someone should really be thinking more about a serious reminder system. I've put together an iotop oneliner that logs disk actions with timestamps which pointed me to anacron. Daily mlocate updating was easy to reproduce and fine tune: simply add your HDD mount points to tho PRUNEPATHS variable of /etc/updatedb.conf . On the other hand, it took a few more attempts and many days in total to track down what causes the HDDs to still start up. When trying to further examine the issue by hand, /etc/cron.daily/standard didn't start them up on first look, perhaps because of caching. However, today after randomly testing things again, it finally did, which took me to adding CHECK_LOSTFOUND=no to /etc/default/cron . It's a pity though, that I'll have to use an alarm clock from now on.

Hugs is a nice little interpreter if you'd like to try out the language Haskell. It has few dependencies and it requires moderate resources to run. The download for a minimal install is less than 1.5MiB in size. If you have an operating system with package management, you can simply install the package 'hugs', or 'hugs98'. For example, on Debian-based systems (including Ubuntu) this amount to simply running: aptitude install hugs On distributions without a decent package manager (like Puppy Linux), you can install the Debian packages manually (refer to your distribution for details, but it usually involves clicking on each downloaded package or typing dpkg -i name.deb ). You first need to select a Debian major distribution version which matches with the versions of libraries on your system. On the Pupeee (Puppy 4.3) I had been using till now, choosing Lenny seems to work fine. So I've downloaded each i386 version from a mirror close-by of the following packages:...

These things have been working for weeks now, it's just that I've been too lazy up till now to write it all down! :-D I have found a new workaround for the notorious Xv flickering bug in my mature S3 Trio3D video card. I have tested it in fullscreen before but it invariably makes it worse: it only displays (the upper) half of the canvas (while the other half is blue). However, I seem to have forgotten to experiment more on this issue, as resizing the window seems to alter the bug. It's plainly correlated to the window size: shrinking it makes it worse, while enlarging it makes it somewhat better. This is so pronounced, that enlarging it to full-window (not fullscreen) fixes it entirely! :-D In the same session a few hours back in time, the weird focus loss bug has happened to me yet again! I have been running Epiphany with the proprietary flash plugin, a flash video has just loaded in the very instant that the (unstable) MPlayer from debian-multimedia has brought up a windo...

The first OS I have installed was probably some DOS for a friend or classmate in primary school, I can't remember which. You understand if normal people can't install and configure that properly, as it is considered pretty difficult. I then did winblows a few times, though that's a harder treat. How do you expect a normal user to feel at home with his computer if he can't even install it for himself? It's supposed to be user friendly or so. Also note, that after removing the installer disk and placing it on the shelf does not end your responsibilities. If you install new hardware, software, or just simply switch some setting that change a major part of the system, you will need to get used to handling setup dialogs and wizards. And by the way, if the installation process is usually done by a semi-professional anyway - either in the shop before you buy, or if you ask help from a friend - then that voids the major part of the very common argument against using any unu...

I'm not specialized in doing that, but I had to commence many operating system installs to this day. I plan to write a bit on that next time. Here's how I've installed Debian 5.0 Lenny (qualified as testing as of September of 2008). I did it two times in a row to be exact, because of an unfortunately hardware fault after two days of usage (okay, maybe it was partially mine). The second one should have taken much less time, but I goofed with the settings of apt-move. You see I got it right with Etch before, but I forgot to write it down (I found it in the file anyway). I have been writing down what I customize from the start just because of that. Thankfully, that's a good habit of mine. Some words about the instructions in the file ("almost" a shell script). I tried to be self-explanatory, and have written a little preface to help place things in context. NO WARRANTY OF ANY KIND: I am not held liable for anything you do wrong with the text given below, not even...