My thoughts on Slackware, life and everything

Category: Rant (Page 8 of 10)

Only 24 hours in a day

cat_asleep

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

Call for help: Slackware on an ARM Chromebook?

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

Busy days, not Slackware related

In the next days or weeks, I am going to try and rest and re-vitalize myself. It would be a waste of effort if I burnt myself out. But the shitty weather does not help. Who feels like it is summer in Europe? I have just emptied the buckets in the hallway which caught the water seeping through the crack in the roof… repair money is not available right now.

During the past week, there were many such distractions to keep me away from hacking at Slackware. This will likely remain unchanged during the next weeks. We had a fire in the kitchen, which caused damage (the stove and oven were destroyed), but luckily no one got hurt! It takes time to invite experts to assess the damage, arrange repairs and such. I als got hooked on some e-books I had loaded onto my Sony E-reader… reading is eating away precious time faster than you think!

Anyway, all this distraction had consequences for the package pipeline. With regular releases of KDE, LibreOffice, OpenJDK and VLC – all pretty big builds – my free time is increasingly limited to building updates for these aforementioned programs. It is frustrating at times that I have to make an advance planning because especially KDE and LibreOffice releases tend to come at roughly the same time. Building in several virtual machines at the same time hurts my server’s performance and it does not help the total build time per program…

Also, I really need to pick up the pace with my new but currently stalled ARM port of Slackware (which will have differences to the existing ARMedslack port). I am talking to some people about what would be a cool computer to own which really should be running Slackware. The outcome of those discussions I will reserve for a future post, because I will probably need assistance.

That is why I decided that I am not going to build packages for the upcoming KDE 4.9-rc2. I will wait for the final release of 4.9.0 instead.

I will try to get LibreOffice packages compiled for the 3.5.5 release which was announced today. It depends on the errors I encounter during compilation… I do not have time to hunt compilation issues down and fix them. So, fingers crossed!

End of rant.

Eric

Using SQLite for this blog

Just to let you know, I created a permanent page (as opposed to a blog article) called “PDO Powered“. You’ll find it in the left sidebar of the blog – right below the link to my  “About” page.

A few posts back when I wrote about a blog upgrade where I finally fixed my database tables and my performance issues, someone asked me if it were possible  that I create a pre-configured empty blog using SQLite. The reason being that it is no longer possible to configure a SQLite backend if you start off with the most recent version of WordPress.

The instruction set on my new page is meant to show you how to do that yourself. I also added a link to a tarball containing such a pre-configured blog so that you can use that too as a bootstrap for your own portable blog.

If you used my instructions or the tarball, it would be nice if you add a link to your blog in the comments section of the “PDO Powered” page (I will check for SPAM attempts!). Perhaps if enough independent blogs show up using SQLite, the WordPress developers will reconsider their point of view (they do not care for other database backends except MySQL).

Eric

Dumping google toolbar

Well, I guess it is time to dump good old Google Toolbar.

In a previous post of mine, I showed you how to allow Firefox to keep using the Google Toolbar even though it lists as “unsupported” since firefox-5. But this is not a long-term option of course – at some point the plugin will become incompatible because it is no longer being developed and it will de-stabilize my browser.

So I was thinking, what are the reasons why I wanted to stick with the Google toolbar for so long? The plugin has some great features which I really don’t want to miss. Let me list them here, along with ways to get the same or similar functionality in Firefox but without using the Google Toolbar.

  1. Search through my search history. I guess this is is the feature I use most. Of course, Firefox keeps an accessible history of the URLs you visited, but re-using previous search phrases is something different. The Google Toolbar showed your entire search history in a neat dropdown. But this functionality is also present in Firefox’s own search field… I just never knew. If you type a single space character into the search entry field, then Firefox will display a dropdown with all your previous search phrases.
  2. Translate web pages. Using this a lot as well, to find out what those damn Russians are telling about Slackware… but there are other plugins that add the same functionality to your right-click context menu in Firefox. One that seems to get the best reviews because of its feature set is gTranslate. One disadvantage compared to the googlebar is, that it does not give me the option to translate a complete web page, it is limited to translating selected bits of text.
  3. Bookmark sync. When you work on many different computers and want your bookmarks available everywhere, then Google Toolbar woould let you. However, Firefox has its own “sync” functionality since version 4 which allows you to sync your bookmarks, history and other stuff to a central server, much like Google does too. And if you do not want to rely on 3rd party servers you can always setup your own private bookmark server like I did, using SiteBar. A killer feature of SiteBar is that it has ACLs (access control lists) allowing users of the service to share (parts of) their bookmarks with other users or groups.
  4. Use highlighted text to search in Google. It is so convenient to just highlight a piece of text and then right-click to use that text as a search phrase in Google. It is a must-have feature for me, but luckily there is an add-on called Context Search which will even expand the list of selectable search engines to beyond just Google.

Well that was not all that many reasons for needing the Google Toolbar, but even then: their value is high because of the way they allow me to be more productive and efficient in my work. I guess I will have to give the alternatives a try and see if I can live without the Google Toolbar. Realizing that I have to, I can only say “so long, and thanks for all the fish” to the people who have been developing this plugin over the years.

While I am at it, I think I am also going to try out Right-Click-Link (opening URLs in a new tab that are listed in a page as plain text), which seem to be useful as well.

Eric

« Older posts Newer posts »

© 2024 Alien Pastures

Theme by Anders NorenUp ↑