Technology news and Jobs 
Our Blogs Open Sauce Was it Automatix or bad RAM that killed Ubuntu?
Our Blogs Open Sauce Was it Automatix or bad RAM that killed Ubuntu? | Was it Automatix or bad RAM that killed Ubuntu? |
|
|
| by Sam Varghese | |
| Friday, 23 November 2007 | |
|
Page 1 of 2 This came to light when Stan sent his box back to his system-builder to get an additional hard drive installed, the idea being to run Windows and Linux as a dual-boot system on separate drives. However, that does not exactly exonerate Automatix altogether because the software does cause some pretty weird behaviour on a Ubuntu 7.10 installation, judging from my own testing. I have Ubuntu 7.10 running on a PC built from old bits and pices - an Asus A7N8X motherboard, a AMD XP 2600 processor, a bog standard GeFORCE video card, an 80GB WD drive and 2 GB of RAM. Yes, it's not exactly downmarket even though I say old bits and pieces! After writing my last piece, I decided to walk into the lion's den myself and installed Automatix 2 on this box, using the instructions from the developers' website. That bit went okay, which is more than I can say for what happened later. Automatix is defined as "a free graphical package manager for the installation, uninstallation and configuration of the most commonly requested applications in Debian based Linux operating systems." One can install the following using Automatix: (once again this is taken from the offcial website): Acrobat Reader, Swiftweasel Browser & Plugins, Swiftdove, Extra Fonts (including MS Fonts, Liberation Fonts), Skype, Google Earth, dvdrip, Firefox MPlayer Plugin, Totem Xine, Google Picasa, Wine, w32dvdcodecs, nautilus scripts, Sun Java 6 JRE/JDK, Openoffice Clipart, xdvdshrink, checkgmail, Songbird, Crossover Office Standard 6.1.0, Crossover Office Professional 6.1.0, Devessentials, and Microsoft Office Open XML Converter. A few other applications are to be added shortly. I started Automatix and selected the w32dvdcodecs, extra fonts, dvdrip, Acrobat Reader and the Firefox MPlayer plugin. But after starting the process of applying these updates, I saw a message that some dependencies could not be met as some packages - which it listed - were missing. (This is the first time I have used a package manager on a Debian-based system and found that it will not do its basic task - which is to resolve dependencies and install the software I want.) |
| < Next story in category | Previous story in the category > |
|---|
