Home Home > 2008 > 05
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

Archive for May, 2008

Making openSUSE 11.0 LiveUSB : The Easiest (and Fastest) Way

May 31st, 2008 by

LiveUSB desktop

In earlier post, I’m writing “How to build openSUSE LiveUSB with Kiwi” tutorial guide and thinking how to get same results with more easier tips. Another distro came with easy trick to make a bootable LiveUSB and I think openSUSE should be 😉 . Kiwi is a great tools for making openSUSE liveUSB, QEMU Image, VMWare Image, XEN Image and LiveCD Image but it would not fit with any situation.

I’ve search various topics and found some of them looks pretty interesting to try. After reviewing some tips, here is a tutorial guide to make openSUSE 11.0 LiveUSB with the easiest way :


  1. Tutorial can be used on Linux or Windows
  2. Do not need to install openSUSE onto hard disk for making LiveUSB as it was with KIWI. Just download the LiveCD ISO image and a tools for make an extract of ISO content (7-zip on Windows and mount -o loop tips on Linux)
  3. Can used FAT 32 file system for interoperability (marketing hype 😉 ) and mobility of data. Flash disk could be accessing by various OS
  4. Simple, only need a few step
  5. Fast process, required a few minutes for copying ISO image and initrd process


Social Marketing for a Little Green Lizard

May 29th, 2008 by

With only like three weeks until openSUSE 11.0 is released to the world, now would be a good time to start the buzz around it. OK, so there’s already been a lot of buzz around 11.0, for example this article from Ars Technica which reached the front page of Digg, not to mention our own countdown and openSUSE 11.0 pages. But there’s many more ways you and I can help people know about openSUSE 11.0.

If your into the whole Web 2.0/Internet/Social Networking thing, you know how much of a help and marketing tool (aka timewaster) it can be. The trick is to not bother people and throw openSUSE in their face every day (sorry Twitter friends!). But there are many ways you can use these tools to help openSUSE. Our own community manager Zonker has talked about using Twitter to spread openSUSE, and it does work. In terms of Twitter, however, it depends on who your followers are. For example, many of my followers are Linux or SUSE users already. How does Twitter help with those people? I’ll answer that in a minute.

A few days ago, I started an event on Facebook: openSUSE 11.0 Public Release (you need to be logged into Facebook to view) as a type of meta-event. It doesn’t have a specific real world location (the location is set to opensuse.org; the city, which is required, was set to Nuremberg, Germany for obvious reasons) but it serves to bring the awareness of openSUSE 11.0’s release, and also encourages anyone else starting an actual release event (such as a openSUSE User Group or Linux user group) to add their event to Facebook and link it from the above event. Within 3 days, the number of people confirming their “attendance” is growing, and at least one person has mentioned that she plans on hosting a release party.

So, do you have any other ways to help share openSUSE 11.0? Are there openSUSE groups or 11.0 release events on other social networking websites the community should know about? Let me know through the comments!

Oh, and openSUSE 11.0 Release Candidate 1 should be out today!

BTW, this is my first post. I’m Kevin Dupuy, and instead of rehashing it all here, I’ve got my bio up on the wiki here.

It builds!

May 29th, 2008 by

Out of total insanity I promised Adrian a couple of weeks ago to test local installation of the OBS build service and interconnect it with the build.opensuse.org instance. Last night I couldn’t sleep due to the heat, so I finally did. Half an hour later, everything was installed and set up correctly according to the README.SETUP instructions in the obs-server package. I’ve fixed a couple of small issues in the README while doing so.

This morning, Michael Schroeder fixed the remaining bugs in the scheduler so that it actually runs. And now it builds 🙂

Source and binary interconnects work fine, so I can e.g. branch a package that is somewhere in the openSUSE buildservice (some KDE:KDE4: package or even openSUSE:Factory) and modify it locally in a test project, and watch the resulting build failures. There are some smaller issues with “osc linkpac” and “osc branch”, but editing the _link  files directly works.This way one can do experimental changes to packaging without actually breaking the repository for all other users, or slow down the build power ressources for everybody else due to unnecessary rebuilds.

As a test case, I’ve imported KDE 4.0.5 packages into a local branch of KDE:KDE4:STABLE:Desktop for testing. More seems possible, like for example doing a daily rebuild of the KDE 4.

Really cool stuff. Buildservice guys, keep rocking!

I’m going to LinuxTag ;)

May 28th, 2008 by

I’ll be in Berlin on Thursday and Friday. As this is my first LinuxTag i’m really excited and looking forward to meet as many people from the “openSUSE universe” as I can find 😀 .

See you at the openSUSE booth!

Preparation for openSUSE Booth on IGOS Summit 2

May 27th, 2008 by

Martin Lasarsch looks quite busy with his project, preparing openSUSE booth on Linux Tag at Berlin 😉 , and so do with us here in Indonesia, preparing openSUSE booth for IGOS Summit 2 event. IGOS stand for Indonesia goes Open Source and IGOS Summit 2 dedicated for open source promo and community building.

Preparation for IGOS summit 2

Indonesian openSUSE Monthly Meeting-May 2008

May 27th, 2008 by

Last week, Indonesian openSUSE community (openSUSE-ID) had a regular monthly meeting on Saturday, May 24, 2008. for promotional and marketing benefit, we choose Detik.com-currently biggest online newspaper in Indonesia) office at Aldevco Octagon Building Jakarta as our location for meeting. This is our sixth regular meeting since November 2007.

As scheduled on my previous post, this meeting covering up some agenda, ie : openSUSE 11.0 features preview, knowledge share about zypper package manager, our preparation for booth on IGOS Summit 2 event, openSUSE 11.0 release party and openSUSE on Live USB demo. (more…)

learning ruby…

May 26th, 2008 by

Recently, I wanted to show how the buildservice makes packaging easier by creating a specfile template for you (just click the “Create RPM SPEC file templat” checkbox when creating a new package). Unfortunatelly, the template it creates is not really useful for someone not skilled in writing spec files. Also, it’s just a static template, so you have to write the summary and description even though you have just entered both in the web form. Definitely nothing to show off to newbies ;-). But knowing that the buildservice developers have more important stuff to do, and wanting to learn something new, I decided give it a try and fix it myself.

My idea is: The buildservice api asks a set of questions, which are presented by the client (webclient, osc, …) to the user, and creates a specfile based on these questions. Also, the api tries to suggest good defaults where possible. After spending some time learning ruby, rails and the api code, I have an ugly 200 line patch to the api that generates a working specfile for GNU hello ;-).

wizard in action

The user interface part is not yet done, but should be easy. What’s more chalenging is adding heuristics to “do the right thing”: detecting the build system (autotools, cmake, Makefile.PL, etc), detecting build dependencies, and so on. Right now, it only extracts the version number from the tar name.

Today Agenda : openSUSE-ID Monthly Meeting

May 23rd, 2008 by

Today (Saturday, May 24, 2008), Indonesian openSUSE Community (openSUSE-ID) have a regular monthly meeting. Meeting for this month will be held on detik.com office, Jakarta.

We got about 30-40 registered members will be attending the meeting. It would reach more than 30 members because some of our regular meeting members didn’t submit their registration. The registration process itself only counted how much the attendees for better meeting room preparation.

This month, the agenda of meeting will cover up some discussion topics : openSUSE 11.0 features and highlight preview, presentation about zypper package manager, openSUSE on USB Live Stick demo, preparation for IGOS Summit 2 event (The event looks similar with FOSDEM in Europe. We have openSUSE booth at the event) and openSUSE 11.0 release party.

I’ll be update with some picts of our monthly meeting.

Garden Party

May 21st, 2008 by

Yet again the guardians of the garden are boogieing.

The GNOME Team are holding their meeting tomorrow Thursday 22nd May at 1600GMT/UTC/ZULU (or translate it into your local time). As always you can get sight of the agenda; the main themes for this week are Factory Testing, Bugs – under prioritised/bug voting/10.3 bug squashing, and a new item to the show Community Clinic.

“What pray tell is that last item?” I hear you ask (you did ask didn’t you?).  It is an item aimed at the code contributing challenged.  Basically we hope to be able to provide means for those that are unable to hack (for whatever reason) a way of helping out.  This could be packaging, documentation, pimping our wares and even HALO insertions behind enemy lines for guerrilla hit and run attacks.  Okay maybe not the last item but you get the idea.

So please come along and join the party, you don’t have to BYOB but the more the merrier we become 😀


May 21st, 2008 by

Collaboration is not always an easy thing: Talking, meetings, making decisions and finding compromises. Sometimes I have the impression that some people in our business find this inter personal activities very exhausting and thus prefer to work on their own. Depending on how genius one is that works far. But for obvious reasons working alone has limits. If we talk about a whole Linux distribution for example one can not succeed: The working power, creativity and time of one is not enough.

That is one reason why we consider it as one of the keys for success that the Build Service enables people to work together in a useful and non annoying way. We think of tools in the Build Service which help. That is difficult because some formalism and guidance (in business often called ‘process’) is needed to keep things going in a transparent and reproduceable way. Control should stay there where it needs to be, for example at the maintainer of a project. On the other hand collaboration tools should not constrict people and their working together.

Here is a little story of Karl who wants to change something in the openSUSE Factory project. He needs to work with the Factory maintainers and this is how that is planned for the future:

Karl, a developer working for a small software company, loves openSUSE but not really the one package Kabax because there is a packaging problem Karl has analyzed.

Karl wants to change that to make sure that the next version of openSUSE contains a good version of Kabax.

For that, a branch of Kabax in Factory is needed where the fixes can be put in, built and tested. Karl uses osc to create a branch. The package is not really maintained in Factory itself, because the few Factory maintainers can not care about all packages there. Kabax has a Devel Project entry in its meta data that points to the project where it is actually maintained by the expert Karsten.

Because of the devel project, osc branches not really from the Factory package but from the development project where the development happens by Karsten. That might be different from the Factory package, but is clearly the development version that soon will be synced to Factory. When that happens is up to Karsten and the maintainers of Factory.

In the branch Karl starts to work on Kabax and creates a beautiful patch. Since his branch package also lives on the Build Service, it builds live for all relevant repos and along the changes of the devel project.

Once Karl is happy with his work he raises the attention of Karsten on his change by creating a submit request. A request in general informs others of something somebody else has done which requires action. In the case of the submit request it tells Karsten that there is a valuable change to his package that should make it’s way to Factory. Karsten now accepts the request and Karls contribution is in.

The nice thing about all this is also that the branch packages as well as the requests are open and visible to everybody who is interested in. That gives us the transparency we need. And of course that does not only work for Factory but for all projects if one wants to change something on a package where he/she does not have permissions yet.

How do you like this story?