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

FoundationDB Source Code Shared

​Learn to use GitHub, ​GitHub Releases Atom 1.26

  • ​Learn to use GitHub with GitHub Learning Lab
    The most popular open-source development site in the world is GitHub. It's used by tens of millions of developers to work on over 80 million projects. It's not just a site where people use Linus Torvalds' Git open-source distributed version control system. It's also an online home for collaboration, a sandbox for testing, a launchpad for deployment, and a platform for learning new skills. The GitHub Training Team has now released an app, GitHub Learning Lab, so you can join the programming party. GitHub Learning Lab is not a tutorial or webcast. It's an app that gives you a hands-on learning experience within GitHub. According to GitHub, "Our friendly bot will take you through a series of practical, fun labs that will give you the skills you need in no time--and share helpful feedback along the way."
  • Atom 1.26
    Atom 1.26 has been released on our stable channel and includes GitHub package improvements, fuzzy-finder support for Teletype and file system watcher improvements.
  • Atom Hackable Text Editor Gets GitHub Package, Filesystem Watcher Improvements
    GitHub announced the release of the Atom 1.26 open-source and cross-platform hackable text editor for Linux, macOS, and Windows platforms with more improvements and bug fixes. In Atom 1.26, the GitHub package received various improvements and new features, among which we can mention the ability of the ’s Git pane to display a read-only list of recent commits for quick reference, and support for storing your GitHub username and password credentials in the Git authentication dialog.

Games Leftovers

Linux and Linux Foundation

  • V3D DRM Driver Steps Towards Mainline Kernel, Renamed From VC5
    The Broadcom VC5 driver stack is being renamed to V3D and developer Eric Anholt is looking at merging it into the mainline Linux kernel. The VC5 DRM/KMS and Mesa code has been for supporting the next-generation Broadcom VideoCore 5 graphics hardware that's only now beginning to appear in some devices, well, it seems one device so far. Though as I pointed out a few months back, there's already "VC6" activity going on too as the apparent successor to VC5 already being in development.
  • Azure Sphere Makes Microsoft an Arm Linux Player for IoT [Ed: Microsoft marketing at LF (only runs on/with Windows and Visual Studio etc.)]
  • Keynotes Announced for Automotive Linux Summit & OS Summit Japan [Ed: "Senior Software Engineer, Microsoft" in there; LF has once again let Microsoft infiltrate Linux events; in the words of Microsoft’s chief evangelist, “I’ve killed at least two Mac conferences. […] by injecting Microsoft content into the conference, the conference got shut down. The guy who ran it said, why am I doing this?”]
    Automotive Linux Summit connects those driving innovation in automotive Linux from the developer community with the vendors and users providing and using the code, in order to propel the future of embedded devices in the automotive arena.