Welcome to Planet openSUSE

This is a feed aggregator that collects what openSUSE contributors are writing in their respective blogs.

To have your blog added to this aggregator, please read the instructions.

30 November, 2015


Se acerca una de las mejores lluvias de meteoros del 2015: las Geminidas.


Marco has come over to the Netherlands to pay me a visit, and to hack a little bit together, in person. So with the weather clearly suggesting to stay inside, that’s what we did over the weekend, and how better to entertain yourself than to work on mobile software?

Marco has been working for a while on components that follow Plasma’s human interface guidelines and make it easy to implement applications with a common navigation pattern and look and feel. Obviously, these components use a lot of Plasma under the hood, so they get excellent integration at a visual and at a technical level. This high integration, however, comes at the price of having a non-trivial chain of dependencies. That’s not a problem in Plasma Mobile, or other Plasma workspaces, since all that is already there, anyway.
We thought that an interesting exercise would be to find out what really defines a “Plasma application”, and how we can make the concepts we engrained in their design available to application developers more easily. How hard could it be to use Plasma components in an Android app, for example? The answer is, not entirely trivial, but it just became a whole lot easier. So what did we do?

For those reading this article via a feed aggregator, hop over to youtube to watch the demo video.
We took Subsurface, which is a piece of Free software used for logging and analysing scuba dives. Subsurface has a mobile version, which is still in its infancy, so it’s an excellent candidate to experiment with. We also took Marco’s set of Plasma components that provide a reduced set of functionality, in fact, just enough to create what most applications will need. These components extend QtQuick components where we found them lacking. They’re very light weight, carry no dependencies other than QtQuick, and they’re entirely written in QML, so basically, you add a bunch of QML files to your app and concentrate on what makes your app great, not on overall navigation components or re-implementing for the n-th time a set of widgets.

So after solving some deployment issues, on Saturday night, we had the Plasma mobile components loading in an Android app. A first success. Running the app did show a number of problems, however, so we spent most of the Sunday to look into each problem one by one and trying to solve them. By early Monday morning, we had all of the glaring issues we found during our testing solved, and we got Subsurface mobile to a pretty solid appearance (pretty solid given its early state of development, not bug free by any means).

So, what to take a away from this? In a reduced form, Plasma can be a huge help to create also Android applications. The mobile components which we’re developing with Plasma Mobile as target in mind have had their first real world exposure and a lot of fixes, we got very

29 November, 2015



About an year ago, I was playing around with Cassandra for a quick prototype in then dayjob. It opened up the world of distributed systems to me and I was piqued. Audaciously, I decided to implement a simple distributed database, Keeri, to have a grasp of the fundamentals of the implementation of distributed databases. In the past, I have implemented a simple filesystem which has helped me immensely when I was working as a filesystem engineer. Also, I have always been fascinated by the theory behind the database internals right from college days, but did not get my hands dirty.

After a few weeks of work, I was able to implement a recursive-descent SQL parser, which analysed the incoming SELECT queries, made a tree with the subqueries properly branched as sub-trees. I made a simple columnar store that appends data (via an API as opposed to SQL) but without any atomicity guarantees. In short, it was a rudimentary, in-memory system that functions decently. However, I was nowhere near the initial goal of implementing a distributed database.

I realised that there were plenty of design choices in a distributed database implementation, right from architecture, replication, membership, consensus, CAP, etc. I even took a coursera course that helped me understand the basics in detail. As of today, I have enough confidence in my skills and knowledge to implement a distributed database which could serve as a good teaching material, if not as a production software. However, I have not made a single line of code in the past seven months to the project. Abandoning (at least temporarily) the project, hurts.

Yesterday, my daughter decided to wake me up from my sleep after midnight, I spent the remaining night wide awake, while she slept, thinking why I have not made progress in keeri. I realised that I have been overwhelmed by the amount of things to do, that are not core to the system. For example, after I decided that the database has to be NEWSQL based, it is imperative that I needed a SQL parser. But there are a dozen types of parsing (LL, LR, Recursive Descent, ANTLR etc.) techniques. Understanding the pros and cons of the each type and finding the most suitable candidate is a non-trivial task. SQL Parsing is just one component of the system. There are other components such as the choice of datastructures (based on read/write ratio, type of load etc.) One approach is to proceed with the simplest choices for each component with well-defined borders. The individual components can be later replaced. By the time, I completed the SQL query to a decision tree code, I felt exhausted, even before I began the core database and distributed systems functionality.


From my past open source experience, I have known the synergic boost that developers experience in FOSS communities. It is always good to work in a like minded team of developers rather than individually when working on big problems. I started thinking what other

28 November, 2015


Aprovechando unos cuantos dias de descanso gracias al Dia de Accion de Gracias, y tambien la poca nubosidad de la temporada, logre al fin dedicarle un poco mas de tiempo a la captura de imagenes del Sol en Hidrogeno alfa. El filtro de Etalon permite el paso unicamente de la frecuencia del Hidrogeno alfa por […]

Michael Meeks: 2015-11-28 Saturday.

17:37 UTCmember

  • Up earlyish; tried (somehow) to get GStreamer to work on Miriam's OpenSUSE 13.1 - enabled packman, burned many unhappy minutes wrestling with different versions of different things, broken gst pipelines, switching packages incrementally between vendors, installing more and more bits. I used to like VLC because it was one big lump of download that "just worked" until they decided to go with the "one hundred pieces any developer with lots of time can just plug together and debug, while no user can install or use anymore". Eventually discovered that deleting my ~/.cache/gstreamer, ~/.gstreamer* made things suddenly work: nice, sadly don't have the bad files now.
  • Breakfast - cheering. Nicki over with kids - plugged at reading around SalGraphics usage; more horrors.
  • Lunch, out to buy a new fireplace/surround in Cambridge. Anything to be rid of the 30's monstrosity we have; an interesting selection - left the esthetics to J.
  • Home; back to SalGraphics - eventually discovered that (depending on backend) we can and do end up with multiple wrappers of the same underlying OS resources; which causes my issues. Something like a rampant mis-use of multiple fdopen's on the same underlying file; fun. At least it makes sense finally.


Para los más puristas del software libre y de GNU/Linux una opción es el proyecto Freed-ora que ofrece una versión de Fedora 100% software libre.


El pasado 3 de noviembre de 2015 se publicó la nueva versión de Fedora, la distribución de GNU/Linux comunitaria auspiciada por Red Hat.

A partir de ese proyecto, Marcus Moeller ha creado una ISO de Fedora pero 100% software libre. ¿Qué quiere decir esto? ¿No es Fedora software libre?

El kernel Linux que libera Linus Torvalds con una gran comunidad detrás no es totalmente libre. Hay partes del código que no incluyen el código fuente, código ofuscado, o código que no se distribuye bajo licencia de Software Libre, o que incita o requiere que utilices parte de software adicional que no es Software Libre.

Hay un proyecto del que ya he hablado por el blog, que lo que hace es “liberar” ese kernel Linux y eliminar la parte no libre, GNU Linux-libre o Freedo

Ya escribí por el blog sobre cómo hacer openSUSE libre:

Y recientemente en el blog de Marcus Moeller pude leer que él mismo había creado una ISO de Fedora con linux-libre:

A esa versión, llamada Freed-ora, además del linux-libre, también se le ha eliminado todo el software privativo y viene con el navegador Icecat.

La ISO que ofrece está basada en Fedora 23 Workstation, que ofrece el escritorio Gnome por defecto. También se le ha añadido el repositorio Freed-ora.

En el enlace del artículo en cuestión también ofrece las pistas para poder crear un spin basado en Fedora Xfce por ejemplo, también libre. Quizás os apetece probar la experiencia de liberar completamente vuestra distribución de GNU/Linux, esta puede ser una opción.

Otra opción puede ser la distribución BLAG (Brixton Linux Action Group) una distribución 100% Libre, que forma parte de las distribuciones recomendadas por la FSF, y que también está basada en Fedora, pero liberándola por completo de las partes no libre, tanto el kernel, como el software y los repositorios.



27 November, 2015

Michael Meeks: 2015-11-27 Friday.

21:00 UTCmember

  • Mail chew; hackery; lunch; interviews. Poked at the SalGraphics lifecycle - which is a complete mystery; inconclusively and at length; rather important if you want to key a cache/double-buffer of the screen contents on it.


The Open Build Service has the nifty feature that you can tell it to use a specific kernel to boot the worker VMs that build your software. To use that, you don't need any special setup, just a package which contains a kernel and an initrd:

   /.build.kernel.kvm # used by KVM workers
   /.build.kernel.xen # used by Xen workers

So you just need this package and make sure it is installed in the VM using the VMinstall: tag in the project config.
If the build service worker script detects that after preparing the VM, such a kernel and initrd are present, they will be used for booting the worker VM that finally builds your package or image. If it is *not* detected, then the kernel the worker server is running with (usually a SUSE kernel) will also be used for the VM.

In the openSUSE Buildservice instance, all "recent" SUSE distributions are configured for that: they use the kernel-obs-build package, which gets created automatically when building the kernel rpms.

Now I am right now using a buildservice instance for cross-distribution package- and imagebuilds. The challenges of trying to build RHEL/CentOS 7 images with KIWI in OBS warrant at least one additional blog post, but one thing I noticed was, that some of the kiwi stuff, when done with a CentOS 7 userland, apparently also needs a CentOS kernel, otherwise kiwi's parted calls, for example, will exit with code 1 (without issuing an error message, btw).
So I have built a kernel-obs-build from the CentOS 7 kernel and configured my OBS instance to use it, which brought me quite some steps further to building CentOS images with KIWI in OBS.
The code (or rather: the spec files) to "convert" the CentOS kernel to an OBS kernel is at https://github.com/seife/kernel-obs-build, a short README on how  to use it is included.

Note that right now it only works with KVM workers as I was not able to get the worker code to boot the kernel correctly in a Xen VM, even though drivers are all there, the reason is probably that the obs worker scripts rely on some of the specifics of a Xen-specific kernel (e.g. the device name of the block devices being passed through to the VM from the config, which is not true for a generic PV-capable kernel).
But I guess this will improve soon, now that openSUSE has dropped the kernel-xen package, they will face the same issues and hopefully someone will fix them ;)


Dear Tumbleweed users and hackers,

Week 48 brought three snapshots – the content of 20151118 has been well advertised in last weeks review already (as a small preview, as it was so close to completion).

I will repeat it’s items this time around, as they were factually only released after the last weeks report.

So, this week we received:

  • Switch of the default fonts to Roboto for Sans and Serif families and Source Code Pro for Monospace
  • Ghostscript 9.18
  • X.Org 1.18 – at this point again a warning: AMDs fglrx driver is not supporting this yet
  • Mesa 11.0.5 – with a bunch of crash fixes
  • AppStream-glib was updated to 0.5.2 – this is a minor update with significant impact on the AppStream meta data generation: newly, only packages with an appdata.xml file are considered. Attempted auto-conversion from .desktop files no longer happens (it resulted in badly represented applications). This means we now have much less ‘applications’ as we used to have (see http://gs-stats.leuenberger.net/ ). If you want to application to show up in GNOME Software (and future Software Centers based on AppStream): act now and add an appdata.xml file to your package
  • Wireshark 2.0 – newly with a Qt interface
  • KDE Framework 5.16.0
  • Plasma 5.4.3
  • GStreamer 1.6.1

Pretty impressive list, considering that this week too was only 7 days long.

In staging, besides regular smaller updates here and there (incl. another Mesa update), the most notable thing at the moment is the change in the kernel packages, as was announced here. XEN will still be supported but no longer will require a special kernel package.

Wish you a great weekend – and always remember to have a lot of fun.


I use the Open Build Service to work on openSUSE packages. There is a useful tutorial HERE.

Important resources:

  1. post-build-checks source code
  2. Spec file guidelines

And here is a summary of 'osc' commands I use the most:

alias oosc='osc -A https://api.opensuse.org'

Assuming you will be using the openSUSE Build Service, you will need to include the -A option on all the commands shown below. If you set up this alias, you can save a lot of typing.

osc search PKG

Search for a package. You can also use http://software.opensuse.org/ and zypper search PKG is also helpful.

osc meta pkg PRJ PKG -e

If you are project maintainer of PRJ, you can create a package directly using this command, which will throw you into an editor and expect you to set up the package's META file.

osc bco PRJ PKG

osc branch -c PRJ PKG

If you are not a project maintainer of PRJ, you can still work on PKG by branching it to your home project. Since you typically will want to checkout immediately after branching, 'bco' is a handy abbreviation.

osc ar

Add new files, remove disappeared files -- forces the "repository" version into line with the working directory.


Build the package locally -- typically I do this to make sure the package builds before committing it to the server, where it will build again. The REPOSITORY and ARCH can be chosen from the list produced by osc repos


Builds take place in a chroot environment, and sometimes they fail mysteriously. This command gives you access to that chroot environment so you can debug. In more recent openSUSEs the directory to go to is ~/rpmbuild/BUILD/

osc vc

After making your changes, edit the changes file. For each release you need to have an entry. Do not edit the changes file yourself: instead, use this command to maintain the changes file "automagically".

osc ci

Commit your changes to the server. Other SVN-like subcommands (like update, status, diff) also work as expected.

osc results

Check what the server is doing. Typically a build will be triggered by your commit. This command lets you see the status.

osc sr

'sr' is short for submitrequest -- this submits your changes to the PROJECT for review and, hopefully, acceptance by the project maintainers. If you're curious who those are, you can run osc maintainer (or osc bugowner)

osc rebuildpac

Sometimes it's desirable to trigger a rebuild on the OBS server.

osc results

This command shows the current build status. Adding -v gives more information.


JFYI: http://spdx.org/licenses/ lists all well known licenses and their original source. This becomes extremely handy if you start packaging.


Una vista peculiar de la Galaxia en donde vivimos.


Tumbleweed-black-greenTumbleweed had one snapshot so far this week that brought more appeal to users of openSUSE.

Snapshot 20151123 changed fonts for openSUSE. The terminal font changed to Adobe Code Pro and Roboto was also added as the default font.

The fonts are not only available in Tumbleweed; users of Leap can update the fonts as an option. The reason for the change was to provide a more appealing, complete font.

Wireshark upgraded to 2.0 in Tumbleweed and the new features are a new user interface. The legacy interface is expected to be removed in Wireshark 2.2. Wireshark’s RPM-based package definition provides the new interface in the “wireshark-qt” package and the old interface in the “wireshark-gtk” package.

Fixes were made for Boost version 1.59 and GStreamer 1.6 and these two are expected to make it into a Tumbleweed snapshot soon.

More updated versions are available in the snapshot and there are three new packages that were added to the reliably rolling distribution.

The three new packages added to Tumbleweed were bundle-lang-common-ca, libpoppler57 and libqpdf17.


Users of openSUSE Leap 42.1 who update will notice several updates are available. Maintenance updates for SUSE Linux Enterprise 12 Service Pack provided updates to Samba libraries, systemd, GNOME and Java. Community fixes were also added and the Machinery Project updated to version  1.16.2.

openSUSE Asia.Summit

openSUSE is coming to Asia. The openSUSE Asia.Summit is Dec. 4 -6 at the National Taipei University of Education. The schedule looks great for this event. There are 46 hours worth of talks at this event. There will be 15 long-talks and 7 workshops.

From customizing openSUSE with SUSE Studio to building laaS Cloud with openSUSE and OpenStack, this summit is something you don’t want to miss. Admission is free and you can still sign up for the event.


No.. I haven’t forget you! I think of you every day, night and if I’m honest all the time. You and you and you and especially you who are reading these lines. This is going to be sort blog entry. I want you to know what you should start doing! Yes just stop being social in internet. Get out of your comfort zone and start spank the monkey (oh.. sorry not spank the monkey this is children approved blog..) er.. learning new stuff.

Start you maker project and learn how to 3D with Blender (it’s marvelous 3D application). After Blender there is no excuse and it’s free (but remember if you really like it give something back). Are you on more on CAD? Learn 3D CAD with FreeCAD (Again amazing tool). Want to ride IoT wave but you don’t have too much money then get new shiny Tiny $5 Raspberry Pi Zero or 9$ C.H.I.P and make your Fritzing electric boogie with ease (and by the way you can commit those boards to library. It’s open source!). You are in music how about doing some DJ:n with linux? Mixxx just got shiny 2.0 RC1 out. Are you more reading type and need something to manage you e-books: Calibre is here to help. Huh so much to do so less time!

Where to get them? openSUSE have RPM for all of them just learn to search them from Packman or from OBS. Sorry to say Raspberry Pi Zero is currently not supported but you can help to add it to ARM boards working with openSUSE same problems with C.H.I.P (If you have Raspberry Pi 1/2 just get image for them from openSUSE ARM image and start hacking). You should learn how to add new repos to YaST2 and add Packman repo for new FreeCAD, Fritzing and Mixxx. Yes! most of them run also on Windows and Mac OS X. Now smile on, thumbs up and get your groove on with title song: De La Soul – Ring Ring Ring (Ha Ha Hey)

Ray Chen: 古典的小趣味

05:06 UTCmember


這兩個終端機小工具可以顯示作業系統的 logo 和簡單的系統資訊

1. screenfetch

如果沒有 -E 的參數,在 KDE 5 會出現

[[ ! ]] Qt: Session management error: networkIdsList argument is NULL


2. linux_logo


linux_logo -L list

可列出所有的 logo


kscreen wayland backend in action

kscreen wayland backend in action

That moment when the application “just works” after all your unit tests pass…

A really nice experience after working on these low-level bits was firing up the kscreen systemsettings module configured to use my wayland test server. I hadn’t done so in a while, so I didn’t expect much at all. The whole thing just worked right out of the box, however. Every single change I’ve tried had exactly the expected effect.
This screenshot shows Plasma’s screen configuration settings (“kscreen”). The settings module uses the new kwayland backend to communicate with a wayland server (which you can see “running” on the left hand side). That means that another big chunk of getting Plasma Wayland-ready for multi-display use-cases is falling nicely into place.


I’m working on this part of the stack using test-driven development methods, so I write unit tests for every bit of functionality, and then implement and polish the library parts. Something is done when all units tests pass reliably, when others have reviewed the code, when everything works in on the application side, and when I am happy with it.
The unit tests stay in place and are from then on compiled and run through our continuous integration system automatically on every code change. This system yells at us as soon as any of the unit tests breaks or shows problems, so we can fix it right away.

Interestingly, we run the unit tests live against a real wayland server. This test server is implemented using the KWayland library. The server runs headless, so it doesn’t do any rendering of windows, and it just implements the bits interesting for screen management. It’s sort of a mini kwin_wayland, the real kwin will use this exact same library on the server side, so our tests are not entirely synthetical. This wasn’t really possible for X11-based systems, because you can’t just fire up an X server that supports XRandR in automated tests — the machine running the test may not allow you to use its graphics card, if it even has one. It’s very easy to do, however, when using wayland.
Our autotests fire up a wayland server from one of many example configurations. We have a whole set of example configurations that we run tests against, and it’s easy to add more that we want to make sure work correctly. (I’m also thinking about user support, where we can ask to send us a problematic configuration written out to a json file, that we can then add to our unit tests, fix, and ensure that it never breaks again.
The wayland test server is only about 500 lines of relatively simple code, but it provides full functionality for setting up screens using the wayland protocol.

Next steps…

The real kwin_wayland will use the exact same library, on the server as we do in our tests, but instead of using “virtual screens”, it does


El cometa C/2013 US10 empieza a ser visible desde Nicaragua.

26 November, 2015

Michael Meeks: 2015-11-26 Thursday

21:00 UTCmember

  • More tinderbox fixage; various nasty dependency issues, unwound a gallery build bootstrapping nasty. Plugged away at other bugs. ESC call in the afternoon, chat with Kendy. Dinner. More hackery until late.


Nebojte se příkazové řádky Linuxu! Je to mocný a přívětivý nástroj. Prakticky shodně funguje příkazová řádka i v Mac OS X, BSD a dalších UNIXových systémech, nejen v Linuxu. Základní znalost Linuxu není nutná. Kurz bude probíhat v Linuxu, ale většina věcí funguje stejně na Mac OS X a dalších UNIXech. Znalosti práce v Linuxu/UNIXu se hodí např. při zpracování molekulárních a jiných dat. MetaCentrum je služba CESNETu poskytující přístup k obrovské výpočetní kapacitě. Bude-li se kurzu účastnit alespoň jeden člověk nemluvící česky, kurz bude anglicky.

Kurz proběhne v Krajinově posluchárně, Benátská 2, 2. mezipatro, 28.-29. 1. 2016 od 9:00 do 18:00 (s pauzou na oběd:-). Kurz je rozvrhnutý a lze si jej zapsat v SISu

Zájemce o kurz prosím o vyplnění krátkého dotazníku, který mi pomůže s přípravou kurzu a komunikací s účastníky.

Přehled témat (může být upraven podle požadavků účastníků):

  • Co to je UNIX, Linux, GNU, jaký je mezi nimi vztah a jaká je architektura systému, jádro
  • Co to znamená “open-source”, jaké licence se používají, jaká je filozofie, jaký je obchodní model
  • Jaký je rozdíl mezi jednotlivými linuxovými distribucemi, jak se v tom vyznat, jak si vybrat
  • Vyzkoušení pomocí živých CD/USB nebo virtualizace
  • Speciální užití - záchranná CD, BusyBox v embedded zařízeních (NAS a další síťová zařízení, Android, …)
  • Diverzita grafických nadstaveb vs. podobnost v příkazové řádce
  • Instalace, diskové oddíly, jejich vytváření a kontrola
  • Souborové systémy, struktura adresářů Linuxu, jména souborů a jejich konvence, kde se skrývá konfigurace a data
  • Oprávnění souborů, spustitelnost, ACL, další atributy
  • Root a běžní uživatelé, sudo
  • Proč je důležitý dobrý textový editor, jaké jsou možnosti, kódování znaků, rozdíly mezi operačními systémy
  • Příkazová řádka: Shell - Bash a ti druzí
  • Proměnné, cesta ke spustitelným souborům, aliasy, úpravy chování příkazové řádky
  • Terminály a jejich emulátory, vícenásobné přihlášení, virtuální terminály, přihlášení ke vzdálenému serveru
  • Správa software z příkazové řádky (zypper, rpm, apt, aptitude), spuštění skriptu, kompilace
  • Spouštění Java aplikací
  • Základní informace o systému, volné místo, zjištění typu souboru, hardware
  • Uživatelé, změna hesla, správa služeb (SystemD a jiní)
  • Pohyb v adresářové struktuře, hledání
  • Automatické spouštění úloh
  • Sledování systému, procesy a jejich zabíjení
  • Doplňování klávesou TAB, historie, řetězení příkazů
  • Standardn

25 November, 2015

Michael Meeks: 2015-11-25 Wednesday

21:00 UTCmember

  • Mail chew. Fireplace salesman arrived to measure up a couple of rooms. Nursed some tinderbox breakage - odd event ordering bits throwing up pre-existing bugs; nice. Nailed a VBA unit test issue, and another writer SolarMutex issue.
  • Chat with Bjoern, Florian & Thorsten; Lunch. Crunched some update stats, board call, built ESC agenda.
  • Remembered to link to the awesome 1st Packaging as directed by my great Sister in Law & Husband, for any of your of plastic packaging needs; end advert.
  • Helped H. get setup with her first mobile buy / mend / resell iteration. Worked late, while J. at a PCC meeting. Changing global headers is insanely expensive.


¿Tienes un Samsung Ace GT-s5830i al que has instalado nuevas ROMs y quieres volverlo a recuperar? Así lo conseguí yo.


Los que tenemos una especie de “vicio” en destripar máquinas y tratar de escudriñar cómo funcionan, la tecnología nos da muchos “juguetes” en los que saciar nuestro afán de jugar, aprender, pasar malos ratos, descubrir y a veces conseguir (aunque sea a medias) lo que se quiere.

La cosa es que yo tengo ese tipo de móvil, un Samsung Galaxy Ace gt-s5830i, y como he comentado en otra ocasión conseguí rootearlo para eliminar aplicaciones basura que vienen “de serie” con el sistema y que no me interesan para nada. Aqui comenté el proceso:

Pero siempre quise tratar de eliminar Google y por ende Android del móvil, y tratar de instalarle alguna ROM de CyanogenMod, pero aunque había leido alguna cosa nunca me puse a ello, la verdad no me apetecía arriesgarme a dejar inservible el móvil.

Pero a raiz de un artículo del blog del Cangrejo Linuxero (curioso nombre, que espero que algún día nos cuente el motivo) me entró el gusanillo de tratar de probar en el proceloso mundo del “flasheo” de móvil (aka instalarle un nuevo kernel y sistema operativo) y los posibles riesgos de un “brickeo” en toda regla (aka dejarlo inservible y tener un tecnológico pisapapeles a batería).

El artículo en cuestión es este:

En un comentario le pregunté si sabía alguna manera de “flashear” el móvil para instalarle CyanogenMod. El Cangrejo en una respuesta a ese comentario me pasó un enlace de cómo hacerlo, e incluso con un videotutorial, que explicaba el proceso y los enlaces a los archivos a descargar. Después de verlo y leer un poco al respecto, me animé. El proceso en sí no parecía complicado, y parecía funcionar. Dicho y hecho, descargué los archivos necesarios, y me puse manos a la obra.

Lo primero instalar arrancar en modo de recuperación o “recovery” e instalar ClockWorkMod, una aplicación que modifica el menú de “recovery” de nuestro móvil, permitiéndonos más opciones. Hecho eso, basta instalar el kernel en cuestión y la ROM que hayamos descargado. Hecho esto llegan momentos de incertidumbre… ya que el primer inicio después de estas operaciones tarda un poco más de lo habitual…

Mientras arranca el teléfono, ya veo que algo ha cambiado. Al tradicional arranque de mi móvil, le sustituye uno más animado, de una ROM de CyanogenMod, la cosa parece que tiene buena pinta.

Terminado de arrancar, introduco el PIN de mi tarjeta SIM, y ya empiezan los contratiempos, parece que no lo reconoce, por lo que no me deja iniciar el sistema. Retiro la SIM, y vuelvo a arrancar, ahora sí puedo explorar el


Cliquez sur l'image pour l'afficher en taille normale

Nom : Leap-green-254x300.png 
Affichages : 1932 
Taille : 31.8 Ko 
ID : 3237
Antoine vous a présenté, il y a peu, la dernière release openSUSE 42.1 (Leap), si vous voulez en savoir plus, alors voici 2 superbes screencasts réalisés par la chaîne

24 November, 2015

Michael Meeks: 2015-11-24 Tuesday

21:00 UTCmember

  • More struggling with main-loops; product team call. Discovered that the new scheduler has the (non-optimal) idea of setting a MAX_UINT64 timeout in milliseconds to the glib main-loop timeout; and this is really a non-clever idea.
  • Also (thanks Dimstar) managed to find the SRPMs for openSUSE 13.2 which was surprisingly hard (though finding the source in the build-service is easy).
  • Plugged away; tested on windows; Norbert kindly tested on Mac; all good (encouragingly). Read stories for babes.

23 November, 2015

Michael Meeks: 2015-11-23 Monday

21:00 UTCmember

  • A day of E-mail, and lots of calls; 1:1's, partner team meeting, bit of hackery; team meeting; more hackery until late - trying to unwind a lot of evil in the VCL main-loop; we badly need a real 'idle' concept; starting to get to that.

22 November, 2015


For all Ceph interested people in Germany, especially Bavaria: There will be a Linux-Stammtisch next week on 24.11.2015 in Munich. I will present about "Ceph - Overview, Experiences and Outlook". If you are interested, the meeting starts at 19:00 (CET) at the Paulaner Bräuhaus. You find more information and can register here.

There will be also a talk held by Andreas Pöschl from BMW. The topic is: "Erfahrungen bei der Integration von Open Stack in eine Enterprise-Umgebung". And for sure there will be time for networking and beer after the talks and discussion.


Navegación desde Firefox entre las fotografías de Digikam

Michael Meeks: 2015-11-22 Sunday

21:00 UTCmember

  • Off to NCC, Claire spoke, quickly home for a fine roast lunch with M&ampD bid 'bye to them later, slugged a bit. Off to see David, some ladder steadying, and weather-board sawing action together. Home for tea, bed early.

Sankar P: AWStruck

09:17 UTCmember



A long post about my experience with implementing a quiz software in my college, a decade ago and wondering how easy things have become now due to AWS.


In 2002 (iirc) (thirteen years ago, as of composing this post) when I was in college, we had an inter-collegiate technical symposium, where Online Quiz was one of the events. A Microsoft Visual Basic 6.0 (which I personally consider to be one of the best software ever developed) application was developed in-house and installed on about 50 computers, where various contestants from different colleges could come and take the test. However, as Murphy predicted, due to various virus issues, the software failed spectacularly. Some answers/responses got corrupt, accumulation of responses from different machines proved faulty, the scoring went awry in some corner cases, etc. Overall, the application turned out to be total chaos. However, since India is populous, we were able to throw more people at the problem and finish the event, with a lot of manual effort, inspite of a few unhappy participants.

In the planning phase for the subsequent edition of the symposium two years later, a software development committee for formed. It would do all the software for the entire event,  (like creating a website, developing flash/swish videos, software for the individual events, etc.). The quiz event had two rounds, a preliminary round where all the appearing colleges contested and a final round where six (or probably more) top colleges from the previous round were selected. An eloquent person was made incharge of the quiz event. I proposed to the person that we do the software for the preliminary rounds ourselves, instead of depending on the committee. The committee was already swamped with work and they were happy to get rid of a piece that has more chances of failure. Some adventurous people (like Antony) expressed their interest in joining the project. Thus it all began.

The Adventure

Much to the amusement of my roommate Bala, I started with planning the architecture and design on paper (complete with UML diagrams, etc.), instead of starting with coding as is the norm for us those days. Much later I came across an interesting quote by Alan Kay, "At scale, architecture dominates material". Having learnt from the mistakes of the previous years, I made some decisions.

* The software should follow the web (client-server) model, that is getting popular. At least this is an excuse to learn some new (then) technologies, like JSP, Javascript, Tomcat etc.
* The server machine becomes a single point of failure for the entire system. It could prove to be a performance bottleneck to, as our machines were all having a humongous 32 MB of RAM. There was one 64 MB ram in our lab which I planned to use as the server. In our hostel, some had a machine with luxurious 128 MB of RAM, which I was planning to borrow if the need comes.
* The single point of failure, the server should

21 November, 2015

Michael Meeks: 2015-11-21 Saturday

21:00 UTCmember

  • J. out at a Pregnancy Crisis conference in Birmingham with Sarah. Looked after Isaac; H. and N. out to YFC Edwardian tea-party event; played with M. and N. got a bit of work done too.
  • David over in the evening; dinner, really good to catch up with him; M&D over, call with Tom & Becky; J. returned, up late chatting.


¿Quieres que te echa un cable con KDE? Pues aqui tienes!

Echando un vistazo en una tienda regentada por vendedores asiáticos, me he topado con varios artículos comercializados con la marca KDE, no sé si será legal utilizar esa marca…

Aqui me tenéis con un cable de red marca KDE, que supongo que será compatible al 100% con mi escritorio Plasma! :) Aunque el modelo de cable dice que es una CACA!

Otra curiosidad más que se une al Debian kebab que comparti hace un tiempo:

¡Qué cosas!




Έχω αναφερθεί πως μπορεί να βάλει κάποιος στατική IP με την χρήση του YaST. Το συγκεκριμένο άρθρο αναφέρεται στο Raspberry Pi αλλά η χρήση του είναι ίδια και σε υπολογιστή.

Εδώ θα δούμε πως μπορούμε να ορίσουμε στατική IP με την χρήση τερματικού (όχι του YaST ncurses).
Πρέπει να αλλάξουμε 3 αρχεία.

Έστω ότι θέλετε να ορίσετε την IP:

1. Πρώτο αρχείο είναι το εξής:

sudo nano /etc/sysconfig/network/ifcfg-eth0

Εδώ εάν η κάρτα δικτύου σας έχει άλλο όνομα, θα βάλετε το αντίστοιχο όνομα (αντί για eth0). Συνήθως υπάρχει μέσα στον κατάλογο network. Το αρχείο σας πρέπει να το αλλάξετε και να είναι όπως το παρακάτω:


2. Επόμενο αρχείο που πρέπει να αλλάξετε είναι:

sudo nano /etc/sysconfig/network/routes

και να γράψετε την IP του router σας.

default - -

3. Τέλος ελέξτε και το

sudo nano /etc/resolv.conf

και εδώ εισάγετε την IP του router σας. Λογικά θα την έχει πάρει αυτόματα, αλλά για να είστε σίγουροι, τσεκάρετε το αρχείο αν την έχει.


Older blog entries ->