Dec 092016
 

Oops I Did It Again…

Live Upgrade, with my tried and trusted method. By now that method is so polished that I had no issue whatsoever, so I did all three computers at the same time. I’m just glad to have a decent internet connection… I think the total downloads added up to somewhere near 15 gigabyte.

May 142016
 

I just finished a major heart surgery on my laptop. Many thanks to the guys who made some youtube tutorials about taking that laptop apart! The Acer E5-571G is definitely NOT built to be taken (apart) lightly (Here is the german tutorial that I was following, and here is an english one).

After swapping out the 2x 4G memory modules for 2x 8G ones, and the 1TB laptop hard disk drive for a 1TB SSD disk, and putting everything back together, the real fun began.

  • install the old harddisk in an external USB3.0 harddisk enclosure (the drive was still good after all)
  • boot from a Windows 10 installer
  • partition the disk and install Windows 10 in about half of the available space
  • the usual windows installation hijinx: install a driver, reboot, repeat ad nauseam
  • when windows is about done with the initial installation stuff, plug in the old harddisk on USB3.0 and copy the data from your old user account to your new

Then the linux fun begins, but be aware that this method will only work if the existing linux installation on the old disk was based on a LVM setup!

  • boot from openSUSE 13.2 installer DVD, but boot into rescue mode!
  • partition the unused space on the new disk as follows:
    • 250MB /boot
    • one LVM physical volume from the remaining space, but do not create the actual PV yet
  • plug in the old disk again
  • mount the /boot partition from the old system somewhere
  • create ext4 filesystem on the new /boot partition, and mount it somewhere
  • rsync the content of the old /boot to the new one
  • unmount the old and new /boot partitions
  • check that you can see and access your old logical volumes via the usb3 connection to your old disk (lvs, lvdisplay, vgs, vgdisplay, pvs, pvdisplay)
  • now create a PV on the new partition that you created a few steps ago
  • add that PV to the volumegroup on your old disk
  • move all used extents away from the old disk with pvmove
  • once this is done you can remove the pv that is located on the old disk, unplug the disk and use it for something else.
  • make sure the /boot partition on the new disk is not mounted
  • mount your root volume to /mnt
  • prepare your mounted root for chroot
    mount -o bind /dev /mnt/dev
    mount -o bind /sys /mnt/sys
    mount -o bind /proc /mnt/proc
  • Change into your installed system with chroot
    chroot /mnt /bin/bash --login
  • Edit /etc/fstab, make sure all references to mounted filesystems are correct (partition label/identifer for the EFI partition, UUID for /boot, etc)
  • regenerate the initrd with mkinitrd
  • recreate the grub2 configuration with grub2-mkconfig
  • reboot, enter the BIOS setup, go to the UEFI boot settings and make sure the boot order is correct and secure boot is OFF.
  • the next reboot should get you into a working GRUB2 that lets you boot linux but not windows, so boot linux, start yast2 and reinstall the grub bootloader again from there.

That’s it folks!

Jan 092015
 

I finally updated my last machine from openSUSE 12.3 to 13.1 (in the usual way), and with that one I had a bit more fun than the other few times I’ve done this by now.

First mysql refused to start, then quite a few services that were enabled on 12.3 decided to be disabled on 13.1, but nothing during the update “told me so”… but now all seems to work fine.

Dec 022014
 

I have suggested firewalld from fedora/RHEL7 for inclusion in openSUSE, as an alternative for SuSEfirewall2 for setups with highly volatile networking.

test rpm packages for openSUSE 13.2 can be obtained here:

firewalld-0.3.12-1.noarch.rpm

firewall-config-0.3.12-1.noarch.rpm

firewall-applet-0.3.12-1.noarch.rpm

firewalld-0.3.12-1.src.rpm

You will also need to enable the repository from here to get the dependencies.

Nov 232014
 

I’ve done it again… a live upgrade from openSUSE 13.1 to 13.2.

I’ve been following the usual process that I’ve outlined in a few posts so far, and it went pretty smoothly on three different computers.

The actual process has evolved into this:

  1. run this script (after editing to fix the version numbers):
    #!/bin/bash
    old=13.1
    new=13.2
    repodir=/etc/zypp/repos.d
    newrepodir=/etc/zypp/repos.d_${new}
    
    mkdir -p ${newrepodir}
    cd ${repodir}
    for repofile in *repo; do
    {
        echo -n converting ${repofile} to ${newrepodir}/$(echo ${repofile}|sed -e "s/${old}/${new}/g") ... ;
        cat "${repofile}" | sed -e "s/${old}/${new}/g" > "${newrepodir}/$(echo ${repofile}|sed -e "s/${old}/${new}/g")" ;
        echo done.
    }
    done;
  2. move /etc/zypp/repos.d out of the way, for example rename it to /etc/zypp/repos.d_old
  3. move /etc/zypp/repos.d_13.2 to /etc/zypp/repos.d
  4. clean zyppers cache:
    zypper cc --all
  5. refresh zypper:
    zypper ref

    When you do this, you might get errors for some repositories because they don’t exist yet for 13.2. To disable them, do this:

    zypper mr -d -R 

    On the other hand you might want to investigate if there are 13.2 versions of those repositories, and edit the repo files accordingly.
    Then, repeat the zypper ref command.

  6. Once you can run through zypper ref without errors, get updated versions of zypper, libzypp and rpm, and install them:
    zypper up --download only zypper libzypp rpm
    zypper up zypper libzypp rpm
  7. Once that finished without errors, do the same two commands for the whole distribution (Pay attention to any warnings and/or conflicts here. You’ll have to make the right choices about what should be done to resolve them, and I can’t really give you a recipe):
    zypper dup -l --download only
    zypper dup -l
  8. After all is done you can reboot. The first reboot should lead into textmode in case you have to re-install/upgrade your nvidia or AMD binary drivers. To boot into text mode, append this kernel parameter:
    systemd.unit=multi-user.target

Have a lot of fun!

Dec 282013
 

Seeing that there are only two more weeks until openSUSE 12.2 reaches end of life, I’m doing my usual upgrade with zypper.

If you are about to say “didn’t you do that already some months ago“, that was a virtual machine…now it’s my “production” system. Let’s hope all goes as well as it did on the VM.

So far all is looking good, but 4500 packages takes some time, so I can’t really say anything yet. I’m doing 12.2 -> 12.3 and KDE 4.11 -> KDE 4.12 at the same time, so it might get a bit hairy at some point.

The fun part comes next week… if this goes well I’ll do the same to my wife’s laptop, where a failure will be way more painful…

 

Update: finished, all seems to be working fine.

Oct 262013
 

…at least with KDE4 on openSUSE 12.2.

In a previous post I mentioned that there are single-sign-on methods available for KDE to open the wallet right on login, but they do not work when you’re using NIS accounts.

Turns out they do work after all, you just need make sure that the references to the pam_kwallet module is after pam_unix2.so in common-auth, like this:

#%PAM-1.0
#
# This file is autogenerated by pam-config. All changes
# will be overwritten.
#
# Authentication-related modules common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
auth required pam_env.so
auth required pam_unix2.so
auth optional pam_kwalletopener.so use_first_pass
auth optional pam_gnome_keyring.so

After this, you just add the two modules pam_dbus_launch and pam_kwallet in common-session like this (pam_dbus_launch needs to be before pam_systemd, and pam_kwallet at the end):

#%PAM-1.0
#
# This file is autogenerated by pam-config. All changes
# will be overwritten.
#
# Session-related modules common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of modules that define tasks to be performed
# at the start and end of sessions of *any* kind (both interactive and
# non-interactive
#
session required        pam_limits.so
session required        pam_unix2.so
session optional        pam_umask.so
session optional        pam_dbus_launch.so dbus-launch=/usr/bin/dbus-launch
session optional        pam_systemd.so
session optional        pam_kwalletopener.so    maxwait=60 session_timeout=360 localwallet start_daemon kwalletopener=/usr/bin/kwalletopener
session optional        pam_gnome_keyring.so    auto_start only_if=gdm,gdm-password,lxdm,lightdm

With these settings the pam modules work with any kind of useraccounts. Keep in mind that it will not work for automated logins where the system doesn’t actually prompt for a password.

The required pam modules can be installed from this OBS project.

Apr 152013
 

Like I already said before, openSUSE 12.3 was released today, and I’ve done the usual live upgrade with zypper.

The upgrade itself worked without any problems, and the resulting installation was usable without issues right from the start.

I logged into KDE 4.10 and everything that I’ve tried works just fine. I admit, I can’t say anything about performance as my test machine is accessed via a NoMachine remote desktop session.

After that I upgraded the KDE 4.10.0 to 4.10.1 from the opensuse build service, and that also went well and posed no problems afterwards. Now I’m waiting for my own repository for 12.3 to rebuild against KDE:Release:410.

I’m pretty confident in saying that with 12.3 the process of a live update via zypper can be done without major fear, as long as one has ones repositories set up properly, and with the right priorities (packman and KDE from OBS should have a higher priority than the stop openSUSE repositories).

Mar 132013
 

Today, openSUSE 12.3 got released after 6 months of hard work by openSUSE members and contributors.

As usual, I’m doing a zypper live upgrade, but so far it’s still downloading packages, so I can’t say anything about 12.3 just yet.

I am going to post a review of the process and the results after it is finished. In the mean time, if you’re in the area (southern Germany), why not go to the release party in Nürnberg? It starts at 7pm at artefakt.

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