Alien Pastures

While I am working hard on ARM packages with the goal of being able to start X.Org on the ChromeBook, the KDE developers keep strictly to their release schedule. So I had to make some time to create Slackware packages  for the fresh KDE Software Compilation 4.10.2. Released yesterday, this iteration brings “bugfixes and translation updates” and no new functionality. If you want to know more about the fixed bugs, check out the KDE bugtracker for the KDE 4.10.2 fix set.

I expect that KDE 4.10.2 will be added to Slackware-current very soon, so after a chat with Patrick I decided to stay on the path I had started on, and bring you this KDE update as a set of Slackware 14 packages.I used the KDE.SlackBuild framework of slackware-current because Pat enhanced the script somewhat after the previous release… if you are running Slackware-current it is better that you wait for the official packages.

How to upgrade to KDE 4.10.2?

You will find all the installation/upgrade instructions that you need in the accompanying README file. That README also contains basic information for KDE recompilation using the provided SlackBuild script. Please note that if you are not yet running one of my KDE builds, you should upgrade from a (preferably) full installation of Slackware 14. I had some feedback from Slackware users who installed Slackware 14, excluded the whole “KDE” package series from that installation, and then installed my KDE packages on top.  That way, you will be missing a lot of packages, several of them essential to the proper functioning of KDE! If you skipped the whole KDE series and install my KDE packages, you still need to get these from a Slackware 14 package tree (the essentials are highlighted):

amarok
k3b
kaudiocreator
kdevelop-pg-qt
kplayer
ktorrent
kwebkitpart
libktorrent
networkmanagement
polkit-kde-agent-1
polkit-kde-kcmodules-1
quanta
wicd-kde

You are strongly advised to read and follow these installation/upgrade instructions!

Download locations (using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server):

• http://alien.slackbook.org/ktown/ (the master repository), rsync URI: rsync://alien.slackbook.org/alien/ktown/
• http://taper.alienbase.nl/mirrors/alien-kde/ (my fast mirror), rsync URI: rsync://taper.alienbase.nl/mirrors/alien-kde/
• http://repo.ukdw.ac.id/alien-kde/ (willysr’s Indonesian mirror), rsync URI: rsync://repo.ukdw.ac.id/alien-kde/

Have fun! Eric

During the Easter weekend, I have been working on almost 150 SlackBuild script updates for my ARM hardfloat port. That costs time… and with several setbacks like creating a new gcc-4.8.0 compiler package which then refuses to compile anything else; a new glibc-2.17 package which causes segfaults of every binary after installation (an exclusive ARM hardfloat issue apparently); the creation of a new llvm package which was needed for icu4c to compile on an ARM platform took NINE hours to complete, so I had to setup distcc and a new cross-compiler on my AMD Phenom build server to distribute the load… and then it was Easter too!

So, I am a bit behind on other stuff I wanted to do. The new KDE 4.10.2 is around the corner and I am going to provide Slackware 14 packages (Pat will hopefully update the KDE in slackware-curent at the same time). There is also the new LibreOffice 4.0.2 which I want to make available for Slackware 14. Even LibreOffice 3.6.6 was released in the rock-stable old 3.6 branch (for which I am going to create Slackware 13.37 packages). KDE just started compiling here, and that will take most of tomorrow to finish (the 32-bit packages will be created while I am away for work). That means, don’t expect LibreOffice packages before friday.

But what I really want is some more sun, higher day temperatures and an end to this horribly cold and hard East-wind!

Eric

There were updates to kernel, gcc and lots of other stuff yesterday in our Slackware development tree. See the Slackware-current ChangeLog.txt for all the details. It seems that Patrick is getting into the habit of telling a lot more about the decision process around the development than he used to. It is nice to read that information, I am sure you all agree to that.

The update of the gcc packages needs to be followed by a similar update in my multilib repository. The new gcc-4.8.0_multilib packages have been available since yesterday, but I did not have an opportunity to blog about that. Downloads are available from places like:

• http://slackware.com/~alien/multilib/current/ (the primary server)
• http://alien.slackbook.org/slackware/multilib/current/ (slackbook mirror, bandwidth-capped)
• http://taper.alienbase.nl/mirrors/people/alien/multilib/current/ (my mirror)
• http://repo.ukdw.ac.id/alien-multilib/ (willy’s mirror)

Remember, a multilib configuration is (only) needed if you want to use binary-only 32-bit software on 64-bit Slackware – think of Valve’s Steam Client, the WINE emulator, Citrix client etc.

If you are looking for instructions on how to add or update multilib on your 64-bit Slackware, check out our Slackware Documentation Project which has this information and much more.

Cheers, Eric

Well folks, the ARM-powered Chromebook built by Samsung can finally be bought in the Netherlands, and this raises a hairy question. Should I buy one and have a real-life target for my ARM port of Slackware which has been on the backburner for a year?

As you may remember, I started an ARM port of Slackware which is different from SlackwareARM.The design goals I have set for my own port are:

1. it should have SlackBuild scripts which are compatible with official Slackware – i.e. Pat Volkerding should be able to just grab an unaltered script for the ARM port and build a 64-bit Slackware package with it
2. it should target modern ARM architectures. SlackwareARM targets older generations of ARM CPU’s – notably without hardware floating point support. I want to create a port which can be used on “powerful” ARM tablets, and laptops.
3. it should be a port from scratch and the process should be documented

I bought a TrimSlice ARM computer late 2011 but unfortunately that hardware did not live up to the promise.It is a nice developer box (meaning it builds packages faster than other ARM computers) but it has not become a consumer product.

I have been thinking about buying a tablet as my new target for the ARM port, but there are no interesting hardware choices really which warrant the effort I have to spend on making Slackware work really well on a touch device. There are some tablets which are catering for Open Source OS-es, like The ZaTab, but it is relatively expensive, not too powerful and this too, never became a viable consumer product. The Vivaldi tablet created by KDE developers is still awaiting its birth and I have no idea if this tablet will be more than a gimmick or even vaporware.

And here is that ARM powered ChromeBook! With 7 hours of battery life, no moving parts, fan-less design, a real keyboard and an exceptional screen (I have held one in my hands) it does not come with any local storage of interest… because it runs ChromeOS on a 16 GB SD card, and you are supposed to store and access all your stuff online in a Google Drive. But, if this laptop would run Slackware, you could add a larger SD card, or plug in a USB hard drive and have a very interesting laptop indeed!

Well, here is the catch. I do not have the funds to buy this laptop. Financially it is looking a bit bland here at the moment. There is some donation money coming in every month, but that is a trickle and does not even pay the electricity bill for the server (which is OK since this is not my job, it is my hobby after all).And this laptop has been eyeing at me from its Google web page, and I seriously like it, and like to have one. I know that Stuart Winter (creator of SlackwareARM) bought one for himself and is working on a SlackwareARM boot.

I decided that there is only one way in which I can revive my own ARM port, and build a hard-float ARM image of Slackware with KDE for that ChromeBook. And that is to ask you people for support.

Note that I already received those 300 euros I needed to purchase the ChromeBook… in fact I received three times as much! As explained on the ARM Port page, the additional money will go into the purchase of additional hardware after I finish the ARM port, or earlier if I need more ARM computers to speed up the compiling process.

Yes, a “donate” button. What I propose is that I try to collect the 299 euros in donation money that it will cost to buy the ARM ChromeBook in the Netherlands. The “donate” button above will lead to a PayPal page where you can contribute an amount of money that you can spare. I will create a blog page http://alien.slackbook.org/blog/armport on which I will keep track of the progress and will mention everyone who made a donation to this cause. If you do not want your name listed,  you can tell me so on the donation page.

In return for the donation money, assuming I am able to collect these 299 euros:

• I will resume my ARM hard-float porting effort (yes, this may affect the update frequency of other packages I maintain).
• That porting effort will not be “behind the curtains” like it has been so far. I will upload packages and scripts and will welcome ideas and feedback
• The Chromebook will be the target hardware to build a bootable Slackware image.
• I will upload the from-scratch cross-compiler and minirootfs which I created already, to start with
• I am going to document on docs.slackware.com about porting to a new architecture from scratch.
• I will also tickle Pat Volkerding’s interest in the ARM port.

I do think that this ARM ChromeBook might be a real viable consumer product worth buying by more than just developers and geeks, and if Slackware runs on it that would be awesome!

What do you think? Am I crazy to ask you for support money? And what if I do get money, but more than 300 euros? Should I try to buy another ARM product (like, a tablet) or return the surplus money? If I fail to collect those 300 euros, people will get their donations back in any case. Feel free to spread the link to this page so it gains some more attraction.

Eric

Today’s update to the Slackware-current ChangeLog.txt comes with a large piece of communication by Pat Volkerding. A new kernel, a start of UEFI boot support in the Slackware installer, and new glibc packages are the most important changes mentioned in the post. If Pat had a blog this would definitely be a proper “blog post” considering its size. A recommended read for followers of the Slackware development effort.

Of course that glibc update warrants a companion update of the multilib packages which I maintain on the side. Check out these download locations:

• http://alien.slackbook.org/slackware/multilib/current/ (the primary server, but bandwidth-capped)
• http://taper.alienbase.nl/mirrors/people/alien/multilib/current/ (my mirror)

Remember, multilib configuration is (only) needed if you want to use binary-only 32-bit software on 64-bit Slackware – think of Valve’s Steam Client, the WINE emulator, Citrix client etc.

If you are looking for instructions on how to add or update multilib on your 64-bit Slackware, check out our Slackware Documentation Project which has this information and much more.

Cheers, Eric