Blog of Leonid Mamchenkov

Point Nine is looking for some talanted people.  They are working in the financial sector, and seeking Python and C++ programmers, as well as Linux system administrators.  They seem to be an interesting company, judging both by their technology stack and hiring techniques.   For example, I’ve spotted their job ad on The Daily WTF.  Cool stuff.  If I wasn’t working where I am working, I would have applied for the job already.

There is an interesting post at The Open Source Advocate blog - “Win the desktop, and you will win the server“.  Tristan Rhodes, the author of the blog, suggests that in order for an operating system to conquer the server market, it should first conquer (or fight reasonable well for) the desktop market.

I have to admit that when I just read the article, I felt almost like agreeing.  But something kept buzzing me from the inside, so I kept that tab open for a few days.  Now that the post was processed at the back of my brain, I have to say that I don’t agree with that point.

There is, of course, a correlation.  Once sysadmins start using something they like on the desktop, it’s pretty soon that they try to see how well that thing handles server tasks.  So, of course, people using Windows on the desktop were checking out how to make a server out of it.

But.  I don’t think that conquering the desktop is the only way to the server.  Not at all. There are more ways, I somehow feel that those other ways are actually simpler.  For one thing, Linux has never been particularly good with desktops.  However, only the stubbornest and the most ignorant of sysadmins will argue against Linux server superpowers.

Furthermore, real sysadmins (which are, of course, in the minority) clearly understand the differences between a desktop computer and a server.  What’s good for one might not be so good for the other.

And then there is this whole “enterprise” issue.  Big companies (aka “enterprises”) aren’t about desktops.  They are about support services, customizations, and having someone to blame.  If there is someone on the other end of the twisted phone cord, they’ll grab him with both hands.

The historical examples in the Open Source Advocate’s blog post might be related or they might not.  The times were different anyway.  But even if these examples are related, they aren’t as heavy as they seem.  There are many factors to consider (prices, distrubution, documentation, hardware requirements, etc).

What do you guys think?

I have recently upgraded my laptop to Fedora 9.  Those of you who come often to this blog or follow me on Twitter, know that I’ve been waiting for this release like for nothing else.  Two technologies in particular - KDE 4 and Firefox 3 - were the center of my focus.  Of course, I could updated them separately and tried them earlier, but I wanted to follow the path of the distribution.

The upgrade itself went fast and easy.  But starting with the first reboot, I was getting more and more negative towards the new release.  While booting for the first time, I got two messages, notifying me that wpa_suppclient service and CUPS daemon failed to start.  While I don’t care much about printers, wireless connectivity is vital for me, so that was a bit discouraging.

The login screen.  It was changed quite a bit, and I didn’t like it much.  Logging in.  Somehow I ended up in Gnome, even though my desktop environment was KDE for the last 7 years or so.  Logout.  Switch into long awaited KDE 4.  From the first look it was beautiful, even though not quite for my tastes.  Surely, I’d need to reconfigure and change a few things. Not a problem for me at all - even more fun so.

[Read more →]

Fedora 9 is coming Real Soon Now ©. I mentioned before that I am desperately waiting for this release, since it brings KDE 4 and Firefox 3. One thing that I haven’t seen noticed anywhere until I read this interview is “preupgrade”. It sounds pretty cool:

By now, the “preupgrade” package should be available in updates-testing for Fedora 8. Enable the updates-testing repo and install it. It currently shows up as “Upgrade Fedora” in your Applications -> System menu.
From there, it’s very simple - follow the screens to choose what to upgrade to, wait for everything to download, hit “Reboot”, and the upgrade will begin!

Basically, what happens is that Fedora 9 installer is downloaded together with all the required packages, while you are still using Fedora 8. Once everything is in place, you can simply reboot and upgrade your system, without burning any CDs or DVDs or waiting for long downloads while having nothing to do.

Here is a quote from a wise comment in the discussion of the “Linux system programming” book review:

Build your code with -Wall -Werror (or your compiler’s equivalent). Once you clean up all the crud, that pops up, crank it up with -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith. Once there — add -Wreturn-type -Wcast-qual -Wswitch -Wshadow -Wcast-align and tighten up by removing the no in -Wno-unused-parameter. The -Wwrite-strings is essential, if you wish your code to be compiled with a C++ compiler some day (hint: the correct type for static strings is ” const char *”).
For truly clean code, add -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls.
The people, who wrote and maintain the compiler, are, most likely, several levels above you in understanding programming in general and C-programming in particular. Ignoring the advice their code generates is foolish on your part…
As a minimum, solved warnings will make your code more readable by reducing/eliminating the “Why is he doing this?” questions. More often than not, they point out bugs you would otherwise spend hours chasing with a debugger later.
And they make your code more portable. But if you don’t understand, why a warning is generated — ask around. Don’t just “shut it up”. For example, initializing a variable at declaration is usually a no-no. If the compiler thinks, the variable may be used before being initialized, scrutinize your program’s flow. If you can’t figure out, it may some times be better to disable this one warning temporarily with -Wno-uninitialized to move on, instead of shutting it up for ever by a bogus “= 0″ or some such…