For the past year, I’ve been posting to a private server that I was running. Now that server is offline because I need to save money and so I’ll be writing here again.

Esta tecnologia é impressionante apresentada pela NVIDIA, Neural graphics primitives (NeRF) reconstrói cenas 3D a partir de imagens 2D. A técnica utiliza a predição do campo de radiância , ou seja, prevendo a cor da luz que irradia em qualquer direção. Segundo a NVIDIA este princípio computacional é a mais rápida até o presente momento. Assim proporcionando um tempo 1000x menor com renderizações em 1080p em insignificantes milissegundos.

Principais evoluções:

• utilização uma determinada GPU para a tarefa do algoritmo de renderização/treinamento, que são muito mais rápidos do que tensores densos;
• uma eficaz pequena rede neural, mais rápida do que rotinas de multiplicação de matriz de em geral;
• e por último, tecnica da NVIDIA (codificação de grade de hash multiresolução), e disponibiliza uma melhor velocidade/qualidade comparado as outras técnicas.

NeRF utiliza a lib CUDA Toolkit e a biblioteca Tiny CUDA Neural Networks. O código fonte esta disponível nesta página; de acordo com a NVIDIA, a rede neural é leve o suficiente para rodar facilmente em uma única GPU.

Spending less and less time on each track in Weeklybeats is making me a little nervous as to whether I will be able to finish such a marathon.

However a radical constraint of a single hour to lay down a pattern and record a jam, perhaps spending a few extra minutes to produce a video, has been extremely satisfying.

Even not being able to figure out how to do dual mono mix on the M8 is not a show stopper in such scenario (apologies to every one using headphones).

I hope a proper spring comes soon as I can’t wait to FPV. This one pack in the garden was painful on the fingers.

Previously, Previously, Previously, Previously, Previously.

Tumbleweed es una distribución «Rolling Release» de actualización contínua. Aquí puedes estar al tanto de las últimas novedades.

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 esta semana.

El anuncio original lo puedes leer en el blog de Dominique Leuenberger, publicado bajo licencia CC-by-sa, en este este enlace:

• https://dominique.leuenberger.net/blog/2022/04/opensuse-tumbleweed-review-of-the-week-2022-13/comment-page-1/#comment-338088

El anuncio original de esta semana ha coincidido con el famoso April’s fool de la cultura anglosajona, similar el día de los inocentes, donde se gastan bromas.

Por eso el anuncio en inglés «insinuaba» que para evitar retrasos innecesarios en la publicación de nuevas «snapshots» se iba a dejar de utilizar openQA y se publicarían directamente las snapshots todos los días a las 5 pm. Porque los desarrolladores y empaquetadores no se equivocan nunca y confiamos ciegamente en ellos… Bueno, obviamente esto no es cierto

Lo que sí es cierto es que en esta semana se han publicado 4 snapshots (0324, 0328, 0329, y 0330).

Que entre otras han traído estas actualizaciones:

• GStreamer 1.20.1
• Snapper 0.10.0
• Mozilla Firefox 98.0.2
• systemd 250.4
• timezone 2022a
• ibus 1.5.26 – soluciona algunas incompatibilidades con GNOME 42

Y en próximas actualizaciones podremos disfrutar de:

• Linux kernel 5.17.1
• KDE Plasma 5.24.4
• Mesa 22.0.1
• gcc12: se está preparando la migración a esta nueva versión del compilador
• procps-ng 4.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

• • • ¿Por qué deberías utilizar openSUSE Tumbleweed?
    • zypper dup en Tumbleweed hace todo el trabajo al actualizar
    • ¿Cual es el mejor comando para actualizar Tumbleweed?
    • Comprueba la valoración de las «snapshots» de Tumbleweed
    • ¿Qué es el test openQA?
    • http://download.opensuse.org/tumbleweed/iso/
    • https://es.opensuse.org/Portal:Tumbleweed

——————————–

Dear Tumbleweed users and hackers,

During this week, we only managed to get 4 snapshots (0324, 0328, 0329, and 0330) out of the door. Seems QA is slowing us down too much, so I decided to give up on it. To make Tumbleweed more plannable for upgraders, the new process will foresee a fixed time when a snapshot will go out – daily at 5 pm UTC. We will just ship out whatever we have built by that time. This is a minimal tradeoff between stability and plannability – after all, we all trust our developers and maintainers and we know that they test things before sending them your way. So no more need to slow down using QA!

Anyway, the 4 snapshots we delivered during this week contained these updates:

• GStreamer 1.20.1
• Snapper 0.10.0
• Mozilla Firefox 98.0.2
• systemd 250.4
• timezone 2022a
• ibus 1.5.26 – fixes some incompatibilities with GNOME 42

Of course, we continue planning what will come through in the next few days; currently, the plan includes:

• Linux kernel 5.17.1
• KDE Plasma 5.24.4
• Mesa 22.0.1
• gcc12: we won’t be switching to it as the default compiler yet, but we will start using the provided libstdc libraries from gcc12 (phazes migration, as done in the past)
• procps-ng 4.0

The latest pull request to syslog-ng adds a really useful feature: the flip-parser(): https://github.com/syslog-ng/syslog-ng/pull/3971

It allows you to flip the message text, reverse it, or both. As I also reported a couple of minor problems related to UTF-8 character handling, this PR most likely will not be merged today. However, you can compile it yourself, or if you use openSUSE Tumbleweed, use my packages from the openSUSE Build Service.

You can read the rest of my blog at https://www.syslog-ng.com/community/b/blog/posts/new-syslog-ng-parser-flip-parser

Sigo con la nueva sección en el blog dedicado a los Scripts de Kwin, esas pequeñas modificaciones a Kwin que le confieren nuevas funcionalidades. Y aunque he cambiado el título por razones de accesibilidad voy a hablar de Autocompser o cómo evitar los efectos 3D en aplicaciones en pantalla completa o lo que técnicamente se llama compositing.

Cómo evitar los efectos 3D en aplicaciones en pantalla completa – Scripts de Kwin (III)

Me encanta seguir encontrando nuevas funcionales no oficiales para KWin con los que seguir experimentando con nuestro escritorio, y más cuando éstas pueden ayudarme a ser más eficiente al utilizar mis ordenadores.

En el blog ya hemos hablado de algunas de ellas, como es el caso de KWin dynamic workspaces, de Mudeer, Windows Gaps o Always Open on Primary Screen scripts que mejoran el comportamiento de nuestro entorno de trabajo, pero últimamente están apareciendo tantos en la Store de KDE que no hay duda que merecen un hueco constante en el blog.

De esta forma, me complace presentaros Autocomposer una creación de es20490446e que evita los efectos 3D que en ocasiones relantizan el funcionamiento de las aplicaciones que se abren pantalla completa en nuestro escritorio.

Y es que una característica de Plasma es que se lleva bien con entornos 3D de escritorio, tal y como se lee en la página userbase de KDE, KWin es compatible con composición, que consiste en utilizar efectos 3D para manejar tus ventanas. Y esto que es bueno para el mayor tiempo funciona muy bien, algunas ocasiones puede no ser oportuno.

Y Y como siempre digo, si os gusta el script podéis “pagarlo” de muchas formas en la mutante página de KDE Store, que estoy seguro que el desarrollador lo agradecerá: puntúale positivamente, hazle un comentario en la página o realiza una donación. Ayudar al desarrollo del Software Libre también se hace simplemente dando las gracias, ayuda mucho más de lo que os podéis imaginar, recordad la campaña I love Free Software Day de la Free Software Foundation donde se nos recordaba esta forma tan sencilla de colaborar con el gran proyecto del Software Libre y que en el blog dedicamos un artículo.

Más información: KDE Store

La entrada Cómo evitar los efectos 3D en aplicaciones en pantalla completa – Scripts de Kwin (III) se publicó primero en KDE Blog.

En estos dí­as me apetece las entradas ligeras. De esta forma comparto con vosotros unos cursores minimalistas para tu PC sencillos y muy agradables a la vista. Se trata los cursores Nordzy, los cuales tiene un aspecto muy planos pero con toques de colores que se adaptan a cualquier estilo de escritorio.

Cursores minimalistas para tu PC, Nordzy

Nacidos de la mano y de la mente de alvatip nos llegan los cursores Nordzy un conjunto de cursores ideales tanto para temas claros y oscuros basados en los temas Vimix y cz-Viator.

Como se puede ver en la imagen superior, los cursores Nordzy se adaptan perfectamente a cualquier estilo de escritorio gracias a su borde grueso y oscuro.

Y como siempre digo, si os gusta este conjunto de cursores Nordzy podéis «pagarlo» de muchas formas en la página de KDE Store, que estoy seguro que el desarrollador lo agradecer?: puntúale positivamente, hazle un comentario en la página o realiza una donación. Ayudar al desarrollo del Software Libre también se hace simplemente dando las gracias, ayuda mucho más de lo que os podéis imaginar, recordad la campaña I love Free Software Day 2017 de la Free Software Foundation donde se nos recordaba esta forma tan sencilla de colaborar con el gran proyecto del Software Libre y que en el blog dedicamos un artículo.

Más información: KDE Store

Cómo cambiar el tema de los cursores en Plasma

Al igual que con los iconos hay varias formas de cambiar el tema de cursores en Plasma, pero la más fácil es:

• Abrir las Preferencias del Sistema
• Ir a la sección Tema de Cursor
• En esta ventana pinchar en «Obtener nuevos temas»
• Buscar Material, seleccionar el estilo y dar a instalar.
• Seleccionar el tema y aplicar.

Si tenéis dificultad, simplemente se debe descargar a tu disco duro y extraer el tema en «/usr/share/icons» o «~/.icons».

Rápido, sencillo y efectivo, como la mayoría de cosas en en el escritorio Plasma de la Comunidad KDE.

La entrada Cursores minimalistas para tu PC, Nordzy se publicó primero en KDE Blog.

 So I've updated my Clang to the newly released version 14, and while doing the LibreOffice rebuild afterwards I noticed that it seemed to build faster. I didn't measure it, but the build finished sooner than I expected. So of course I've measured it.

As a simple reference I used my year-old post about Clang 11 building faster with PCH, where Calc'c Library_sc built in 4 minutes and 39 seconds. And indeed now it's faster:

 1105.84user 88.35system 2:55.07elapsed 682%CPU (0avgtext+0avgdata 1666576maxresident)k
 180904inputs+2272520outputs (41390major+23529938minor)pagefaults 0swaps

Just to make sure it's not something else, I went back to Clang 13 to test it:

 1581.76user 93.84system 4:14.75elapsed 657%CPU (0avgtext+0avgdata 1916380maxresident)k
 153912inputs+2316696outputs (41891major+27245569minor)pagefaults 0swaps

So yes, it's real, and it's the compiler. It also suggests that there was an improvement also between Clang 11 and Clang 13, although not as noticeable as this.

I have no idea why that is, it seems too big of a difference to be just something random, but I see nothing relevant in the release notes (and it's not DWARF5, I tested that one). I also have no idea if it's a code change or if it's the compiler being faster because it generates faster code and is self-built. But hey, it's nice. I still vaguely remember the times when I was trying to avoid full Calc rebuilds like a plague, but that seems like a long time ago.

It is our pleasure to announce the availability of the first installation image based on D-Installer. Since our initial announcement in January, we have been working on going from a non-working proof-of-concept to something that you can actually use.

This article aims to summarize project's current status and what you can expect from the near future. Additionally, we will dig a bit into some internal details so you have a better overview of the path we are following.

D-Installer (kind of) works​

D-Installer can install openSUSE Tumbleweed in simple scenarios. But, please, bear in mind that it is still an experimental project, so it is better to use a virtual machine if you decide to give it a try. After all, we do not want to be responsible for any data loss. 😉

You can grab a Live ISO from OBS. We refresh this image as often as possible to include the latest D-Installer changes for testing purposes. Once the ISO boots, log into the installer using "root" as user and "linux" as password and you should see the "Installation Summary" page.

As we do not include any repository in the image, you need the machine to be connected to Internet so it can access Tumbleweed packages.

How D-Installer looks now​

The "Installation Summary" page is the central point in the D-Installer's user interface. It allows the user to check the installation settings at a glance. You can think of this page as the "Installation Settings" screen in YaST. The main difference is that, in this case, it is the starting point, so you do not need to traverse any wizard to get into it.

The overview is reduced to a few sections: language and product selection, partitioning settings, and users management.

Unsurprisingly, the language selector allows setting the language in the installed system. Take into account that, at this point, the user interface is not localized yet, so it does not affect the installer itself. Moreover, we would like to add support to change the keyboard layout in the future.

Software selection is pretty limited by now. D-Installer allows you to select which product to install, but that's all. Picking patterns or system roles is not supported yet.

Regarding partitioning, D-Installer relies on the YaST guided proposal, although it only allows selecting a device to install the system on. We plan to offer most of YaST's guided partitioning settings (using multiple disks, choosing a file system type, etc.).

Last but not least, D-Installer allows configuring the root's authentication (password or SSH public key) and/or creating a first user to log into the installed system, similar to what YaST supports.

Once you tweak the installation options, clicking the Install button starts the installation.

YaST, D-Bus, React and Cockpit​

We promised to dig a little into the details, so here we go. When it comes to the architecture, the approach has not changed that much from the one we described in the initial announcement. It is composed of three different parts: a system service, a D-Bus interface, and a web user interface.

The core is the D-Installer system service, which uses YaST libraries to inspect and install the system. We are reusing as much YaST code as possible, but at the same time, we are trying to use only the bits that we need. This service provides a D-Bus interface, so the user interface can interact with it. We are trying to keep the D-Bus interface decoupled from the business logic, although we do not plan to replace it for anything else.

Regarding the user interface, we decided to build a React application using PatternFly components. Why PatternFly? You will understand the reason in a minute if you keep reading. :-)

How do the components we have described talk to each other? That's an interesting question. Instead of rolling our own solution, we decided to rely on Cockpit. So we use Cockpit's infrastructure to connect the UI and the system service (through D-Bus). We even use Cockpit's web server to expose the UI in the installation medium.

And that's actually the main reason to use PatternFly. There is a chance that we can reuse parts of the installer UI in a Cockpit module in the future. Time will tell.

What to expect from now​

We have learned a lot during this iteration, so we will use that knowledge to develop a roadmap. However, there are some areas we would like to work on soon that should get a prominent place in such a roadmap. Let's have a look at some of them.

Error reporting and user interaction​

Our D-Installer service can send information about its current status and the installation progress. However, it is pretty bad at error reporting and cannot ask the user for additional information. For instance, it does not implement any mechanism to ask for the password if it finds an encrypted disk while analyzing the storage devices.

We consider this a critical requirement, so we would like to develop a reliable solution in the next iteration.

Better software handling​

Selecting a product is not just picking a set of packages: it might affect the installer's behavior. For instance, if you want to install MicroOS, the partitioning proposal needs to be adapted to mount the root file system as read-only. Not to mention showing products' licenses or release notes. So it is not that simple.

Moreover, we have the concept of system roles, which may affect the software selection, services configuration, etc.

As there are many moving pieces, we need to define how far we are going with software handling. Of course, licenses and release notes are a must. But do we plan to support system roles? Most likely, yes. Which options would be supported? And what about selecting patterns or just individual packages? Too many open questions yet.

Full guided proposal supported​

We do not plan to bring the partitioner to the web interface anytime soon. Instead, our plan is to support all the guided partitioning options, so you can select multiple devices, choose a different file system, enable LVM, use encryption, etc. So, in the medium term, it looks like a fair trade.

The user interface​

We think that the user interface is good enough for the first iteration, but given that we plan to add support for more features, we need to work with our UX experts to improve the overall approach. For instance, using pop-ups all over the place is far from ideal.

Not to mention that, although we are using PatternFly, we try to stick to EOS Design System principles, so we might need some help.

Share your opinion​

Now that you have something to try, it would be great if you shared your opinion. You can contact us through the GitHub project's page or, as usual, in our #yast channel at Libera.chat or the YaST Development mailing list.

Have a lot of fun!