As posted to the openSUSE-GNOME Mailing List.

Thanks to all who showed up to help on the bug day on
Friday, your efforts are greatly appreciated.

We started with just over 70 bugs and left the *obby
session available over the weekend.  By the end of the
weekend, we had reviewed 14 bugs (9 of which we closed).

These were all Critical and Major bugs listed for openSUSE
11.1.

I will be closing the *obby session this afternoon at about
1700 CDT.

Thanks again!
–
Christopher M. Hobbs [chobbs@siloamsprings.com]
Network Administrator, City of Siloam Springs

PSA sent to opensuse-gnome@opensuse.org, opensuse-project@opensuse.org, opensuse-announce@opensuse.org

Please join us for the openSUSE-GNOME BugDay code named “Community Effort” tomorrow
(Friday 14 MAY 2009) at 1100EDT/1500UTC.

We’ll be squashing blocker, critical, and major bugs in 11.1 related to GNOME.

More information can be found on the wiki:
http://en.opensuse.org/GNOME/BugDays/20090514

A Gobby session will be announced at the beginning of the meeting to assign/close
bugs. Should you have any questions, feel free to ask in #openSUSE-GNOME on Freenode,
or email me directly.

We hope to see you there!
–
Christopher M. Hobbs [chobbs@siloamsprings.com]
Network Administrator, City of Siloam Springs

Roll up those sleeves and mark your calendars, because here comes another BugDay!

During Community Week (http://en.opensuse.org/CommunityWeek), I’ll be hosting another openSUSE-GNOME BugDay on Fri, 15 MAY 2009. We’ll start promptly at 1000 CDT and will continue until 1600 CDT. I will be around very early in the day to start prep for the meeting should you have any questions.

We’ll conduct business in #opensuse-gnome on Freenode (irc.freenode.net). I will establish a Gobby session as I’ve done in the past, and we’ll work off of that.

Can’t wait to see you there!

This was a bit of a bear, but I’ve inhereted a generic looking USB EVDO stick at the office. After some research and elbow grease, I’ve managed to get it working. In this post, I’ll detail EVDO configuration under SLED 10. I’ll leave out most of the gory technical details as others have covered that for me. I’ll link to the appropriate reference where necessary.

(more…)

So you just got an HP Mini-Note 2133 pre-loaded with SLED 10?  Great, right?

Well…  It’s not been so great for a lot of people.  It seems that HP simply put this laptop together, half-assed a SLED load and sent it out into the wild.  I’ve had a ton of problems with it, the two major ones being that I couldn’t register the machine with the Novell Customer Center (not even with my site license) it ships with a non-working wireless card.

My wifi fix was simple, buy a new usb wifi dongle…  Registration, however, was a little easier to fix (after some wailing, gnashing of teeth, and chat in #opensuse-GNOME… thanks captiain_magnus!).

If you attempt to use YaST to register you copy of SLED on the 2133, you’ll be re-directed to a “special” Novell Customer Center login.  It’s a little different than the normal one in that it wants an HP license, not any other SLED license you may have.  The biggest difference, however, is that it’s broke.  It simply refreshes the page when you click submit and sends nothing to Novell.

They’re pretty sneaky about hiding your license number as well.  It happens to be on your restore DVD.  It’s located on the right hand side below the HP logo and the “2133″ text.  It’s in a series something like NNNNNN-XNN, where N’s are numbers and X is some letter.

To get around the registration bug, have your license number handy and fire up your terminal.  Use ’sudo’ or just ’su to root and issue the following command:

suse_register -n -a serial-hp=NNNNNN-XNN

Where “NNNNNN-XNN” is your registration code.  Sit back and wait, it took almost 20 minutes for this command to finish for me and you’ll receive absolutely no indication that it’s functioning.  Once it’s done, you’ll simply be returned to your prompt.  Fire up YaST or your favorite terminal emulator and check your repositories.  You should now have a Novell repository added.

Enjoy!

Please join us for the GNOME Team meeting in #openSUSE-GNOME on
irc.freenode.net.

The current agenda can be found here:
http://en.opensuse.org/GNOME/Meetings/20090205

For time conversions, please see:
http://www.timeanddate.com/worldclock/fixedtime.html?day=22&month=1&year=2009&hour=22&min=0&sec=0&p1=0

Thanks!

There’s been some discussion about Rails on openSUSE recently, so I thought I’d add to my Ruby articles with a Rails installation guide.

Getting started with Rails on openSUSE is a breeze.  In this particular article, I’ll quickly outline installation and startup of Rails on openSUSE 11.1.  You’ll need to install Ruby, ruby-sqlite, and ruby gems.  I’ve detailed these in my previous articles on ruby.

(more…)

As per the request of Andrew Wafaa, I thought I’d set up a quick guide to how I got teaming running on SLES.  The documentation for Teaming on the administrative end was relatively sparse, but the installation guide was sufficient for most purposes.

Read on to learn more about Teaming and SLES…

(more…)

Welcome to yet another installment of our Ruby mini-series.  Capistrano (http://capify.org/) is a DSL written in Ruby for automating common tasks.  While Capistrano is more often used for Rails deployment, it can easily be used for system automation as well.

A while back, I put together a presentation for the local Ruby user’s group.  The presentation covers a very brief intro to Capistrano for simple system automation.  You can download it here.  I’m aware of at least one typo (a missing single quote) in the slides, there may be others.

Rather than repeat myself here, I’ll let the PDF do the talking.  For the official documentation, see http://capify.org/getting-started

So here we are, the second installment of my openSUSE+Ruby mini-series.  See this link for the first article covering installation and configuration.  In this post, I’ll give you a fast introduction to Ruby and a sample system script on openSUSE.

(more…)