Feb 192013

As announced on the Heise newsticker (article in german) the linux kernel version 3.8 has been released. If you look closely on kernel.org though, you’ll find that the latest stable version is still 3.7.9, but I don’t know if that’s because of something about the 3.8 kernel, or just because I looked there too early.

There are several interesting things in that version:

On the server-side the most important new feature, in my opinion, is the possibility to create namespace containers as a regular user. Such a container can be understood similar to a chroot jail, or a virtual machine, so that regular users can run privileged applications inside a container and not endanger the integrity of the system as a whole. Also there’s now a Ballon driver for Hyper-V which means that a Virtual Machine with a linux guest running 3.8 can release memory to the Windows host that runs it, and reclaim that memory later.

Also, there is improved support for the modern NUMA architectures, and lots of improvements for btrfs and ext4fs.

On the desktop the most important changes are better 3d hardware acceleration support with the Nouveau driver, a driver for Phillips PSC724 “Ultimate Edge” sound cards, and several improvements for DMA handling in regard with video streaming.

For mobile devices (and of course, servers and desktops with SSD storage) there is a new filesystem, f2fs, which is specifically designed for flash storage.

The upcoming openSUSE 12.3 release, which is scheduled for around mid-March, is still using the 3.7.7 kernel, or at least was last time I looked, and I don’t think the openSUSE team is going to switch kernels just 3 weeks before the gold master.

If you want to read about the 3.8 kernel in greater detail the kernel log on heise open is quite good (but in german).

Jan 102013

I’ve done it, and upgraded my wife’s and my own laptop to openSUSE 12.2 with zypper, following the same procedure as mentioned before. My experiences so far:

  • My wife had trouble with pulseaudio / phonon playing correctly through HDMI to the built-in speakers on her monitor. I had to actually delete all user settings for phonon, pulseaudio, and gstreamer, but now it works without a hitch.
  • Initially some KDE apps didn’t want to remember that they are supposed to start minimized. Same as before, deleting the settings files solved it.
  • Certain older software that comes only as binary does not work anymore. No actual surprise there.
  • Certain older games from some of the humble bundles that comes as binary RPM got uninstalled because openSUSE 12.2 does not have the required libraries anymore. No surprise there either, and no personal loss as I played those only on my phone.
  • Certain older software does not build anymore because it comes with old, outdated versions of some required libraries, and those don’t build with gcc 4.7.1.
  • After a resume, the network interfaces are still down. Not good when you’re operating on a NIS/NFS setup. Workaround: disable automatic suspend to disk.

Enough of the bad, here are some few of the positive things that stand out:

  • With the 3.4 kernel we can have Solaar which basically monitors the battery charge in logitech wireless equipment.
  • Steam runs on it. Yep, steam as in http://store.steampowered.com/. Maybe linux gaming will finally get somewhere where Loki games should have taken it 10 years ago.
  • The whole setup feels snappier than 12.1.

All in all, this upgrade is one of the better ones. I like it so far.

Jan 032013

If you notice that your ssh agent and/or gpg agent aren’t running after logging in to KDE4 on openSUSE, and you just upgraded your KDE from the KDE:Release:49 buildservice repository, there is a simple fix.

Run this command as root:

ln -sf /etc/X11/xdm/Xsession /usr/share/kde4/config/kdm/Xsession

That will do it. By the way, the bug report for this bug is here. Please add your 2 cents worth if you are hit by it.

Dec 122012

I’m doing it again. Upgrading a live system with zypper, this time the step is 12.1->12.2.

The procedure has been described here and here; let’s see what happens.


Everything worked fine, with the small exception that the ssh daemon config needed one small tweak to get nxserver to work again.
Hint: nxserver uses authorized_keys2, suse uses authorized_keys as the ssh key file name.

Nov 142011

It seems that “the community” consists of three separate groups of people:

  1. the people who loudly demand features
  2. the developers who loudly debate the ethic, moral, technical religious impacts if the features demanded by 1. would be implemented
  3. the small group of developers who watch 1. and 2. and at some point say “Oh for crying out loud. What a noise over 5 lines of code.”

As an example, look at the discussion over the feature request in kmail where someone wants kmail to be able to remove attachments from mails.

As another example, look at this one. Some people would like to see single-sign-on in KDE4. The discussion was long and loud.

And, if you Google a bit, you find that the wallet daemon has had the required dbus call since KDE 4.4.2, for crying out loud!

Just that noone has bothered to point a finger at the required pam modules and helpers.

I’ve packaged them for openSUSE, get them from my OBS project and configure them as described in the readme files included in the packages, and you have single sign on.

Note: single sign on only happens if you actually enter a password on login. The typical suse setup with an user session starting automatically on boot can’t work with this.

Note: this seems to work only for local useraccounts, but not in a NIS environment.

Nov 102011

I’ve been testing openSUSE 12.1 RC2 for a week now, and so far I’m impressed.

Network installation went pretty well (after I had figured out that the reason for the initial woes was the DHCP server here at work, not suse), and so far a lot of stuff that used to need manual intervention “just works” now. For eexample the use of ksshaskpass for ssh-add and other little quirks.

On the other hand there are a few oddities, none of them being the fault of the openSUSE team, as far as I can tell:

  • kopete refuses to “do” MSN – MicroSoft has changed something on their end; kmess needed a patch & rebuild as well
  • no sun java – Oracle has changed the licensing and disallows redistibution now.

Other than that: cool beans.

Especially KDE4 is impressive on this version – KDE 4.7.2 actually works now.

Mar 212011

Some of you might have heard of tmpfs.
For those who haven’t, here’s a link to wikipedia. In short, tmpfs is what amounts to be the good old trusted ram disk. How can this be useful to speed up your computer?

Simple enough, use it for temporary files. On unix systems, that usually means putting /tmp on a tmpfs. On openSUSE, all you need to do is putting this line in your /etc/fstab (after cleaning out /tmp or the mount won’t work):

none                 /tmp                 tmpfs      size=1024m,defaults                   0 0

That line creates a ramdisk of 1Gbyte under /tmp.

but… what if you restart your computer? Right, everything in /tmp will be gone. So, if you don’t want to lose your stuff in there, you’ll need this little script:

#     Template SUSE system startup script for example service/daemon FOO
#     Copyright (C) 1995--2005  Kurt Garloff, SUSE / Novell Inc.
#     This library is free software; you can redistribute it and/or modify it
#     under the terms of the GNU Lesser General Public License as published by
#     the Free Software Foundation; either version 2.1 of the License, or (at
#     your option) any later version.
#     This library is distributed in the hope that it will be useful, but
#     WITHOUT ANY WARRANTY; without even the implied warranty of
#     Lesser General Public License for more details.
#     You should have received a copy of the GNU Lesser General Public
#     License along with this library; if not, write to the Free Software
#     Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307,
#     USA.
# /etc/init.d/synctmpfs
#   and its symbolic link
# /(usr/)sbin/rcsynctmpfs
# Template system startup script for some example service/daemon synctmpfs
# LSB compatible service control script; see http://www.linuxbase.org/spec/                                                                                              
# Note: This template uses functions rc_XXX defined in /etc/rc.status on                                                                                                 
# UnitedLinux/SUSE/Novell based Linux distributions. If you want to base your
# script on this template and ensure that it works on non UL based LSB
# compliant Linux distributions, you either have to provide the rc.status
# functions from UL or change the script to work without them.
# See skeleton.compat for a template that works with other distros as well.
# Provides:          synctmpfs
# Required-Start:    boot.localfs
# Should-Start:     
# Required-Stop:     boot.localfs
# Should-Stop:      
# Default-Start:     3 5
# Default-Stop:      0 1 2 6
# Short-Description: synctmpfs XYZ daemon providing ZYX
# Description:       Start synctmpfs to allow XY and provide YZ
#       continued on second line by '#'
#       should contain enough info for the runlevel editor
#       to give admin some idea what this service does and
#       what it's needed for ...
#       (The Short-Description should already be a good hint.)
# Any extensions to the keywords given above should be preceeded by
# X-VendorTag- (X-UnitedLinux- X-SuSE- for us) according to LSB.
# Notes on Required-Start/Should-Start:
# * There are two different issues that are solved by Required-Start
#    and Should-Start
# (a) Hard dependencies: This is used by the runlevel editor to determine
#     which services absolutely need to be started to make the start of
#     this service make sense. Example: nfsserver should have
#     Required-Start: $portmap
#     Also, required services are started before the dependent ones.
#     The runlevel editor will warn about such missing hard dependencies
#     and suggest enabling. During system startup, you may expect an error,
#     if the dependency is not fulfilled.
# (b) Specifying the init script ordering, not real (hard) dependencies.
#     This is needed by insserv to determine which service should be
#     started first (and at a later stage what services can be started
#     in parallel). The tag Should-Start: is used for this.
#     It tells, that if a service is available, it should be started
#     before. If not, never mind.
# * When specifying hard dependencies or ordering requirements, you can
#   use names of services (contents of their Provides: section)
#   or pseudo names starting with a $. The following ones are available
#   according to LSB (1.1):
#       $local_fs               all local file systems are mounted
#                               (most services should need this!)
#       $remote_fs              all remote file systems are mounted
#                               (note that /usr may be remote, so
#                                many services should Require this!)
#       $syslog                 system logging facility up
#       $network                low level networking (eth card, ...)
#       $named                  hostname resolution available
#       $netdaemons             all network daemons are running
#   The $netdaemons pseudo service has been removed in LSB 1.2.
#   For now, we still offer it for backward compatibility.
#   These are new (LSB 1.2):
#       $time                   the system time has been set correctly
#       $portmap                SunRPC portmapping service available
#   UnitedLinux extensions:
#       $ALL                    indicates that a script should be inserted
#                               at the end
# * The services specified in the stop tags
#   (Required-Stop/Should-Stop)
#   specify which services need to be still running when this service
#   is shut down. Often the entries there are just copies or a subset
#   from the respective start tag.
# * Should-Start/Stop are now part of LSB as of 2.0,
#   formerly SUSE/Unitedlinux used X-UnitedLinux-Should-Start/-Stop.
#   insserv does support both variants.
# * X-UnitedLinux-Default-Enabled: yes/no is used at installation time
#   (%fillup_and_insserv macro in %post of many RPMs) to specify whether
#   a startup script should default to be enabled after installation.
#   It's not used by insserv.
# Note on runlevels:
# 0 - halt/poweroff                     6 - reboot
# 1 - single user                       2 - multiuser without network exported
# 3 - multiuser w/ network (text mode)  5 - multiuser w/ network and X11 (xdm)
# Note on script names:
# http://www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB/scrptnames.html
# A registry has been set up to manage the init script namespace.
# http://www.lanana.org/
# Please use the names already registered or register one or use a
# vendor prefix.

# Check for missing binaries (stale symlinks should not happen)
# Note: Special treatment of stop for LSB conformance

test -x $synctmpfs_BIN || { echo "$synctmpfs_BIN not installed";
 if [ "$1" = "stop" ]; then exit 0;
 else exit 5; fi; }

# Source LSB init functions
# providing start_daemon, killproc, pidofproc,
# log_success_msg, log_failure_msg and log_warning_msg.
# This is currently not used by UnitedLinux based distributions and
# not needed for init scripts for UnitedLinux only. If it is used,
# the functions from rc.status should not be sourced or used.
#. /lib/lsb/init-functions

# Shell functions sourced from /etc/rc.status:
#      rc_check         check and set local and overall rc status
#      rc_status        check and set local and overall rc status
#      rc_status -v     be verbose in local rc status and clear it afterwards
#      rc_status -v -r  ditto and clear both the local and overall rc status
#      rc_status -s     display "skipped" and exit with status 3
#      rc_status -u     display "unused" and exit with status 3
#      rc_failed        set local and overall rc status to failed
#      rc_failed   set local and overall rc status to 
#      rc_reset         clear both the local and overall rc status
#      rc_exit          exit appropriate to overall rc status
#      rc_active        checks whether a service is activated by symlinks
. /etc/rc.status

# Reset status of this service

# Return values acc. to LSB for all commands but status:
# 0       - success
# 1       - generic or unspecified error
# 2       - invalid or excess argument(s)
# 3       - unimplemented feature (e.g. "reload")
# 4       - user had insufficient privileges
# 5       - program is not installed
# 6       - program is not configured
# 7       - program is not running
# 8--199  - reserved (8--99 LSB, 100--149 distrib, 150--199 appl)
# Note that starting an already running service, stopping
# or restarting a not-running service as well as the restart
# with force-reload (in case signaling is not supported) are
# considered a success.

case "$1" in
 echo -n "Syncing to tmpfs "
 ## Start daemon with startproc(8). If this fails
 ## the return value is set appropriately by startproc.
 rsync -aAX /tmp-bak/ /tmp/
 # Remember status and be verbose
 rc_status -v
 echo -n "backing up tmpfs "
 ## Stop daemon with killproc(8) and if this fails
 ## killproc sets the return value according to LSB.
 mkdir -p /tmp-bak
 rsync -aAX /tmp/ /tmp-bak/

 # Remember status and be verbose
 rc_status -v
 echo "Usage: $0 {start|stop}"
 exit 1


activate it with this command:

chkconfig synctmpfs on

On boot this will copy /tmp-bak into /tmp after the filesystems have been mounted, and on shutdown it will copy /tmp into /tmp-bak.

Now you’ll notice a distinct increase in speed at starting KDE, for example. Another application would be your browser cache.


Mar 172011

Here’s a little followup to my previous post about how to upgrade to 11.4.

This one describes how to make the whole process even more risky. You have been warned.
It’s even possible to do this remotely through a ssh session. If you attempt to do that, do it from inside a screen session!

Actually, this first bit makes it a bit easier:



mkdir -p ${newrepodir}

cd ${repodir}

for repofile in *repo; do
 echo -n converting ${repofile} to ${newrepodir}/$(echo ${repofile}|sed -e 's/11.3/11.4/g') ... ;
 cat "${repofile}" | sed -e 's/11.3/11.4/g' > "${newrepodir}/$(echo ${repofile}|sed -e 's/11.3/11.4/g')" ;
 echo done.


This script creates a directory /etc/zypp/repos.d_11.4 with all your configured repos switched to their 11.4 counterparts.

After you run this script, all you have to do is move the old /etc/zypp/repos.d out of the way, rename the new one to /etc/zypp/repos.d and make sure that all the paths in the repo files exist. If they don’t, “zypp ref” is going to complain.

now, before you begin, run these two commands:

zypper cc --all
zypper ref

The first one clears all zypper cache folders, the second one refreshes all repositories (here’s where you’ll see if all paths are correct).
If you have a custom X11 setup (dualscreen or such), now would be the point to make a copy of your xorg.conf file.
Now you jump into the instructions in my previous post, right at #6.

Mar 142011

Here’s a quick and dirty HOWTO about upgrading from openSUSE 11.3 to 11.4, with all additional repos enabled…

  1. Switch to runlevel 3: as root, execute “init 3”
  2. Login as root
  3. Make a backup of all your repositories:
    cd /etc/zypp
    cp -r repos.d repos.d_11.3
  4. Go through all your .repo files in /etc/zypp/repos.d and replace “11.3” with “11.4”.
    Here’s a “before/after” example:

    [openSUSE 11.3 OSS]
    name=Haupt-Repository (OSS)


    [openSUSE 11.4 OSS]
    name=Haupt-Repository (OSS)
  5. Refresh your repository cache:
    zypper ref
  6. Upgrade zypper:
    zypper install zypper

    You have to pay attention on the list of conflicts. Generally the best of the proposed solutions is the one the would uninstall the least number of packages while still installing/upgrading what you want.

  7. Do the full upgrade:
    zypper dup

    Again, pay attention to any listed conflicts, and resolve them carefully. Again, the best of the proposed solution would be the one that installs what you want while uninstalling as little as possible.

  8. The scary moment:
    Reboot your system. If all went well you will be greeted by a working openSUSE 11.4 installation.
  9. Cleaning up afterwards:
    Login as root, and run the following command:

    LANG=CTYPE zypper search -si | grep "(System Packages)"| cut -d "|" -f 2

    That will list all installed packages that are not available from any of the configured repositories anymore.
    You might want to carefully remove them one by one with “zypper remove”. If you use “zypper remove -u” instead, you will also remove all dependencies that are not needed anymore. This can really break things.

Jan 272011

I just installed 11.4 M6 in a VirtualBox VM, and all I can say is that I’m going to upgrade all computers that I can lay my hands on to 11.4 as soon as possible.

For one simple reason.

SCPM is back (at least in M6).

That being said, KDE 4.6 doesn’t look half bad either.

Optimization WordPress Plugins & Solutions by W3 EDGE
%d bloggers like this: