Home Home > Distribution
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 the ‘Distribution’ Category

Distro Competition Sessions needed?

March 23rd, 2011 by

In my last blog I was mentioning the “Distribution Wettstreit” which translates in “distribution competition” held on the Chemnitzer Linuxtage event. The idea of that session is to have distros lined up on stage and give them a task and see how each of them is able to solve it and compare that. I participated for openSUSE but the session left some question marks for me. Here are my thoughts how the idea could be improved.

As far as I know it happened the second time in Chemnitz, were Debian, Fedora, Mandriva, Pardus, Ubuntu and openSUSE were on stage. The tasks we got were every day problems, such as playing a flash movie or how to display a html 5 page. openSUSE was lucky with a one week old release, so wonder why we can handle HTML5 directly and others who released earlier can not?

Apples and Oranges

Apples and Oranges

I have to say that I do not like this kind of session too much. It is great to compare distributions, and also to do it kind of interactively and live. But even given that all involved know that its not about finding a winner and a looser, in this format there are too many parameters that influence the whole thing: First, the release date. Younger distros tend to be better than older ones. Second, it highly depends on the person who sits in front of the machine and explains what he does to solve the problem. One must be able to solve the task technically, and than she/he must be able to talk about it appealingly.

Different distros target at different user groups, and you quickly compare apples with oranges. I think it should be realized as a benefit that we’re different, and that does not necessarily need to end up in a competition everywhere. Moreover, we should appreciate if people remain playful and try distros as they like instead of trying to nail them to one forever.

Maybe next time we can rather have a “The combined power of the Linux variety” -session [working title] instead? In that we could try to work out the differences between the distros and which user groups could benefit from them. I mean, the variety in the FOSS community is the great advantage that we have over other systems and we should express it. And our similarities which we certainly have should also be brought on the table. To whom do we really compete? I guess we should be compared against commercial systems which tend to lock the user in with huge consequences or have security-, innovation- and other issues. Why not line up on stage and show the audience how we together beat these system with free software in various ways for the good of the user?

Yes, playing flash movies is a every users problem, and I know the “I don’t care, it simply needs to work!”-attitude lots of users do have. We as free software distributions had and have to find ways to deal with it, and we all have our solutions. But whats really important is not to present new users that we even though in general can not work with Flash, we found a workaround.

The more important message is why its dark in some corners of FOSS world, how that can be improved and who is able to change that. I think it would be awesome if that could be taken more into account the next time we have the opportunity to speak to such an audience as distributions together.

Chemnitzer Linuxtage 2011

March 23rd, 2011 by

Last weekend I spent on Chemnitzer Linuxtage 2011 which is a popular linux event in Chemnitz, Germany. It was the first time I have been there and was very positively surprised. It is a very well organised event, in a building providing the perfect environment and a large amount of volunteers helping to make the whole weekend enjoyable and relaxed. Thanks for that, it really was fun to meet so many people in this all-inclusive atmosphere :o)

openSUSE had a booth there (thanks Fedora for the picture) and we were lucky enough to have brand new 11.4 promo DVDs there which were handed to interested people. openSUSE 11.4 in general is very well received at most visitors, they were quite happy with our latest release. That is also true for the feelings for openSUSE all over: I heard so much positive feedback about what we do and how we do it, for example the OBS with the collaboration features, the distribution or the activity all over. People recognize our efforts.

I gave a talk about Kraft, as people hinted me that there might be the right audience for the topic of Linux in the small business. The interest was huge, the room was more than full and people seemed to like the way I was approaching the challenge. Unfortunately I had to fight with the notebook/beamer phalanx in the beginning (I apologize for that) so that I had to skip the live demo of Kraft in the end. But still I got a lot of interesting discussions afterwards and got some nice contributions already. Thanks for that.

On saturday noon there was a “Distribution competition” where I was pulled in to show openSUSE. It went ok for all distros taking part and was fun for us presenting 🙂

Booster Michal was giving a workshop about creating packages in the OBS for multiple distributions and a very well received “whats new in 11.4?” talk was given by Sirko in the beginners track.

It was a great event, even though I quite exhausted arrived home late on sunday night. I will be there next year again.

Policy proposal for Factory: Make source of tar balls trackable

March 21st, 2011 by

I like to suggest a general policy for openSUSE:Factory project to document from where a tar ball (or any other file from upstream) is comming from. Why that ? It makes it much easier to review version updates and it guarantees that no one can inject some mal code via a modifed tar ball.

So far I added the source services “download_url” and “tar_scm” to our OBS instance, which downloads the files and stores them as files via a commit. Some people use them already, some others don’t like them because they store the files with _service: prefix.

In last hackweek, I added another way to handle this, which I would like to request as setup and policy for openSUSE:Factory project. You can add a project wide source service, for example the new “download_files” service. That would mean that no needs to add a _service file to the sources anymore. It is enough to add an URL to the spec file Source: tags. The service will automatically download it from there.

But that does mean we still have have _service:download_files:osc-0.1.tar.bz2 file names ? Not when we also add the new “trylocal” parameter and use latest osc versions. This parameter will let act osc to execute the services, but name the files without prefix and commit them together with the other files.

Where is the advantage then ? The server is still validating that this is an identical file. It downloads it again and compares it. In case it is the same file, nothing will happen.

What will happen, when the file differes ? We basically have two options, either we can let the service mark the source as broken or we would store the file with _service: prefix again.

The later mode has the advantage that you can still do version upgrades via slow connections and let the server download the files.

Please find some more details about new possibilities with the source services here.

An example setup for this can be tested via

osc bco home:adrianSuSE:FactoryTest bc

and do for example a version downgrade to 1.05 version to see how it works. Please note that you need the osc from openSUSE:Tools:Unstable project for this.

We can also apply the still suse-internal spec formater and validator scripts via this way later one.

Another advantage of this setup would be the new “update_source” service, which could run in some openSUSE:Factory:AutoUpdate project and tries automatic version upgrades when upstream releases a new version. They could be reviewed and just picked (directly or with additional manual fixes).

First Survey on openSUSE Version naming is open now

March 16th, 2011 by

Following my last blog post on “how to name the distribution release“, I’ve opened up a public survey and look forward to your votes. There is also a good discussion going on on the opensuse-project mailing list.

This is the first iteration. Coolo and myself discussed to use a second survey with the group of winners on connect.opensuse.org.

How to name the distribution releases?

March 11th, 2011 by

We had this week a discussion on IRC on how to name the next release and I took the action item to do a poll on connect.opensuse.org now to help us solve the naming of openSUSE distribution releases. I’ve started earlier today a discussion on the opensuse-project list and already incorporated some comments I received in this text.

openSUSE does not have a major and minor numbering, even if it seems so. There is right now no difference in any way between what we would do for openSUSE 11.4 or 12.0 – and no sense to speak about openSUSE 11 or openSUSE 11 family. We also have no process on how to name the next release (when to increase which parts of the number).

Here are some options, if I miss some, please tell me and I will then soon setup a poll. I’m listening the next version we would use as well as how the following would be called as an example. Remember we have releases every 8 months, so the next releases will be in:
November 2011, July 2012, March 2013, November 2013, July 2014, March 2015.

Here are the options I collected so far:

(more…)

openSUSE in ETEC of Bebedouro/Brazil.

March 1st, 2011 by

The ETEC of Bebedouro, brilliantly is teaching his students about free software. In the name of the openSUSE community, I thank the area coordinator Mr. Wagner Vieira, Teachers Augusto Aguiar Campos and Rodrigo. Read more…

Default Wallpaper for GNOME:Ayatana

February 21st, 2011 by

Not that I know a lot about Artwork or Wallpapers… For those, I am mainly a ‘customer’ most of the times, and things get easy for… either I like it, or I don’t. There’s a lot of stuff available out there, and initially I loved the snake (I still do), but since I couldn’t distribute it due to licensing, I’ve spent a couple of hours looking for Artwork with a compatible license and contacted a few artists about licensing and the possibility of using/distributing their work.

To distribute for GNOME:Ayatana on the 11.4 cycle, I’m going to use ‘Spaceman Goldrush Edition’ from ‘mydarktime’, a German artist. I’m happy that mydarktime has been so kind in allowing openSUSE to distribute this package under CC-BY-SA. I will also take the opportunity to quote him:

“(…)  I would be very pleased to see mine in it” (wallpaper pack on GNOME:Ayatana).

I find this wallpaper very attractive and it doesn’t really tire me up from looking at it, which is really, really nice! I hope everyone else likes it also!

Spaceman Goldrush Edition @ Deviant ART

ATI/AMD fglrx 8.821 Catalyst 11.2 available for openSUSE 11.2, 11.3, 11.4

February 19th, 2011 by

Updated : April 4th 2011

Preambule : free software

Warning

I would notice everybody which will install these software : you will install proprietary softwares on your computer. Nobody will be able to debug them, nor help you to resolve what can be happen. That must be said !

The free future

The real future is already in place : it’s called radeon (or free-radeon), it’s fully integrated in kernel & xorg. Actually ( for openSUSE 11.4, or openSUSE 11.3 with kernel-stable + X11 obs repo ). Support for many chipset is in real progress even for the 6xxx series.
Give it a try before using the proprietary software, report any bugs you find with it. Only your contributions can help and will make a real differences. Thanks for doing that !

Unofficial but working repository

I offer for those of you that for any reasons can’t use successfully the free-radeon drivers a repository where you will find the latest fglrx/catalyst drivers following the packaging policy made avalaible by AMD.
Thanks to Sebastian Siebert ( check his blog ) to work in coordination with ati/amd and follow the catalyst packaging. His work allow us to have that driver available for openSUSE.

The quick how-to

Adding the repository

For openSUSE Factory
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_Factory/ "ATI/AMD FGLRX"
For openSUSE 11.4
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.4/ "ATI/AMD FGLRX"
For openSUSE 11.3
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.3/ "ATI/AMD FGLRX"
For openSUSE 11.2
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.2/ "ATI/AMD FGLRX"

Installing the driver

Nota previous version

Due to change in ati/amd way of life, it’s recommanded to completely remove any version of fglrx previously installed with a zypper rm

I can only recommand to also (as root)

# Remove old conf & stuff
rm -fr /etc/ati
# Remove any old fglrx inside kernel modules
find /lib/modules -type f -iname "fglrx.ko" -exec rm -fv {} \;
New installation

Once the repo has been added, you will certainly have to reboot to get ride off free radeon module. At boot on the grub line add
nomodeset blacklist=radeon 3
Don’t panic you will be land to a console, open it with root account to install fglrx.
Search the software you want for example under openSUSE 11.4

zypper se -s fglrx
Loading repository data...
Reading installed packages...

S | Name                  | Type    | Version | Arch   | Repository
--+-----------------------+---------+---------+--------+-----------
i | fglrx64_xpic_SUSE114  | package | 8.831-1 | x86_64 | ATI/AMD fglrx non-official  
  | fglrx64_xpic_SUSE114  | package | 8.821-1 | x86_64 | ATI/AMD fglrx non-official  
  | fglrx_xpic_SUSE114    | package | 8.831-1 | i586   | ATI/AMD fglrx non-official
  | fglrx_xpic_SUSE114    | package | 8.821-1 | i586   | ATI/AMD fglrx non-official

Starting with 8.821 (Catalyst 11.2) ATI use now xpic (full explanation)
So use that one. I’ve removed all non xpic drivers the 2 April 2011.

For a 64bits version
zypper in fglrx64_xpic_SUSE114
For a 32bits version
zypper in fglrx_xpic_SUSE114

During the installation process, all the dependencies will be added, which mostly are needed to build the kernel modules. Expect around 200MB to dowload.

Then the installer will build the module for your installed kernel.
And if there’s a kernel update, the script will automagically detect that, and will rebuild the module for the new kernel installed. (So if you find that your workstation is slow on reboot just press the esc key to see the details … )

Preparing xorg to use fglrx

Once the module is build and installed, you should have a file fglrx.conf or 50-fglrx.conf in /etc/modprobe.d

cat /etc/modprobe.d/50-fglrx.conf
blacklist radeon

Next ati recommend to use ati –initial-config but that break the auto-detect stack of xorg. So I recommend changing one line in file /etc/X11/xorg.conf.d/50-device.conf
just change driver line to driver “fglrx”
All the rest of the setup (double screen etc) will be made lately with the ati catalyst control center (command is amdcccle).
For those of you which want to have an xorg.conf file just have a look at aticonfig –help command.

Start X

If you are inside the console we start to use before just run “init 5” to start xorg, and normally you will find your normal xorg login screen (kdm, gdm, ldm, xdm).
Hit ctrl+alt+f1 to return to the console and type exit or logout or ctrl+d to close it.
then ctrl+alt+f7 to return to the xorg session.

Updates

ati/amd catalyst are release on a month basis, but this vary from 3 weeks to 8 weeks.

  • Catalyst 11.2 – fglx 8.821 : 14 February 2011

References

Sebastian Siebert blog ( German ) with nice howto and problem resolution.
My previous post on the subject

Virtual launch party for openSUSE 11.4 : RC1 is done

February 14th, 2011 by

Successfull RC1 launch!


Dear followers, after the official announcement, we test yesterday the place, and check how fun and cool it can be with several attendees.

The danse party Pop/Rock music themed was animated by DJ Yazz (Brittany Haefeli). Starting at 8:30 CEST the party was crowded during it’s 2 hours and a half. More than 50 people came and visit us during that time. Great that was twice what we expected !
(more…)

ATI Amd flgrx 8.812 catalyst 11.1 available also for 11.4/factory

February 13th, 2011 by

A quick note for the week-end, I’ve build and uploaded the new fglrx drivers.
The good news, they are also available for 11.4/factory,

Unofficial-but-working repository

For openSUSE 11.4 (factory) NEW !

zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.4/ "ATI/AMD FGLRX"

I would like to have feedback about how that works for you, please comment !

Factory specifics troubles

on a fresh auto-configuration factory install : libomp43

Problem: fglrx64_7_6_0_SUSE114-8.812-1.x86_64 requires gcc, but this requirement cannot be provided
  uninstallable providers: gcc-4.5-16.1.i586[openSUSE-11.4-11.4-1.35]
                   gcc-4.5-16.1.x86_64[openSUSE-11.4-11.4-1.35]
 Solution 1: deinstallation of libgomp43-4.3.4_20091019-5.23.x86_64
 Solution 2: do not install fglrx64_7_6_0_SUSE114-8.812-1.x86_64
 Solution 3: break fglrx64_7_6_0_SUSE114 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c): 1
Resolving dependencies...
Resolving package dependencies...

The following NEW packages are going to be installed:
  binutils-gold fglrx64_7_6_0_SUSE114 gcc gcc45 glibc-devel 
  kernel-default-devel kernel-desktop-devel kernel-devel kernel-source 
  kernel-syms kernel-xen-devel libgomp45 linux-glibc-devel make patch 

The following package is going to be REMOVED:
  libgomp43 

15 new packages to install, 1 to remove.
Overall download size: 127.9 MiB. After the operation, additional 600.9 MiB 
will be used.

Normally this bug (in M5/M6) should has been resolved in RC1.

See full details on my previous dedicated post
//lizards.opensuse.org/?p=4673