Re: Canonical recommends against using 64-bit Ubuntu

July 19, 2010 at 1:08 pm (64-bit operating systems (OS), Adobe Flash, Desktop, Linux) (, , , , , , )

The Canonical’s recommendation is not appropriate and expedient but it’s generally correct.

Every desktop-oriented (Linux) user uses Mozilla Firefox and Adobe Flash. And Adobe Flash is not supported on 64-bit systems (neither Linux-based, nor Mac OS)  so it has to be emulated through wrappers in order to function.

Well, ADOBE FLASH is a piece of software of controversial quality on 32-bit systems. However, on 64-bit systems its utilization is even EXTREMELY DISTURBING (often buggy) experience.

I’ve an Intel Core 2 Duo T7200 (2 x 2 GHz) dual-core 64-bit processor and nevertheless, I DOWNGRADED to the 32-bit Ubuntu version. And I really did NOT WANT to do so. However, I’m a true desktop-oriented only user. I use Firefox and review Flash content more often than not.

I believe that there should be a different message pointing out why the 64-bit Ubuntu is not fine for desktop use. There should be a notice that Adobe Flash does not provide 64-bit support and that’s the main reason why the whole 64-bit Linux is not recommended FOR DESKTOP USE.

To sum up, we, the Ubuntu developers and contributors, complain about the poor Adobe Flash quality but we does not STATE IT CLEARLY. However, this is the right way to make Adobe Systems Incorporated (“Adobe”) reconsider its politics concerning the Linux world.

Come on Canonical, come on Ubuntu! Come on Linux contributors! DO NOT BE AFRAID!
Let we show the people around the world how deep the Rabbit hole really goes.


Permalink Leave a Comment

I want to address the boot loader problem in Ubuntu 9.10 (Karmic), and 10.04 LTS (Lucid) and 10.10 (Maverick)

April 12, 2010 at 6:00 pm (Linux) (, , , , , , , , )

In Ubuntu Linux version 9.10 (Karmic Koala) and above there is one major downfall and it is connected with the new buggy GRUB2 operation system boot loader.

This how-to is for all the people which have already faced this serious problem and were left with corrupted Master Boot Record and in this sense useless unbootable system.

Firstly, you need to add these lines in your ‘sources.list’ file and it should go like this:

1. Open a terminal and write:
sudo nano /etc/apt/sources.list

2. Add these lines at the end of the file (after these lines there should be one empty line at the end of the file so add the lines and just hit enter once):

a) for Karmic Koala (9.10):

deb karmic main
deb-src karmic main

b) for Lucid Lynx (10.04):

deb lucid main
deb-src lucid main

c) for Maverick Meerkat (10.10):

deb maverick main
deb-src maverick main

Then hit “Ctrl+O” to save the file and “Ctrl+X” to exit the program.

Secondly, import the repository key signature (as normal user that is to say without “sudo” in the beginning of the commands below):

gpg --keyserver --recv 55708F1EE06803C5
gpg --export --armor 55708F1EE06803C5 | sudo apt-key add -

Thirdly, install BURG and the related themes using these commands (with root privileges):

sudo apt-get update
sudo apt-get install burg

And finally, install BURG to MBR with the following command (with root privileges again):

sudo burg-install "(hd0)"

or I highly recommend using the next command instead  (because the GRUB2 bug still occurs on my system if the first command is used):

sudo burg-install –alt “(hd0)”

(You should have in mind that there are two dashes before “alt” and (hd0) is surrounded by standard inverted commas)

Change hd0 if you want to install to other disk.

This workaround was proposed to me by one of the main developers of BURG. And it really works! Thanks, bean!

* Works perfectly on Ubuntu 9.10 (Karmic Koala) and Linux Mint 8 (Helena). There is a bug in 10.04 LTS (Lucid Lynx) Plymouth package and you may encounter some display problems (if there are such, I’ll give you a solution – just let me know).

Permalink 33 Comments