People interested in openSUSE and kernel development probably know about the existence of the Kernel Of The Day (KOTD). This is the latest and greatest code from the internal kernel source repository that is build once a day and synced out to ftp.suse.com. The intention of the KOTD is to ease the testing and running of development snapshots that likely become the next maintenance update.

Some people might have noticed the Kernel: projects that produce a quite heavy load on the build farm. These are KOTD projects that are mirrored to the openSUSE Build Service every night around 4pm CET if there are changes in the internal source repositories.

Currently the following KOTD projects exist:

• Kernel:HEAD is the KOTD of openSUSE:Factory
• Kernel:SL111_BRANCH is the KOTD of openSUSE 11.1
• Kernel:SL110_BRANCH is the KOTD of openSUSE 11.0
• Kernel:SL103_BRANCH is the KOTD of openSUSE 10.3

Additionally there are two projects that are related to upstream kernel development:

• Kernel:Vanilla includes the latest sources from Linus Torvalds’ linux-2.6 GIT tree
• Kernel:linux-next includes the latest sources from Stephen Rothwell’s linux-next GIT tree

With the help of the openSUSE Build Service running the KOTD became even more convenient since the project repository can be added to zypper. Besides that it is now very easy to build external kernel modules (KMP) matching the KOTD.

Today, I’ve played a bit with an idea to allow starting of YaST Server module from the YaST System Services module.

The only visible difference is the additional “Configure…’ button at the bottom of the dialog. This button would be active only if there is a YaST module associated with the entry. After clicking it, the respective YaST module would be started:

With this simple principle, the YaST control center ‘Network Services’ section would be reduced to:

And all those YaST modules would be available from ‘System’ section:

This approach could be used even further. You can see that the ‘Network Services’ section contents do not really match the section name anymore. In fact, most of the items could be moved to other modules as well. E.g. introducing a module for authentication/authorization, which would cover Kerberos client, LDAP client, etc. The NFS client is in fact a part of the new Disk Partitioning module already. So, the section could vaporize completely.

However, there are drawbacks. The biggest one I see is a ‘starting point’ problem. Just imagine you want to have a Apache2 running in your system. Until now, the YaST HTTP module is installed and can be used to bootstrap your configuration – it will install the packages and help to set up the basics. But with the new approach, the apache2 package is not installed, therefore System Services module would not see the apache2 service (init script) and does not show it at all! I’m not sure how to address this. Maybe the best would be to attach the YaST  module to apache2 package or HTTP server pattern and the Software Management module would become such starting point. Would it be better? I don’t know.

Then, there is an issue of a quick access – if you are moderately experienced user, you know what you are looking for and you start a proper module right away. But to figure out what is the configuration starting point if it’s hidden in another module, that might be a blocker.

I’m sure there are more problems. Anyway, I find the idea quite useful for reducing the number of YaST modules. What do you think?

So first of all, happy new year!
I'm proud to announce the Brasero 0.9.0 release, i've build openSUSE 11.1 packages on my build service home, Mandriva also updated on cooker and i'm sure the other distros will follow as well.

The other good news is that after Brasero proposal for inclusion on GNOME 2.26, Brasero will follow some of the tips said by another fellow developers and it's going to be split into a library. This means we will have language bindings and support for another applications. The action is on trunk now.

Release notes for 0.9.0:

Updated dependencies:
GTK+ 2.14
no more libgnomeui dependency

New features:
New option not to replace symlinks by their targets
Many small and big improvement when brasero is spawned from an application plugi
n
Improved session handling

Bugs fixed:
Many fixes (to be backported in a 0.8.5 release) for video project
See ChangeLog for other ones

New translations:
latvian: Raivis Dejus <orvils@gmail.com>

Updated translations:
et.po: Translation updated by Mattias Põldaru
sv.po: Daniel Nylander <po@danielnylander.se>
de.po: Mario Blättermann <mariobl@svn.gnome.org>
es.po: Jorge Gonzalez <jorgegonz@svn.gnome.org>
hu.po: Gabor Kelemen <kelemeng@gnome.hu>
zh_CN.po: 甘露(Gan Lu) <rhythm.gan@gmail.com>
sr.po, sr@latin.po: Updated Serbian Translation (by Miloš Popović).
da.po: Kenneth Nielsen <k.nielsen81@gmail.com>
sl.po: Matej Urbančič <mateju@svn.gnome.org>

Thanks to all the people who contributed to this release through patches, transl
ations, advices, artwork, bug reports.

Homepage: http://www.gnome.org/projects/brasero

Please report bugs to: http://bugzilla.gnome.org/browse.cgi?product=brasero

Mailing List for User and Developer discussion: brasero-list@gnome.org

Svn Repository: http://svn.gnome.org/viewcvs/brasero/

Thanks to all the people who contributed to this release through patches, transl
ation, advices, artwork, bug reports.

7 months have been passing by since the launch of the official openSUSE forums back in June. Since then a lot has been done by both the membership and the forums team to make this a big gain for the whole openSUSE community. From now on we are going to provide status reports on a monthly basis to represent the progress we make. As this is the first issue of status reports, we’d like to provide some long-term openSUSE forums statistics along the statistics for December 2008.

Up to the 31st of December 2008, we achieved a membership of 18.772 members, 18.144 threads and 105.203 posts, which is quite a lot considering that we started with an empty database due to some technical issues we had during the merge of the three independent parties that initially joined forces. Most users ever online was 7.771 – including guests – on the 2nd of December 2008.

The following diagram shows the monthly development of new user registrations, user activity, new threads and new posts since the launch in June. The user activity measures the number of individual visits to the openSUSE forums. We started strong with the release of openSUSE 11.0, then the traffic has been slowly declining followed by another peak with the release of openSUSE 11.1.

The next diagram outlines the daily statistics of the same measurements for December 2008. As you can see, the release date of openSUSE 11.1 – the 18th of December – had a significant impact on all presented measurements.

Kudos to our Top5 posters during the last 7 months…

• oldcpu – 4.558
• caf4926 – 3.643
• kgroneman – 2.536
• ken_yap – 2.375
• swerdna – 2.355

…and to our Top5 posters during December 2008.

• caf4926 – 795
• oldcpu – 658
• mingus725 – 449
• ken_yap – 441
• BenderBendingRodriguez – 284

Thanks a million for making the openSUSE forums useful.

We’d like to take the opportunity to thank the whole openSUSE community for their participation – without your great support during the last 7 months the success of the openSUSE forums would never be possible. The openSUSE forums are accessible through the website and the NNTP gateway. If you’re interested in the latter possibility, be sure to read my former article about NNTP access to the openSUSE forums.

As of the issue #49 of the openSUSE Weekly Newsletter, we present hot topics and asserted threads at a dedicated openSUSE forums section to the openSUSE community. If you are a frequent forums visitor and you’d like to contribute to this openSUSE forums section, you are very welcome to join the Newsletter Team. If you’re interested, please contact me – rhorstkoetter/at/opensuse.org – for further information.

Happy New Year from the whole openSUSE forums team!

Today while trawling around on the opensuse mailing list I found this gem of a quote from one of the user's answers that summarize really well why I love and continue to use Linux and why any other thing would feel wrong ....

"""
I use openSUSE and Linux because it allows me to use my computers the
way I want. I have some almost new hardware and some really old
stuff. I'm typing this on a Thinkpad laptop with a P3/1Ghz and 256mB
RAM while I have 4 ssh sessions into my server running 2 movie
re-encodes and doing file maintenance in the other 2. I've got 2
directories on my server mounted on this and 1 directory on this
laptop mounted on the server to copy files with. If I was using MacOS
or Windows I'd barely be able to do anything.
""" - Larry Stotler

Thank you Larry for converting my thoughts into such simple but expressive words.

There have been mixed reviews for OpenSuSE 11.1, some lauding it while others panning it for a disaster almost as bad as the 10.1 release mostly surrounding KDE-4 desktop choice. The desktop environment is so much a part of a distro nowadays that normal users do not usually make the distinction between what is the distro and what is the desktop environment. For them, KDE or OpenSuSE they are both the same. For me I applaud the OpenSuSE team for taking a brave new step ahead! KDE-4 has it's faults no doubt but as usual I put my total trust in the OpenSource community to mold into something better than the current 3.5.x. I will still look forward to keeping OpenSuSE as my main working distro.

Finally to all the readers of this blog. Merry belated Christmas and a Happy Profitable new year ahead!

Just upgraded my X61's opensuse from 11.0 to 11.1 and found that the opensuse team bumped up the python version from python-2.5.x to python-2.6. Woohooops! Definitely won't win them any new fans in the Python camp for that move. For one deluge no longer works as it uses Python-2.5.x. As a comparison, although the folks over at the Fedora-10 camp is also known for their up to date apps, they still maintained python at version 2.5.2 to maintain a semblance of sanity with some of the apps that need python 2.5. I am just going through the multitude of Python applications I have on my box to see which one greets me with a "Goodbye cruel world" bomb. Why oh why do you have to be like that opensuse?! Well on the upside the whole desktop experience has improved and I had a relatively smooth upgrade path.

Something else too, kde-4.1 which used to be pretty clunky and unusable in 11.0 has been improved and after a while of getting used to it, I am beginning to think it's pretty good.

Well, when the lizard gives you lemon make lemonade I guess ... time to revisit ktorrent. I just hope everything else is intact.

Is over now. Hope everyone had a relaxing time.

As for work... Since December 10:

- We released openSUSE 111!!!11!elf1 (since every says openSUSE 11 to openSUSE 11.0 a little bit freedom here).

2 hours later we started releasing security updates for it, complete with delta support etc.
7 security updates after 24 hours.

- Slow down for Christmas break... Over Christmas break we of course do not close the SUSE and
throw the keys away, but most developers are on holidays. We are of course checking E-Mails
and reacting on critical issues. So far no critical issues yet.

- Wine 1.1.11 released, RPMs as usual on the buildservice.


But now I am on vacation, spent a week at my parents place, helped dig up the forest of grandma for planting new trees, eat lots of food, tried showing the Nintendo Wii to my family (so far no one has played with it, only the husband of my sister), and sleeping long and general relaxing.

What I did in OSS stuff:
- You can now dump and configure most of the Nikon D70s properties. (also used by the other Nikons). So every aspect that can be remote controlled is (will be) remote controllable with a nice interface. Also planned for the other Nikon DSLRs.
- Fixing the KDE4 camera:/ ioslave and configuration module. Still ingoing, but the kcontrol module was completely broken at least due to some automagic conversions run over it.
The kioslave troubles seem related by yet more semantic changes in KIO behaviour. I rewrote parts of kio kamera already to make it less prone to such unclear behaviour, not yet finished / committed.

I was curious about some discussion threads posted in LinkedIn's Open Source group. One had the following content:


Is 2009 The year of "supported open source" Do you agree or disagree ?

I have to admit having worked on both sides of the fence the biggest trend we are now experiencing on web related project requirements is the shift to "supported open source technology"...

The days of 6 figure plus licence fees are now over "phew" our clients thankfully quote...

Old versus New

Interwoven / Vignette versus Alfresco / MySource Matrix ?
Salesforce versus Sugar CRM ?
Documentum / Trim versus Alfresco / Sharepoint Integrated CMS's

What are your thoughts fellow CM Professionals ? Don't just take my word for it... http://cmswatch.com/Feature/189


I read some interesting opinions below, such as this one from Tony Wasserman:

To me, the issue here is adoption and use of open source software by companies and governments for activities that are essential to their businesses. One of the key corporate criteria for that type of software acquisition is availability of long-term 24x7 support, including service level agreements for problem resolution. These CIO's and other decision-makers just don't accept the idea that they can post their issues on a forum and that someone will post a reply. They want a toll-free telephone number to call with the assurance that someone knowledgeable will answer and address the issue.

For example, while small companies and the technically knowledgeable will download and install the Drupal CMS (and its underlying components), the corporate buyer, by contrast, will go to Acquia, gladly paying for support. As a better example, many of the installations of open source software in corporate environments are being done through consultants and system integrators, such as Wipro, Infosys, Accenture, and IBM.

So now the next question is whether the demand for open source software will increase in 2009. For that, I would give a qualified "yes". Startups have been building their companies on open source software for most of this decade, and will continue to do so, but they are not spending a lot of money on support, consulting, and training services. Developers in companies of all sizes have also long used open source software packages and libraries, including Eclipse, NetBeans, JBoss, MySQL, and hundreds of others, again without much money changing hands.

For enterprise applications, companies have already made substantial investments in existing proprietary software from Oracle, SAP, Microsoft, and other vendors, so it is hard for them to justify replacing it. The enterprise opportunities for open source come with new applications, and with growing companies that need these applications.

So I think that there will be growing revenue in 2009 for the system integrators providing open source support and services, as well as some money for the vendors of commercialized open source products, such as Zenoss, Groundwork, and other infrastructure packages. I think that the growth for the application packages is probably a little further out, though I would make an exception for OpenOffice.org , which has already seen a lot of acceptance.


Or this one from Glenn A. Curry:


Tony brings up an interesting issue. That of access to tech support. But our experience has been that the tech support available from commercial software manufacturers is in many cases worse than nonexistent. Not all have 24x7. And even if there is someone that answers the phone, there typically is little value in talking to them.

In trying to resolve software issues for our customers, we are most often given answers like "just keep reinstalling it till it works". Or they want security settings reduced because their interface is sloppy. Or they just flat give bad answers. The extremely poor level of phone support so often found is incredible. The battle required to move up the chain to someone that actually has a clue is frustrating and costly to the customer as they have to pay for our time while on the phone.

e.g. we spent days dealing with Sage on a Peachtree upgrade. Their solution (besides the before mentioned "just keep reinstalling it, that usually makes it work eventually") was to run as administrator all the time to get around a security problem. Eventually we found the problem and solved it with some port mapping. It was a common problem based on discussions on techie sites. AFAWK it is still a problem for them. We sure are not going to tell them how to fix THEIR bad software design for free. And noe one there had a clue.

And I won't even begin to list the massive Microsoft tech support nightmares.

Just because a company claims 24x7 tech support, does not mean it has an actual usable value.


So, without trying to be devil's attorney, I gave my opinion:


I think Tony and Glenn raise good points about support, but I would like to arise a third point, that maybe contrasts with them. The issue is not about support itself, but about what does "support" mean in open source software:

1) Yes, in open source, there's no monopoly about technical support, and this is always a good thing, except for the cases in which it can be seen wrongly as bad quality, because:
a) It may happen that there's no company behind an open source project, just one or some developers, and it's a bit awkward to ask them for support if they're not professionally gathered in some way. Besides, if the developer base is so small, it's going to be difficult to find another company which gives you support if they don't know much about the product.
b) It may happen that the developer-base is spread around many companies (for example: OpenOffice, the Linux kernel), so the company that needs support is normally confused as to which one is the best one to request support. This is awkward to a company which normally considers a product to come from "just one company".

2) Propietary software may mean a monopoly in regards to technical support but, let's face it: many incompetent people working inside companies just prefer some provider to blame if something goes wrong: "we're stuck in this issue because Oracle (or put you're favorite propietary software company here) technical support sucks", and it's not their fault anymore. If they had chosen an open source software solution, they may be accused of:
a) Not choosing the best provider for technical support.
b) Not fixing the issue themselves, since, if you have the code, it's just a matter of time to solve it, right?

Well, just trying to be realistic. Of course I advocate open source (I work on it on a daily basis), but just wanted to give some clues about why it's not getting the success it should have.


In general, the (2) point and (2a) in particular, is very similar to the reason why still incompetent but huge companies survive on the market: I've heard many cases of people just buying Oracle or Accenture because they're the most expensive. If all goes wrong, it's impossible they would be accused of selecting the wrong provider if they selected the most expensive one, right?

UPDATE 16-FEB-2008: Even though the above given problems about choosing open source solutions, here's a nice guide to try to overcome them: Convincing Management To Approve Free Software.

Merry xmas everyone!!

I'm spending my xmas night with my parents and then (when they fall sleep) i will be with my friends eating, drinking and drinking until the sun rises. It's a tradition here. I'm feeling very happy for this day i hope the best for everyone!

PS: I got a gift from my parents, a Emporio Armani Code perfume, my favorite.
PS2: Cleaning some bugs at GNOME bugzilla  and submiting new 2.25 packages for opensuse.

Happy xmas!