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.
Archive for the ‘Documentation’ Category
Thats how I roll: Installing Ruby on Rails on openSUSE
February 5th, 2009 by Christopher HobbsThere’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.
Automatic Import Calendar news.opensuse.org > KOrganizer
January 24th, 2009 by Sascha MannsI’m very happy. Regularly i’m checkin the Calendar from news.opensuse.org for my work in OpenSUSE Weekly News. It is possible to Download the actual Calendar as *.ics File. But as i understand this, this is a Snapshot. The Calendar not updated himself regularly. So i tried this:
First of all we go to the KOrganizer. Click on the green Cross, left from the Calendararea. Add Calendar. Then we find an Menu similar this:
Then we klicking on “Filecalendar from Remote Computer” (I had translated this on the fly, i’m not shure, that it called so in english). After them we see the next Field:
In this Field i edited :”http://news.opensuse.org/?ec3_ical”. I choosed regularly updating, but no Saving on the Remote Computer.
Now we have the Community Entrys in our Calendar. We see:
If i have understood all right, we have an automatic Calendar. Have fun…
Novell Teaming on SLES
January 21st, 2009 by Christopher HobbsAs 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…
Controlling your minions with Ruby and Capistrano
January 21st, 2009 by Christopher HobbsWelcome 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
Flashrom Utility for LINUX (part1)
January 21st, 2009 by Sascha MannsThis blog entry is a little bit OffTopic. I’m writing not about an openSUSE Theme, but about
Linux. Last week i’ve chatted with the guys in #coreboot @ freenode and it was very
interesting. This article based on an collaborative PR Project from Carl-Daniel Hailfinger. This first Part of the Article presents Flashrom. The next Article presents Coreboot. The web site of that project is:
The flash utility is known as “Flashrom”.
Flashrom is a universal flash programming utility used to detect, read, erase, or write BIOS
chips (parallel, LPC, FWH and SPI technologies) in various packages (DIP, PLCC, SOIC).
It can be used to flash firmware images such as traditional BIOS or coreboot or to back up
the existing firmware.
Everybody who does not want to boot DOS or Windows just to perform a BIOS update can use
flashrom. It does not require a graphics card, monitor or keyboard and can even be used
over SSH on a remote machine. You do not have to reboot to run flashrom, but it is recommended
to reboot after a successful update. Many people are using flashrom as a replacement for
the various AMI/Award/Phoenix BIOS flashing tools out there.
Flashrom supports over 100 flash chips and it is really easy to add support for a new chip
if your board happens to have an unsupported chip.
Flashrom has its own home page: http://www.coreboot.org/Flashrom
It is free software released under the terms of the GNU General Public License version 2.
Flashrom is a “normal” user space application, but it requires superuser privileges.
Some hardened kernels (which deny access to physical memory) do not support flashrom, but
most distributions out there work fine.
Of course, the usual requirements for BIOS updates apply here as well. You should have a
stable power supply. Switching the machine off during flashing will make your machine
unbootable. Since flashrom treats BIOS files as opaque blobs, you usually do not get any
of the failover/dual BIOS features advertised on some boards.
Backup the current BIOS image into a file:
$ flashrom -r backup.bin
For other usage instructions, please refer to the flashrom home page or the man page.
In case something goes wrong, do NOT reboot, but join #coreboot @freenode and tell the
flashrom developers about it. As long as the machine is still running, there is a good
chance that everything can be fixed.
The Value of (Good) Documentation
January 16th, 2009 by Thomas SchraitleMaybe you know this situation: You find an interesting software that is worth to play. After you’ve installed it there are two possibilities: either the software is (a) very easy and self-explanatory, or (b) it is very complex.
As most software fall into category (b), one way to get used to it is you can play around and discover it by yourself. Sometimes it works, sometimes not. In case you need help, you can either ask a programmer, or write a post to a mailinglist or forum. But when you need an answer for your question now what else remains? Right! You need documentation!
And with documentation, I mean good documentation. Not something with “Documentation? Use the source!”
Using Ruby for system scripts
January 14th, 2009 by Christopher HobbsWhat’s green, red, and awesome all over?
January 10th, 2009 by Christopher HobbsopenSUSE/SLES and Ruby!
Considering that my blog no-longer exists and I’ve got a couple of topics floating around in my head, I thought I’d make use of my Lizards account and contribute something useful for once.
openSUSE has quickly become my favorite development platform and Ruby is my language of choice these days. The two together make an excellent combination and it couldn’t be easier to get started. In the next few posts, I’ll cover how I use the Ruby scripting language with SUSE on a daily basis.
That being said, lets start with installation…
RPMLINT Wiki Side overworked
January 8th, 2009 by Sascha MannsI’m an new Packager in OpenSUSE BuildService, and i like this work. But if i would like to package for Factory, RPMLINT gives me any Errors or warnings. But these things to fix, are very difficult. Our Wiki Side for RPMLINT doesn’t contain many Error or Warningcodes.
But yesterday i’ve found an Side, with other Errorcodes from RPMLINT. Today i imported these Codes to our Wikiside http://en.opensuse.org/Packaging/RpmLint. I think it is not possible to list all codes on the Side. But i wish, that the side includes more Codes in the future.
No i would like to make an Call for contribution. If every Packager insert the codes, that he knows, we have an good library soon.
And on this Moment i would like to make an request about helping- Thank you all for the hard Work.
Advertisement
-
Lizards
Adrian Schröter (12)
Agustin Chavarria (6)
Alessandro de Oliveira Faria (13)
Alex Barrios (12)
Alexander Naumov (10)
Alexander Orlovskyy (3)
Alin M Elena (5)
Andrea Florio (27)
Andreas Jaeger (70)
Andreas Stieger (12)
Andrew Wafaa (31)
Arvin Schnell (9)
Atri Bhattacharya (3)
Bernhard Wiedemann (31)
Bonnie Kurniawan (1)
Bruno Friedmann (98)
Calumma Brevicorne (29)
Carl Fletcher (1)
Christopher Hobbs (17)
Ciaran Farrell (3)
Stephan Kulow (17)
craig gardner (2)
Stephan Barth (2)
Thomas Schmidt (2)
Dinar Valeev (1)
Dirk Mueller (2)
Dmitry Serpokryl (7)
Efstathios Iosifidis (21)
Fabio Mucciante (5)
Federico Lucifredi (9)
Greg Freemyer (1)
Holger Sickenberg (2)
Hubert Mantel (1)
Ilya Chernykh (5)
Ismail Donmez (1)
J. Daniel Schmidt (2)
James Tremblay (7)
Jan Blunck (4)
Jan Loeser (3)
Jan Madsen (1)
Jan-Christoph Bornschlegel (3)
Jan-Simon Möller (20)
Javier Llorente (12)
Jigish Gohil (85)
Jiri Srain (1)
Jiří Suchomel (3)
Johan Kotze (5)
José Oramas M. (6)
Josef Reidinger (16)
Juergen Weigert (1)
Julio Vannini (9)
Dinar Valeev (5)
Kevin "Yeaux" Dupuy (11)
Klaas Freitag (55)
Lars Vogdt (11)
Ludwig Nussel (13)
M. Edwin Zakaria (4)
Marcus Hüwe (39)
Marcus Meissner (2)
Marcus Moeller (3)
Marcus Schaefer (4)
Martin Lasarsch (8)
Martin Mohring (11)
Masim "Vavai" Sugianto (20)
Michael Andres (1)
Michael Löffler (7)
Michal Marek (7)
Michal Vyskocil (12)
Miguel Angel Barajas Hernandez (2)
P Linnell (2)
Nelson Marques (55)
Nenad Latinović (1)
Nikanth Karthikesan (2)
Przemyslaw Bojczuk (1)
Peter Pöml (4)
Petr Gajdos (2)
Petr Mladek (60)
Petr Uzel (5)
Ray Wang (1)
Raymond Wooninck (1)
Ricardo Chung (7)
Ricardo Varas Santana (7)
Richard Bos (11)
Robert Schweikert (16)
Rossana Motta (1)
Rupert Horstkötter (10)
Sascha Manns (66)
saydul akram (3)
Sebastian Siebert (6)
Shawn Dunn (2)
Stanislav Visnovsky (7)
Stefan Haas (1)
Stefan Hundhammer (5)
Stefan Schubert (7)
Steffen Winterfeldt (8)
Suresh Jayaraman (3)
Susanne Oberhauser (3)
Thomas Göttlicher (6)
Thomas Schraitle (26)
Togan Muftuoglu (3)
Tuukka Pasanen (36)
Will Stephenson (22)
YaST Team (90)