Language Selection

English French German Italian Portuguese Spanish

Reviewing OpenLab myself

Filed under
Linux
Reviews

[A regular at] TuxMachines.org has asked me [the lead developer] to do my own review of OpenLab, I won't deny that it feels rather odd to be doing so. After all, I am obviously biassed. But the request does justify the idea very well, so I reckoned I would give it my best bash. I'm not going to try to be dispassionate - any attempt at that is unlikely to completel succeed anyway, but more than that it would feel dishonest. So rather, I will try to explain how we were thinking at various stages of the system, what motivated certain decisions over others and what is really happening sometimes. Such a review will actually be usefull to people trying to make a decision, without being either too much like false marketing or too modest.

So let's start at the beginning, the CD-bootup screen. This screen has drawn praise from other reviewers as it shows one of the things we spent the most time on - trying to be explanatory at all times and give newbies an easy point of departure with lots of help and tips. We did do that but it's not all you can say about this screen. The text color there actually needs a bit of work, this is already on the list for next time, the colour we chose is nice but on some screens hard to see. A bigger thing is that since you cannot test on all pieces of hardware, I really wish I could rewrite the troubleshooting page now - as I now know two more entries that I wish I had known about when we first wrote that.

One little thing here that I'm very proud off is that if you do need to follow any of the troubleshooting things to boot the LIVEcd, and you then install - OpenLab will automatically make sure your troubleshooting lines are in your lilo.conf file so that you won't need to worry about adding them later.

Full Review.

about openlab

it was quite interesting to read a review from developer's own perspective - this was a good idea! However there are still a few questions none of the reviews I've seen so far addressed, for example:

- what is the state of multi-media apps and codecs in openlab? For example, will it play mp3s, avi's etc out of the box, or does it follow the big names in not including these apps and codecs? I realise the focus of openlab was on education market first of all, but I do consider multimedia applications and codecs they depend on an essential part of my system, and I'm becoming increasingly unhappy about having to install them myself...

- what tools does openlab offer to keep the system up to date or install additional software?

- how compatible is openlab with Slackware 10.2?

- what about installing binary nvidia/ati drivers?

Finally, I have to comment on your decision to 'not explicitely give the option to install lilo in a partition rather than an MBR...' While I understand your desire to simplify the installation, unfortunately it makes life very difficult for those of us who are multi-booting several systems, already have a perfectly functioning bootloader, and do not want to replace it or mess with it in any way! We might be few, but we are the early adopters, and writers of the reviews... Smile
So I think an 'advanced' option would be useful, and hopefully not too confusing for those who don't need it.

Re: About OpenLab

Let me try to answer your questions.

- what is the state of multi-media apps and codecs in openlab? For example, will it play mp3s, avi's etc out of the box, or does it follow the big names in not including these apps and codecs? I realise the focus of openlab was on education market first of all, but I do consider multimedia applications and codecs they depend on an essential part of my system, and I'm becoming increasingly unhappy about having to install them myself...

*Well one advantage of developing in South Africa is that we are not subject to US patent laws, so we can and do include every codec with a license that allows redistribution. OpenLab is meant to be free software except where important things simply do not have viable replacements (yet). So three non-free things are include. Java JRE, Flash plugin and windows multimedia codecs. We ship with totem as default video player, enabled for all the codecs I have encountered, and mplayer is in there as a fallback as well.

- what tools does openlab offer to keep the system up to date or install additional software?

*OpenLab uses slapt-get and gslapt for this. Our default package sources are all fully dependency tracked and this makes for quite an easy to use update system which we work hard to keep up to date.

-how compatible is openlab with Slackware 10.2?

*100% compatible, but I need to qualify that. Out of the box, a large number of 10.2 packages will complain about missing dependencies this was caused by slackware 10.2 being released after we did, on our update mirror however (which is preconfigured in OpenLab), has been an updated and installable elflibs package for some time, if you install it, you will instantly be able to install any slackware 10.2 package you wish again or even do a dist-uprade.

- what about installing binary nvidia/ati drivers?
I am an nvidia user myself so firstly let me assure you they do work.
That said we did not wish to ship non-free drivers in the base system, so the Nvidia drivers specifically is shipped on the KARMAcd, that package is self-installing and largely self-configuring as well.
To install the package from nvidia.com you will obviously need the kernel sources, which if you don't purchase the disk set you will need to install yourself.You don't need to configure it though, you can get the .config file from /proc/config.gz

As to the lilo locations, in fact the advanced options are already in front of you, it is just not explicitely said on screen. All the drop-down menu's in the OpenLab installer are editable so that if at any point our detected lists were wrong (which I have never seen happen) you could enter a corrected value yourself. In the same way when the lilo install screen come up, if you type /dev/hda1 as an option it will install to the partition rather than the MBR.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: Gaming

Leftovers: Software

  • Hyper Is a Terminal Emulator Built Using Web Technologies
    A lot of us use the terminal on Ubuntu, typically from an app like GNOME Terminal, Xterm or an app like Guake. But did you know that there’s an JS/HTML/CSS Terminal? It’s called Hyper (formerly/also known as HyperTerm, though it has no relation to the Windows terminal of the same/similar name) and, usefulness aside, it’s certainl a novel proof-of-concept. “The goal of the project,” according to the official website, “is to create a beautiful and extensible experience for command-line interface users, built on open web standards.”
  • Little Kids Having Fun With “Terminal Train” In Ubuntu Linux
    Linux is often stereotyped as the operating system for tech savvy users and developers. However, there are some fun Linux commands that one can use in spare time. A small utility named sl can be installed in Linux to play with the Terminal Train.
  • This Cool 8-Bit Desktop Wallpaper Changes Throughout The Day
    Do you want a dynamic desktop wallpaper that changes throughout the day and looks like the sort of environment you’d be able to catchPokemon in? If so, check out Bit Day wallpapers. Created by Redditor user ~BloodyMarvelous, Bit Day is a collection of 12 high-resolution pixel art wallpapers.
  • This Script Sets Wallpapers from Imgur As Your Desktop Background
    Pyckground is a simple python script that can fetch a new desktop background on the Cinnamon desktop from any Imgur gallery you want. I came across it while doing a bit of background on the Bit Day wallpaper pack, and though it was nifty enough to be of use to some of you. So how does it work?
  • Productivity++
    In keeping with tradition of LTS aftermaths, the upcoming Plasma 5.9 release – the next feature release after our first Long Term Support Edition – will be packed with lots of goodies to help you get even more productive with Plasma!
  • Core Apps Hackfest 2016: report
    I spent last weekend at the Core Apps Hackfest in Berlin. The agenda was to work on GNOME’s core applications: Documents, Files, Music, Photos, Videos, Usage, etc.; to raise their overall standard and to make them push beyond the limits of the framework. There were 19 of us and among us we covered a wide range of modules and areas of expertise. I spent most of my time on the plumbing necessary for Documents and Photos to use GtkFlowBox and GtkListBox. The innards of Photos had already been overhauled to reduce its dependency on GtkTreeModel. Going into the hackfest we were sorely lacking a widget that had all the bells and whistles we need — the idiomatic GNOME 3 selection mode, and seamlessly switching between a list and grid view. So, this is where I decided to focus my energy. As a result, we now have a work-in-progress GdMainBox widget in libgd to replace the old GtkIconView/GtkTreeView-based GdMainView.

Leftovers: OSS and Sharing

  • Did Amazon Just Kill Open Source?
    Back in the days, we used to focus on creating modular architectures. We had standard wire protocols like NFS, RPC, etc. and standard API layers like BSD, POSIX, etc. Those were fun days. You could buy products from different vendors, they actually worked well together and were interchangeable. There were always open source implementations of the standard, but people could also build commercial variations to extend functionality or durability. The most successful open source project is Linux. We tend to forget it has very strict APIs and layers. New kernel implementations must often be backed by official standards (USB, SCSI…). Open source and commercial implementations live happily side by side in Linux. If we contrast Linux with the state of open source today, we see so many implementations which overlap. Take the big data eco-systems as an example: in most cases there are no standard APIs, or layers, not to mention standard wire protocols. Projects are not interchangeable, causing a much worse lock-in than when using commercial products which conform to a common standard.
  • Firebird 3 by default in LibreOffice 5.4 (Base)
    Lots of missing features & big bugs were fixed recently . All of the blockers that were initially mentioned on tracking bug are now fixed.
  • Linux & Open Source News Of The Week — Comma.ai, Patches For Firefox and Tor, And OSS-Fuzz
  • Open Source Malaria helps students with proof of concept toxoplasmosis pill
    A team of Australian student researchers at Sydney Grammar School has managed to recreate the formula for Daraprim, the drug made (in)famous by the actions of Turing Pharmaceuticals last year when it increased the price substantially per pill. According to Futurism, the undertaking was helped along by an, “online research-sharing platform called Open Source Malaria [OSM], which aims to use publicly available drugs and medical techniques to treat malaria.” The students’ pill passed a battery of tests for purity, and ultimately cost $2 using different, more readily available components. It shows the potential of the platform, which has said elsewhere there is, “enormous potential to crowdsource new potential medicines efficiently.” Although Daraprim is already around, that it could be synthesized relatively easily without the same materials as usual is a good sign for OSM.
  • Growing the Duke University eNable chapter
    We started the Duke University eNable chapter with the simple mission of providing amputees in the Durham area of North Carolina with alternative prostheses, free of cost. Our chapter is a completely student-run organization that aims to connect amputees with 3D printed prosthetic devices. We are partnered with the Enable Community Foundation (ECF), a non-profit prosthetics organization that works with prosthetists to design and fit 3D printed prosthetic devices on amputees who are in underserved communities. As an official ECF University Chapter, we represent the organization in recipient outreach, and utilize their open sourced designs for prosthetic devices.

today's howtos