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.


Saturday
20 July, 2019


face

Bodhi review title.png

Linux is a fun thing and trying out other distributions can result in a myriad of experiences. Some distributions concentrate on user experience or mostly the technical underpinnings. Some distributions put their own feel while others minimize their modifications. I am a long time openSUSE user and am perfectly content with all that it has to offer, not just as a distribution but as a project in its totality.  As a part of the Big Daddy Linux Community, there is an optional weekly challenge to try out a Linux distribution. My process for this is to put it in a VM first and then go to “bare metal” for further testing if my initial experience is compelling enough and I have the time.

The latest challenge is Bodhi Linux it is built on the Ubuntu 18.04 LTS but targeting machines with fewer resources. The Bodi Linux Project offers forums for help and advice, they have a wiki to help with configurating the system, and offer a live chat through Discord to get help or just get to know members of the community. Unfortunately, I didn’t notice any IRC options. I downloaded the ISO from here. There are few different options from which to choose. I went with the “AppPack” ISO as it has more applications bundled in it. For more information on choosing the correct ISO for you, see here.

Bottom Line Up Front, Bodhi Linux is well put together and the Moksha Desktop is a crisp, low resource, animated (almost excessively) environment that is worthy of giving it a spin. This distribution is certainly worth the time, especially if you have an older system you want to keep going a little longer. The Moksha Desktop looks good and is more functional than GNOME so that is already a leg up on many distributions.

Installation

When you first spin it up, you are greated with the typical boot menu you would get from a Linux media. My only complain here is that it doesn’t have an install option from here. That is always my preferred option.

Bodhi Linux 1 Live Installer

Booting from the Live Media was pretty rapid. The default desktop was clean and themed correctly, dark. I didn’t even see a light option so well done there! All the icons and menus lend themselves nicely for a dark themed desktop.

The Welcome Screen is nothing more than a local html file of places to go to get started using Bodhi Linux. You are almost immediately greeted with the notice that you are not running the latest Enlightenment. I know that this desktop, Moksha, is forked from it so, just odd that I would see “Enlightenment” there.

Since I wanted to play with this distribution and do things with it, I needed to install it. Although I prefer being able to install out of the gate, I can get along with the Live process well enough. My only issue was. I didn’t know where the installation laucher was to


face
desk lamp with mirror behinddesk lamp with mirror behind

Some time ago, I wanted to make my own desk lamp. It should provide soft, bright task lighting above my desk, no sharp shadows that could cover part of my work area, but also some atmospheric lighting around the desk in my basement office. The lamp should have a natural look around it, but since I made it myself, I also didn’t mind exposing some of its internals.

desklamp-ledstripsSMD5050 LED strips

I had oak floor boards that I got from a friend (thanks, Wendy!) lying around. which I used as base material for the lamp. I combined these with some RGBW led strips that I had lying around, and a wireless controller that would allow me to connect the lamp to my Philips Hue lighting system, that I use throughout the house to control the lights. I sanded the wood until it was completely smooth, and then gave it an oild finish to make it durable and give it a more pronounced texture.

Fixed to the ceilingFixed to the ceiling
Internals of the desk lampInternals of the desk lamp

The center board is covered in 0.5mm aluminium sheets to dissipate heat from the LED strips (again, making them last longer) and provide some extra diffusion of the light. This material is easy to work with, and also very suitable to stick the led strips to. For the light itself, I used SMD5050 LED strips that can produce warm and cold white light, as well as RGB colors. I put 3 rows of strips next to each other to provide enough light. The strips wrap around at the top, so light is not just shining down on my desk, but also reflecting from walls and ceiling around it. The front and back are another piece of wood to avoid looking directly into the LEDs, which would be distractive, annoying when working and also quite ugly. I attached a front and back board as well to the lamp, making it into an H shape.

Light reflects nicely from surrounding surfacesLight reflects nicely from surrounding surfaces

The controller (a Gledopto Z-Wave controller, that is compatible with Philips Hue) is attached to the center board as well, so I just needed to run 2 12V wires to the lamp. I was being a bit creative here, and thought “why not use the power cables also to have the lamp hanging from the ceiling?”. I used coated steel wire, which I stripped here and there to have power run through steel hooks screwed into the ceiling to supply the lamp with power while also being able to adjust its height. This ended up creating a rather clean look for the whole lamp and really brought the whole thing together.


face

Hoy me complace compartir con tenemos entre nosotros una nueva versión de la aplicación para dibujante y artistas gráficos de KDE. En otras palabras, que ha sido lanzado Krita 4.2.3, una actualización de la aplicación que conquista a los creadores que la prueban y que demuestra que la unión de usuarios y desarrolladores en el mundo del Software Libre hace avanzar las aplicaciones libres a un ritmo que las propietarias no pueden seguir.

Lanzado Krita 4.2.3, mejorando su eficacia en dispositivos táctiles

Ya han pasado mucho tiempo desde el lanzamiento de la primera versión de la rama 4 de Krita, la cual no para de mejorar en cada nueva revisión. Esto no significa que no sea motivo de alegría comentar que ha sido lanzado Krita 4.2.3, el cual nos trae pocas pero importantes novedades, como la posibilidad de poder utilizar con mejor eficacia dispositivos táctiles en el lienzo de trabajo.

Lanzado Krita 4.2.3, mejorando su eficacia en dispositivos táctiles

Además, se han resuelto casi 30 errores, con lo que la aplicación gana en estabilidad.

Más información: Krita

Las novedades de Krita 4.2

Aunque no lo publiqué en su día, nunca es tarde para repasar las noveades de Krita 4.2, las cuales vienen acompañadas de un vídeo.

No obstante, para aquellos que no tengan tiempo y quieran simplemente leer las novedades, aquí las presento en forma resumida:

  • Actualizado el soporte para tablets con Windows, Linux y macOS.
  • Posibilidad ver tu imagen HDR en HDR por hardware, con lo que se gana en rapidez y calidad.
  • Siguen las mejoras en la rapidez de los pinceles.
  • Mejorada la ventana de paletas de colores.
  • Añadida  la API para animación con Python
  • Posibilidad de configurar los backups.

Y muchos más pequeñas mejoras.Una gran noticia para un Software que no para de mejorar y que demuestra el gran potencial que tiene el Software Libre cuando se unen esfuerzos.

 

¿Qué es Krita?

Para los que no lo sepan, Krita es el software de pintura digital e ilustración basado en las librerías de la plataforma KDE que antes estaba incluido en Calligra Suite.
A diferencia de otras aplicaciones gráficas, se diseño hace énfasis en la creación de imágenes desde cero, es decir, está especialmente orientado para los artistas gráficos como ilustradores, dibujantes de cómics, etc.
Krita es software libre distribuido bajo la licencia GNU GPL y fue lanzado por primera vez como parte de la versión 1.4.0 de KOffice, el 21 de junio de 2005. (Vía: Wikipedia)

Para ver el funcionamiento de esta aplicación nada mejor que ver un vídeo de Odysseas Stamoglou en la que nos muestra como dibujar una chica futurística con Krita.


face

Three openSUSE Tumbleweed snapshots in the middle of this week brought new minor version updates to ImageMagick, Squid, SQLite, VIM and more. The new KDE Applications 19.04.3 version arrived in the first two snapshots.

The more recent snapshot, 20190718, brought a half-dozen new packages, which include fix for the UrbanCode Deploy (UCD) script data for Unicode 10+ scripts for the OpenType text shaping engine package harfbuzz 2.5.3. A two-year old Common Vulnerabilities and Exposures (CVE) was fixed with the update of libpng12 1.2.59. The tool that cleans RPM spec files, spec-cleaner 1.1.4, added a temporary patch to fix a test that fails if there is no internet connection. Caching proxy squid 4.8 fixed GNU Compiler Collection (GCC) 9 build issues and added a fix to prevent parameter parsing used for a potential Denial of Service (DoS). RISC-V support was added with the virt-manager 2.2.1 update and xclock 1.0.9 was also updated in the snapshot, which is trending at a 97 rating, according to the Tumbleweed snapshot reviewer.

Updates for KDE Applications 19.04.3 were completed in snapshot 20190717. More than 60 bugfixes were made and improvements were made to Konqueror and Kontact so there is no longer a crash on exit with QtWebEngine 5.13. Cutting groups with compositions no longer crash the Kdenlive video editor and the Python importer in Umbrello’s Unified Modeling Language (UML) designer now handles parameters with default arguments. ImageMagick fixed a parsing issue and optimized the PDF reader with the 7.0.8.53 update. GNOME’s hex editor ghex 3.18.4 migrated the build system to meson and added Open Age Ratings Service (OARS) metadata. The kernel-firmware was updated in the snapshot. The newer php7 7.3.7 provided more than a dozen bug fixes to include a fix for reproducible builds that failed with OpenSSL 1.1.1c. The update of text editor vim from version 8.1.1600 to 8.1.1694 provided a large amount of fixes to include a fix for tests that get stuck when running into an existing swap file. The snapshot is also trending at a 97 rating, according to the Tumbleweed snapshot reviewer.

Snapshot 20190716 started updating KDE Applications 19.04.3 and brought users of the rolling release 10 CVE fixes for Mozilla Thunderbird 60.8.0; the updated version also fixed problems when editing event times that related to AM/PM setting in non-English locations. The update to Ceph in the snapshot removed SuSEfirewall2 support. The update of gpg2 2.2.17 provided a new command –locate-external-key to locate the keys given as arguments. LibreOffice 6.2.5.2 removed some merged patches. Relational database management system sqlite3 3.29.0 added the “sqlite_dbdata” virtual table for extracting raw low-level content from an SQLite database to also include a database that is corrupt. The new major version of xreader 2.2.1 fixed incompatible pointer type issues and


face
AWS 以console 及 aws-cli 新增IAM使用者小記

有些專案, 同事需要有 AWS console 登入檢視相關資訊的需求
寫一篇小記紀錄如何建立使用者然後給予相關權限

======== Console 方式 ========

登入 AWS Console -- > 點選 IAM 服務  -- > 點選 使用者

點選 新增使用者
輸入 使用者名稱 , 勾選 AWS Management Console 存取, 設定密碼 
確認 使用者必須在下次登入時建立新的密碼已經勾選
點選 下一個:許可


這次要建立的是只有 EC2 檢視的使用者, 官方建議使用群組的方式來管理
在 設定許可畫面中 , 點選建立群組

輸入群組名稱, 以這邊為例 EC2ReadOnlyAccess
搜尋 EC2Re 可以找到 AmazonEC2ReadOnlyAccess 政策
勾選 AmazonEC2ReadOnlyAccess 政策 -- > 建立群組 

確認 EC2ReadOnlyAccess 群組已經勾選 -- > 點選 下一個:標籤


標籤的部份, 因為在Console 沒有辦法輸入中文, 實物上可能有相關需求, 所以我是之後使用指令來完成, 點選 下一個:檢閱


再次瀏覽相關資訊 
點選 建立使用者
點選關閉 完成設定

接下來進行驗證

另外開啟新的瀏覽器到 AWS 登入Console
以剛剛建立好的使用者登入, 
可以嘗試進行相關動作, 但是因為沒有相關權限, 所以應該會得到相關錯誤訊息



另外一種方式是使用指令的方式

======== Console 方式 ========

一樣使用之前建立的 Container with 雲平台工具

OS: Container with openSUSE Leap 15

==== 在主機上面 ====

啟動 container

> docker  run  -v  ~/.aws:/root/.aws -v  ~/.azure:/root/.azure  -v ~/.config/gcloud:/root/.config/gcloud  -v  ~/.ssh:/root/.ssh  -it  sakana/ansible_opensuse15  /bin/bash

==== 在 container 內 ====

參考官方文件

建立使用者

# aws  iam  create-user --user-name  max

{
    "User": {
        "UserName": "max", 
        "Path": "/", 
        "CreateDate": "2019-07-20T03:41:17Z", 
        "UserId": "AIDA2MGTTTNPHXG2DWTKL", 
        "Arn": "arn:aws:iam::781126831704:user/max"
    }
}

給予 console login 權限

# aws iam create-login-profile --user-name max --password YOURPW  --password-reset-required

{
    "LoginProfile": {
        "UserName": "max", 
        "CreateDate": "2019-07-20T03:47:35Z", 
        "PasswordResetRequired": true
    }
}


接下來就是建立群組, 讓使用者加入還有設定政策

# aws  iam  create-group  --group-name EC2ReadOnlyAccess

{
    "Group": {
        "Path": "/", 
        "CreateDate": "2019-07-20T03:54:14Z", 
        "GroupId": "AGPA2MGTWTNTKQRGBFF7U", 
        "Arn": "arn:aws:iam::781126831704:group/EC2ReadOnlyAccess", 
        "GroupName": "EC2ReadOnlyAccess"
    }
}


將政策( Policy ) 加入到群組
在加入政策之前要先先找到相關 政策還有他的 ARN

先觀察相關資訊, 先列出兩個
#aws  iam  list-policies --max-items 2

{
         "Policies": [
        {
                "PolicyName": "AdministratorAccess",
                "CreateDate": "2015-02-06T18:39:46Z",
                "AttachmentCount": 5,
                "IsAttachable": true,
                "PolicyId": "ANPAIWMBCKSKIEE64ZLYK",
                "DefaultVersionId": "v1",
                "Path": "/",
                "Arn": "arn:aws:iam::aws:policy/AdministratorAccess",
                "UpdateDate": "2015-02-06T18:39:46Z"
              },
              {
                "PolicyName": "ASamplePolicy",
        "CreateDate": "2015-06-17T19:23;32Z",
        "AttachmentCount": "0",
        "IsAttachable": "true",
                "PolicyId": "Z27SI6FQMGNQ2EXAMPLE1",
        "DefaultVersionId": "v1",
                "Path": "/",
                "Arn": "arn:aws:iam::781126831704:policy/ASamplePolicy",
                "UpdateDate": "2015-06-17T19:23:32Z"
              }
        ]
}

  • 這邊可以觀察到有 2 種 ARN, 官方ARN以及有帶 使用者帳號ID 的 ARN 

實務上我會使用 list-policies 加上 egrep 方式來找出我想要的
例如 # aws iam list-policies | egrep  '*EC2*' 

這次的作法是要找出 EC2 然後 ReadOnly
所以我會這樣搭配

# aws  iam  list-policies | egrep  -i   '*EC2*ReadOnly*'

            "PolicyName": "AmazonEC2ReadOnlyAccess", 
            "Arn": "arn:aws:iam::aws:policy/AmazonEC2ReadOnlyAccess", 

  • 這邊一定要用 egrep 而不是 grep

接下來把 找到的 AmazonEC2ReadOnlyAccess 政策套用到群組

# aws  iam attach-group-policy --policy-arn arn:aws:iam::aws:policy/AmazonEC2ReadOnlyAccess --group-name  EC2ReadOnlyAccess

最後就是把使用者加到群組

# aws  iam  add-user-to-group --user-name max --group-name EC2ReadOnlyAccess


先記下來
~ enjoy it

有關於 IAM 使用者 加上標籤可以參考之前的 Blog


Reference:


Friday
19 July, 2019


face


使用 Ansible 安裝 netdata  on GCP 小記

OS: Container with openSUSE Leap 15


因為同事很習慣使用 netdata 觀察機器狀況, 所以就寫了一篇紀錄使用 Ansible 安裝 netdata 小記

Netdata

這次要實驗的機器是同事習慣的 CentOS 7 on GCP

Ansible 的部份是使用自己建立的 Container with openSUSE Leap 15 


==== 在主機上面 ====

啟動 container

> docker  run  -v  ~/.aws:/root/.aws -v  ~/.azure:/root/.azure  -v ~/.config/gcloud:/root/.config/gcloud  -v  ~/.ssh:/root/.ssh  -it  sakana/ansible_opensuse15  /bin/bash

  • 這邊我有透過 -v 把本機上面的三個平台的設定檔掛載到容器內, 還有 .ssh 目錄 也掛載上面, 因為 google 的 SSH 金鑰 也會存放在裡面


==== 在 container 內 ====

使用 gcloud 指令建立 CentOS 7 的 GCE ( VM )

# gcloud  compute  --project=sakanatest  instances  create  --zone=asia-east1-b  --machine-type=n1-standard-1  --image-project=centos-cloud  --image-family centos-7 --boot-disk-size=30GB  test20190718

  • --project 是因為我有多個 profile 所以指定那一個專案

檢查相關資訊

# gcloud  compute  instances  list

NAME               ZONE MACHINE_TYPE   PREEMPTIBLE INTERNAL_IP EXTERNAL_IP    STATUS
test20190718  asia-east1-b n1-standard-1                                   10.120.0.34 32.194.143.80 RUNNING


嘗試使用 gcloud 指令連線 SSH 到 GCE 

# gcloud  compute  ssh  sakana@test20190718  --zone  asia-east1-b

[sakana@test20190718 ~]$ 

  • 這邊要用 使用者@SERVER_NAME, 因為預設不允許讓 root 登入
  • 使用者帳號就要看當初 GCE 內的 SSH 金鑰使用者名稱

登出 GCE 回到 container 內

[sakana@test20190718 ~]$  exit

到這邊可以確認 gcloud 可以建立 GCE , 連線 SSH 到 GCE

接下來確認一下 在容器內也可以使用 SSH 私鑰 連線遠端的 GCE

# ssh  -i  /root/.ssh/google_compute_engine -l sakana  YOUR_VM_IP
[sakana@test20190718 ~]$ 


登出 GCE 回到 container 內

[sakana@test20190718 ~]$  exit

接下來進入 Ansible 的部份

hosts 檔案如下

# ----------------------------------------------------------------------

test20190718  ansible_host=YOUR_VM_IP ansible_ssh_private_key_file=/root/.ssh/google_compute_engine

# ----------------------------------------------------------------------

# 安裝 netdata
[netdata]
test20190718

先來進行基礎的 ping 測試

# ansible  -u  sakana  -m ping  test20190718

test20190718 | SUCCESS => {
    "changed": false, 
    "ping": "pong"
}


安裝 netdata 的 playbook 檔案 netdata_install.yml 檔案如下

---
# edit by sakana 2019/7/18
# 感謝亦德提供安裝的playbook 讓我修改
#########################################################  
#
#########################################################  

- name: Install netdata and run service
# use group
  hosts: netdata
#  sudo: True
  become: True

  tasks:
#    - name: test setup moudule
#      setup: filter=ansible_distribution

# 下載 netdata 安裝 script
    - name: downlaod netdata software
      get_url:
        url: https://my-netdata.io/kickstart.sh
        dest: /usr/local/src/

# 使用非互動的方式安裝 netdata
    - name: install netdata
      shell: bash /usr/local/src/kickstart.sh --dont-wait

    - name: clean yum cache
      shell: yum clean all
      args:
        warn: no

# 移除 kickstart.sh
    - name: remove netdata software
      shell: rm -rf /usr/local/src/kickstart.sh
      args:
        warn: no

# 修改 Global 的 history 為86400
    - name: change netdata.conf
      shell: sed -i '1,30s/# history = 3996/history = 86400/g' /etc/netdata/netdata.conf
      args:
        warn: no

# 重新啟動 netdata
    - name: restart and enable service netdata
      systemd:
        name: netdata
        state: restarted
        enabled: yes


#-------------------------------------------------------


使用 ansible-playbook  指令安裝 netdata

# ansible-playbook -u  sakana  netdata_install.yml 

到這邊 netdata 已經安裝完畢
剩下最後一個動作, 開啟該 GCE 的 firewall

使用 gcloud 指令建立 firewall 允許 netdata 預設 port  19999 存取

# gcloud   compute  --project  sakanatest  firewall-rules create  "netdata"  --source-ranges "YOUR_IP_RANGE" --allow  tcp:19999

開啟瀏覽器 http://YOUR_IP:19999


大功告成
在 GCP 上面又前進一步

~ enjoy it

結束實驗, 刪除相關資源

# gcloud  compute  instances delete  test20190718
# gcloud  compute  --project sakanatest  firewall-rules delete "netdata"

Reference:


face

Nos acercamos a agosto, el segundo mes del año elegido para que el equipo de desarrollo de KDE haga el lanzamiento de su gran revisión de sus aplicaciones. Pero antes de este gran actualización siempre hay que probar. Por eso me complace anunciar que, tal y como estaba previsto en su calendario, ha sido lanzada la beta de KDE Aplicaciones 19.08. ¡Esto no para! ¡esto es KDE!

Lanzada la beta de KDE Aplicaciones 19.08

Lanzada la beta de KDE Aplicaciones 19.08Hoy 19 de julio el equipo de desarrollo de la Comunidad KDE anunció la beta de KDE Aplicaciones 19.08, otro paso más en la evolución de su ecosistema de programas que tiene dos objetivos fundamentales: seguir mejorando las aplicaciones KDE y continuar la migración de más aplicaciones al entorno de trabajo Qt5/KF5.

Tras un trabajo que se inició antes del día que se lanzó KDE Aplicaciones 19.04, los desarrolladores han estado trabajando de forma silenciosa pero coordinada y constante preparando las nuevas funcionalidades que nos esperan en como regalo navideño.

Ahora es el momento de congelar las funcionalidades y las dependencias, y que el equipo de desarrollo (y todas aquellas personas que así lo deseen) se centren en corregir errores y pulir las aplicaciones.

Más información: KDE.org

Pruébalo y reporta errores

Lanzada la beta de KDE Aplicaciones 17.12

Konqi siempre se encuentra dispuesto a buscar bugs y solucionarlos.

Todas las tareas dentro del mundo del Software Libre son importantes: desarrollar, traducir, empaquetar, diseñar, promocionar, etc. Pero hay una que se suele pasar por alto y de la que solo nos acordamos cuando las cosas no nos funcionan como debería: buscar errores.

Desde el blog te animo a que tú seas una de las personas responsables del éxito del nuevo lanzamiento de las aplicaciones de KDE. Para ello debes participar en la tarea de buscar y reportar errores, algo básico para que los desarrolladores los solucionen para que el despegue de KDE Aplicaciones 16.04 19.04 esté bien pulido. Debéis pensar que en muchas ocasiones los errores existen porque no le han aparecido al grupo de desarrolladores ya que no se han dado las circunstancias para que lo hagan.

Para ello debes instalarte esta beta y comunicar los errores que salgan en bugs.kde.org, tal y como expliqué en su día en esta entrada del blog.


face

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

Tumbleweed

openSUSE Tumbleweed es la versión “rolling release” o de actualización continua de la distribución de GNU/Linux openSUSE.

Hagamos un repaso a las novedades que han llegado hasta los repositorios estas semanas.

El anuncio original lo puedes leer en el blog de Dominique Leuenberger, publicado bajo licencia CC-by-sa, 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 este comando aunque desde hace poco un simple zypper dup hace ya todo el trabajo.

Durante las pasadas 2 semanas, openSUSE Tumbleweed ha sido reconfigurado para compilar todos los paquetes de software (donde esto fuera posible) utilizando LTO (Link-Time Optimization).

Siempre que hay un gran cambio en el compilador, se recompila la distribución entera, con más de 12.000 paquetes de software disponibles, el recompilar todo, lleva su tiempo. Incluso OBS, la herramienta con la que se crean los paquetes, tiene un limitado número de tareas que puede realizar

Desde la anterior revisión que publiqué en el blog, se han publicado 4 nuevas “snapshots” (0708, 0713, 0716 y 0717).

Entre los cambios que han traido se pueden destacar los siguientes:

  • Completo recompilado habilitando LTO
  • Mesa 19.1.2
  • Mozilla Thunderbird 60.8.0
  • KDE Applications 19.04.3
  • FreeType2 2.10.1
  • Linux kernel 5.1.16
  • TeXLive 2019

Y estos son los cambios que pronto llegarán a los repositorios de openSUSE Tumbleweed:

  • Squid 4.8
  • Linux Kernel 5.2.1
  • Dracut 049
  • KDE Frameworks 5.60.0
  • KDE Plasma 5.16.3
  • Mozilla Firefox 68.0

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

Geeko_ascii

——————————–


face

Dear Tumbleweed users and hackers

During the last two weeks, openSUSE Tumbleweed has been reconfigured to build all packages (where possible) using LTO (Link-Time Optimization). Whenever we have such a big change in compiler or compiler flags, we are rebuilding the entire distribution. With the  12k source packages, that can take a moment. Even OBS has a limited number of workers it offers to produce the distro. Since the last review, we published 4 snapshots (0708, 0713, 0716 and 0717). Sadly, the announcer did miss two of those snapshots (0708 and 0713), due to technical difficulties (in manager lingo – in technical language, there was simply a bug exposed in Leap 15.1 and the machine creating the announcements was updated from Leap 42.3 to 15.1).

The snapshots contained those changes/updates:

  • Full rebuild with LTO enabled
  • Meas 19.1.2
  • Mozilla Thunderbird 60.8.0
  • KDE Applications 19.04.3
  • FreeType2 2.10.1
  • Linux kernel 5.1.16
  • TeXLive 2019

These things are currently being forged and tested:

  • Add -Werror=return-type to CFLAGS
  • Squid 4.8
  • Linux Kernel 5.2.1
  • Dracut 049
  • KDE Frameworks 5.60.0
  • KDE Plasma 5.16.3
  • Mozilla Firefox 68.0

face

After our (really long) sprint report, which featured information from 3 different sprints together, we are back to our regular schedule of publishing a blog post after each sprint.

In a nutshell, these are the highlights from the previous one:

  • A new version of yast2-network will be submitted to Tumbleweed shortly, including quite some internal changes as part of the refactoring effort.
  • The support for offline installation of SUSE Linux Enterprise products has been improved to handle modules and extensions dependencies automatically, among other goodies.
  • The partitioning proposal has been adapted to support SUSE Manager special needs.
  • The guided partitioning ignores now the adjust_by_ram parameter in IBM z Systems, where it is basically useless.
  • Some (open)SUSE 15 features have been backported to 5th Service Pack of SUSE Linux Enterprise.

And last but not least, we have some words to say about the feedback we get from you (that we really appreciate!) and the future of YaST.

Shipping Another Round of Network Refactored Code

One of the problems we wanted to avoid while refactoring yast2-network is diverging too much from the version shipped in Tumbleweed. As we mentioned in our last report, we have done quite some work, especially when it comes to the internals of the user interface, and codebases are starting to look quite different.

For that reason, we decided to merge the new code into the master branch so it can be included in Tumbleweed shortly. We are talking about a pull request which contains more than 340 commits, adds 9000 lines, removes 5000 and modifies 197 files. So, what could possibly go wrong? To be honest we did quite some testing but there is a chance that you can find some issues. In that case, please, open a bug report and we will happily fix it.

About the technical details, we put most of our efforts into drawing a clear line between the user interface and the business logic. In parallel, we are still working on the new data model which enables us to read/write the network configuration using different backends, although at this time we are only supporting sysconfig. We have made some progress during this sprint (you can check the pull request if you are interested), but we will not merge this code into our master branch yet. You can find more details in the updated documentation.

After reading this status update about the yast2-network refactoring, you might be wondering about our plans. Basically, we would like to finish the support to read/write network interfaces configuration and start using it through all the code, killing some rather old and buggy modules like LanItems.

Offline Media Support

For SUSE Linux Enterprise 15 products, there are two installation media:

  • The installer media, which contains only basic packages for a minimal system.
  • The so-called Packages DVD, which contains several modules and extensions, like the Development Tools Module or the Server Application Module.

The main use case of the Packages DVD is allowing to install the


face

The Travel Support Program (TSP) provides travel sponsorships to openSUSE community who want to attend the openSUSE.Asia Summit and need financial assistance. openSUSE.Asia Summit 2019 will be in Bali, Indonesia, at Information Technology Department, Faculty of Engineering, Udayana University on October 5 and 6.

The goal of the TSP is to help everybody in and around openSUSE to be able to attend the openSUSE.Asia Summit!

When and how

Requests for the TSP for this year’s openSUSE.Asia Summit have until August 24 to submit their request.

Remember: All requests will be managed through the TSP application at http://connect.opensuse.org/travel-support.

You will need an openSUSE Connect account in order to login to the application and apply for sponsorship. Please be sure to fulfill all of your personal details at openSUSE connect account to avoid delays or negative request. A good application with good information will be processed faster.

A few reminders

  • Please read the TSP page carefully before you apply.
  • Any information you send to the Travel Committee will be private.
  • We want everybody there! Even if you think you would not qualify for the travel support, just submit and make it worth! If you don’t try you won’t get!
  • If you submitted an abstract to be presented you should mention it in your application.
  • The Travel Committee can reimburse up to 80% of travel and/or lodging costs. That includes hotel, hostel, plane,train, bus, even gas for those willing to drive. Remember, no taxi!
    • Important: Food and all local expenses are on you!
  • We want to sponsor as many people as possible so please check the best deal.
  • The Travel Committee won’t be able to book or pay anything in advance. The reimbursement will be done after the event finishes and based on your expenses receipts.
  • no receipts = no money It is the rule! (Original receipts are required from German residences.)

If you have any question regarding your trip to the conference do not hesitate to ask the TSP or openSUSE.Asia Summit organizers.

We hope to see you there!


face

Em breve a Positivo lançará o celular básico P70S com direito a tudo que a tecnologia mobile necessita. Mas com uma enorme diferença, o sistema KaiOS! Este sistema é a ressurreição do FirefoxOS, e o mais importante, esta tecnologia abre um novo mercado e o fim da segregação digital.

Pois com aproximadamente 279 reais todos poderão acessar as tecnologias móveis com um baixo custo. É um novo mercado para explorar com o potencial de 3 bilhões de usuários. No link a seguir um artigo do Viva O Linux de como desenvolver seu primeiro aplicativo Gaia e mais informações sobre o assunto.

TUTORIAL NO VIVA O LINUX

Link: KaiOS: A ressurreição do FirefoxOS e o fim da segregação digital

Parabéns POSITIVO, agora nós da comunidade de desenvolvedores poderemos proporcionar tecnologias para as pessoas de baixa renda com a qualidade QUE SOMENTE O SOFTWARE LIVRE PODE OFERECER!

A seguir um video demonstrativo da plataforma de desenvolvimento.


Thursday
18 July, 2019


face

Este es un aspecto bastante técnico del modo en que se crea openSUSE Tumbleweed, la distro GNU/Linux de actualización contínua de openSUSE.

Al ser un tema bastante técnico, espero que me perdonéis si meto la pata tratando de explicarlo. Se agradecerán, como siempre, los comentarios constructivos que aporten más información y aclaren más el asunto.

Ayer al actualizar mi openSUSE Tumbleweed mediante un zypper dup en la consola, zypper me informaba que eran más de 6000 paquetes los que iba a actualizar.

Hace unos días había leido que openSUSE iba a actualizarse a el compilado GCC 9, por lo que hay que recompilar todos los paquetes a esa versión, por lo que supuse que ese sería el motivo. Pero esta actualización ha traído más miga.

Esa primera “snapshot” es la primera en la que se habilita de manera predeterminada LTO las siglas de “link-time optimizations” ¿y eso es bueno o malo? Aquí es donde empieza la parte técnica en la que me pierdo un poco, por tanto explicaré lo que he creido entender.

Esta nueva opción a la hora de compilar paquetes, hace que estos sean menos pesados y más rápidos, junto con otras ventajas a la hora de realizar el compilado de dichos paquetes. Esto quiere decir, que se reduce un poco el tamaño de la distro y supongo que conlleve otros beneficios.

Esto ha sido gracias al trabajo y cooperación de diversos hackers de la comunidad de openSUSE junto con otras personas que trabajan en otros campos.

Por tanto, si vas a actualizar tu openSUSE Tumbleweed en estos días, no te asustes de la cantidad de software que dice que tiene que actualizar. Y en mi caso, después de la actualización no ha ocurrido ningún problema.

Todo parece funcionar correctamente, y el equipo se desenvuelve sin problemas. Te dejo unos enlaces (en inglés) donde puedes ampliar más información al respecto.

Enlaces de interés


face

Ya se ha publicado el programa de charlas de Akademy 2019 de Milán que se celebrarán del 7 al 11 de septiembre. Es el momento de repasar los temas de las ponencias y que las expectativas del evento crezcan y crezcan.

Programa de charlas de Akademy 2019 de Milán

os eventos grandes del Software Libre son, como todas las grandes ferias, ideales para presentar grandes novedades, avances e incluso cambios de dirección.

Es por ello que se esperan con interés muchas de las ponencias de Akademy para conocer cual va a ser el rumbo que va a seguir la Comunidad KDE durante el año de desarrollo hasta el evento del 2019 y saber cuál será su senda futura.

Programa de charlas de Akademy 2019 de Milán

De esta forma es sumamente grato comentaros que ya tenemos el programa de charla de Akademy 2019 de Milano en las cuales se hablará entre otros temas como las novedades de Plasma y cómo acelerarlo, el reporte de KDE e.V., qué hace el equipo de promoción, como va la conquista de Android o la integración de LibreOffice en Plasma.

Como vemos en esta breve reseña de todo y variado, abarcando temas de todo tipo y plantando temas de futuro.

Más información: Anuncio oficial Akademy 2019 de Milán

¿Qué es Akademy?

Para los que no lo sepan, Akademy es el evento de la Comunidad KDE que aúna en una gran conferencia todo tipo de simpatizantes de KDE como desarrolladores, diseñadores, usuarios, traductores, promotores, ideólogos, etc. Allí se reunirán a lo largo de una semana para compartir charlas, cenas, ponencias, talleres y, en definitiva, para trabajar juntos.
Es una gran semana que sirve para unir más fuerte los lazos que unen nuestra Comunidad, así como para crear nuevos que se mantendran gracias a las listas de correo, canales irc o Sprints.

Hay que recordar que en España tenemos gran tradición en la celebración de Akademy ya que en 2011 se celebró en Gran Canaria, en 2013 en Bilbao , en 2015 en A Coruña y el año pasado en Almería.


face

Le nouveau malware Linux «EvilGnome» espionne les utilisateurs de postes de travail Linux et dérobe des fichiers sensibles: https://fca-team.eu/2019/07/18/le-nouveau-malware-linux-evilgnome-espionne-les-utilisateurs-de-postes-de-travail-linux-et-derobe-des-fichiers-sensibles/ Un autre article en anglais: https://thehackernews.com/2019/07/linux-gnome-spyware.html Soyez vigilents!


face

Recently I gave a syslog-ng introductory workshop at Pass the SALT conference in Lille, France. I got a lot of positive feedback, so I decided to turn all that feedback into a blog post. Naturally, I shortened and simplified it, but still managed to get enough material for multiple blog posts.

This one gives you an overview of syslog-ng, its major features and an introduction to its configuration.

What is logging & syslog-ng?

Let’s start from the very beginning. Logging is the recording of events on a computer. And what is syslog-ng? It’s an enhanced logging daemon with a focus on portability and high-performance central log collection. It was originally developed in C.

Why is central logging so important? There are three major reasons:

  • Ease of use: you have only one location to check for your log messages instead of many.

  • Availability: logs are available even when the sender machine is unreachable.

  • Security: logs are often deleted or modified once a computer is breached. Logs collected on the central syslog-ng server, on the other hand, can be used to reconstruct how the machine was compromised.

There are four major roles of syslog-ng: collecting, processing, filtering, and storing (or forwarding) log messages.

The first role is collecting, where syslog-ng can collect system and application logs together. These two can provide useful contextual information for either side. Many platform-specific log sources are supported (for example, collecting system logs from /dev/log, the Systemd Journal or Sun Streams). As a central log collector, syslog-ng supports both the legacy/BSD (RFC 3164) and the new (RFC 5424) syslog protocols over UDP, TCP and encrypted connections. It can also collect logs or any kinds of text data through files, sockets, pipes and even application output. The Python source serves as a Jolly Joker: you can implement an HTTP server (similar to Splunk HEC), fetch logs from Amazon Cloudwatch, and implement a Kafka source, to mention only a few possibilities..

The second role is processing, which covers many different possibilities. For example, syslog-ng can classify, normalize, and structure logs with built-in parsers. It can rewrite log messages ( we aren’t talking about falsifying log messages here, but anonimization as required by compliance regulations, for example). It can also enrich log messages using GeoIP, or create additional name-value pairs based on message content. You can use templates to reformat log messages, as required by a specific destination (for example, you can use the JSON template function with Elasticsearch). Using the Python parser, you can do any of the above, and even filtering.

The third role is filtering, which has two main uses. The first one is, discarding surplus log messages, like debug level messages, for example. The second one is message routing: making sure that a given set of logs reaches the right destination (for example, authentication-related messages reach the SIEM). There are many possibilities, as message routing can be based on message parameters or content, using many different filtering functions. Best of all: any of


face
GUADEC 2019, Thessaloniki

Όπως γνωρίζετε, συνεισφέρω σε πολλά projects ανοικτού λογισμικού. Σχεδόν όλα οργανώνουν την ετήσια μάζωξη (την λένε συνέδριο), όπου συναντιούνται οι προγραμματιστές και χρήστες του εν λόγω project. Τις περισσότερες φορές, το οικονομικό αποτελεί πρόβλημα για την συμμετοχή. Το αεροπορικό και η διαμονή είναι τα έξοδα που θα πρέπει να δώσεις συγκεντρωμένα. Η διατροφή στην πόλη διεξαγωγής είναι ίσως λίγο ακριβότερη από την πόλη σου (αν βέβαια έτρωγες συνέχεια έξω).

Τα projects διαθέτουν τα λεγόμενα travel support programs (δείτε του GNOME και του openSUSE) όπου σας βοηθούν οικονομικά στην μεταφορά και την διαμονή σας, συνήθως έως 80%. Θα μου πείτε γιατί όχι 100%; Γιατί απλά θα το βλέπατε σαν ταξιδιωτικό γραφείο και όχι σαν project στο οποίο συνεισφέρετε. Τα projects ανοικτού λογισμικού μπορούν να σας υποστηρίξουν οικονομικά και σε τοπικά συνέδρια όπου θα προωθήσετε το συγκεκριμένο project.

Όμως ας αφήσουμε τον πρόλογο. Ένα από τα πολλά project που συνεισφέρω είναι και το GNOME. Το GNOME διοργανώνει κάθε χρόνο το συνέδριο GUADEC (και για την Ασία το GNOME.Asia). Κάθε χρόνο λοιπόν, κοινότητες στην Ευρώπη παίρνουν το χρίσμα να διοργανώσουν το GUADEC. Φέτος λοιπόν οι τυχεροί ήταν κάτι παιδιά από τη Θεσσαλονίκη. Ο Θάνος, η Βίβια, ο Σεμπάστιαν και εγώ, ξεκινήσαμε την έρευνα να δούμε εάν μπορούμε να διοργανώσουμε το GUADEC στη Θεσσαλονίκη. Κάναμε τις επαφές μας και φτιάξαμε την υποψηφιότητά μας. Το αποτέλεσμα; Διοργανώστε το GUADEC. Άρα για να σας απαντήσω το ερώτημα του τίτλου, ΕΓΩ ΠΡΕΠΕΙ ΝΑ ΠΑΩ.

GUADEC, The GNOME conference

Τι πρέπει να γνωρίζετε:

1. Θα διεξαχθεί στο Πανεπιστήμιο Μακεδονίας. Το Πανεπιστήμιο Μακεδονίας είναι συνδιοργανωτής του συνεδρίου. Μας έχει βοηθήσει όσο δεν φαντάζεστε. Τόσο καιρό δεν το έχουμε προωθήσει ως συνδιοργανωτή. Η αλήθεια είναι ότι έχουμε επικεντρωθεί σε λειτουργικά του συνεδρίου παρά στην προώθηση.

2. Η ημερομηνία είναι η 23 έως τις 28 Αυγούστου. Πρόγραμμα δεν έχει βγει επίσημα αλλά έχουν γίνει δεκτές οι ομιλίες και σύντομα θα βγει το επίσημο πρόγραμμα. Γενικά να γνωρίζετε ότι 23-25 θα είναι οι κύριες ημέρες με τις ομιλίες και οι άλλες 3 θα είναι ημέρες για να hackάρετε το GNOME. Θα υπάρχει θεματολογία, δεν θα είναι πολύ χαλαρά. Βέβαια εμείς θα είμαστε στον χώρο από πιο νωρίς. Σίγουρα από τις 20-21 του μηνός αλλά μην σας πω και πιο νωρίς.

3. Στα πιο βασικά τώρα. Για να έρθετε στο συνέδριο, πρέπει να κάνετε την εγγραφή σας εδώ https://registration.guadec.org. Αρχικά πρέπει να κάνετε το registration και να πάρετε το εισιτήριό σας και έτσι να μας βοηθήσετε να ξέρουμε για πόσα άτομα θα ετοιμάσουμε υλικά, φαγητό, καφέδες κλπ. Εάν δεν αντέχετε οικονομικά, μπορείτε να μπείτε στα επίσημα κανάλια και να ρωτήσετε πως μπορείτε να μπείτε δωρεάν (ΠΑΡΑΚΑΛΩ ΝΑ ΜΗΝ ΡΩΤΑΤΕ ΕΜΕΝΑ. ΘΑ ΣΑΣ ΠΑΡΑΠΕΜΠΩ ΣΤΑ ΚΑΝΑΛΙΑ). Μια εναλλακτική είναι να γίνετε εθελοντής (θα τα πούμε αργότερα αυτά). Εάν δεν είστε από τη Θεσσαλονίκη και θέλετε να μείνετε κάπου οικονομικά, μπορείτε να μείνετε στο προτεινόμενο hostel. Βρίσκεται στο κέντρο της πόλης, πολύ κοντά είναι τα πάντα σε φαγητό, διασκέδαση. Παίρνει λίγο χρόνο μέχρι το Πανεπιστήμιο Μακεδονίας αλλά σε σχέση με άλλες χώρες που έχω πάει, είναι ΠΟΛΥ ΚΟΝΤΑ. Τέλος, καλό είναι να πάρετε και την προσφορά για την σίτιση. Περιέχει 3 μεσημεριανά (μας είπανε ότι θα σκάσετε στο φαγητό. Επίσης θα έχει όλα τα ειδικά γεύματα λακτόζες, γλουτένες, βίγκαν, μίγκαν, σίγκαν κλπ) και 9 καφέδες (μην στεναχωριέστε, υπάρχει και καφετέρια για παραπάνω καφέ). Στην γύρω περιοχή δεν έχει κάποιο γυράδικο. Πρέπει να περπατήσετε 10 λεπτά για να βρείτε κάποιο στην Καμάρα.

Όταν τελειώστε, θα ερωτηθείτε και εάν θέλετε να συμμετάσχετε σε κάποια extra social event όπως εκδρομή στη θάλασσα, πικ-νικ, ποδόσφαιρο κλπ.

Τώρα θα με ρωτήσετε, ρε φιλαράκι, δεν έχω αποφασίσει να γραφτώ. Μπορώ να έρθω τελευταία στιγμή; Θεωρητικά ναι αλλά θα είναι λίγο προχειροδουλειά. Δηλαδή δεν θα έχετε εκτυπωμένο το όνομά σας στο καρτελάκι σας, θα έχετε ένα εκτυπωμένο χαρτί για τη μάσα κλπ.

4. Βλέπεις τα παραπάνω και λες ότι θέλεις να είσαι εθελοντής (για να μπεις και τζάμπα). Τι θα κάνεις; Η αλήθεια είναι ότι δεν ξέρω να σου απαντήσω. Όμως αυτό που μπορώ να σου πω είναι να γραφτείς στην λίστα https://mail.gnome.org/mailman/listinfo/guadec-list και να πεις (στα αγγλικά) ότι θέλεις να γίνεις εθελοντής. Ποια είναι τα επόμενα βήματα; Έτσι για να ξέρεις πάνω κάτω, θα μαζευτούν νωρίτερα (ίσως 22 το μεσημεροβράδυ) για να μπει ο καθένας στο πόστο του. Τι πόστα; Κάποιος στις εγγραφές, κάποιος θα εκφωνεί ποιος είναι ο επόμενος ομιλητής (ή να ψάχνει να τον βρει στην καφετέρια), να κουβαλήσει κάποια πράγματα, στήσιμο-ξεστήσιμο κλπ κλπ.

5. Τα μπλουζάκια που θα τυπωθούν είναι καταπληκτικά. Άλλο να σας το λέω, άλλο να τα φοράτε. Απλά σας λέω ότι είναι το νούμερο 37 στο gitlab όσοι θέλετε σπόιλερ.

Να ευχαριστήσω προσωπικά (θα γίνει και επίσημα) τους χορηγούς γιατί χωρίς χορηγούς, συνέδριο δεν γίνεται. Χαίρομαι ιδιαίτερα για το openSUSE διότι ως γνωρίζετε είμαι από τους πρωτοπόρους που κάναμε την αρχή στην Ελλάδα και καταφέραμε να φέρουμε το συνέδριο στη Θεσσαλονίκη.

Όσοι έχετε έρθει σε κάποιο συνέδριο στο εξωτερικό (και όσοι δεν έχετε έρθει σας ενημερώνω τώρα), θα ξέρετε ότι δεν υπάρχει κάποιο αποδεικτικό ότι παρακολούθησες το συνέδριο ή ότι ήσουν εθελοντής. Προφανώς δεν μπορείς να αποδείξεις ότι ήσουν μέσα στις ομιλίες και δεν έπινες μπύρες σε όλο το συνέδριο. Όμως αυτό που θα γίνει είναι ότι την επόμενη έκδοση GNOME 3.34 θα την ονομάσουν Θεσσαλονίκη. Οπότε μπορείτε να βοηθήσετε στις μεταφράσεις της έκδοσης 3.34. Αν δεν ξέρετε πως, μην ρωτάτε εμένα. Διαβάστε την σελίδα της συμμετοχής και μετά μπορώ να σας απαντήσω σε συγκεκριμένες ερωτήσεις (ΟΧΙ ΓΕΝΙΚΟΥ ΤΥΠΟΥ).

Επίσης φροντίστε όταν έρθετε να μιλήσετε με κόσμο, με εταιρίες. Οι χορηγοί σίγουρα θα έρθουν για να προσλάβουν κάποιον από τους τοπικούς συμμετέχοντες (οι ξένοι ήδη δουλεύουν). Συζητιέται πολύ και ο θεσμός των newcomers. Θα υπάρχουν πολλοί νεοφερμένοι που θα προσπαθήσουμε να τους βάλουμε να μιλήσουν με πεπειραμένους ώστε να νιώσουν ευπρόσδεκτοι.

Τέλος για τους λάτρεις των celebrities, θα έρθει και ο ένας από τους ιδρυτές του GNOME, ο Federico Mena Quintero. Υπάρχουν και άλλα μεγάλα ονόματα. Μέχρι τότε όμως, σηκωθείτε από καρέκλες, πολυθρόνες, ντιβάνια, μπαουλοντίβανα και να σας βλέπω να γράφεστε...

Wednesday
17 July, 2019


face

Veamos cómo poder autocompletar de manera sencilla el cierre de etiquetas html cuando utilizamos el editor Vim para editar este tipo de archivos.

Muchos de los archivos que edito con Vim, son archivos html, y hace poco encontré la forma de poder ahorrar tiempo haciendo que Vim nos autocomplete el cierre de las etiquetas html de manera automática. Veamos cómo.

Este tutorial se une a la serie de artículos que he dedicado en el blog al editor Vim, que cada vez va creciendo más. Hasta ahora hemos aprendido cosas como:

Nos ponemos manos a la obra y veamos cómo Vim puede autocompletar el cierre de etiquetas en archivos html.

Lo primero que tenemos que hacer el editar nuestro archivo de configuración .vimrc y añadir la siguiente línea:

autocmd FileType html set omnifunc=htmlcomplete#CompleteTags

Ahora cuando en nuestro archivo html tengamos que cerrar alguna etiqueta (<ul><li><p><a> o cualquier otra) solo tenemos que escribir </ y después pulsar la combinación de teclas Ctrl+x Ctrl+o y Vim nos cerrará la etiqueta correspondiente.

Y lo hace de forma anidada, así que irá cerrando “de dentro hacia afuera”. Pero ¿por qué no mejorar eso, y en vez de tener que pulsar esa doble combinación de teclas, que Vim nos lo haga de una manera más sencilla? ¡Para eso hemos aprendido a crear abreviaturas!

Volvemos a editar nuestro archivo .vimrc y ahora añadimos una abreviatura. Yo he hecho que cuando escriba tres símbolos < automáticamente lo sustituya por un </ y además “pulse” la combinación Ctrl+x Ctrl+o de la siguiente manera:

:ab <<< </<C-x><C-o>

De esta manera cuando quiera cerrar una etiqueta en un archivo html simplemente tengo que escribir <<< y Vim se encargará de hacer el resto por mí facilitándome la tarea. Sencillo ¿no?

Pero comprobemos si esto es realmente así:


face

 

Apakah Anda siap menerima tantangan dari kami?

Daftar sekarang juga di https://s.id/oSAS19-CfV


Tuesday
16 July, 2019


face

Wavebox on openSUSE

From time to time, I like to play around with the universal packaging available in Linux. It has mostly been AppImages and Flatpak but I wanted to Snap something into my system. After working out an AppArmor issue. Snaps were working fantastically well once again. The application I wanted to try was another Chat Message Unification Application. I had heard wonderful things about Wavebox so it was time to try it out. It’s described as, “A clever new home for cloud apps on your desktop bringing Gmail, Inbox, Outlook, O365, Trello, Slack & over 1000 more apps into a configurable client.”

You can look at the details here on the SnapCraft store.

Wavebox Snap 19

In a terminal I installed Wavebox from the Snap Store:

sudo snap install wavebox

Installation was a snap (haha) and it created an entry in the application menu of KDE Plasma, just as one would expect. It should also be noted that the system tray icon also looks great next to the rest of the icons sitting there too.

Wavebox Snap 20 System Tray.png

When the Application started up, I didn’t notice any lengthy start up time that has been complained about in the past with Snaps. It was delightfully… snappy… and when it settled I was greeted with a pleasant interface. There was no question as to what I needed to do, create an account.Wavebox Snap 2

Going through the process was really quite trivial. You begin by entering your name, email and password. I elected to setup two-factor authentication which did require me to install an application on my phone…

After you have logged in, you can add your first application. I went with Slack, specifically the Bad Voltage slack group. There is a convenient search box right at the top of the uncluttered interface.

I am not 100% sure what the “Pic a Colour” section does, entirely but it does create a ring around thee account on the side tab of the service. Setting up Slack was trivial and has the same basic feel of what you would have in the web browser.

What I think is interesting is the different customization features you can specify for each module you add. What is interesting to me is the ability to put a tab to sleep and stop it after some time of inactivity. I don’t know exactly what that means and how it is implemented but if that is what I am thinking it is, that should be more kind to your system when on battery power. I find with all the services running in either a browser or other Chat Unification applications, the CPU usage is noticeable.

Wavebox Snap 11

I wanted to install the G-suite of tools and began that process by selecting the Gmail icon when adding an application. There is a similar “Pick a Colour” selection then you can choose which services it loads into this “tab”. I didn’t test all the functions but the ones that did worked as expected. The Hangouts button doesn’t give me


face

Apart from our usual development sprint reports, we (the YaST Team) sometimes publish separate blog posts to summarize a new feature or to present an idea we are working on. Lately, several of those posts have been focused on new features of the YaST Partitioner, like the support for Bcache or the new Btrfs capabilities. But today it’s the turn of another part of yast2-storage-ng: the partitioning proposal, also known as the Guided Setup.

As you may know, YaST is an universal installer used to configure all the (open)SUSE and derivative products. Moreover, the installer options and steps can be refined even further by each of the system roles available for each product. The goal of this blog post is to present some ideas aimed to add new possibilities in the area of the storage guided proposal for those who configure the installer for a certain product or system role. With that we hope to ease the life for the creators of SUSE Manager, the SUSE’s purpose-specific distribution to manage software-defined infrastructures.

Although many of the presented capabilities will land soon in openSUSE Tumbleweed they will not be used by default. Not only because they are not targeted to the openSUSE use-case, but also because so far this is just a prototype. That means all texts are subject to change and most screens will get some adaptations before being used in a final product… or maybe they will even be completely revamped.

One Guided Proposal to Rule them All

Although the Expert Partitioner can be used to tweak the storage configuration of any SUSE or openSUSE distribution during installation, the installer always tries to offer a reasonable proposal about it. Moreover, the “Guided Setup” button in the “Suggested Partitioning” screen leads to a wizard that can be used to configure some aspects of such a proposal, as shown in the following diagram (some actions have been blurred just to emphasize the fact that the concrete list of actions will change after each execution of the wizard).

Default Guided Setup wizard

The exact behavior of the Guided Setup is different in every product and, potentially, in every system role. Many things can be adjusted by the creators of the product or the role, like the partitions and LVM volumes to be proposed, the options to be offered in the wizard, the default value for every option and much more. But all those possibilities were still not enough in the case of SUSE Manager and its unique approach to organize the storage devices.

The Strange Case of SUSE Manager

First of all, the SUSE Manager documentation suggests to allocate each of several data directories (/var/spacewalk, /var/lib/pgsql, /var/cache and /srv) in its own dedicated disk when installing in a production environment. For such setup to make sense, it’s absolutely crucial to choose the right disk for every data directory taking into account both the size and the speed of the disks.

The documentation also suggests to use LVM in


face

Veamos cómo cambiar el tamaño de los botones de la barra de título en el tema Breeze del escritorio Plasma de KDE y también el tamaño de la fuente en el título

Soy usuario del escritorio Plasma de la comunidad de KDE, desde los inicios de mi andadura en GNU/Linux, ¡cuando ni siquiera se llamaba Plasma! Soy un tipo fiel, me mantengo usando la combinación de KDE + openSUSE desde hace muchos años.

El entorno de escritorio Plasma de la comunidad de KDE, me parece muy bonito y muy funcional. Con el tema Breeze o Brisa, el equipo de diseño de KDE dio en el clavo, aunque para gustos colores.

En este artículo veremos cómo poder poner en el tema Breeze, los botones de un tamaño menor, y también de paso veremos cómo reducir el tamaño de la fuente de la barra de título.

Esto hará que se reduzca un poco el tamaño de nuestra barra de título, algo que hace tiempo quería saber cómo poder hacerlo.

Para reducir el tamaño de los botones de la barra de título del tema Breeze del entorno de escritorio Plasma de KDE, deberemos ir a las configuraciones del tema de escritorio, para ello escribimos en una consola:

breeze-settings5

Y se nos abrirá una ventana de configuración del tema. Escogemos la pestaña de “Decoración de ventanas Brisa” y en el apartado de “Tamaño de botones” escogemos el tamaño que queremos y aplicamos los cambios.

Veremos que los botones de nuestras ventanas se han reducido. Podéis echar un vistazo a las otras opciones que hay en esos ajustes por si queréis cambiar algo más del aspecto del tema Brisa.

Ahora si queremos reducir la fuente de la barra de título, tenemos que ir a Preferencias de Sistema de KDE, desde el menú de aplicaciones y en el apartado “Aspecto” ir a “Tipos de letras”

En la opción “Título de ventana” escogemos la fuente y el tamaño deseado, si queremos reducirlo, quizás 9 u 8 es un tamaño adecuado. Pero podéis escoger la opción que más se adapte a vuestros gustos.

Aplicamos los cambios y con esto podemos ver que al reducir el tamaño de los botones y de la fuente utilizada, nuestra barra de título de las ventanas también se ha reducido un poco… menos en la ventana de Firefox.

En Firefox a pesa de haber configurado esto, los botones siguen siendo igual de grandes, y de momento no he encontrado la manera de hacer que se vean igual que el resto de botones de ventanas de Plasma.

Espero que os haya gustado el tutorial y el pequeño truco para configurar más aún nuestro escritorio Plasma. Podéis compartir vuestras configuraciones en los comentarios del blog para que sirvan a


Monday
15 July, 2019


face

In my ongoing mission to ensure that I am keeping up on as many wiki pages for openSUSE as I can, I noticed that the information I put in for the terminal installation process for the Budgie Desktop was not right, I didn’t look through the history but I’m sure it was absolutely my fault. Regardless, I decided to test it out in a VM and see that it installs properly and I could play around in it without crashing. Sure enough, it seems to be working well and after switching things up to a dark them, I thought it looked pretty darn good.

A simple command in the terminal makes the magic happen:

sudo zypper install budgie-desktop

After Zypper does its thing, logging out and logging back in will give you a pretty darn decent implementation of the Budgie-Desktop. There isn’t any openSUSE customization with it, as far as I can tell, it runs well and feels clean.

Oddly, instead of a Budgie Logo for the menu it is a GNOME logo. I am not sure if that is the upstream default or not but it just seems odd to me.

Screenshot_opensuse15.1_2019-07-15_19:08:20

Though, I don’t much care for the light theme, that is easily fixed in the Budgie Settings. I went for Breeze-Dark with everything, just because I think that is the best thing going as of today. I must say that the settings are nice, neat and simple which I think works well for this desktop.

Screenshot_opensuse15.1_2019-07-15_19:10:13.png

I noticed that when I switched the icon theme to Breeze Dark the Plasma logo appeared on the menu icon. I guess if you have Gnome with the Adwaita theme it is only reasonable that you would have the Plasma logo with the Breeze theme. It still seems a bit odd to me.

I hung out here and played around, browsed the web, and tested out a few of the tools. I don’t feel like Budgie is quite right for my “home”. It’s a nice home, very well put together, from what little I experienced hanging out, it is just not one I feel compelled to move into.

Final Thoughts

The ease of installing other Desktop Environments (DEs) in openSUSE is super simple and I truly appreciate it. It is also nice to see that playing with other DEs doesn’t seem to mess things up at all. They all seem to cohabitate quite nicely on a single installation.

I am quite sure this is the vanilla configuration of Budgie that is just how openSUSE does Desktop Environments. I do, however think the Budgie Logo or the openSUSE logo would be preferred on the menu but that would be the only real change I would make.

Budgie is a nice, crisp Desktop Environment but it just isn’t for me. I think KDE Plasma has spoiled me. I also need to do a better job of keeping on top of the different wikis hosted by openSUSE. It


face

La comunidad de KDE está mejorando aspectos básicos de distintas partes del escritorio y aplicaciones para pulir errores y mejorar las aplicaciones. Este es un repaso semanal a algunas de esas tareas.

Como ya pudiste leer en otro artículo del blog, parte de la comunidad de KDE está inmersa en la ardua y extensa tarea de pulir y mejorar ciertos aspectos del escritorio Plasma y de las aplicaciones de KDE.

Desde hace ya varias semanas empecé la tarea de traducir y publicar en mi blog los anuncios en inglés para tratar de difundir y dar a conocer el trabajo que realiza la comunidad de KDE

Puedes leer todos los artículos que he traducido en este enlace:

Una semana más Nate Graham nos trae a su blog las novedades en cuanto a mejoras, correcciones de pequeños y grandes errores y nuevas opciones:

En este artículo traduzco, una vez más, el artículo de Nate Graham, para difundir lo que nos traerá KDE. Empezamos…

Ahora sí, sin más preámbulos veamos cuales son esas novedades:

Nuevas características

Corrección de errores y mejoras de funcionamiento


Sunday
14 July, 2019


face

In my quest to remove inefficiency in my life and make activities more functional, I purchased this Gladiator Geartrack Gardening Pack by Whirlpool Corporation. I want to make it understood that I do work for Whirlpool and they in no way sponsor, support or endorse any of this. I was given an opportunity to get this pack at a bit of a discount and the purpose of this kit “fit the bill” for an organizational pain-point at my house. My gardening items have been sitting in a 5 gallon bucket in the garage in the corner with several other items scattered about on the floor or haphazardly shoved on a shelf.

I am continually looking for ways to enhance efficiency. I have more tasks to do in any single day, generally more than I can effectively accomplish. Time is short when running a house, being the sole provider, home educating and wanting to give my kids as many fun or interesting memories through their childhood. Gardening is an activity that I enjoy. It doesn’t take up much time and I can teach my kids a thing or two about caring for plants.

This is another “best effort” attempt at learning Kdenlive, a video editing software package for Linux. I am running this on openSUSE Tumbleweed seemingly trouble free. Feel free to be critical of the video, I have my list of things I need to do in order to improve video content creation. Maybe… someday… it won’t be terrible. I also can evaluate all my areas for improvement on presentation of an idea or thing.

Unboxing, packaging engineering

Since spending time in the product engineering area, I have become more and more impressed with packaging engineering. So much time and effort is put into making sure that products arrive to their destination without damage and most consumers just chuck it and don’t take the time to appreciate it.

Installation

The instructions that come bundled with this pack are nicely detailed. As long as you have the least bit of knowledge and the right tools, following these instructions will be no problem.

The tools I used were a cordless drill, stud finder and a level. It is recommended that you fasten the Geartrack into the wall studs for maximum strength

Quality of Components

The quality of components is pretty clear when you handle them. The Geatrack Channel is solid and stout. It doesn’t have even the slightest bit of flimsiness to it. I think you would be hard pressed to really mess it up.

Gladiator Geartrack Gardening Pack

The hooks are all of solid steel construction with pretty generous welds. The spring retention keeps the hooks in place so they are not likely to just fall off the Geartrack.

The gardening basket is a fine piece of kit that is not only well made, it gives you more storage options than I can immediately use which is far better than the typical insufficiently featured and lacking utility designs you often find


face
Au total, cinq clichés openSUSE Tumbleweed depuis le début du mois de juillet et tous les clichés font preuve d’un excellent niveau d’une stabilité.


face

Debian review title

I have used Debian for years on and off… probably more off than on… but when I had some odd hardware to install Linux, Debian is always the go to distribution. In my mind, Debian is known for old packages and a crusty installer. For many applications, old packages are fine and a crusty installer is not a big deal, after all, my early Linux experience did include installing Debian Linux on HP PA RISC systems. It wasn’t a cake walk but it wasn’t exactly difficult. The Debian installer works well if you are willing to read what is on the screen.

This is my biased review of Debian 10 from an extremely entrenched openSUSE user. I am perfectly happy where I am and have no intention on switching to any other distribution. I will be looking at the KDE Plasma Desktop on Debian and comparing it to my regular home of the KDE Plasma Desktop on openSUSE Tumbleweed.

The bottom line, up front, Debian is great. It is a pure and sterile experience, not much emphasis is put onto the look and feel but it is very apparent that they put their effort into the technical underpinnings. If I had to choose between an artistic piece or a technically sound technology, I will go for the technical merits and do the last mile of polish to satisfy my needs. I can highly recommend Debian to any intermediate user.

Installation

Installation was pretty straight forward. I went with the graphical installation tool and being familiar with the text installer, this was much the same but with more “modern” graphics.

The installer will start off by asking you to select a language and your country.

Next you need to select the keyboard map. The installer will then load components. This takes just a bit.

Next you will set the host name and the domain name. These are each on different screens. I think they could have consolidated this to one screen but that is just my opinion.

Your first “account stop” is setting up the root password with a well written instruction and precautions about setting up the root user. You are also notified that if you leave the password empty, the root account will be disabled and the initial user will be given the power to become root using the sudo command.

Debian 10 8 Installation

You will then be prompted for a Full Name followed by the Username. This too could have probably been put on a single screen but stepping through one at a time has its merits.

After you enter your password for your user account, you’ll be prompted to set the timezone of the system clock.

The partition setup of the system will be next, for the purposes of this installation, I chose the guided – use entire disk and the virtual disk presented itself on the next screen.

For the Partition disks setting, I chose the option recommended for new users and that is all files in


Saturday
13 July, 2019


face

Sébastien Poher aka sogal

About me

I’m 1.80m, I love to wear unreadable thrash metal bands t-shirts and prefer beer over wine (or any sort of drinks really).

My Beginnings

The first computer I ever touched was an Apple II. I remember spending hours playing this one game on a 5 1/2″ floppy disk where I had to drive, via a clunky joystick, a spaceship through the abysses of an asteroid, killing monsters around.

I got into Linux in two steps, first, in 2007 but I was the only one among my friends to use it so I ended up sticking to the shitty OS I had. My next re-discovery of Linux was later in 2012 when I started professional training in system administration.

Why openSUSE

I tried many Linux and BSD distributions but always got frustrated after a while. Leap offered me the exact perfect balance I was looking for between stability, reliability and relative freshness of packages.

My first contribution

I wanted to have an up-to-date package of Tilix (a tiling terminal emulator) so I worked on it; this made me discover the Open Build Service (OBS), which is such a wonderful tool, but above all, I found it easy to contribute. I think that one strength of the openSUSE Project is that the step someone would need to make to start contributing is a really small one.

About the community

I am a bit of a misanthropist so seeing that people from different origins, that do not necessarily know each other, are able to work together in a constructive, peaceful and funny way provides me a good dose of hope!

What I do in the realm of openSUSE

I maintain a small set of packages. It’s fun to do and it makes me learn a lot about the process of creation and all the clockwork behind a distribution. However, the highlight of my openSUSE activities is my involvement in the French openSUSE community through an association called Alionet. We do our best to relay openSUSE’s news and documentation in French (yeah, French people are terrible at English).

Challenges that faces openSUSE

The lack of volunteers among the users community -at least around me- tends to be a real problem. It is hard to get people involved “on the field” and keep them motivated.

openSUSE needs…

A periodic communication targeted for end users. I am glad to see this “People of openSUSE” project being revived, I would be happy to see the same thing happening with short articles about different software available in openSUSE or tips and tricks related to Leap, Tumbleweed or other openSUSE projects. Maybe by the end of the year or next year I will have more time to make this happens.

Me beyond openSUSE

I learn to play drums. It is kinda hard yet funny to see that, at first, my body does not obey my brain but after a while they manage to work together and create


Thursday
11 July, 2019


face

Let’s say you’ve got a computer with a single processor and you want more computational power. A good option is to add more processors since they can mostly use the same technologies already present in your computer. Boom. Now you’ve got a symmetric multiprocessing (SMP) machine.

But pretty quickly you’re going to run into one of the drawbacks of SMP machines with a single main memory: bus contention. When data requests cannot be serviced from a processor’s cache, you get multiple processors trying to access memory via a single bus. The more processors you have, the worse the contention gets.

To fix this, you might decide to attach separate memory to each processor and call it local memory. Memory attached to remote processors becomes remote memory. Now each processor can access its own local memory using a separate memory bus. This is what many manufacturers started doing in the early 1990’s, and they called it Non-uniform Memory Access (NUMA), and named each group of processor, local memory, and I/O buses a NUMA node.

NUMA systems improve the performance of most multiprocessor workloads, but it’s rare for any workload to be perfectly confined to a single NUMA node. All kinds of things can happen that result in remote memory accesses, such as a task being migrated to a new NUMA node or running out of free local memory.

This might sound like the pre-1990 memory bus contention problem all over again, but the situation is actually worse now. Accessing remote memory takes much longer than accessing local memory, and not all remote memory has the same access latency. Depending on how the memory architecture is configured, NUMA nodes can be multiple hops away with each hop adding more latency.

So when a task exhausts all of local memory and the Linux kernel needs to grab free block from a remote node it has a decision to make: which remote node has enough free memory and the lowest access latency?

To figure that out, the kernel needs to know the access latency between any two NUMA nodes. And that’s something the firmware describes with the ACPI System Locality Distance Information Table (SLIT).

What are SLIT tables?

System firmware provides ACPI SLIT tables (described in the section 5.2.17 of the ACPI 6.1 specification) that describe the relative differences in access latency between NUMA nodes. It’s basically a matrix that Linux reads on boot to build a map of NUMA memory latencies, and you can view it multiple ways: with numactl, the node/nodeX/distance sysfs file, or by dumping the ACPI tables directly with acpidump.

Here is the data from my NUMA test machine. It only has two NUMA nodes so it doesn’t give a good sense of how the node distances can vary, but at least we’ve got much less data to read.

$ numactl -H
available: 2 nodes (0-1)
node 0 cpus: 0 1 2 3 4 

face

El comando del “punto” . en el editor #Vim es una interesante herramienta que nos puede ser muy útil.

Continuamos con la serie improvisada de tutoriales sobre el editor Vim, de cosas que voy aprendiendo y que comparto en el blog.

Hasta ahora hemos aprendido cosas como:

Y en esta ocasión veremos qué uso darle al comando del punto “.” y cómo nos puede hacer muy sencillas muchas tareas en Vim.

Este artículo es una traducción/adaptación de un artículo en inglés escrito por Jovica Ilic, a quien pedí permiso para poder utilizarlo en mi blog, que publicó en su web y que te recomiendo visitar:

El comando “.” en Vim lo que hace es repetir el último comando ejecutado, tantas veces como lo pulses. Veamos unos ejemplos de cómo nos puede ayudar al usar Vim.

Pongamos el ejemplo de que queremos borrar 5 palabras en un texto. Para ello podemos borrarlas de una vez mediante el comando 5dw

Esto “nos obliga” a, mientras estamos editando, contar mentalmente el número de palabras que queremos borrar. Y puede que a veces sean más palabras o a veces menos. Aquí es donde el comando del punto . nos viene a ayudar.

Si queremos borrar una cantidad de palabras desde la posición del cursor hacia adelante, y no sabemos la cantidad de palabras a borrar y no queremos contarlas mentalmente, simplemente ejecutamos el comando dw que nos borrará una palabra y después borramos las siguientes palabras pulsando el punto . y repetirá el comando tantas veces como palabras queramos borrar.

El comando del punto . repite el último comando ejecutado. Pero solo aquellos que modifican el contenido del buffer. Por ejemplo, si ejecutamos el comando Ctrl+D para bajar una página del texto, si después pulsamos el punto “.” esto no repetirá el comando bajando otra media página el texto.

Te recuerdo que al pulsar el punto solo se repetirán los comandos que de alguna manera inciden en el buffer, modificando de alguna manera el texto.

Espero que te haya resultado útil y que poco a poco vayas conmigo descubriendo lo que ofrece Vim, o que si ya eres un experto usuario/a de Vim quizás hayas descubierto algo interesante en este u otro artículo de la serie.

Older blog entries ->