 |
bjfs: the web logThe man formerly known as Kobayashi-san |
| 6th August 2011 A.D. |
As you might already know, I own a license to a Microsoft operating system which was preinstalled with my Fujitsu-Siemens (yep, a pair being long since defunct) ultramobile box. Unfortunately it didn’t work very well with this hardware since it liked to reboot itself every now and then, until it finally refused to boot at all.
Fortunately the Innotek, I mean Sun, I mean Oracle’s VirtualBox is able to handle Windows very well, including support for USB gadgets. In fact, if it weren’t for those USB drivers, I wouldn’t bother emulating that imperial system (apart from editing this note from Microsoft Word, but WTH). Thing is, I gave it insufficient disk space, as 25 gigabytes provides quite a challenge to handle the system partition nowadays. As I plan to have more data from my devices (more of them), I had to find a bigger boat. Saving space through the shared folder with host didn’t solve everything. So here’s what I’ve done:
Continue reading…
| 22nd February 2011 A.D. |
So from time to time I use a linuxen gadu-gadu protocol (and Tlen, and XMPP, and IRC) client called ekg2. I could write lengthy document about my IM experience, but that would be somewhat out of scope. Thing is, this stuff has CLI which makes it extremally versalite like a swiss-army knife. Yes, there’s an interface for the Gimp Toolkit (GTK), but that’s a bonus like various UIs for Linux kernel configuration; visual aid…
How to log?
Well anyway, as for a geeky tool, this baby sports logging in plain text format with Unix timestamps! So unless you calculate that in your memory or have access to appropriate utilities, you’ll have difficulty with figuring out the time of all your chatting archives!
And you have to /dump each and every time the content of your window to have the text saved in a file appropriate to the argument of that command. Mess, but… hey! There comes the possibility to log stuff in a SQL database. Current choices are Oracle (sic!) and sqlite3.
The choice
Since I’ve heard good things about the latter, I thought it’s about time to make use of that. Unlike the usual SQL systems you don’t need to have a server to hold your data as everything sits in a file. So all in all it’s just bigger and more messy than your regular plain text. Why bother then?
Read on to see why…
How to log?
Well anyway, as for a geeky tool, this baby sports logging in plain text format with Unix timestamps! So unless you calculate that in your memory or have access to appropriate utilities, you’ll have difficulty with figuring out the time of all your chatting archives!
And you have to /dump each and every time the content of your window to have the text saved in a file appropriate to the argument of that command. Mess, but… hey! There comes the possibility to log stuff in a SQL database. Current choices are Oracle (sic!) and sqlite3.
The choice
Since I’ve heard good things about the latter, I thought it’s about time to make use of that. Unlike the usual SQL systems you don’t need to have a server to hold your data as everything sits in a file. So all in all it’s just bigger and more messy than your regular plain text. Why bother then?
Read on to see why…
Top