Donnerstag, 5. Juli 2007

Evolution (or) The growth of Fedora

I started to contribute to Fedora(.us) years ago; Fedora has grown a lot since then -- especially now with the merge we are lot more people that have to interact with each other.

What really disappoints me about that: the tone on the mailing lists afaics got and constantly gets worse and unfriendlier (¹). Sure, there were flamewars in the past (and I were part of them as well), but people showed more respect to each other.

I'm not sure if I would start contributing to Fedora today if I would be searching for a project to contribute to.

(¹) -- no, there is not special mail or flamewar that got me to write this blog entry. Just a general impression.

Donnerstag, 14. Juni 2007

I need a new Laptop

I need a new Laptop. I was thinking about that for months already, but the wish to actually buy one gets bigger and bigger...

Why you ask? Well, the machine itself was fast enough for me when I bought it three years ago. It likely would still be fast enough if I would run CentOS 4 or something similar on it, but with recent Fedora releases the machines feels to slow. It has just 512 MByte of RAM and afaics these days that's not enough to run Gnome, Gnome-terminal, Thunderbird, Firefox and Pidgin in parallel without swapping. In fact there is enough free RAM when I start the machine and those apps freshly, but after some days of use (software suspending it in between) with running OpenOffice.org in between the RAM is filled; so the machine starts swapping and a "yum update" makes everything nearly unusable slow.

Does anybody remember the good old days when Linux needed less hardware resources? Seems that was long long ago...

Sonntag, 3. Juni 2007

Why many comments in config files are bad

Just yum-updated my local home-server from FC6 to F7 (my main machines at home and work used rawhide for weeks already). After such upgrades I always look over the .rpmnew files that got created and merge the changes back from them into the proper config files with meld and delete the rpmnewfiles.

That's no big deal; with a script of of mine I normally would be able to do it in one or two minutes for that machine. I would, if there wasn't dovecot.conf and squid.conf. They have lots of comments in them that explain nearly each of the settings. That just sucks because I now have to look over all of them :-((

Especially dovecot.conf is bad:


[thl@truhe etc]$ diff -u dovecot.conf dovecot.conf.rpmnew | grep '^+' | wc -l
127
[thl@truhe etc]$ diff -u dovecot.conf dovecot.conf.rpmnew | grep '^+' | grep '#' | wc -l
119
[thl@truhe etc]$


Most of those eight non-comment lines are probably settings I actually did.

Dienstag, 24. April 2007

***thl is now known as knurd

I never was really happy with my TLA as nickname -- but well, thl (from Thorsten Heiner Leemhuis oder Thorsten Leemhuis) was the thing that sprung to my mind when I needed a nickname for IRC. I actually tried to think about something else quite a bit of time back then, but I didn't find something better that was free, so I just started using thl.

But recently I thought again to look out for something else -- IRC once again was the trigger, as thl was owned by someone else on OFTC already (and there was actually somebody else on freenode that tried to use thl these days). So I searched for something else.

I considered "steinlaus" (Petrophaga lorioti), but that joke is hard to understand for people outside of Germany (I'm actually wondering how many Germans will understand it these days), so I took something more international.

Samstag, 14. April 2007

Evil?

'Our informal corporate motto is "Don't be evil."' -- that's written on the top of Google's Code of Conduct. Well, they managed that in the beginning imho when they were still a search engine and not much more. But they are becoming evil more and more in my eyes -- they were imho more then big enough already to be trusted and had much to much control over the Web already. Now they are buying DoubleClick. That really makes me anxious; where will that end? I'm starting to fear a Google controlled Internet where I can't visit a website without having "Big Brother Google" watching me. Just imagine what might happen if Google buys Microsoft (or vice versa); just a cooperation would be bad enough probably. <Prediction of the day>But I suppose Google will buy Canonical first</prediction of the day> ;-)

Google until now was one of the rare sides that were allowed to set cookies on my machine for more than one session as I had some settings saved that influenced what search results I get and how they are formated. That will change now. I'll probably look out for another blog hosting, too, and will try to get rid of gmail (which I'm using for jabber only anyway).

Donnerstag, 5. April 2007

exclude=*-devel.i386 [Update]

I'm normally trying to use the default software and settings my linux distribution provides as much as possible, as everything that one changes in my experience fires back sooner or later and requires manual adjustments (read: time) to make it work again; that makes slightly advantages often obsolete if looked back at the situation in retrospective later.

But well, today I made a big exception again. I added "exclude=*-devel.i386" to my /etc/yum.conf; getting all those *-devel.i386 packages by default really annoyed me, as I always forgot to add the ".x86_64" when running "yum install foo-devel". The download of those i386 packages consumes bandwidth and takes time; installing and updating the packages later takes even more time. And even worse: you end with lots of unwanted and unneeded userspace apps and libs for i386 as well, as the devel packages normally depend on them; those packages are not cached by rpmdev-rmdevelrpms either, so I end up with lots of cruft on my hardisk.

All this IMHO for a small benefit: to be able to develop i386 packages on a x86_64 host. How big is the number of users doing that? And does it really work in practice? A lot of configure scripts and apps (including rpm) in my experience seem to get confused if you try to compile something for i386 on a x86_64 host (even when remembering to use setarch). So it's really the best and the safest to use a chroot (e.g. mock) for this purposes as far as I can see.

So in other words: is installing *-devel.i386 packages on x86_64 really a sane default for Fedora? I really doubt it. It creates more trouble for the growing number of x86_64 users and makes it a slightly bit easier for only a small group of users. I'm really wondering if it would be better to have those *-devel.i386 packages in a separate Fedora-add-on repository that people just can enable if they really want them.

[Update] Seems I need to clarify something, as I got two comments on this blog now, and it seems both users got tracked into the wrong direction. Rahul for example wrote:

>> All this IMHO for a small benefit: to be able to
>> develop i386 packages on a x86_64 host
> This is not the primary benefit. The primary reason
> is that there is a number of third party software that
> are still 32 bit and multi lib by default helps them
> work better without fiddling.

You got me wrong here. I'm all for having .i386 libs and maybe even some i386 apps (like firefox) in the repo, because (as your write) they are needed for third party software (for example). I was taking about the *-devel.i386 packages only.

Dienstag, 27. März 2007

I can still write spec files

My Fedora involvement in these days seems to me more in housekeeping/organization areas than packaging. But it seems I haven't lost all of my packaging skills in the past months and got two new Packages into Fedora over the weekend: rss2email and python-html2text -- the latter is needed by the former. Patrice Dumas, thanks for the quick review.

BTW, that's all your fault Max -- you shamelessly placed the idea of running an rssfeed-to-email daemon or cron job in my head with your blog post months ago. But rss2email suited my needs better than newspipe, which seems to be your preferred choice.

You're wondering what rss2email actually does? Well, it reads a rss or atom feed and sends all new (or, if you like, updated) entries to you by mail (html or plain text -- whatever you prefer). You can even use different e-mail addresses per feed and point the output directly to the proper IMAP folder that way.

Why all that? Easy: with rss2email I don't have to synchronize a rss-reader's settings-directory between different computers, I don't have to run and learn and additional application and I don't have to tell any web-service which feeds I like.

My usual way of browsing the web changed dramatically due to rss2email already -- I spend even more time in Thunderbird now (is that possible? I'm there already a lot to read all those mailing lists...) and less in Firefox.

BTW, is anyone still interested in having websec in Fedora? I'm using it on one of my servers for ages, but it seems I accidentally never packaged it up for Fedora :-(