Other articles

  1. Upgrading Fedora 23 to 24

    Fedora 24 was released a few days ago.

    I've upgraded one of my machines. The others are soon to follow. One problem I discovered was that the default Gnome-X-Session does no longer support my touchpad, disabling tap-to-click for me. Switching to the Wayland session worked very well and I have yet to hit any glitch.

    If you're running Fedora 23 you can easily upgrade to Fedora 24 running the following console commands. But before that, make sure your system is fully upgraded and rebooted, especially if you installed some kernel updates.

    sudo dnf install dnf-plugin-system-upgrade
    sudo dnf system-upgrade download --releasever=24 --allowerasing
    

    The --allowerasing argument allows some packages to be deleted during the process. I had some dangling haskell packages, that needed to be deleted. No problem there.

    Once all the downloads are done, type sudo dnf system-upgrade reboot to reboot your system starting the actual upgrading process.


  2. Installing Cockpit on Raspbian

    Cockpit

    Cockpit

    I was playing a bit with with a Raspberry Pi B and raspbian and I wanted to install Cockpit on my pi. Sadly, we can't use the provided debian repository since they do not provide packages for our Pi's processor architecture.

    So we do it ourselves.


    First thing, we need to install node. If you already have a current node installation, you don't need to do that.

    Starting with node, we download the latest node source code and unpack it wget https://nodejs.org/dist/v5.9.1/node-v5.9.1.tar.gz && tar -xzf node-v5.9.1.tar.gz. We now can just cd in there (cd node-v5.9.1) and build and install it (./configure && make && sudo make install). This will take quite some time. This might even take a few hours. After the configure step, you can make > makelog & and then disown in order to leave that session alone and even close it. But don't forget to sudo make install once it's done.


    Now on to building Cockpit itself.

    First we need to install all the build dependencies:

    sudo apt-get install autoconf intltool libglib2.0-dev libsystemd-journal-dev libjson-glib-dev libpolkit-agent-1-dev libkrb5-dev libssh-dev libpam-dev libkeyutils-dev glib-networking
    

    After we've installed all the build dependencies, we can download the sources of the latest release from github. In my case, this was 0.99.

    wget https://github.com/cockpit-project/cockpit/archive/0.99.zip && unzip 0.99.zip
    

    After we cd-ed into the source directory, we can, more or less, follow the building instructions.

    Create and switch to the build directory and run autogen.sh. I had to disable pcp because I wasn't able to find the header files in the raspbian repository. We also disable documentation creation.

    mkdir build
    cd build
    ../autogen.sh --disable-pcp --disable-doc
    

    And once this step is done, we compile it, install it and copy some authorization files.

    make
    sudo make install
    sudo cp ../src/bridge/cockpit.pam.insecure /etc/pam.d/cockpit
    sudo sh -c "cat ../src/bridge/sshd-reauthorize.pam >> /etc/pam.d/sshd"
    

    And we're basically done. Start cockpit with sudo systemctl start cockpit.socket and enable it to run on boot with sudo systemctl enable cockpit.socket.

    You're now good to go to access cockpit on port 9090 or integrate it in your cockpit landscape.


  3. wordpress certificate error preventing upgrade

    I had the following problem after upgrading my wordpress installation to 4.4: SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed.

    The problem is that wordpress ships its own, old certificate bundle. You can fix this by downloading http://curl.haxx.se/ca/cacert.pem and overwrite your /wp-includes/certificates/ca-bundle.crt with it.

    This will be needed after every wordpress upgrade that does not fix the issue itself which is probably an outdated server missing the certificate or a php version being compiled with an old version of openSSL.


  4. Upgrading Fedora 22 to 23

    Fedora 23 was released a few days ago.

    I've upgraded one of my machines. The others are soon to follow. I have yet to hit a problem with Fedora 23.

    If you're running Fedora 22 you can easily upgrade to Fedora 23 running the following console commands. But before that, make sure your system is fully upgraded and rebooted, especially if you installed some kernel updates.

    sudo dnf install dnf-plugin-system-upgrade
    sudo dnf system-upgrade download --releasever=23 --best
    

    The --best argument makes sure if there are any transaction problems, the installation will not continue. I've had to remove some old gstreamer-plugins that are sure to come back with a new installation of fedy.

    Once all the downloads are done, type sudo dnf system-upgrade reboot to reboot your system starting the actual upgrading process.


links

social

Theme based on notmyidea