Monday, February 19, 2007

openSUSE 10.3 Alpha1

Last week I released openSUSE 10.3 Alpha1 and installed it on my laptop as well. There are not many user visible changes in the system, in most cases it looks like 10.2. But under the hood a number of changes have been done that will everybody:

  • The GNOME packages are now installed to /usr and not to /opt/gnome anymore - and therefore in the standard place. This allows us to remove a couple of patches and hacks.
  • KDE was updated to KDE 3.5.6.
  • Linux Kernel updated to 2.6.20 with new hardware support and drivers. With Alpha1, there's no Xen support enabled but this should be fixed in the next Alpha.
  • A lot of people have asked for a real minimal text installation - and we have changed the patterns to allow this.
  • has been updated to version 2.1.
  • The whole distribution is build now with -fstack-protector to better guard against some buffer overflows.
  • Usage of LUKS by default for crypto partitions in YaST. Both GNOME and KDE handle removable LUKS media now (see the screenshot below).

As usual, all bugs should get reported in our bugzilla as explained in, discussion is most appropriate on the mailing list.

To download media there are links at

The next planned release is Alpha2 in four weeks (March 15th).


g said...

Hi Andreas

I have a question about the 2.6.20 kernel which will go in openSUSE 10.3. At the moment I'm still using openSUSE 10.2 but I downloaded the 2.6.20 kernel RPM from the build service and recompiled it myself to fit my system. All went well, but after trying to build the nVIDIA driver, it failed by saying that the driver uses GPL'd syscalls but its license is non-GPL'd. Does this mean that as of SUSE kernel 2.6.20, closed source drivers will be excluded, or am I doing something wrong here and support for those drivers will be there?


Andreas Jaeger said...

We're not doing any changes in our kernel in this area and take the offiical Linux kernel. Something must be wrong with your build. If this would be a generic problem, I assume that it would be reported on the linux kernel mailing list.

Btw. we might as well go with 2.6.21 or newer - depending when those get released.