A look at openSUSE 12.3
The March 13 release of openSUSE 12.3 comes just six months after its predecessor, which is a bit quicker than the target of eight months between releases that the project has set. But the shorter development cycle does not mean that openSUSE 12.3 is lacking for new features. From the kernel up through the desktops and applications, 12.3 offers much that is new.
![[openSUSE 12.3 KDE]](https://static.lwn.net/images/2013/openSUSE12.3-kde-sm.png)
The project was nice enough to provide members of the press with early access to the 12.3 final release. The distribution comes in multiple flavors, of course; I tried the Live KDE version to get a feel for the new release. It has been many years since I ran openSUSE, and I never ran it in anger, so I tried to put it through its paces a bit over the five or six days since it was made available.
Since a Live distribution is somewhat cumbersome to use as a regular system, I opted to install it as a dual-boot system with Fedora on my trusty laptop. While I was ultimately successful in getting things installed that way, it took a rather extensive detour through GRUB 2, GUID partition table (GPT) partitions, resize2fs, and so on to get there. It's not clear that openSUSE or its installer were the only culprits, as I have dark suspicions about the BIOS on the laptop, but it is clear that allowing the installer to write to the master boot record (MBR) in a dual-Linux setup leads to an unbootable system—at least it did for me, and more than once. It should be noted, though, that the Live media was quite useful in helping to recover from that state as it had all of the GRUB 2 tools and GPT-aware utilities needed to fix things up.
One new thing that came in with 12.3 is a change to Live media. It is now nearly 1G in size, which means it won't fit on a CD—either DVD or USB sticks must be used instead. That extra space allowed for additional packages, including LibreOffice 3.6 and OpenJDK 7, though not GIMP 2.8 as promised in the RC2 news item.
Installation was straightforward, with the only "tricky" piece being the partition and filesystem layout. 12.3 gives the option of using Btrfs for all non-boot filesystems, which seemed worth trying. I haven't done anything particularly interesting with Btrfs (yet), but it seems to be working just fine for / and /home.
Other than some cosmetic differences (theme, background, and so on), openSUSE 12.3 didn't seem much different from Fedora 18 once I logged into the KDE desktop (or Plasma workspace if that's the new terminology). It comes with KDE 4.10, which is more recent than Fedora's 4.9, but that difference was not particularly obvious. It works well for the limited desktop use cases I need—terminal windows, a browser, email client, and so on. I was able to use the Dolphin file manager to mount and access the encrypted /home that I use on the Fedora side, for example, which was convenient, but I still haven't gotten the hang of KDE Activities.
KDE is not the only desktop available for openSUSE 12.3; there is, of course, a GNOME version of the distribution based on GNOME 3.6. Community manager Jos Poortvliet put together a lengthy preview of openSUSE 12.3 for desktop users that covers both desktops. KDE was chosen as the default for openSUSE back in 2009, but its GNOME support is said to be top-notch as well.
UEFI secure boot support is available in 12.3, and the systemd integration that started in earlier versions has been completed. The switch to MariaDB as the "default MySQL" has been completed. MySQL is still available, but MariaDB has been chosen as a more community-oriented, drop-in replacement for MySQL.
The kernel is fairly recent, based on 3.7. It exhibited the same annoying blinking WiFi indicator behavior that I have seen on the laptop with other recent kernels, though it was easy set a driver parameter for iwlegacy and get rid of it. In fact, the same file I used on the Fedora side (with a minor name change) just dropped into /etc/modprobe.d on openSUSE. Perhaps that's not surprising, but it is indicative of how it felt to use 12.3; it was often hard to remember that I wasn't still running Fedora. Some adjustments were needed (e.g. retraining fingers to type "zypper" rather than "yum"), but the two distributions are quite similar.
There are a few oddities. The default is for the primary user to be logged in automatically, which doesn't seem like the most secure of choices. Installing Emacs led to a complaint about a lack of Asian fonts for Java. The auto-lock-screen appears not to work, as any key will unlock the screen, which seems to be a known problem, though it doesn't start working after 60 seconds for me. But those are pretty minor.
A more substantive complaint could be made about one of the more advanced features being touted for the release: using the Open Build Service (OBS) to get the latest and greatest packages. There is even a video in that news item describing how to use software.opensuse.org to update LibreOffice from the 3.6 version that comes with 12.3 to LibreOffice 4.0.
Perhaps LibreOffice was a poorly chosen example, but the video paints a picture that is very different from what a user will actually run into. In fact, it stops before things get interesting. The "one click install" offered does bring up the YaST software installer, but there are many more clicks ahead. If it were just extra clicks, it would be a pretty minor issue, but the new package conflicts with the old LibreOffice, so the user needs to make a decision about what to do—without a reasonable default (like "go ahead and break LibreOffice 3.6"). Beyond that, the upgrade caused YaST to choose an enormous number (over 100) of additional packages to install, many of which (telnet, screen, GIMP, ...) seemed to have nothing to do with LibreOffice. Licenses for Flash and Fluendo GStreamer plugins had to be clicked through as well. That said, once the process was complete, LibreOffice 4.0 was up and running on the system, it was just a lot more complicated than the video (which does feature some amusing Geeko animation) depicted.
But openSUSE is not specifically targeted at non-technical users, and anyone who has used Linux before has likely run into these kinds of issues once or twice. For technically savvy users, openSUSE provides a solid operating system with the ability to get bleeding-edge applications via OBS. For Fedora users, a switch will probably be uneventful, while other distribution users (non-systemd, .deb-based, or build-it-from-quarks-and-gluons, for example) may have some adjustments to make. It's not clear that there is a strong reason to do so, but if some "distro hopping" is in your plans, openSUSE should certainly be on the list. But for those who already use it, openSUSE 12.3 will be a welcome upgrade.
Posted Mar 14, 2013 14:16 UTC (Thu)
by jospoortvliet (guest, #33164)
[Link]
But most of the issue you had, the 100 packages with Gimp etc was the usual after-installation-update. openSUSE has a lot of packages set as 'recommended' but not installed on the live image and thus not on a fresh-from-live-stick install. Upon the first update, these, including flash and some other less-fully-open things, get pulled in.
If your first 'update' action is clicking a one-click-install, the two get combined and it does indeed get rather messy.
As you say, not something a slightly experienced user won't be able to deal with but it still is something that leaves room for improvement. But hey, that's a good thing - gives fun stuff to do ;-)
Posted Mar 15, 2013 15:46 UTC (Fri)
by geuder (subscriber, #62854)
[Link]
My comment does not directly relate to the authors experience because a.) I have still been too lazy to learn EFI and b.) my 12.3 image is just downloading as I type.
However, in general OpenSUSE approach to the bootloader has never met my personal criteria of least surprise. By default they install grub (nowadays grub2 to be exact) into the /boot partition (I typically have a separate one). Into the MBR they install a generic bootloader, which does nothing more than 1.) looks at which DOS partition has the boot flag set and 2.) calls the bootloader inside that partition.
It's a while since I installed the last OpenSUSE in a multi-boot configuration, but if that's the default regardless whether they are the only one on the disk or not it is not very co-operative to say it friendly.
Generally I have failed to get the idea with their generic loader. It could look like a symmetric way of having multi-boot using different boot loaders (or versions thereof) for the different systems instead of chain-loading. But I'm not aware of any user-friendly way to switch boot flags between power-on and boot, so it makes no sense for supporting multi-boot. Or do BIOSes acutually support this??? Now that I write it, it comes to my mind that I might not have looked at BIOS menus a lot after I first used OpenSUSE some 2.5 years ago. Well even if it could be done in BIOS, it seem slow than jumping through 2 levels of grub menus in chain-load scenario.
Posted Mar 17, 2013 20:41 UTC (Sun)
by geuder (subscriber, #62854)
[Link] (1 responses)
There is at least one issue in the Release Notes: https://www.suse.com/releasenotes/i386/openSUSE/12.3/RELE... (maybe that was not yet documented during the press preview)
Posted Mar 20, 2013 16:04 UTC (Wed)
by jospoortvliet (guest, #33164)
[Link]
Posted Mar 20, 2013 18:30 UTC (Wed)
by thoeme (subscriber, #2871)
[Link]
A look at openSUSE 12.3
bootloaders on openSUSE
openSUSE 12.3 does not boot
openSUSE 12.3 does not boot
A look at openSUSE 12.3
Hm, I have just installed 12.3 parallel to 12.2, with installing 12.3 GRUB2 in the MBR (my usual choice). Starting 12.3 and 12.2 works flawlessly. Maybe its playing nicer with older openSuSE versions than with Fedora et. all.