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 June, 2016


Tomorrow the German OpenStack Days 2016 (Deutsche OpenStack Tage) will start in Cologne. I will give a talk on Ceph and OpenStack about "OpenStack at 99,999% availability with Ceph".

It seems the event is already sold out completely, but as far as I know the presentations (mostly conducted in German) will be recorded and available after the conference. If you have already a ticket, have a interesting OpenStack conference in Cologne!


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


Una nueva revisión de lo que ha acontecido esta semana 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” para disfrutar de esas actualizaciones.

Esta semana ha sido una semana con mucha actualidad. De nuevo se han liberado 4 nuevas instantáneas de openSUSE Tumbleweed (0609, 0611, 0612 y 0613) y con estas llega el final de una época, el final de Tumbleweed compilado con GCC5. Como es normal, el final de una época significa el inicio de algo nuevo.

Ahora las nuevas versiones serán compiladas utilizando la nueva versión de GCC como compilador, es decir GCC 6 como compilador de la distro openSUSE Tumbleweed.

Pero primero echemos un vistazo a lo que ofrecen estas instantáneas:

¿Que hay preparado para el futuro? como se ha mencionado, la próxima instantánea, la que será la 0614, está ya siendo compilada con GCC6 lo que hará que sea una gran actualización de paquetes de software.

Es una gran labor ya que están surgiendo errores en la gran cantidad de paquetes que tienen que ser compilados. Puedes si te apetece participar en la depuración de errores.

Pero el desarrollo no para y nuevos paquetes llegan a Tumbleweed, y de esta a todos los usuarios que están así disfrutando de lo más novedoso, como por ejemplo:

  • Qt 5.6.1
  • KDE Applications 16.04.2
  • KDE Framework 5.23.0
  • TeXLive 2016
  • GIT 2.9.0

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

Enlaces de interés



19 June, 2016

Michael Meeks: 2016-06-19 Sunday.

21:00 UTCmember

  • Up; Fathers Day cards; out to NCC - Roy spoke; home for a fine BBQ lunch; with Baked Alaska - wow. Watched The Martian - which (apart from some gratuitous language) was good fun for the babes. Party left-overs, put babes to bed.


Mozilla recently announced a new feature that is being tested in the Firefox browser called “Contextual Identities”. The idea behind this feature is that users will be able to separate different types of browsing into different identities, allowing them to protect their data with more control. The images below were all taken from the announcement page and should provide a good example of how this feature works.

Unlike Private Browsing Mode which is a temporary store, and wipes everything when it ends, these Contextual Identities will allow storage of certain data so that things like history are not lost but cookies and other sensitive data is still protected. You may wonder what makes these different from profiles/users and from what I can tell, its simply that these are more seamless and can be loaded at the same time so all you need to look for is the visual cues to know what context you are browsing in.




All in all I think this is a very neat feature and look forward to seeing how Mozilla improves it in the future (also if Chrome will implement a similar feature). If you are interested in learning more about this feature and how to use it, head on over to the Mozilla announcement here and check it out.

18 June, 2016

Michael Meeks: 2016-06-18 Saturday.

21:00 UTCmember

  • Up earlyish; slugged - cooked breakfast; a 39th birthday - nearly officially 'old'; some nice cards & presents. Barabara & Colin popped in - a nice surprise, and Mary Rogers too - lovely. Prepped for E's party lunch.
  • Into Cambridge on the train with H. and N. - started them on Truckers; went Bowling with the David, E. and lots of small people - fun; home for a party tea, and a series of games.
  • Neve had a sleep-over, plus Simpsons The Movie with E. Bed.

Now that Nextcloud 9 is out, many users are already interested in migration so I'd like to address the why and how in this blog post.

Why migrate

Let's start with the why. First, you don't have to migrate yet. This release as well as at least the upcoming releases of own- and Nextcloud will be compatible so you'll be able to migrate between them in the future. We don't want to break compatibility if we can avoid it!

Of course, right now Nextcloud 9 has some extra features and fixes and future releases will introduce other capabilities. With regards to security, we have Lukas Reschke working for us. However, we promise that for the foreseeable future we will continue to report all security issues we find to upstream in advance of any release we do. That means well ahead of our usual public disclosure policy, so security doesn't have to be a reason for people to move.

Migration overview

If you've decided to migrate there are a number of steps to go through:
  • Make sure you have everything set up properly and do a backup
  • Move the old ownCloud install, preserving data and config
  • Extract Nextcloud, correct permissions and put back data and config
  • Switch data and config
  • Trigger the update via command line or the web UI
Note that we don't offer packages. This has been just too problematic in the past and while we might offer some for enterprise distributions, we hope to work together with distributions to create packages for Nextcloud 9 and newer releases. Once that is done we will of course link to those on our installation page.

There are other great resources besides this blog, especially this awesome post on our forums which gives a great and even more detailed overview of a migration with an Ubuntu/NGINX/PHP7/MariaDB setup.


First, let's check if you're set up properly. Make sure:
  • You are on ownCloud 8.2.3 or later
  • Make sure you have all dependencies
  • Your favorite apps are compatible (with ownCloud 9), you can check this by visiting the app store at apps.owncloud.com
  • You made a backup
Once that's all done, time to move to the next step: cleaning out the old files.

Removing old files

In this step, we'll move the existing installation preserving the data and configuration.
  • Put your server in maintenance mode. Go to the folder ownCloud is installed in and execute sudo -u www-data php occ maintenance:mode --on (www-data has to be your HTTP user). You can also edit your config.php file and changing 'maintenance' => false, to 'maintenance' => true,.
  • Now move the data and config folder out of the way. Best to go to your webserver folder (something like /var/www/htdocs/ and do a mv owncloud owncloud-backup

Deploying Nextcloud

Now, we will put Nextcloud in place.

17 June, 2016

Michael Meeks: 2016-06-17 Friday.

21:00 UTCmember

  • Up; out for a run with J, partner call, mail chew; out for a fine lunch with Bruce & Anne; & J. partner call. Wrote LXF column. Submitted backlog of GCloud6 nul returns.
  • Poked at Elize's computer - apparently un-bootable, Windows MBR corruption; odd.


limba-smallI wanted to write this blogpost since April, and even announced it in two previous posts, but never got to actually write it until now. And with the recent events in Snappy and Flatpak land, I can not defer this post any longer (unless I want to answer the same questions over and over on IRC ^^).

As you know, I develop the Limba 3rd-party software installer since 2014 (see this LWN article explaining the project better then I could do 😉 ) which is a spiritual successor to the Listaller project which was in development since roughly 2008. Limba got some competition by Flatpak and Snappy, so it’s natural to ask what the projects next steps will be.

Meeting with the competition

At last FOSDEM and at the GNOME Software sprint this year in April, I met with Alexander Larsson and we discussed the rather unfortunate situation we got into, with Flatpak and Limba being in competition.

Both Alex and I have been experimenting with 3rd-party app distribution for quite some time, with me working on Listaller and him working on Glick and Glick2. All these projects never went anywhere. Around the time when I started Limba, fixing design mistakes done with Listaller, Alex started a new attempt at software distribution, this time with sandboxing added to the mix and a new OSTree-based design of the software-distribution mechanism. It wasn’t at all clear that XdgApp, later to be renamed to Flatpak, would get huge backing by GNOME and later Red Hat, becoming a very promising candidate for a truly cross-distro software distribution system.

The main difference between Limba and Flatpak is that Limba allows modular runtimes, with things like the toolkit, helper libraries and programs being separate modules, which can be updated independently. Flatpak on the other hand, allows just one static runtime and enforces everything that is not in the runtime already to be bundled with the actual application. So, while a Limba bundle might depend on multiple individual other bundles, Flatpak bundles only have one fixed dependency on a runtime. Getting a compromise between those two concepts is not possible, and since the modular vs. static approach in Limba and Flatpak where fundamental, conscious design decisions, merging the projects was also not possible.

Alex and I had very productive discussions, and except for the modularity issue, we were pretty much on the same page in every other aspect regarding the sandboxing and app-distribution matters.

Sometimes stepping out of the way is the best way to achieve progress

So, what to do now? Obviously, I can continue to push Limba forward, but given all the other projects I maintain, this seems to be a waste of resources (Limba eats a lot of my spare time). Now with Flatpak and Snappy being available, I am basically competing with Canonical and Red Hat, who can make much more progress faster then I can do as a single developer. Also, Flatpaks bigger base of contributors compared to Limba is a clear sign


¿Usas Plasma como escritorio y muchas otras aplicaciones de KDE? Que suerte poder hacerlo en tu idioma ¿verdad?


Si eres usuario de KDE podrás disfrutar de todas sus aplicaciones y su entorno de escritorio en tu idioma, o lengua. Así puedes tenerlo en castellano, catalán, gallego, y muchos otros idiomas… vaya ¡qué casualidad! … ¿o no es tal?

Si puedes disfrutar de estas aplicaciones en tu lengua materna, no es por casualidad, ni por generación espontánea, ni porque alguien ha creado un bot que traduce directamente del inglés en todos los idiomas posibles… no!

El motivo por el que tienes disponible el proyecto KDE en tu idioma es porque detrás hay un equipo de personas, como tu y como yo, que en su tiempo libre traducen, revisan, mejoran las aplicaciones para que esten disponibles en muchas lenguas e idiomas.

Esta gente que crea las traducciones es gente que aporta su tiempo, esfuerzo y conocimientos para que toda la comunidad pueda disfrutar de KDE en muchos idiomas. Gente que un día decidió dar un paso más y ayudar de esta manera con un poco de su tiempo, usuarios que son parte de KDE al igual que tu mismo puedes serlo ¿cómo?

Lo primero echa un vistazo a la lista de equipos de traducciones de idiomas disponibles:

Si no encuentras el idioma que quieres puedes incluso ponerte manos a la obra y hacer tu mismo que este disponible. Si está en la lista el idioma con el que quieres colaborar, echa un vistazo a su página donde encontrarás toda la información y respuestas a todas las preguntas de novato que se te planteen. Por ejemplo esta del equipo de traducción al español.

¿Ya estás más animado/a? Pues suscríbete a la lista de correo, es el medio por el que se organizan los equipos, y presentate. Allí tendrás más ayuda y te asignarán tus primeros trabajos para que te vayas familiarizando con las herramientas y el modo de trabajo del equipo.

Importante leer la sección de preguntas más frecuentes y la página de glosario de términos. Esta última sirve para que haya una traducción consistente, similar y sin errores comunes en todas las aplicaciones de KDE.

Participando en el equipo de traducción puede servirte para:

  • practicar tu nivel de idiomas, desarrollando más vocabulario y “obligándote” a leer/escribir en ese idioma.
  • utilizarás herramientas de desarrollo que si bien pueden abrumarte en un principio, una vez que practiques con ellas las manejarás sin problemas.
  • contribuirás con una gran comunidad de software libre en un gran proyecto.
  • harás que el software libre sea más accesible a más gente al ofrecerselo en su propio idioma, facilitando as


Dear Tumbleweed users and hackers,

It has been a very busy week, but it has shown how much enthusiasm every contributor puts into Tumbleweed. There have been again 4 snapshots released (0609, 0611, 0612 and 0613) and this marks the end of ‘Tumbleweed being built using GCC 5’. As usual, one end is just the beginning of something new: starting with Snapshot 0614 (or any higher number, in case openQA won’t agree) the entire distribution is built using GCC 6 as compiler.

Let’s first look back what the four snapshots delivered:

  • QEmu 2.6.0 (we were at 2.4 for way too long, and missed openGL support)
  • Wayland 1.11.0 – stable release (you already enjoyed the RCs though)
  • Mozilla Firefox 47.0
  • Linux kernel 4.6.2 – Some broadcom users were waiting for that
  • A lot of YaST updates – See also the YaST reports for what nice things they work on

What can we expect from the future? As mentioned, snapshot 0614 is currently being built using GCC 6. This will be a rather large update, as literally everything is being rebuilt again. After being in Stagings for quite a while, everything up to Ring2 (stuff on the DVD, ~2200 packages) built. With GCC 6 now being the default compiler, it was expected that quite some of the non-ring packages (another ~ 7000 packages!) will cause some trouble. The build is not all done yet, but we are at around 200 errors that need fixing (see boo#984984 for a reference what still needs work).

And despite all this, no contributor is getting tired and many more, even bigger updates are scheduled in the Staging areas:

  • Qt 5.6.1 – some important bug fixes it seems
  • KDE Applications 16.04.2
  • KDE Framework 5.23.0
  • TeXLive 2016
  • GIT 2.9.0

If there is anything you want to discuss with the community, next week is THE opportunity, as the openSUSE conference will be held in Nuremberg, starting Wednesday, June 22nd. I am looking forward to see you there.

A note regarding the breakage we had seen in snapshot 0605 (pam config files getting overwritten): we have since configured a new test in openQA that installs a current Tumbleweed snapshot and will try to update this new install right to the snapshot that is being tested. This should help us catch such issues next time around.

Let’s have a lot of fun


This week I was invited by Memblaze to give a talk on Data Center Technology Conference 2016 about Linux MD RAID performance on NVMe SSD. In the past 3 years, Linux community make a lot of effort to improve MD RAID performance on high speed media, especially on RAID456. I happen to maintain block layer for SUSE Linux, back port quite a lot patches back to Linux 3.12.

From this talk, I list a selected recognized effort from Linux kernel community on MD RAID5 performance improvement, and how much performance data is increased by each patch (set), it looks quite impressive. Many people contribute their talent on this job, I am glad to say “Thank you all ” !


A slide in Mandarin of this talk can be found here, currently I don’t have time to translate it in English, maybe several months later …

16 June, 2016

Michael Meeks: 2016-06-16 Thursday.

21:00 UTCmember

  • Up early; sometimes it is annoying getting https:// certificates right; but then I poke Orange's website to top-up H's phone - and discover a litany of failures: poor certificates, scripts loaded from elsewhere etc. fun.
  • Postal voted (somewhat reluctantly) for 'Remain' (for now) in the EU election. Built ESC stats. ESC call, JanI call.


Win9X 在存取 Samba Service 時若有出現要輸入 IPC$ 的密碼時, 如


解決方式如下 :

  1. 編輯 /etc/samba/smb.conf , 添加下列描述到 [Global] 內

    lanman auth = Yes
    client lanman auth = Yes
    client plaintext auth = Yes
    client ntlmv2 auth = no

  2. 確認你 Win9X 登入的使用者帳號在 Samba 上面也有一樣的帳號名稱
  3. 重新啟動你的 Samba 服務


15 June, 2016

Michael Meeks: 2016-06-15 Wednesday.

21:00 UTCmember

  • Mail chew; team call; sync. with Philippe, partner call, interview, bed.

OS: openSUSE Leap 42.1

目前 ansible 在 openSUSE Leap 42.1 版本為 1.9.3-1.1
# zypper   search   -v  ansible

S | 名稱    | 類型 | 版本      | 結構   | 套件庫                
 | ansible | 套件 | 1.9.3-1.1 | noarch | openSUSE-Leap-42.1-Oss

參考網路上的 systems management repo

新增 systems management 的套件庫 參考自己先前的文章 (http://sakananote2.blogspot.tw/2016/03/docker-unstable-package-install-with.html )

正在新增儲存庫 Various software for easier management of multiple systems (openSUSE_Leap_42.1) ....................................................[完成]
已成功新增套件庫 'Various software for easier management of multiple systems (openSUSE_Leap_42.1)'
已啟用       : 是                                                                             
自動重新整理 : 是                                                                             
GPG 檢查     : 是                                                                             
優先權       : 99                                                                             
位址         : http://download.opensuse.org/repositories/systemsmanagement/openSUSE_Leap_42.1/
  • --gpg-auto-import-keys 為自動匯入 gpg key
  • -f 為自動 refresh

搜尋 ansible

# zypper  search  -s  ansible
正在取出套件庫 'Various software for easier management of multiple systems (openSUSE_Leap_42.1)' 中介資訊 .........................................[完成]
正在建立儲存庫 Various software for easier management of multiple systems (openSUSE_Leap_42.1) 快取 ...............................................[完成]

S | 名稱    | 類型     | 版本         | 結構   | 套件庫                                                                         
 | ansible | 套件     | | noarch | Various software for easier management of multiple systems (openSUSE_Leap_42.1)
 | ansible | 套件     | 1.9.3-1.1    | noarch | openSUSE-Leap-42.1-Oss                                                         
 | ansible | src 套件 | | noarch | Various software for easier management of multiple systems (openSUSE_Leap_42.1)

安裝 ansible
# zypper  -n   install   ansible

# zypper  search  -s  ansible

S | 名稱    | 類型     | 版本         | 結構   | 套件庫                                                                         
i | ansible | 套件     | | noarch | Various software for easier management of multiple systems (openSUSE_Leap_42.1)

後續的實驗有關於 VMware 會用到 python-pyvmomi
VMware vSphere Python SDK

正在新增儲存庫 Python Modules (openSUSE_Leap_42.1) ................................................................................................[完成]
已成功新增套件庫 'Python Modules (openSUSE_Leap_42.1)'
已啟用       : 是                                                                                    
自動重新整理 : 是                                                                                    
GPG 檢查     : 是                                                                                    
優先權       : 99                                                                                    
位址         : http://download.opensuse.org/repositories/devel:/languages:/python/openSUSE_Leap_42.1/

# zypper  install   python-pyvmomi

將會安裝下列 3 個新的套件:
 python-ndg-httpsclient python-pyvmomi python-requests

下列 1 個推薦的套件已自動被選取:

3  新套件將被安裝.
全部下載大小:699.5 KiB。已快取:0 B。 完成操作後,將增加 3.7 MiB 的使用。
要繼續嗎? [y/n/? 顯示所有選項] (y):


~enjoy it


Si usas Firefox como navegador y utilizas a menudo las miniaturas de los sitios más visitados en la página de nueva pestaña, este tutorial quizás te interese.


Hoy toca un pequeño tutorial, quizás muy simple, pero al que quería encontrar la solución y hasta hoy no me he puesto a ello. Veamos cómo cambiar el número de miniaturas que se muestran al abrir una nueva pestaña en Firefox.

En Firefox por defecto al abrir una nueva pestaña y si lo tenéis configurado para que os muestre una miniatura de los sitios que más visitáis, os mostrará una cuadrícula de 5 columnas y 3 filas con los 15 sitios que más visiteis.

Esto ahorra mucho tiempo y es muy cómodo para acceder a los sitios más usuales. Pero ¿qué pasa si como yo queréis tener no 15 miniaturas si no alguna más? En las configuraciones más evidentes y accesibles de esta página no encontré la manera de hacerlo. Pero en el todo poderoso (y peligroso) about:config encontré el medio de hacerlo, si te interesa te cuento cómo lo hice yo.

Escribimos en una nueva pestaña el conocido about:config y prometemos tener cuidado en la zona hostil para manazas. En la caja de búsqueda introducimos el texto: newtab.

Ahora de entre todas las opciones que se nos presentan deberemos modificar estas 2:

  • browser.newtabpage.columns | es el número columnas, está predefinido a 5, yo lo he cambiado a 6
  • browser.newtabpage.rows | es el número filas, está predefinido a 3, yo lo he cambiado a 4

Hecho esto podemos cerrar esta página de configuración, y con esto habremos pasado de tener 15 miniaturas a 24. Ya sabes que puedes recolocarlas a tu gusto, eliminarlas, fijarlas en una posición en concreto, etc.

Pero quizás ahora al abrir una nueva pestaña no podamos ver de un vistazo todas, ya que ahora el número de miniaturas ha aumentado. Para ello lo que he hecho es reducir el zoom de esta página. Por lo que en el menú de las tres barras horizontales podemos reducir el zoom, o bien pulsando la tecla de Ctrl y girando la rueda del “scroll” del ratón.

Así es como se ve en mi navegador después de seguir estos pasos mi página de miniaturas de nueva pestaña.


Pincha sobre la imagen para ampliar



Tumbleweed-blackA new GNU Compiler Collection for openSUSE‘s rolling release Tumbleweed is scheduled to arrive soon.

Tumbleweed 20160613 snapshot will be the last snapshot to be based on GCC 5, according to the openSUSE Project’s Dominique Leuenberger.

GCC 6 will become the new default compiler, but the release date of the snapshot is difficult to predict right now because Tumbleweed is competing with builds allocated for the next Alpha 2 release of openSUSE Leap 42.2, which is scheduled to be release next week before the openSUSE Conference.

Some fixes in the GCC 6 snapshot will likely be needed, so users should pay attention to the openSUSE Factory Mailing List for any fixes that might be necessary.

Previous snapshots this week also brought some goodies in the repositories for users. Snapshot 20160612 provided Mozilla Firefox 47.0, kernel-firmware 20160609 and AppStream 0.9.6.

The 20160611 snapshot provided git 2.8.4 and several updated YaST packages in the repositories while snapshot 20160609 brought updates to gstreamer, Wayland (1.11.0) and autoyast2.

Help Test Alpha 2 Release

As for Leap 42.2, a lot of focus was made on systemd and GNOME for the Alpha 2 release. Once Alpha 2 is released, we encourage people to test it and get involved with the development on the openSUSE Factory Mailing List.

View the road map for Leap 42.2 releases at https://en.opensuse.org/openSUSE:Roadmap.


Thank you to everyone who came out to LinuxFest Northwest 2016 April 23 and 24! The Geeko crew had a lot of fun in our newly-expanded openSUSE Lounge, where we were able to seat more than a dozen people and have some great conversations.

The openSUSE Lounge at LFNW2016

The conference overall drew nearly 2,000 open-source enthusiasts, setting yet another record for the event! All the openSUSE sessions were well attended, and that gave our team some excellent feedback for future sessions. We were pleasantly suprised to find that “Q&A with openSUSE board members (plus another guy)” (video) was a standing-room-only event, with the audience providing plenty of thoughtful questions for us to answer. “Make the Leap from Dev to Production with openSUSE Leap“, co-presented by Richard Brown and James Mason, provided a thoughtful developer-oriented talk to another full room. Richard also showed some cross-distribution love for openSUSE tooling, co-presenting “openQA – Avoiding Disasters of Biblical Proportions” with Fedora’s Adam Williamson.

Getting back to having a lot of fun, Bryan Lunduke organized a Geeko selfie contest, and we had dozens of tweets and posts of people showing Big Geeko some love, and taking home a little Geeko for their trouble. In the end, we picked our favorite, and gave away Big Geeko himself. Congrats to Alicia Williams on the win!

Screenshot from 2016-06-07 19-29-04

All of these great interactions, though, would be impossible without the openSUSE community! So, here is to you. A special thank you goes out to the volunteers who helped setup the lounge, and spent the whole LFNW weekend answering questions, discussing why they’ve chosen openSUSE, and of course, handing out lots of fun swag. Thank you Adrian, Bob, Caleb, and Carl for all your work, and we look forward to seeing everyone again next year!

14 June, 2016

Michael Meeks: 2016-06-14 Tuesday.

21:00 UTCmember

  • To the office; met a series of pleasingly smart engineers, and business guys back to back; fun. Rushed to the airport - to home in time for E's birthday. Lovely to see her, installed openSUSE Leap onto her laptop - so the much-requested pink-pony works - even if the Broadcom wifi doesn't.

The nature of Open Source is, in a sense, dualistic. It encourages collaboration through the threat of not collaborating--a fork. When I was approached by Struktur AG to join them to work on ownCloud and Spreed, I loved the idea. I always wanted an ecosystem around ownCloud, which is why I pushed things forward like our collaboration with Western Digital Labs and Collabora, matters of no business interest to the company I worked for. I believe a stronger ecosystem benefits everybody.

Ecosystems and confidence

A major point which makes open source so beneficial for businesses is that it puts pressure on suppliers to offer great service and support. If they don't, another can enter the market and out-service them. Tight control over the community tough things like CLA and trademark makes it hard to grow such an ecosystem and negates some of the benefits of open source for customers.

Luckily, in the end, the AGPL license protects the future of a project, even if its steward clings to power. From conversations with Niels early on, it was clear to me that he has a very different and very confident view on his ability to run a real open source company. His history at Red Hat results in frequent comparisons. And indeed, Red Hat runs things the right way, even supporting a project like CentOS which many other companies would consider an existential threat to their business model. Just as their investment in opensource.com shows: they aim to grow the pie, not grab a bigger slice.

former 'enterprise feature' done right (and open)

I'm super proud and happy that we could announce today, with our first release, that Nextcloud will not be doing proprietary code. No closed apps means no inherent conflict between sales and community management/developers within the company, but a full alignment in one simple direction: servicing the customer.

And if you wonder about the collaboration with Collabora/LibreOffice Online and with Western Digital: yes, of course, we'll go full steam ahead and will facilitate where we can! No, we're not afraid that either would 'compete' with us: both will complement and strengthen the ecosystem. So we will work together.

Why? Because the core contributors and founder shared an ambitious goal for Nextcloud: be THE solution for privacy and security.


¿Quieres utilizar Tor porque has oido que sirve para proteger tu privacidad en la red? Aqui tienes 7 cosas que deberías conocer sobre Tor.

Parece que existen algunos errores comunes sobre lo que es Tor. Esta es una muy buena oportunidad para tratar de aclarar algunos de los mitos más comunes y errores de conceptos.

Esta página es una traducción de un artículo publicado en la web de Electronic Frontier Foundation (EFF por sus siglas en inglés). Puedes leer el artículo original en inglés en este enlace:

Espero que sirva como ayuda a quien tenga curiosidad por esta herramienta y de la que quizás haya oido hablar muchas cosas… Empezamos:

1. Tor sigue siendo útil

Una de las muchas cosas que hemos aprendido de las filtraciones de documentos de la NSA es que Tor sigue funcionando. De acuerdo a los documentos revelados por The Guardian de la NSA, esta no es capaz de interceptar por completo el anonimato proporcionado por Tor. Han sido capaces de comprometer a ciertos usuarios de Tor en situaciones específicas.

Historicamente esto se ha realizado encontrando un exploit para el Navegador Tor o explotando una vulnerabilidad de un usuario que ha realizado una mala configuración de Tor. El FBI, posiblemente en unión con la NSA, fue capaz de encontrar un serio exploit para Firefox que implicaba la caida de Freedom Hosting y sus usuarios. Firefox fue parcheado rápidamente, y no ha habido más exploits para Firefox que afecten a los usuarios de Tor desde entonces.

Como los desarrolladores de Tor revelaron en 2004, si alguien está monitorizando de manera activa tanto tu tráfico de red como el tráfico de la red en servicios de internet que uses para comunicarte, Tor no puede prevenir que se pueda deducir de que está usando ese servicio. Su diseño asume que al menos una parte de la conexión no está siendo monitorizada por aquellos de los que estás tratando de permanecer anónimo.

Se puede concluir con esto, que Tor no ha sido probablemente comprometido a nivel criptográfico. El mejor ataque en Tor son ataques a fallos del navegador o a configuraciones erróneas del usuario y ataques de correlación del tráfico.

2. Tor no es usado sólo por criminales

Uno de los mayores errores que oimos es que Tor es únicamente utilizado por criminales y pedófilos. ¡Esto simplemente no es verdad! Hay muchas maneras en la que la gente utiliza Tor.

Los activistas lo utilizan para eludir la censura y ofrecer anonimato. Los militares lo usanpara utilizar comunicaciones seguras y planificar. Las familias usan Tor para proteger a sus hijos y preservar su privacidad. Los periodistas lo usan para realizar búsquedas de historias y comunicarse de manera segura con sus fuentes.

El sitio web de Tor tiene una excelente explicación de porque Tor no es de

13 June, 2016

Michael Meeks: 2016-06-13 Monday.

21:00 UTCmember

  • Up; mail chew, quick calls; train / plane for a customer visit; plugged away at bits of work; bus, train, finally arrived. Out for a fine dinner with Christian in the evening.


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


Una nueva revisión de lo que ha acontecido esta semana 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” para disfrutar de esas actualizaciones.

Esta semana 23 del 2016 pasará a la historia como la semana en la que un “snapshot” de openSUSE Tumbleweed se coló en todos los test de openQA, ocultando un problema a la mayoría de usuarios experimentados.

El equipo de openSUSE Tumbleweed quiere pedir disculpas por los problemas que hubiera causado la imagen de 20160605. Más adelante se explicarán los detalles de lo ocurrido y la manera para impedir que vuelva a suceder.

Pero por el momento veamos qué hay de nuevo en los cuatro “snapshots” publicados, estos son: 0602, 0603, 0605 y 0607. Con interesantes actualizaciones.

  • Postfix 3.1.1 (actualizado desde la versión 2.11.7)
  • Linux Kernel 4.6.1
  • Ruby 2.3

Y además se están preparando:

  • GCC 6 como compilador por defecto, pretendemos que este preparado para la conferencia de openSUSE
  • Linux Kernel 4.6.2
  • Libreoffice 5.2.0
  • QEmu 2.6.0 (seguramente este disponible en el snapshot 0609)
  • Mozilla Firefox 47.0
  • Ruby 2.1 está programado para eliminarlo

Y ahora vienen las explicaciones de cómo el “snapshot” 0605 se coló en openQA provocando varios problemas.

openQA está comprobando un montón de combinaciones, desde instalaciones en limpio con varias configuraciones hasta actualizaciones desde varias versiones de openSUSE. Ninguno de esos test provocaron problemas.

La razón es bastante simple: la actualización de pam-config reemplazando los archivos previos con los actuales con una configuración básica. La configuración básica no contenía una integración con logind/systemd (pam_system.so) lo que es intencionado.

Te invito a que leas la explicación completa en el enlace que encabeza el artículo, con más detalles técnicos que no termino de comprender del todo… y donde también ofrecen la solución para que este error no vuelva a producirse.

Por cierto en el caso de que no se haya resuelto aún un problema en tu equipo derivado de esto (una actualización a una nueva snapshot no lo corrige!) puedes ejecutar este comando en una terminal:

 sudo zypper in -f systemd

Lo que volverá a registrar systemd en la configuración pam.

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

Enlaces de interés




GitLab 如果忘掉了系統管理員 root 密碼時, 可以透過下列方式進行重建 :

  • sudo gitlab-rails console production
  • 接著在 irb(main):002:0 > 後方輸入 u = User.where(id:1).first
  • irb(main):002:0> u.password=’Password’ 輸入新的密碼
  • irb(main):003:0> u.password_confirmation=’Password’ 再一次輸入新的密碼
  • 最後儲存剛才的設定 irb(main):004:0> u.save!

12 June, 2016

Michael Meeks: 2016-06-12 Sunday.

21:00 UTCmember

  • Up; of to NCC - Claire explained Psalm 3 very clearly, back for pizza lunch - Ben & Miriam over in the afternoon, dropped and collected N. from a party; M. returned home - exhausted.
  • Got laptops upgraded, installed and played pink-pony with small girls; read stories, put babes to bed, slept.


OS: openSUSE Leap 42.1

因為實驗環境的需要, 要使用 port forwarding 機制
之前有考慮 Zeroshell http://www.zeroshell.org/

但是考量也是 linux 環境, 後來就使用 openSUSE firewall 內的機制來使用即可.

在 Firewall NAT 啟動的狀況下

如果希望內網的 的 SSH 可以被外面連入

外網    -- 指定的 port  -- >   NAT    -- 指定內網主機 + port -- >  服務主機

啟動 Yast2 firewall
# yast2   firewall

點選  Masquerading  -- > 點選  Add

2016-06-12 19-23-37 的螢幕擷圖.png

在 Requested Port 輸入外面要連入的 port number
在 Redirect to Masqueraded IP 輸入內網主機的 IP
在 Redirect to Port 輸入指定的 port
點選 Add

2016-06-12 19-24-09 的螢幕擷圖.png

完成 firewall 設定

這樣就可以輕鬆完成 port forwading 的機制. ( 網卡的 IPv4 Forwarding 也要開啟 )


~ enjoy it

11 June, 2016

Michael Meeks: 2016-06-11 Saturday.

21:00 UTCmember

  • Up earlyish; missing M. (at cub camp), breakfast together; off to the Queens Birthday Celebration on the studlands green: free food, bouncy castle, music etc. Popped in to see Roy too.
  • Dropped Maurizio at the station; back to clean the church with Mike, got a few work related loose ends cleaned up; watched some iPlayer, sleep.


Aujourd'hui, on s'intéresse à la bureautique dans le cloud et au travail collaboratif en ligne. Face aux géants Google Docs et Office 365, des alternatives libres progressent. Ces derniers mois, il y a eu pas mal d'avancées, entre les services toujours plus complets fournis par l'association Framasoft, basés sur des technologies libres, et des avancées techniques remarquables comme LibreOffice Online. Revue de quelques-uns de ces projets libres prometteurs.

Nom : patchwork.jpg
Affichages : 838
Taille : 107.5 Ko

10 June, 2016

Michael Meeks: 2016-06-10 Friday.

21:00 UTCmember

  • Up; off to morning customer meeting - met Julie in person, and an interesting set of IT managers; admired an extraordinary container-ized HP data-center - fun. Lunch, and to the airport, customer call - caught up on E-mail.
  • Sat next to a Quentin Coehn on the plane; a fine Christian chap with an amazing life story; encouraging. Home, cider with Maurizio, and up late talking.


Nach dem Server-Umzug ist mir aufgefallen, dass viele meiner Scripte unterschiedliche Zeichensätze s.g. Zeichenkodierungen aufweisen. Das war auf dem alten System kein Problem, da es großzügig darüber hinweg gesehen hat. Auf dem neuen werden Dateien etwas strikter behandelt. So wird aus einem Ä mal ganz schnell ein Ã¤ ö ü. o.ä. … Nun könnte man alle Dateien mittels Kwrite o.ä. manuell behandeln, allerdings gibt es dafür schon ein schönes Script (inkl. Fehlerbehandlung):


Einfach in ein übergeordnetes Verzeichnis kopieren und im Terminal mit “ ./converter.sh /pfad/zu/den/Dateien „aufrufen. Es behandelt den Ordner rekursiv d.h. bezieht auch alle Unterordner ein. Dabei wandelt es nur Dateien um, die dafür geeignet sind (es wird auf ein Array mit Endungen zurück gegriffen) und noch nicht in UTF-8 sind.

Ein wichtiger Hinweis an dieser Stelle: legt euch vor dem Umwandeln unbedingt eine Kopie der Daten an.
Sollte das Charset einer Datei nicht erkannt werden, wird diese auch nicht konvertiert. Diese Sicherheits-Einstellung wird für die Liste filestoconvert aufgeweicht. Es kann daher vorkommen, dass 0-Byte Dateien entstehen. Wer auf Nummer-Sicher gehen will, leert die Liste. Andernfalls sollte z.B. mittels Kompare der Zustand vorher und nachher verglichen werden. Auch praktisch ist folgende Code-Zeile, die alle 0-Byte Dateien auflistet: find $dir -size 0 -print


# Created by LEXO, http://www.lexo.ch
# Version 1.0
# This bash script converts all files from within a given directory from any charset to UTF-8 recursively
# It takes track of those files that cannot be converted automatically. Usually this happens when the original charset
# cannot be recognized. In that case you should load the corresponding file into a development editor like Netbeans
# or Komodo and apply the UTF-8 charset manually.
# This is free software. Use and distribute but do it at your own risk. 
# We will not take any responsibilities for failures and do not provide any support.

#checking Parameters
if [ ! -n "$1" ] ; then
  echo "You did not supply any directory at the command line."
  echo "You need to provide the path to the directory that contains the files which you want to be converted"
  echo ""
  echo "Example: $0 /path/to/directory"
  echo ""
  echo "Important hint: You should not run this script from within the same directory where the files are stored"
  echo "that you want to convert right now."

# This array contains file extensions that need to be checked no matter if the filetype is binary or not.
# Reason: Sometimes it happens that .htm(l), .php, .tpl files etc. have a binary charset type. This script
# does not convert binary file types into utf-8 because it might destroy your data. So we need to include these file types
# into the conversion system manually to tell the conversion that binary files with these special extensions may be converted anyway.
filestoconvert=(htm html php txt tpl asp css js)

# define colors
# default color
# Successful conversion (green)
# No conversion needed (blue)

<- Current blog entries