Thursday, February 24. 2005
Start an initiative to make it practically mandatory to get every application certified and signed, introduce strict criterias that must be fulfilled in order to get an application signed, make those certifications expensive (US-$ 350 for an "ACS Publisher ID", plus US-$ 195 to US-$ 560 for the first submission to a test center, plus around US-$ 200 for every following submission), and the introduce the strict policy in the latest version of your operating system that unsigned code is not allowed to do any user interaction. Et voila, you practically killed your freeware scene, as nobody can afford such expensive and time-consuming certificates.
Wednesday, February 23. 2005
Due to my rage about so little space on my desk and in my room, I just decided to sell to my still working SGI Indy for (at least) EUR 100,- or highest bid. The buyer has to pick up the machine in Linz, pay cash, no guarantee. It comes with a 20" monitor, a keyboard and a 3-button mouse, 32 MB RAM, a 2 GB harddisk, and Debian GNU/Linux preinstalled. I have no Irix discs or whatever, as it is crap, anyway (and anybody who has used it will agree with me). Pictures are available on request. If you're interested, write an email to ak@synflood.at.
Monday, February 21. 2005
I'm recovering again, at least for now, I'm able to continue working on mutt-ng again, and I'm happy with my girlfriend, again.
Today I created a mutt-ng development blog on supersized.org. Supersized.org is a free weblog provider, similar to livejournal et al, but it comes with some cool weblog software installed, that is s9y. Kristian Köhntopp was so friendly to point to it in his blog. So, no more mutt-ng blogging here.
Wednesday, February 16. 2005
Yes, you read the title correctly: I'm about to burn out. Probably my mistake was that I was going too long without any real holidays. Of course, it doesn't mean that I will burn out immediately, but I feel that the processes already started slowly. To my colleagues who read my blog: don't be afraid, I will still make it a few months, and I asked for holidays already, anyway.
But nevertheless, that burning-out makes me kind of unhappy, and don't really feel well, and it has negative impact on my overall love life: today I had to temporarily postpone my (remote) relationship with my girlfriend until I've recovered, as I'm currently unable to commit my whole spirit to her.
And that's my plan to recover: no more programming outside work, going out more, relaxing more, sleeping more, no more (active) blogging, no more instant messengers, no excessive emailing, no more posting on the usenet, just getting my head free and getting myself relaxed. But I will not totally give up life, so bits of music and alcohol are still allowed. And I hope that I will get my holidays in about a month, which will be the "climax" of my plan to recover. If anybody knows other ways to get recovered in a long term by whatever measures, feel free to post them.
Good-bye for now.
Sunday, February 13. 2005
le posted an entry about essential questions, and although (or since?) I'm currently drunk, I would like to add my part of it:
Star Wars oder Star Trek? - both of them. Star Trek managed to build up a way better universe than Star Wars did.
Alien oder Predator? - Alien, because the 4th (??) part of it shows you how to get a 2 meter alien through a 2 cm hole.
U2 oder R.E.M.? REM, because they've got a cooler name (a spy jet code name vs. "rapid eye movement"), and their music is better, and they collaborated with Pearl Jam.
Die Ärzte oder Die toten Hosen? Both, but only the old stuff.
Rot oder blau? Green. Is that the politcal question or what?
Hund oder Katze? Neither of them. I hate them both. Probably I hate cats more because I had to do a checkup for canine madness, because I was attacked by one when I was 7 years old.
Wir sind Helden oder Juli? Neither of them. Both commercial crap. Mia rules.
Kelly's oder Pringles? Neither of them. The riffle chips from the 3rd company whose name I totally forgot are definitely the best.
And to answer the questions from the comments:
* Kafka oder Brecht? Kaminer har
Spanish or French? Español es mas bueno. Frances es la idioma de las putas y por los putos. (*harhar*) Yeah, I'm currently learning Spanish. No offence to gay people[1], BTW.
Populärkultur oder Subkultur? subculture. Diversity is better.
Standard Printausgabe oder Kurier Printausgabe? Standard, because I've got a subscription, and because it's the only newspaper with a moral obligation nowadays.
And finally my questions:
Nirvana or Pearl Jam? - Pearl Jam. Kurt Cobain couldn't even wash his hair, but Eddie Vedder cut it to overcome the grease-in-the-hair problem. And they make the better music, on a side note.
vim or emacs? vim. Modal editors are just more powerful.
KDE or Gnome? KDE. I used to be a Gnome zealot, but in the meantime, KDE is simply better, and made greater progress in terms of technical advantage.
Yes, I'm drunk, and I feel it.
[1]: the sentence means "French is the language of the whores and for the fags." (or for the "male whores", that depends on how you interprete "putos")
Saturday, February 12. 2005
Today I configured my very first iSCSI target and initiator, both on Linux. Unfortunately, I only have old and slow hardware at home (you are still invited to donate), so the performance isn't really a lot of fun (see below), but installation and configuration is a charm: basically you only need iSCSI Enterprise Target for Linux (2.6.9 or later required) for the target (that's the server in iSCSI speak) and linux-iscsi on the initiator (that's the client in iSCSI speak). Installation of both is really easy, just follow the instructions in the README files. Then, you need to configure at least one node on the target. This HOWTO explains how. Even though it's referring to the Ardis Technologies implementation, the description works fine with the iSCSI Enterprise Target, since it's simply a fork. After that, configure the initiator after the same HOWTO (in my case, the ietd.conf on the target and the iscsi.conf on the initiator both have 6 lines each, so it's really very easy) and start iscsid on the initiator. Have a look at your syslog on both hosts. With iscsi-ls you can view your available iSCSI nodes on the initiator, and you can partition, format and mount them like any other devices.
Here you have the bonnie++ output, as already mentioned, the performance is quite poor, but the bottleneck in my case was the slow network (one of the involved hosts only has a 10 MBit network card, and every other 100 MBit network card I tried made Linux crash...):
Version 1.02b ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
nirvana 56M 1011 68 1148 4 395 3 678 49 916 6 65.2 4
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 225 97 7786 97 6054 100 236 98 7671 97 832 98
Friday, February 11. 2005
Thursday, February 10. 2005
Who can donate some hardware to me? It would be only for a few weeks, and then I will return the hardware when I'm finished.
Why? Because I want to do some experiments with iSCSI on Linux, using iSCSI Enterprise Target, the iSCSI initiator from the Linux-iSCSI project and the Microsoft iSCSI initiator, do performance tests and compare the performance of the different filesystems with the performance of network filesystems like NFS and SMB.
What hardware do I need? Two reasonably fast computers (fast enough to handle GBit ethernet), GBit ethernet cards, a GBit ethernet switch and the right cables, and one of two computers should have a dedicated SCSI harddisk.
What is the outcome? First of all, I will write a report about the performance tests, and publish it. You will be given credits as donator.
If you can donate all or parts of the required equipment, please contact me. If you write an email to some @synflood.at address, please be aware that I will able to answer tomorrow evening, because I fucked up my mail server today in the morning, and neither fetchmail nor ssh are currently running, so I cannot even fix it remotely. :-/
Tuesday, February 8. 2005
I had to play with creating another panorama picture, and, well, here it is:
Below you can see my very first panorama picture, taken from my balkony, and put together using autopano-sift, hugin and this tutorial. It's not perfect, but nevertheless, it's a start:
Thursday, February 3. 2005
I just don't get: so many times, digitally signing/"certifying" applications is presented as the solution to application security issues. But what does digitally signing applications have to do with application security? Nothing, it seems to me, as it only proves that the application was signed by a certain entity. It makes absolutely no point about any security implemented in the application. Digitally signing an application doesn't mean auditing it. It would be way to much work to code-audit every single application that is about to be signed and published, and still wouldn't actually prove security. So what is the point of digitally signing applications, except for triggering a false sense of security in the lay-user? Or am I just too stupid to get the whole concept?
|