Michael G

Video coverage
of the

This Week in Rails newsletter

Practice your command-line skills while seeing how many words you can make from 9 random letters. Read More at Enable Sysadmin

The post Learn Gawk by playing a fun word game appeared first on Linux.com.

Dear community

GNU Health 4.2.1 patchset has been released !

Priority: High

Table of Contents

• About GNU Health Patchsets
• Updating your system with the GNUHealth control Center
• Installation notes
• List of other issues related to this patchset

About GNU Health Patchsets

We provide “patchsets” to stable releases. Patchsets allow applying bug fixes and updates on production systems. Always try to keep your production system up-to-date with the latest patches.

Patches and Patchsets maximize uptime for production systems, and keep your system updated, without the need to do a whole installation.

NOTE: Patchsets are applied on previously installed systems only. For new, fresh installations, download and install the whole tarball (ie, gnuhealth-4.2.1.tar.gz)

Updating your system with the GNU Health control Center

Starting GNU Health 3.x series, you can do automatic updates on the GNU Health HMIS kernel and modules using the GNU Health control center program.

Please refer to the administration manual section ( https://en.wikibooks.org/wiki/GNU_Health/Control_Center )

The GNU Health control center works on standard installations (those done following the installation manual on wikibooks). Don’t use it if you use an alternative method or if your distribution does not follow the GNU Health packaging guidelines.

Installation Notes

You must apply previous patchsets before installing this patchset. If your patchset level is 4.2.1, then just follow the general instructions. You can find the patchsets at GNU Health main download site at GNU.org (https://ftp.gnu.org/gnu/health/)

In most cases, GNU Health Control center (gnuhealth-control) takes care of applying the patches for you. 

Pre-requisites for upgrade to 4.2.1: None

Now follow the general instructions at

 https://en.wikibooks.org/wiki/GNU_Health/Control_Center

 

After applying the patches, make a full update of your GNU Health database as explained in the documentation.

When running “gnuhealth-control” for the first time, you will see the following message: “Please restart now the update with the new control center” Please do so. Restart the process and the update will continue.

 

• Restart the GNU Health server

List of other issues and tasks related to this patchset

• bug #64014: Update gender identity in patient evaluations and reports
• bug #64009: Include signing health professional and avoid scrolling in patient evaluation
• bug #64007: Summary report is not using FreeFonts family
• bug #63993: Python-sql error on patient evaluation report

Update gender identity in patient evaluations and reports

For detailed information about each issue, you can visit :

 https://savannah.gnu.org/bugs/?group=health

 

About each task, you can visit:

 https://savannah.gnu.org/task/?group=health

For detailed information you can read about Patches and Patchsets

• https://en.wikibooks.org/wiki/GNU_Health/Patches_and_Patchsets

Google announced today that it would enable WebGPU support in its Chrome browser by default starting in version 113, currently in beta. In development since 2017, WebGPU is a next-generation graphics API that aims to bring the benefits of low-overhead APIs like Microsoft’s Direct3D 12, Apple’s Metal, and Vulkan to web browsers and other apps. WebGPU support has been available but off by default in Chrome for a while now, because the API wasn’t finalized and things could break from update to update. Google says that Mozilla and Apple will eventually support WebGPU in Firefox and Safari, and browsers like Microsoft Edge and Opera that rely on the Chromium browser engine can presumably choose to switch it on just as Google has. Chrome 113 supports WebGPU on Windows, macOS, and ChromeOS to start, with “support for other platforms” like Linux and Android “coming later this year.” This browser version should roll out to all Chrome users sometime in May. I’ve never really needed any advanced 3D rendering in my day-to-day browsing, but that might just be a case of the chicken and the egg.