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.

20 March, 2017


Uma nova revisão do que aconteceu esta semana em openSUSE Tumbleweed a versão “rolling release” de atualização contínua da distribuição de GNU/Linux openSUSE.

O anúncio original você pode ler no blog de Dominique Leuenberger, no link abaixo:

Como de costume, Tumbleweed continua em movimento e em um ritmo constante. Nesta 11ª semana dno ano, lançamentos 5 snapshots 0310, 0311, 0314, 0315 e 0316. Houve alguns pequenos hick-ups com a remoção de gcc5 que poderia ser resolvido.

Os 5 snapshots nos trouxeram atualizações importantes como:

  • O GCC5 não está mais disponível nos repositórios. Libffi, que fazia parte do gcc5, foi substituído por uma biblioteca autônoma
  • Postfix 3.2.0
  • Firmware do kernel 20170303 - suporte para mais cartões nvidia
  • Grub2 atualizado com suporte para TPM2.0 causou problemas em sistemas não-uefi. A atualização foi revertida
  • Aplicações do KDE 16.12.3
  • Kernel Linux 4.10.3 
  • Mais atualizações python singlespec 

É ótimo ver esta constante entrada de atualizações, especialmente também porque "itens mais interessantes do" que apenas atualizações de versão. Itens como python singlespec e a forma como os usuários / grupos de sistema são tratados recentemente são apenas grandes exemplos sobre como o openSUSE se move para a frente.

Itens que estão sendo trabalhados atualmente:

  • GCC7 ficará disponível em Tumbleweed (ainda não como compilador padrão)
  • O GNOME 3.24.0 está agendado para lançamento a montante no dia 22 de março. A equipe pretende entregar uma atualização rápida para Tumbleweed logo depois

Se você quiser descobrir onde você pode ajudar nas várias áreas de preparação, você pode sempre olhar para as falhas listadas no painel que você pode encontrar em:

As ISO’s são instáveis, porém se você já utiliza openSUSE Tumbleweed em seu equipamento, simplesmente deverá atualizá-lo mediante o comando “zypper up” assim seu sistema receberá as atualizações.Para realizar o download acesse o link abaixo:

Mantenha-se atualizado e você sabe: Divirta-se!


openSUSE Tumbleweed es una distribución “Rolling Release” en desarrollo continuo. Aquí puedes estar al tanto de las últimas novedades.

Empieza una nueva semana del mes de marzo, a puntito de empezar la primavera. Echemos un vistazo a lo sucedido la semana pasada en openSUSE Tumbleweed la versión “rolling release” o de actualización continua de la distribución de GNU/Linux openSUSE.

El anuncio original lo puedes leer en el blog de Dominique Leuenberger, en este enlace:

Las ISO’s son instalables, pero si ya estás disfrutando de openSUSE Tumbleweed en tu equipo, simplemente deberás actualizarlo mediante “zypper up” o este otro comando que recomiendan en las listas de correo, para disfrutar de esas actualizaciones.

Como viene siendo habitual, se ha publicado un buen número de nuevas actualizaciones, ya que todos los test han transcurrido sin problemas. En concreto se publicaron 5 nuevas “snapshots” (0310, 0311, 0314, 0315 y 0316).

Estas 5 “snapshots” nos han traido notables actualizaciones/cambios:

  • GCC5 ya no estará disponible en los repositorios. libffi,que era parte de gcc5, ha sido reemplazado por una sola libreria
  • Postfix 3.2.0
  • Kernel firmware 20170303 – con soporte para más tarjetas nvidia
  • Una actualización de grub2 con soporte para TPM2.0 tuvo que ser revertido por problema con sistemas no uefi
  • Continua la reestructuración de los patrones de instalación
  • KDE Applications 16.12.3
  • Kernel Linux 4.10.3 (4.10.2 también fue publicado esa semana)

Cosas que se están preparando para futuras publicaciones:

  • GCC7 estará disponible en Tumbleweed (aunque todavía no como compilador por defecto)
  • GNOME 3.24.0 está programada su publicación para el miércoles día 22 de marzo. Y se espera que se publique una rápida actualización disponible para los usuarios de Tumbleweed poco tiempo después de eso.

Suena interesante ¿verdad? Y todavía son muchas las cosas que se están preparando.

Si quieres estar a la última con software actualizado y probado utiliza openSUSE Tumbleweed la opción rolling release de la distribución de GNU/Linux openSUSE.

Mantente actualizado y ya sabes: Have a lot of fun!!

Enlaces de interés


19 March, 2017


As long as one sticks to printing PLA, a printer without heatbed is ok, but for ABS or PETG a heatbed is a must.
The TinyBoy2 bed is actually a heatbed, although the wiring is missing, and a thermistor is required as well. The SMELZI controller board has a PWM controlled MOSFET, which is connected to the „HOT-BED“ socket, so making the bed a heatbed is straightforward.

Required Tools:

  • Soldering Iron (80W minimum)
  • Hex screwdriver
  • 2.5 mm Drill
  • File or handheld milling machine (Dremel) or …


  • 100k SMD thermistor (size 0805, or 1206)
  • pair of thick wires (35 cm) for the heater
  • pair of thin wires for the thermistor
  • 2,54 mm 1×2 connector (e.g. Dupont connector)
  • M3x6 screw
  • thin sheet of plastic, ~10×30 mm

1. Adding the thermistor

Added SMD thermistor, 1206 is slightly to large for a 0805 footprint …

The heatbed has a footprint for a SMD size 0805 thermistor on the bottom center.
Any 100k thermistor with a beta of 3950 will do, if the beta differs you have to adjust the firmware.
I used a Vellemann K8200 spare part thermistor. With a size of 1206 it is slightly to large so it does not fit exactly, but from a functional point of view it does its job.
After soldering it to the heatbed, check its function: measure the resistance of the wire pads on the left edge of the bed, it should show somethink like 30kΩ to 90kΩ, slowly going up while it cools down after soldering.

2. Soldering the wires to the bed

As the bed is aluminium, soldering anything to it can be tricky, and you need a powerful soldering iron to get the solder to temperature. I ended up using two soldering irons simultaneously, one on each end of the solder blob.

The two wires for the heater go to the larger pads, the thermistor sensing cable has to be connected to the smaller pads. As we are connecting resistors here, direction does not matter.

3. Creating a strain relief for the wires

The wires will be bent all the time while the bed moves in the Y direction, so we need a strain relief or the cables will break after short time of operation.

I drilled a 2.5 mm hole into the red bed bracket/slide and pushed a M3 screw into it. The strain relief is created from a small sheet of plastic, size 10×30. Pick 3 small holes into the plastic, at 5, 15 and 25 mm from the edge. Wrap it around the cables, the holes should line up. After assembling, it should look similar to this:

Heater cables (red), temperature sensing cables (striped)

It is important the cables do not extend beyond the edge of the slide, otherwise the cables will colide with the case.

4. Creating a duct from the top to the bottom

The cable has to go from the printing area through the acrylic glass plane to the bottom

Michael Meeks: 2017-03-19 Sunday.

21:00 UTCmember

  • Off to NCC at The Stable; did the kids work with Klara downstairs - fun. Back for a pizza lunch, snoozed with J. for a while. Pottered around with babes. Out for a walk with Sue & Russell & back for tea. Put babes to bed.


Dear Tumbleweed users and hackers,

As usual, things keep on moving at a steady pace. Week 11 brought us 5 snapshots (0310, 0311, 0314, 0315 and 0316). There were a few minor hick-ups with the removal of gcc5 which could be sorted out.

The 5 snapshots brought us those noteworthy updates / changes:

  • GCC5 is no longer available in the repositories. libffi, which was part of gcc5, has been replaced by a standalone library
  • Postfix 3.2.0
  • Kernel firmware 20170303 – support for more nvidia cards
  • One grub2 updated with support for TPM2.0 caused issues on non-uefi systems. Update was reverted
  • Work towards splitting the pattern packages into smaller chunks that can then have different maintainers
  • KDE Applications 16.12.3
  • Linux kernel 4.10.3 (4.10.2 was also shipped in that week)
  • Even more python singlespec updates

It’s great to see this steady incoming of updates, especially also ‘more interesting things than just version updates. Things like python singlespec and the way system users/groups are newly handled are just great examples on how openSUSE moves forward.

Things that are currently being forged:

  • GCC7 will become available in Tumbleweed (not yet as the default compiler though)
  • GNOME 3.24.0 is scheduled for upstream release on Wed, Mar 22. The team aims to deliver a quick update for Tumbleweed shortly after

And I’m sure the hackers and packagers will come up with even more fun stuff.


The TinyBoy2 is a Indiegogo backed 3d printer. On the plus side, it is very small (16×18 cm² desk space), and it does it jobs.

Like a lot of crowd funded projects, there is essentially no after campaign support. The firmware is a hacked version of Marlin 1.1.0-RC3. The code for the firmware which is shipped with the hardware is supplied as a code drop, but there is no changelog, and the diff to the upstream RC3 contains a lot of awkward changes, e.g. changes to the display SPI code, although the TB2 display uses I₂C. The diff between the code drop and RC3 is 53 files changed, 2196 lines removed, 2072 lines added.

As I wanted to update my printer to a recent firmware (RC3 was tagged December 2015) to get all the new features and bugfixes, and also to change the FW behaviour, I started with the current Marlin GIT, and added the necessary changes on top.

The nice part is that current Marlin is completely capable to drive the printer, support is mostly added by creating a suitable Configuration and setting the right pins for steppers, PWM, encoder and so on. The changes have been submitted upstream, or you can just pull the patched tree from my Marlin github repo.

Download the compiled firmware

In case you do not want to compile the FW yourself, I have prepared 4 variants: L10/L16, both with and without heatbed support:


Hash: SHA1

bd1af0b14e81c344d5ecac27a7c8ba09aaa96a0c  Marlin_TB2_L10_HeatBed.hex
fd754b2b9f0ff7271eb53c9cc9f022eee1b247b8  Marlin_TB2_L10.hex
f330e4ec2a3fcc32510c15b8f9c776731aa98598  Marlin_TB2_L16_HeatBed.hex
cc239598f0fe9ba0ccccb31b007c896c1595dea9  Marlin_TB2_L16.hex


Flashing the firmware

Although it is possible to use Arduino to flash the firmware, I consider it much to bloated for the task, and as it uses avrdude behind the curtains, I prefer to call avrdude directly:

Backup shipped FW (sorry, not verified):

avrdude -p m1284p -b 57600 -c arduino -P /dev/ttyUSB0 -U flash:r:Backup.hex:i

Update to new FW:

avrdude -p m1284p -b 57600 -c arduino -P /dev/ttyUSB0 -U flash:w:Marlin.hex

(Update 2017-03-19 18:49 UTC: Added flashing paragraph)

18 March, 2017

Michael Meeks: 2017-03-18 Saturday.

21:00 UTCmember

  • J. out to take H. and M. to "Shine"; got on with some plumbing bits with M. machined a new tap chain connector out of aluminium sheet together. J. back, out to buy some marine plywood with M. Lunch.
  • Knocked together some shelves for walking boots in the porch together in the afternoon. Out to Sandy's birthday party in the evening; nice to see Daniel, Adeline & family there too. H. to Charlotte's for birthday 'sleep'-over.


I went to Chemnitzer LinuxTage last weekend. That was a successful open source event.

openSUSE has got a lot of positive feedback. Some people changed from Ubuntu to openSUSE Tumbleweed and are happy.

There was some misunderstanding with the new release development of openSUSE Leap. Some people thought that would be a second rolling release by openSUSE. After explaining that we want to do that only in the development phase for achieving a more stable operating system and we will have a release day every year again, these cusomers have been happy again and like this idea. More stability is a good reason. 🙂

invis server had his meeting about their new project openSUSE SMB. One openSUSE customer was interested for this project and I brought him to Stefan. Some booth visitors want to visit our next oSC in Nuremberg.

We had more customers than in the year before. Somtimes guys asked how to change to us and to contribute. Linux beginners wanted to have live CDs. We burned flash drives with Tumbleweed live images for them.

Sunday we had a raffle at our booth. The award was a big chameleon. You can see the winner on the picture.At the end I took part of the raffle by Thomas Krenn AG. 🙂

They produce server hardware and storage. Their first award was a low energy server which I won. That‘ s ideal for students like me. The best thing is that this server hardware is supported by openSUSE.

Chemnitzer LinuxTage was a fantasic open source event like every year. Thanks for the sponsoring!

17 March, 2017


As a founding member of our surf club, I’ve decided to do what what was long overdue and took my second surfing lesson.

Surfspot, Scheveningen's harbour pierSurfspot, Scheveningen’s harbour pier

I went to a surfschool in Scheveningen at the North Sea, got in touch with an instructor, and after going over the water situation, currents, swell and technique, we went into the water for a good one and a half hours. There was a good swell, and next to the harbour’s pier, we were mostly out of the wind. After building up some skills, like catching waves and paddling into them, I managed to ride out a few waves, onto the beach. Not over a long distance, but at least I didn’t fall for a few seconds, a few times. Pretty good progress. Next try planned on sunday, weather allowing. It’s still the North Sea, and it’s still winter, so things can get nasty…

The water temperature was 9°C, which seems cold. I wore my 7mm full-length suit, 3mm gloves and a 5mm hood. It didn’t feel cold even in my fingertops after getting out of the water, so even in March, the North Sea is already very manageable.

Surfing was great fun, it’s an interesting break from diving in that it’s much more physically active. In diving, you tend to spend as little energy on anything as possible. That means that if you’re a good diver (and in the right conditions), you actually burn very little energy. That means you’re getting cold much quicker. Bodysurfing, on the other hand means that you’re constantly moving through the swell, swimming, paddling, getting up, falling, so you end up burning a lot of energy. The cold splash of water is really welcome then.

As opposed to diving, there is no buddy system in surfing, so you can go surfing on your own (under the right conditions, of course). That makes it a bit more flexible than diving. It also trains different muscle groups, especially arms and shoulders, so it complements diving well.

Waves are awesome. :)

Michael Meeks: 2017-03-17 Friday.

21:00 UTCmember

  • Up; out to NCC for Men's Prayer Breakfast; mail chew. Partner call. Lunch.
  • Slightly scary with J. training in bereavement counselling to see a calendar appointment labelled: Sudden and Traumatic Death.
  • Hackery left & right, chat with Eloy.

Como instalar o jogo Trigger Rally no Ubuntu, OpenSUSE e sistemas derivados

Gosta de dirigir em terreno acidentado? Experimente o jogo Trigger Rally. Se você quiser experimentar esse game, veja aqui como instalar ele no Ubuntu, OpenSUSE e sistemas derivados.

Leia o restante do texto "Como instalar o jogo Trigger Rally no Ubuntu, OpenSUSE e sistemas derivados"


Facebook, Google, Amazon, son grandes conocidos por comerciar con tus datos. Pero hay muchas otras empresas que generan, compran y los venden. Los datos que generas son un gran valor en esta sociedad.

Si Facebook (por ejemplo) no te cobra por crear una cuenta en su red social y poder comunicarte con tus conocidos y compartir tu vida con ellos por ese medio ¿cómo es posible que sea una de las empresas más beneficiosas y su creador una de las personas más millonarias del mundo?

¿Publicidad? Sí mueve dinero, pero sin duda no es el grueso de los beneficios. ¿Entonces con qué pueden comerciar? La respuesta es con los datos que tu generas. El “big data”

Hoy en día en nuestra sociedad hiperconectada e hiperdependiente de las telecomunicaciones, somos monitorizados de una forma muy precisa.

Generamos una cantidad ingente de datos al utilizar internet ya sea en diversos modos, y en diversas plataformas por los que un montón de empresas pagan cantidades enormes de dinero por no sólo tener esos datos si no por tener la capacidad de cruzarlos, entenderlos, y clasificarlos de alguna manera beneficiosa para ellos o para otras empresas.

El “big data” hace referencia a toda esa cantidad ingente de datos de personas como tu o yo que utilizamos internet. Y a las empresas que crean los algoritmos que “traducen” esa cantidad de datos en información muy valiosa para según qué empresas o sectores.

Todo esto viene a colación de un documental realizado por RTVE que he visto hace poco y que me resultó interesante. Puedes verlo y descargarlo desde archive.org y es este que te presento a continuación.

También puedes verlo en la web de RTVE en la sección de documentales en el programa Documentos TV en este enlace:

Realmente no sé si es tan imprescindible el estar permanentemente conectados ni si esos supuestos avances de esa interconexión merecen la pena de teniendo en cuenta la pérdida de intimidad o el seguimiento que se hace de las personas.

Te levantas por la mañana y la aplicación del móvil (Android o Apple) que utilizas como despertador envía cuantas alarmas tienes activadas y cuantas utilizas y los días que lo haces. Consultas tu Facebook y tu correo de Gmail. Mandas un “Guasap” ves unos vídeos de YouTube. En tu portátil con Windows vuelves a consultar Gmail.

Juegas en tu mólvil o tablet a un juego que te has descargado de la “store” pasas un nivel y lo compartes por las redes a tus contactos. Subes un par de “selfies” a Instagram, y una notificación de amistad en Facebook hace que etiquetes a un par de amigos, sus caras quedan registradas a sus nombre y perfiles. Compartes un par de noticias de tal o


We'll be moving some of our servers on Friday, March 17 starting at 3pm UTC. It will take a few hours. We're sorry about possible service outages.

openSUSE Leap 42.2 安裝小記

桌機的 HD 無預警的升天了......
所以就直接進行升級 :p

記下我安裝 openSUSE Leap 42.2 的相關過程給自己參考
想不到上次裝 openSUSE Leap 42.1 是 2015/12


因為就算安裝 中文輸入法也沒有出現, 所以就用之前的方式
移除 ibus
#yast2  sw_single

取消 ibus  套件

取消 CD 為安裝來源
# yast2  repositories

Google Chrome:

使用one click install 安裝 http://software.opensuse.org/package/freemind
我是使用 editors 那個來源的 ymp 檔案安裝

.mm 的檔案指定用 freemind  開啟

新增 Packman 套件庫:

使用 #yast2  repositories 手動加入 NCHC Packman 套件庫

#yast2  repositories


Firefox download helper:

# zypper   install   flash-player


因為 mplayber 與 smplayer 不知道為何播放 .mp4 有點問題, 但是使用 VLC 就沒有問題
所以我就安裝 VLC Media player

並將 .rmvb 以及 .mp4 預設播放器設定為  VLC

目前的版本是 的版本

#wget  -O  skype-`date +%F`.rpm   http://www.skype.com/go/getskype-linux-beta-suse

下載的 rpm 會被命名為 skype-日期.rpm

因為目前 rpm base 的OS, skype 只有提供 32 bits 的套件

參考 http://en.opensuse.org/SDB:Skype  但是還是有些遺漏, 所以要安裝一些套件

# zypper  -n  install  libqt4-32bit   libqt4-x11-32bit   libpng12-0-32bit
# zypper  -n  install  libXss1-32bit  libQtWebKit4-32bit   libQtWebKit4
# zypper  -n  install  libXv1-32bit  xorg-x11-libs

安裝 skype 套件
# rpm -ivh skype*.rpm

使用 #yast2 sound 調整音效


使用 # zypper install dropbox 來安裝, 因為發現版本比 software.opensuse.org/search 上面新

安裝完之後在終端機下 dropbox  start  -i  來安裝

安裝 GNOME Control center
# zypper  install  yast2-control-center-gnome

然後修改 /etc/sysconfig/yast2

# vi   /etc/profile.d/ls.bash
把 root 的 LS_OPTIONS 的 -A 移除

.7z 支援:
# zypper  install  p7zip


PDF Viewer 安裝:
因為預設的 PDF Viewer 中文顯示有問題所以使用 Foxit

Forticlient SSL VPN 安裝:
Dropbox 內2013/packages 的 source code
# zypper install libgthread-2_0-0-32bit

# yast2  printer

rdesktop 安裝與測試:
#zypper  install  freerdp

#xfreerdp  -g  1280x1024  -u administrator  HOST_IP

VMware workstation Pro 12

安裝 kernel-default-devel  
# zypper   install   kernel-default-devel
# ./VMware-Workstation-Full-12.5.2-4638234.x86_64.bundle

裝完後, 設定取消 share VM access

Yubico Key:
如果 linux 沒有抓到 Yubico 的 U2F Key可以使用以下步驟
讓 linux 支援 Yubico , 我是參考 https://www.yubico.com/faq/enable-u2f-linux/  
存到 /etc/udev/rules.d/70-u2f.rules
將 linux 重開機, 接下來就可以使用了 :-)

smartgit 安裝:

下載 8.0.3

解壓縮到 /opt
# tar  zxvf   smartgit-linux-8_0_3.tar.gz  -C   /opt/

建立 link 讓一般使用者也能使用
# ln  -s   /opt/smartgit/bin/smartgit.sh   /usr/local/bin/smartgit

安裝 git
# zypper  install  git

建立 個人的 ssh key
> ssh-keygen  -t  dsa

將 ssh 的公鑰 id_dsa.pub 新增到 Github 的 Settings -- >  SSH and GPG Keys

接下來就是以一般使用者的身份執行 smartgit 指令
> smartgit


設定 smart git icon 使用 alacarte

在設定好之後發現無法直接開啟資料夾 ( 資料夾上面按右鍵 -- > Open )
Edit -- > Preferences --> 點選  Tools -- > 點選 Re-Add Defaults 得到解決
2016-11-24 15-48-28 的螢幕擷圖.png

ansible 安裝:
#zypper  install  ansible

安裝 pysphere:

為了 ansible and VMware Module

# zypper  install  python-pysphere

Docker 安裝:

#zypper  install  docker

#systemctl  start  docker
#systemctl  enable   docker

Franz 安裝:

將網路換回 NetworkManager - cause wifi select

~ enjoy it

16 March, 2017


When speaking of virtualisation (container-wise) there are two major alternatives: Docker and LXC. If I were deploying web applications I would probably go for Docker, very easy to set up a Docker file installing nginx, php-fpm, etc and doing a few commands to set it up. Docker is not designed for running full machines, you can basically just start one command, that’s it. On the other hand, LXC, you get full machines with a minimal virtualisation layer providing excellent performance. The disadvantage is that you will use more space/memory for running something similar to full machines.

This site provides a wide selection of ready container images, however the openSUSE image is version 13.2 which is running out of support. I could use that image and upgrade it, however they ran install patterns-openSUSE-minimal_base without –no-recommends so you get all sorts of interesting stuff like Mesa you will not need on a server. So I decided to build my own image. It is quite easy, you will basically just need a tarball of the rootfs and a metadata file. On an openSUSE machine the rootfs can be created very easily, thanks to the –root option of zypper. I created a bash script to create a rootfs.tgz, just run it with the requested tarball as argument, i.e. sh make-container.sh /home/you/rootfs.tgz and you are good to go. The script looks like this

tmpdir=`mktemp -d`
echo "Creating tempdir $tmpdir"
zypper -n --root $tmpdir ar -G http://ftp.gwdg.de/pub/opensuse/distribution/leap/42.2/repo/oss/ repo-oss
zypper -n --root $tmpdir ar -G http://ftp.gwdg.de/pub/opensuse/update/leap/42.2/oss/ repo-update
zypper -n --root $tmpdir in --no-recommends patterns-openSUSE-minimal_base iputils net-tools nano timezone
cat <<EOF > $tmpdir/etc/sysconfig/network/ifcfg-eth0
cd $tmpdir
tar cfzv $1 *
rm -rf $tmpdir

Now you have a tarball, you will need a metadata.yaml file:

architecture: "x86_64"
creation_date: 1458040200
 architecture: "x86_64"
 description: "openSUSE LEAP 42.2"
 os: "opensuse"
 release: "leap42.2"

Now you need to pack the metadata.yaml into metadata.tgz. You can import the image into the lxc host in the following way:

# lxc image import metadata.tgz rootfs.tgz --alias=leap

Now you are ready to spin up an instance of the image

# lxc launch leap machinename
# lxc exec machinename bash

That’s it. You need to set the hostname in /etc/hostname, you can use lxd to get networking and NAT.

Michael Meeks: 2017-03-16 Thursday.

21:00 UTCmember

  • Mail chew, customer call; built ESC bug stats, lunch. Spent a while mending the admin console auth token problems with http - fun. ESC call. More admin cleanup & re-factoring.

Como converter vídeo em imagens usando o FFmpeg

Já pensou em transformar um vídeo em um grande conjunto de imagens? Pois então veja como converter vídeo em imagens usando o FFmpeg.

Leia o restante do texto "Como converter vídeo em imagens usando o FFmpeg"

Como instalar o Visual Studio Code no Linux manualmente

A Microsoft lançou seu novo editor de código multiplataforma, que aliás, possui uma versão para o Linux. Se você ficou curioso para experimentar, veja aqui como instalar o Visual Studio Code no Linux.

Leia o restante do texto "Como instalar o Visual Studio Code no Linux"

Como instalar a versão mais recente do VirtualBox no Linux

Se você usa o virtualizador desktop da Oracle e quer estar sempre com as últimas funcionalidades a sua disposição, veja nesse tutorial como instalar a versão mais recente do VirtualBox no Linux.

Leia o restante do texto "Como instalar a versão mais recente do VirtualBox no Linux"

Como instalar facilmente o compilador e vários outros itens relacionados a linguagem Go

Se você é ou pretende ser usuário da linguagem Go, veja como instalar facilmente o compilador e vários outros itens relacionados a essa linguagem.

Leia o restante do texto "Como instalar facilmente o compilador e vários outros itens relacionados a linguagem Go"


Le samedi 25 Mars 2017, nous organisons notre Journée Mensuelle du Logiciel Libre à la Maison St Sever à Rouen. (Centre Commercial St Sever, 10-12 rue Saint-Julien 76100 Rouen) de 14h00 à 18h00. Rouen, Normandie. On fera connaissance avec la toute dernière version de openSUSE, la openSUSE Leap 42.2, Gnome 3.16.2, LibreOffice et beaucoup d’autres distributions […]

Como instalar o Kernel 4.x nos sistemas baseados em RPM

O kernel 4.x está sendo atualizado continuamente. Por isso, se você precisa instalar ou atualizar o Kernel 4.x nos sistemas baseados em RPM, veja abaixo como fazer isso.

Leia o restante do texto "Como instalar o Kernel 4.x nos sistemas baseados em RPM"


Today: But what if I need a new kernel?

A driver update (DUD) can of course update a single driver. But if that’s not enough and you need a whole new kernel to run an installation?

There are two parts to solve:

  1. replace the kernel used during installation and
  2. get the new kernel installed

We’ll need two tools for this (both available in Tumbleweed or here: mksusecd and mkdud).

1. Replace the kernel used during installation

For this it’s important to know which kernel packages you’ll actually need. Typically it will be kernel-default and kernel-firmware. But older SUSE distributions (SLE 11 comes to mind) had the kernel packages split into kernel-default and kernel-default-base – you’ll need them both.

To make things confusing, modern SUSE distributions also have kernel-default-base – but it’s an alternative to kernel-default. In this case we don’t need it.

If unsure, check kernel-default. If it contains the actual kernel (e.g. /boot/vmlinuz) then you don’t need kernel-default-base.

On some architectures modules are also taken from xen-kmp-default. If that’s important for you, you can add this package to the kernel list as well.

In fact you can add any number of kernel packages or kmps you like.

In the past, sometimes a different kernel flavor was used. For example PowerPC had kernel-ppc64 for a while. Simply use the flavor you need.

It’s a good idea to gather all the kernel rpms into a single directory for easier use:

> mkdir k
> cp kernel-default.rpm kernel-firmware.rpm k
> cp kernel-default-base.rpm k    # only if needed
# add any kernel-related rpms you need

Then, take your SUSE installation iso and run

> mksusecd --create new.iso \
  --kernel k/* -- \

Note that the --kernel option accepts a variable number of arguments, so you have to add an isolated -- to terminate the argument list properly.

The output could look like this:

> mksusecd --create new.iso \
  --kernel k/* -- \
kernel version: 3.0.101-63-ppc64 --> 3.0.101-94-ppc64
CHRP bootable (ppc64)
building: 100%
calculating sha1...

The command above will actually get the list of required modules from the old installation iso. If you are missing some driver or the new kernel comes with some additional driver, the module will not be added to the new iso.

But there’s the --modules option. It will add the listed modules together with any implicitly required modules via module dependencies.

For example, let’s add the airport wifi-module to our PowerPC iso:

> mksusecd --create new.iso \
  --kernel k/* \
  --modules airport -- \
kernel version: 3.0.101-63-ppc64 --> 3.0.101-94-ppc64
kernel modules added:
  airport, cfg80211, orinoco
CHRP bootable (ppc64)
building: 100%
calculating sha1...

As you can see, it automatically adds orinoco and cfg80211 as well.

2. Get the new kernel installed

This is relatively simple. A driver update can do this:

> mkdud --create foo.dud \
  --dist sle11 \
  --install repo \

This creates a driver update for SLE 11 (which also applies to SP4) and the kernel rpms are installed


During last week I've noticed several interesting posts about challenges being free software maintainer. After being active in open source for 16 years I can share much of the feelings I've read and I can also share my dealings with the things.

First of all let me link some of the other posts on the topic:

I guess everybody involved in in some popular free software project knows it - there is much more work to be done than people behind the project can handle. It really doesn't matter it those are bug reports, support requests, new features or technical debt, it's simply too much of that. If you are the only one behind the project it can feel even more pressing.

There can be several approaches how to deal with that, but you have to choose what you prefer and what is going to work for you and your project. I've used all of the below mentioned approaches on some of the projects, but I don't think there is a silver bullet.

Finding more people

Obviously if you can not cope with the work, let's find more people to do the work. Unfortunately it's not that easy. Sometimes people come by, contribute few patches, but it's not that easy to turn them into regular contributor. You should encourage them to stay and to care about the part of the project they have touched.

You can try to attract completely new contributors through programs as Google Summer of Code (GSoC) or Outreachy, but that has it's own challenges as well.

With phpMyAdmin we're participating regularly in GSoC (we've only missed last year as we were not chosen by Google that year) and it indeed helps to bring new people on the board. Many of them even stay around your project (currently 3 of 5 phpMyAdmin team members are former GSoC students). But I think this approach really works only for bigger organizations.

You can also motivate people by money. It's way which is not really much used on free software projects, partly because lack of funding (I'll get to that later) and partly because it doesn't necessarily bring long time contributors, just cash hunters. I've been using Bountysource for some of my projects (Weblate and Gammu) and so far it mostly works other way around - if somebody posts bounty on the issue, it means it's quite important for him to get that fixed, so I use that as indication for myself. On attracting new developers it never really worked well, even when I've tried to post bounties to some easy to fix issues, where newbies could learn our code base and get paid for that

15 March, 2017

Michael Meeks: 2017-03-15 Wednesday.

21:00 UTCmember

  • Off to Cloud Expo Europe in the morning; hacked on mail and the Admin console on the train. Switched it over to non-blocking I/O on the train.
  • Out in the evening with J. great that H. can baby-sit, lovely to have a quiet drink & catch-up together.

Como converter vídeos com Avidemux sem complicações

Se você procura uma forma de converter vídeos de qualquer formato para um que você precisa, veja nesse tutorial como converter vídeos com Avidemux sem complicações.

Leia o restante do texto "Como converter vídeos com Avidemux sem complicações"


Since openSUSE Tumbleweed has been upgraded to use rpm 4.13 (snapshot 2017033), you keep on seeing the message “warning: Unsupported version of key: V3” whenever you invoke zypper or rpm. Of course this is highly annoying, and you just want to stop it, right?

First, a bit of background:
RPM uses gpg infrastructure to validate package signatures. As is common, this infrastructure is being developed and the various key formats are versioned. As old formats become obsolete and considered insecure, they are no longer being supported by modern tools. This helps to improve security insofar to not give the user a false sense of safety: a key that is insecure is worth as much as no key at all.

So, let’s stop zypper / rpm annoy you with this! If it’s already not going to use the gpg key, we can as well just get rid of it. But HOW!?

First, we need to find out the ID (or IDs) of the key(s) causing it. RPM can be a bit more verbose when asked to be so, and then it gives us some hints:

rpm -vv -qf /etc
And this will reply with something like

ufdio: 1 reads, 18883 total bytes in 0.000006 secs
D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key
D: couldn’t find any keys in /var/lib/rpm/pubkeys/*.key
D: loading keyring from rpmdb
D: opening db environment /var/lib/rpm cdb:private:0x201
D: opening db index /var/lib/rpm/Packages 0x400 mode=0x0
D: locked db index /var/lib/rpm/Packages
D: opening db index /var/lib/rpm/Name nofsync:0x400 mode=0x0
D: read h# 168 Header sanity check: OK
warning: Unsupported version of key: V3

D: read h# 335 Header sanity check: OK
D: added key gpg-pubkey-7e2e3b05-4be037ca to keyring
D: read h# 390 Header sanity check: OK

I highlighted the interesting parts here for your viewing pleasure. 168 actually refers to the internal id in the rpm database of the key it just complained about.

So, let’s find out what key this is:
rpm -q --querybynumber 168

and you get something like gpg-pubkey-7e2e3b05-4be037ca as reply. With this information, you can find out what key it is – just to satisfy your hunger for information. If you believe that the key in question is still in use, you might want to inform its owner.

rpm -qi gpg-pubkey-3d25d3d9-36e12d04

warning: Unsupported version of key: V3
Name : gpg-pubkey
Version : 3d25d3d9
Release : 36e12d04
Architecture: (none)
Install Date: Tue 06 Jul 2010 07:39:17 AM CEST
Group : Public Keys
Size : 0
License : pubkey
Signature : (none)
Source RPM : (none)
Build Date : Tue 06 Jul 2010 07:39:17 AM CEST
Build Host : localhost
Relocations : (not relocatable)
Summary : gpg(SuSE Security Team )
Description :
Distribution: (none)

This is indeed an old GPG key – from SUSE. As this machine has been updated using zypper dup for such a long time, it’s no surprise some cruft like this accumulated. That key has long

Como instalar a versão multiplataforma do IRPF 2017 no Linux manualmente

E chegou a hora de acertar as contas com o leão, por isso, se você quer fazer sua declaração do imposto de renda pessoa física no Linux, veja aqui como instalar o programa IRPF 2017 no Linux.

Leia o restante do texto "Como instalar o programa IRPF 2017 no Linux"

<- Current blog entries