The latest development version of QComicBook available from the official git repository has finally got internationalisation support! I'm looking for translators, so if you want to support QComicBook development and translate it to a language of your choice, please contact me! The translations will debut in version 0.5.1 of QComicBook.
As of now, QComicBook has been translated to Brazilian Portuguese, Finnish, Ukrainian and Polish. Thanks to all the contributors!
UPDATE: Italian and French translations have been added.
Tuesday, May 11, 2010
Saturday, April 24, 2010
II Wojna Światowa. Backlog książek rośnie.
W EMPIKu, w związku ze Światowym Dniem Książki, do dzisiaj włącznie trwa promocja "3 książki w cenie 2". Trafiłem tam przypadkiem wczoraj i korzystając z okazji, bez większego zastanowienia łyknąłem trzy książki Reynolds'a, poświęcone działaniom dywizji SS na wybranych frontach II Wojny Światowej. Niestety tym samym mój backlog książek do przeczytania wzrósł dwukrotnie ;). W kolejce na półce czeka już kilka innych pozycji, a na horyzoncie zbliża się 'D-Day. Bitwa o Normandię' Beevor'a (premiera za ok. dwa tygodnie; od momenu zapowiedzi ta pozycja ma zarezerwowane 1 miejsce w mojej kolejce)...
Ech... czy wspominałem już, że doba jest zbyt krótka?
Ech... czy wspominałem już, że doba jest zbyt krótka?
Wednesday, April 14, 2010
Arch Linux & AppAarmor
I've just recently started to work on bringing the boon of AppArmor to Arch Linux world. PKGBUILDs for AppArmor-patched kernel and userland tools will soon be published via AUR, just some things need to be polished and finished. Preparing kernel package went smooth. The major effort was to prepare PKGBUILD for AppArmor tools: they should be punished for what they did to its Makefiles. Hardcoded paths to some crucial utiilities (like pod2man), hardcoded dependency/use of rpm, default target that generates not only the binary, but also pdf documentation (and for that you need latex)... Just nightmare... The PKGBUILDs are mostly ready, I just need to put some more effort and create an /etc/rc.d startup script for AppArmor's aa-eventd. Stay tuned for AppArmor packages for Arch Linux!
Sunday, March 28, 2010
Feature request: enable stack smashing protector for Arch Linux packages
I've just created a feature request in Arch Linux Bugtracker to enable stack-smashing protector for Arch Linux packages. Stack smashing protector (SSP for short, aka ProPolice) is a GCC extension for protecting applications from stack-smashing attacks. It is available in stock GCC via -fstack-protector and -fstack-protector-all compile flags.
If you care about Arch Linux security, plase speak up and vote for this feature request!
If you care about Arch Linux security, plase speak up and vote for this feature request!
Saturday, March 27, 2010
Backing filesystems up with FSArchiver
If you are going to backup your filesystem and looking for a simple yet powerful backup solution, then you may want to take a look at FSArchiver. This is a tool I've discovered just recently and despite its youth (first version released on November 2008) it did the job just perfectly. If you want more details, read on...
You probably already know tar or partimage: they are good, but have some limitations. Tar does the good job when comes to backups, but is not very convinient or easy to use for big filesystems (you need to be careful about passing it proper options to preserve file attributes, you need to take care of splitting resulting archives into smaller ones by yourself etc.). Partimage makes copies of entire partitions (and does it fast and well, copying only portions which are really used), taking a lot of burden from you, but you can only restore such images on partitions of same or larger size. Other than that, it still doesn't support ext4.
FSArchiver combines best features of tar and partimage: it works at the file level and creates a backup copy of entire filesystem, that can be then restored to a partition of any size (as long as it has enough space to hold the data, of course). When restoring the backup, it recreates target filesystems by issuing mkfs with proper flags and label. It supports many popular filesystems, including ext3, ext4, xfs, reiserfs and ntfs). FSArchiver can take advantage of dual/quad core CPUs (just pass it -jX flag, where X stands for the number of compression threads to run) and it does its job really FAST.I was really amazed that it took me just around 3-4 hours to backup and then recreate two filestystems (around 70GB worth of data in total) and the size of backup archives was only 25GB! So, to me, FSArchiver is a real winner. Sure, partimage may be faster, but if you need to rearrange your partitions with different sizes (this is what I had to do - and yes, I know about parted and gparted, but didn't want to use them), then FSArchiver is the tool you need.
Be warned though... FSArchiver developers claim it shouldn't be used on production environments yet, however it is well tested and has proven the ability to correctly save and restore filesystems on various Linux distributions. You choose.
You probably already know tar or partimage: they are good, but have some limitations. Tar does the good job when comes to backups, but is not very convinient or easy to use for big filesystems (you need to be careful about passing it proper options to preserve file attributes, you need to take care of splitting resulting archives into smaller ones by yourself etc.). Partimage makes copies of entire partitions (and does it fast and well, copying only portions which are really used), taking a lot of burden from you, but you can only restore such images on partitions of same or larger size. Other than that, it still doesn't support ext4.
FSArchiver combines best features of tar and partimage: it works at the file level and creates a backup copy of entire filesystem, that can be then restored to a partition of any size (as long as it has enough space to hold the data, of course). When restoring the backup, it recreates target filesystems by issuing mkfs with proper flags and label. It supports many popular filesystems, including ext3, ext4, xfs, reiserfs and ntfs). FSArchiver can take advantage of dual/quad core CPUs (just pass it -jX flag, where X stands for the number of compression threads to run) and it does its job really FAST.I was really amazed that it took me just around 3-4 hours to backup and then recreate two filestystems (around 70GB worth of data in total) and the size of backup archives was only 25GB! So, to me, FSArchiver is a real winner. Sure, partimage may be faster, but if you need to rearrange your partitions with different sizes (this is what I had to do - and yes, I know about parted and gparted, but didn't want to use them), then FSArchiver is the tool you need.
Be warned though... FSArchiver developers claim it shouldn't be used on production environments yet, however it is well tested and has proven the ability to correctly save and restore filesystems on various Linux distributions. You choose.
Monday, March 1, 2010
Playstation 3: February 29 bug
Well... this is actually a bit funny... excluding all the people affected by this problem (well, this includes me ;)) and SONY... We all remember Y2K/Millenkum bug, some may be also aware of 2038 year problem in UNIX systems... But would you ever expect a leap year bug? This is what hit PS3 systems today: the hardware clock of PS3 (which you cannot set/reset) assumes it's February 29th, but the OS rejects this date as incorrect. The consequences are disastrous:
From software engineer's perspective I can only say: WOW, that's a nasty BUG. It's amazing what consequences such subtle bug can cause, but on the other hand it's kind of terrifying if you think of other hardware that could suffer from that kind of programming errors, such as planes...
- some files, e.g. saved games, may get corrupted.
- trophy information may not be synchronized correctly and new trophies may get lost.
- most (all?) games cannot be started at all; it doesn't matter whether these are online or single-player (offline) games.
- PSN cannot be accessed.
From software engineer's perspective I can only say: WOW, that's a nasty BUG. It's amazing what consequences such subtle bug can cause, but on the other hand it's kind of terrifying if you think of other hardware that could suffer from that kind of programming errors, such as planes...
Thursday, January 7, 2010
QComicBook turns 5!
QComicBook was first released 5 years ago, on Jan 7th 2005. It took me just 2 or 3 weeks (around Christmas & New Year's Eve time in 2005) to complete the initial implementation, dubbed 0.1.0. The program soon became quite popular as it was probably the first comic book reader available for Linux. It had very good reception and I got a lot of positive feedback at that time. It was later packaged for many popular Linux distributions.
The program was usable from the very first release, of course with a limited set of features. More features were gradually added with new releases. With version 0.3.4 the set of features was kind of "stabilized"; this was November 2006. Version 0.3.4 marks a stagnation period for QComicBook development: the next version (0.4.0) bringing the important Qt4 port was released one year later, on November 2007. But then nothing was happening again for almost two years - till August 2009 & version 0.4.1. In 2009 QComicBook got my full attention again with four bugfix releases (0.4.1 - 0.4.4) and one "major"
release (0.5.0) which brought some new features. I'm now working on new exciting features, one of them being a ....let's keep it secret for a while ;) as it's still in early stages; keep an eye on this blog as I'll soon reveal some details...
Thanks to all of you who support QComicBook by using it, packaging it for your distro, sending me some good words, bug reports, fixes etc. QComicBook would not be here without your help! Cheers!
The program was usable from the very first release, of course with a limited set of features. More features were gradually added with new releases. With version 0.3.4 the set of features was kind of "stabilized"; this was November 2006. Version 0.3.4 marks a stagnation period for QComicBook development: the next version (0.4.0) bringing the important Qt4 port was released one year later, on November 2007. But then nothing was happening again for almost two years - till August 2009 & version 0.4.1. In 2009 QComicBook got my full attention again with four bugfix releases (0.4.1 - 0.4.4) and one "major"
release (0.5.0) which brought some new features. I'm now working on new exciting features, one of them being a ....let's keep it secret for a while ;) as it's still in early stages; keep an eye on this blog as I'll soon reveal some details...
Thanks to all of you who support QComicBook by using it, packaging it for your distro, sending me some good words, bug reports, fixes etc. QComicBook would not be here without your help! Cheers!
Subscribe to:
Posts (Atom)

