Updated my Nexus one to Gingerbread

February 27th, 2011

Google has finally released Gingerbread (Android 2.3.3) for the Nexus one mobile phone. Until the rollout via OTA (Over the Air) will be completed, it will take a few weeks.

I was not willing to wait for such a long time.

So, I just downloaded the image from Google and updated my phone manually.

    Steps needed:

  • Download the image from here
  • Rename the image file to update.zip and copy it to your phone SD card’s root
  • Shut down you phone
  • Press the trackball while powering on the phone
  • Select bootloader (use the volume keys to navigate) and press the power button again
  • When the exclamation mark show up on the screen hold down the power key and then press volume up
  • Navigate to Apply sdcard:update.zip and confirm the action by pressing the track ball
  • Reboot after successfully update your Android to 2.3.3

Benefits of Gingerbread for the Nexus one

  • The overall-speed has been improved, it feels much more snappy now
  • Re-worked user interface. The UI is now much darker than before and has some nice effects like the “glowing” when reaching the top or bottom of a list. A cool eye-candy appears when locking the screen.
  • Improved virtual keyboard. Its is more comfortable than the old versions

Googles definition of “soon”
Google was announcing the availability of the Android 2.3 SDK on early December last year. On December, 20t, Google promised to release Gingerbread for the Nexus One in the “coming weeks”. Later on, rumours that it will be released during the “Mobile World Congress” on Barcelona, Spain have proven wrong.

Since the announcement of Gingerbread to the OTA roll-out to the Nexus One, we had to wait for almost three months. What kept Google back to release it earlier?

Hopefully we do not need to wait such a long time for “Ice Cream” (Android version 4?).

Conclusion
It was worth to buy a Google phone. Its is already the second major version that hit my phone. Other phone manufacturers do either not release any update or roll them out with a delay of a few months.

Have fun!

Share and Enjoy:
  • Twitter
  • Facebook
  • Slashdot
  • del.icio.us
  • Technorati
  • Digg
  • Google Bookmarks
  • Add to favorites
  • MisterWong
  • Reddit
  • Yahoo! Buzz
  • BlinkList
  • Mixx

Updated my blog from WordPress 3.x to 3.1

February 24th, 2011

One sentence: It is working as expected :-)

Share and Enjoy:
  • Twitter
  • Facebook
  • Slashdot
  • del.icio.us
  • Technorati
  • Digg
  • Google Bookmarks
  • Add to favorites
  • MisterWong
  • Reddit
  • Yahoo! Buzz
  • BlinkList
  • Mixx

RHEL6.1 and Red Hat is changing its subscription methods

February 16th, 2011

I just got an email with the subject “Opportunity for Red Hat Certified Professionals to test new Red Hat software”.

Quoting the email:

" The new subscription management tools provide a very different user
   experience than today’s Red Hat Network (RHN). We would like to get
   your feedback on the software so that we can improve the tooling before
   RHEL 6.1 is released. As part of this Beta Program, we will be offering
   you a beta version Red Hat Enterprise Linux Personal Subscription. This
   subscription will allow you to access the tooling that will be provided
   as part of the RHEL 6.1 minor release."

In the same email Red Hat offers the audience to have up to 10 systems registered for free:

  "Under  the Personal Subscription provided via the Beta Program, users are able
   to deploy the software on up to 10 personal systems. The Red Hat
   Personal Subscriptions entitle you to access software and software
   updates"

That are actually great news for us as Red Hat certified professionals. But it also opens new questions about the future of RHN, the RHN Satellite and the subscription model of Red Hat in general.

According to the documentation (You need to be at least RHCE and provide your RHCE number to get access to it), with RHEL6.1 registering systems to the RHN will completely change. No more rhn-register it is now the CLI command subscription-manager.

The most important thing that changed is that the username and password of RHN needs to be transmitted just once, afterwards you will get identified by a X509 client certificate.

The only drawback I’ve found was that the command to register a consumer needs to provide the password in clear text on the command line.

And for Satellite users?
As far as I can see, nothing changes, Satellite users can still provision the systems with activation keys, it is still channel based, not product based.

For enterprise users nothing is changing in the next time, the new entitlement and subscription method does only apply to does users NOT using a Satellite server, at least for now and for RHEL6.1.

The Readme also mentions RHN Satellte 5.5 which is not (yet) released. It is quite unclear what is expecting us with Satellite 5.5.

Reading some bugzilla entries, it is clear that there is still some time until RHN Satellite 5.5. will hit the road.

Please: A public Beta for RHN Satellite 5.5
Please Red Hat, provide a public, or at least a semi-public beta (like for RHEL6.1) release, to give your enterprise customers a chance to do the Q&A which was missing on the release of RHN Satellite 5.4.

Having fun? I do actually not care about RHN Network, I’m a Satellite user. Personally I’m having fun with my 10 personal RHEL6.1 subscriptions for free, it allows me to do lots of tests before putting RHEL6.1 into production.

Share and Enjoy:
  • Twitter
  • Facebook
  • Slashdot
  • del.icio.us
  • Technorati
  • Digg
  • Google Bookmarks
  • Add to favorites
  • MisterWong
  • Reddit
  • Yahoo! Buzz
  • BlinkList
  • Mixx

RHEL 4.9 released

February 16th, 2011

Today, Red Hat released its “service pack” or “maintenance release” of RHEL4. According to Red Hats life cycle policy” it ends the production stage two.

That means: In future only bugs with a high severity will be fixed. The “normal” life cycle of RHEL4 will end in approx. one year.

This means that everyone using RHEL4 systems should think about a migration scenario to RHEL6. Unfortunately, Red Hat does not support OS upgrades, you need to install the systems from scratch. Since RHEL4 was released in February 2005, most of this systems have reached there lifecycle anyway.

Its time to migrate your RHEL4 systems.

For the release notes, please see http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/4/html/4.9_Release_Notes/index.html

Have fun with migrating….

Share and Enjoy:
  • Twitter
  • Facebook
  • Slashdot
  • del.icio.us
  • Technorati
  • Digg
  • Google Bookmarks
  • Add to favorites
  • MisterWong
  • Reddit
  • Yahoo! Buzz
  • BlinkList
  • Mixx

CentOS6 to be released in the next few weeks

February 16th, 2011

According to an interview with Karanbir Singh – a major contributor to the project – it is just a question of a few weeks until we can expect CentOS6 to be released.

CentOS is extremely important for the RHEL community, it is a playground for trying out new stuff before getting into an engineering phase with the Red Hat supported RHEL.

Lets have fun with it…

Share and Enjoy:
  • Twitter
  • Facebook
  • Slashdot
  • del.icio.us
  • Technorati
  • Digg
  • Google Bookmarks
  • Add to favorites
  • MisterWong
  • Reddit
  • Yahoo! Buzz
  • BlinkList
  • Mixx

RHEL 5.6 is released

January 12th, 2011

Today Red Hat has released RHEL5.6 after a beta period of ~2 months. There is no official announcement (yet), so the release highlights are unknown. Probably they are the same like the beta version.

Have fun!

Share and Enjoy:
  • Twitter
  • Facebook
  • Slashdot
  • del.icio.us
  • Technorati
  • Digg
  • Google Bookmarks
  • Add to favorites
  • MisterWong
  • Reddit
  • Yahoo! Buzz
  • BlinkList
  • Mixx

Epson scanners on Linux systems

January 11th, 2011

I’ve got a Epson Perfection 1260 Photo scanner.

Fedora like other distributions such as OpenSuse are recognizing the device since a long long time. The back end chosen for the device is plustek.

Unfortunately when using the default configuration one experience very strange effects with colours. The left and the right 50% of the picture have a colored background, even when scanning a empty page.

I had this problem with OpenSUSE since years and still got it with Fedora 1x. Since I only need the scanner for my yearly income tax declaration, I always forget about what I needed to change.

That’s what is needed to change:

Solution

[root@bond ~]# diff /etc/sane.d/plustek.conf.orig /etc/sane.d/plustek.conf
100c100
< option altCalibration 0
---
> option altCalibration 1
[root@bond ~]#

Since I do not have any other scanners I do not know if this is a bug specifically to this type of scanners, or if it is a general bug.

Using different search engines, the web does not disclose some solutions. That is one of the reasons why I’m blogging about it. The other reason is to find other people with the same problem.

At the end of the day, I’ll try to find out if this is a general bug of the Sane back end, or just specific to some Epson scanners. If it is specific to some Epson scanners, it may be worth to create a new specific back end for those scanners affected.

Having fun? Now I have, my stuff is successfully scanned.

Share and Enjoy:
  • Twitter
  • Facebook
  • Slashdot
  • del.icio.us
  • Technorati
  • Digg
  • Google Bookmarks
  • Add to favorites
  • MisterWong
  • Reddit
  • Yahoo! Buzz
  • BlinkList
  • Mixx

Spice and RHEV, a RHCE goes MCSE

January 11th, 2011

I’m currently working in a project which includes some virtual Linux desktops. The desktop of choice is RHEL6.

How to bring a Linux desktop via WAN to a thin client? VNC -> are you nuts? Remote X11 over SSH -> WAN = no go. NX -> another vendor involved. SPICE -> Spicy! But: Spice over WAN? To be tested…

SPICE is the protocol used by RHEV (Red Hat Enterprise Virtualization). Some time ago I had the chance to test this stuff @Red Hat in Munich. The experience was nice, it is comparable to vSphere, but it only works with MS Internet explorer due to ActiveX and .Net stuff.

The management software needs to be installed on a Windows 2008R2 server. The database to be used is – you guess it – MS SQL. Users are authenticated either by Active Directory (Not generic LDAP!) or local Windows Users. Holy cow!

At first, when I got this product presented by Red Hat I was LOL. Now, it seems that I need to refresh my Windows knowledge because it seems to be the only product capable to provide enterprise ready Linux desktop virtualization. I’m crying :-(

At least the hypervisor used is not MS HyperV, it is KVM based on RHEL5, to replaced with RHEL6 in the future.

There is some light at the end of the tunnel: Red Hat is working on a replacement of the Windows-bound stuff. It will be replaced with some JBOSS and Java stuff. The database will probably be PostgreSQL. It will take some time to develop it before it will be ready for production.

Since Red Hat is opensourcing all (or most) of its products, it would be great to get in touch with the upstream project (release early, release often).

In meantime I need to build up knowledge about Windows Server 2008R2, Active Directory, MS SQL Server and DotNet.

Having fun?

Share and Enjoy:
  • Twitter
  • Facebook
  • Slashdot
  • del.icio.us
  • Technorati
  • Digg
  • Google Bookmarks
  • Add to favorites
  • MisterWong
  • Reddit
  • Yahoo! Buzz
  • BlinkList
  • Mixx

Some impressive figures about Spacewalk and my two cents

December 22nd, 2010

Today, I saw a interessing post on the spacewalk-devel mailing list.

Lines of code
Spacewalk has 2,908,841 lines of code, created in estimated 843 person years. This means 843 developers are needed to rewrite Spacewalk from scratch in one year! That’s amazing.

Number of bugs fixed
As stated in the post, the Spacewalk-team fixed 1012 bugs in the year 2010. Some 1061 bugs are still due to be solved, the Spacewalk-team will not running out of work in 2011. See RHN Satellite bugs and Spacewalk bugs.

Contributions from outside Red Hat
96% of the contributions are from Red Hat people. Looks like my small contribution to the German translation is just about 0.0000001% ;-) . Seriously: This should be improved. More people outside of Red Hat should contribute. How? A good way can be a better support for Debian based distributions as well as for SLES/OpenSUSE and other distributions. I think this would attracting more Red Hat outsiders.

Another important thing: Instead of mailing list posts, Fedora should release its advisories similar to Red Hat. This would enable people to have the errata in its Spacewalk servers. This would lead into more people interested in Spacewalk in the Fedora community.

Communications
The IRC communication stats can somehow be a bit problematic. Is it really needed to log all IRC traffic? Its was stated that 24.1% have been questions, the mail list post also disclosed which are the most aggressive persons and so on. Privacy? For myself: I’m probably going to change my real name nick to something else…

Missing numbers
It would be interesting how many people are subscribed to the spacewalk and spacewalk-devel mailing lists and the number of posts to these lists.

Major achievements in 2010
This is just my point of view…

- PostgreSQL support reached a point where it is ready for broad testing.
- spacewalk-repo-sync allows to directly sync with yum repos.
- Staging of content
- Support for eliminating duplicate system profiles
- Performance improvements (felt, not measured)

Did I had fun this year?
I had a lot of fun with Spacewalk, for sure. I did not challenged Spacewalk with all the stuff that I need @work with the RHN Satellite.

Will I have fun in 2011?
With Spacewalk of course, it is a cool project. If the Fedora project decides to publish Spacewalk-like erratas I’m pretty sure that France will have a problem to produce the amount of Champagne needed. If it comes down to the RHN Satellite: Due to severe bugs, I only can manage RHEL6 systems with some workarounds but I am confident that this will change soon.

In short: Yes I’ll having fun :-)

Share and Enjoy:
  • Twitter
  • Facebook
  • Slashdot
  • del.icio.us
  • Technorati
  • Digg
  • Google Bookmarks
  • Add to favorites
  • MisterWong
  • Reddit
  • Yahoo! Buzz
  • BlinkList
  • Mixx

Important RHN Satellite 5.4 bugs has been fixed

December 15th, 2010

Red Hat recently released some bugfixes for the RHN-Satellite version 5.4. They needed approx. one month to develop a fix for those serious bugs.

If you upgraded to sat540 before those bugsfixes have been released you will have a crippled database. The errata provides a way how to fix it. It needs some time, but it works perfectly. For “my” satellites it was taking about 48h for both satellites, about 12h for the master and 36h for the slave satellite.

This time, Red Hat’s QA also made a good job, it is now working like expected. The developers had a hard time too, according to the git log they worked on weekends too.

If you are new to sat540 or upgrading to it, please ensure that you do NOT take any action before applying the errara!

Have fun! (This time REALLY for sure)

Share and Enjoy:
  • Twitter
  • Facebook
  • Slashdot
  • del.icio.us
  • Technorati
  • Digg
  • Google Bookmarks
  • Add to favorites
  • MisterWong
  • Reddit
  • Yahoo! Buzz
  • BlinkList
  • Mixx