GNU/Linux

This is a kernel module I cooked in a couple of days. The idea is to expose a v4l device that gets its data from user space.

I had 2 use cases in mind:
1) Educational purpose for myself (I'm really a kernel noob).
2) Streaming movies over skype, google talk, ... etc.

The idea could be good or completely rubbish but hey ? Learning can only be done with stupid ideas!

The code is highly unstable. It shouldn't oops the kernel but I'm not responsible. I've been developing and testing it inside qemu.

Thanks to all the hard work by the fglrx packaging team, DRI, MESA, Xorg, Radeon,... etc people!

I've been using fglrx with my laptop since I've had it:

And to the people behind the Debian packaging..
* xserver-xorg-video-radeon from testing.
* libdrm-intel1 and libdrm2 from unstable
* libgl1-mesa-dri and libgl1-mesa-glx from experimental

This post has a bit of my history and emotions. It can be skipped!

The summary is: Katoob has a new maintainer.

...

Yes, a long time.

Back in 2002, Gtk 2.x was just released. Efforts were spent porting, rewriting and redesigning parts of GNOME. The aim was GNOME 2.0 and later on 2.x

I have 2 laptops. My personal one at home and my work one at the office. Both are running testing. A month or two ago, I did a dist-upgrade on the home one. Later on I rebooted (DUH!) it for a reason I can't remember just to end up with very tiny fonts under GNOME. It took me some time to tweak them back again and play with the GNOME anti-aliasing dialog. Now if you know me well, you know that the last thing someone should do to me is to touch my font settings. I have a very sensitive eye (Because I have a very low vision) and I hardly tweak the fonts. All went somehow fine after that.

I was trying to package hunspell-ar for Chinook so I ended up packaging:
* hunspell (libhunspell and its development headers)
* enchant (hunspell and ispell providers but I'll disable ispell soon)
* hunspell-ar
* dictionaries-common and dictionaries-common-dev (hunspell-ar depends on them)

As for dictionaries-common and dictionaries-common-dev, they are different than the Debian ones. Yes I'm using the same source but I'm only providing the bits related to myspell. I didn't include the policy too.

I noticed this because of my work on him-arabic.

If your plugin provides a language other than the 16 "known" languages, It will be displayed as " ()".

Ideally, The fix should be somewhere else but not all of the components are open so even if I can fix it, I won't be able to publish patches or packages.

It seems that the source provided with the SDK is a bit outdated so I had to grab the latest trunk: https://stage.maemo.org/svn/maemo/projects/haf/trunk/hildon-input-metho…

This is my Arabic related TODO list for maemo. It's my personal one not the Nokia employee one :-)

* katoob should be fully functional (I'm learning here). Actually I did more work today and I guess it's fine.
* Package and publish some Arabic fonts (I know there's one provided by the browser team).
* See what can be done regarding input (Low priority. Sorry to say that I don't like the HIM plugin interface).
* Check arabeyes.org apps. Is there anything useful and needs "porting" ?
* glibc/x11 Arabic locale ?
* Any suggestions ?

* A month since I've been here in Finland and started working for Nokia
* I've got my creditcard PIN code in the morning (From the nordea bank suckers). At last they accepted my application but they decided to send the card to the wrong branch. 7 minutes on the phone to convince them to send it to another branch. It takes them also 2-3 days to send it to another branch!
* My debian.org account has been created and NOW I'm at last an official Debian Developer (Technically, this happened on the 14th. An hour ago ;-))

Marc Brockschmidt, my Application Manager wrote it at last :-)

Thanks to all the cool people out there who helped me!