#gnu
www-zh-cn @ Savannah: Join us in saying goodbye to our beloved FSF office on August 16!
Dear Translators:
The FSF is officially going remote, so come visit the FSF office one last time. After August 31st, FSF will no longer be residing at the office on 51 Franklin Street.
For the final time, FSF will open the office to everyone who would like to visit the office one last time on Friday, August 16th from 6:00 p.m. - 8:30 p.m. for the move-out party.
You can also leave your words at the member forum:
https://forum.members.fsf.org/t/we-are-closing-down-the-51-franklin-street-office-do-you-have-any-memories-to-share/5614
You can write your own blog as I have done:
https://liberal.codeberg.page/goodbye-51-franklin-street.html
May FSF long live in our mind.
FSF Events: Free Software Directory meeting on IRC: Friday, August 16, starting at 12:00 EDT (16:00 UTC)
Join the FSF and friends on Friday, August 16 from 12:00 to 15:00 EDT (16:00 to 19:00 UTC) to help improve the Free Software Directory.
rush @ Savannah: GNU Rush Version 2.4
Version 2.4 of GNU Rush is available for download.
New in this release:
- Use getgrouplist(3) call, if available;
- Fixes in the rush-po script;
- Bugfixes
FSF Events: Free Software Directory meeting on IRC: Friday, August 9, starting at 12:00 EDT (16:00 UTC)
Join the FSF and friends on Friday, August 9 from 12:00 to 15:00 EDT (16:00 to 19:00 UTC) to help improve the Free Software Directory.
Éditorial d'août 2024
#art #art_libre #artiste #artlibre #cc-by-sa #chanson #copyleft #creative-commons #creative_commons #creativecommons #culture #culture-libre #culture_libre #culturelibre #francophone #français #gnu #gnu-linux #gnulinux #gpl #informatique-musicale #informatique_musicale #informatiquemusicale #libre #libre-art #linux #linux-mao #linux_mao #linuxaudio #linuxmao #logiciel-libre #logiciel_libre #logiciellibre #mao #mao-linux #mao_linux #maolinux #musicien #musiciens #musique #musique-libre #musique_libre #numerique #productionmusicale
Musiciens, comme je vous envie !
Je suis un éternel dilettante. Les leçons de piano, lorsque j’étais môme, m’ont à jamais éloigné du solfège après une année passée aux côtés d’une dame austère qui m’abreuvait de dictées musicales et autres exercices abstraits (c’est ainsi que je le ressentais) plus rébarbatifs les uns que les autres.
J’étais juste un gosse impatient de pouvoir enfin poser ses doigts sur le clavier et de produire du son. Un an à reluquer avec envie ce couvercle de bois désespérément clos. Ce qui devait arriver se produisit et bien sûr, après 12 mois de calvaire je demandais à mes parents de me désinscrire, à jamais dégoûté du solfège et de la théorie musicale. Blocage.
Vers 14 ans, ma grand-mère m’offrit clandestinement une petite guitare classique sur laquelle, avec l’aide de potes plus avancés que moi, j’appris les accords et les doigtés, à l’oreille, évidemment incapable de déchiffrer une partition. Quelques tablatures secourables complétèrent cet apprentissage.
Les années ont passé et, de paliers en paliers, j’ai lentement progressé avec quelques joies et pas mal de frustrations, souvent liées à mon absence de compréhension analytique de ce que j’écoutais.
Puis vint l’ère des machines, du numérique, de MIDI et mes lacunes se révélaient cruellement face aux séquenceurs et autres boîtes à rythmes. J’ai perdu un temps fou à comprendre ou à programmer, toujours dû à mon manque de bases théoriques.
Alors vous qui lisez une partition comme une note de service, qui "entendez" la mélodie et le rythme au fur et à mesure de votre déchiffrage, oui, je vous envie !
Mais l’histoire de la musique populaire fait aussi la part belle aux autodidactes et les outils collaboratifs dont nous disposons ici, enrichis de toute l’aide de notre communauté, permettent à chacun, pour peu de la motivation soit présente, de concrétiser ses idéaux musicaux.
Cadors du solfège, gratteux autodidactes, percussionnistes de coin de table, chanteurs de karaoké, programmeurs virtuoses, un bel été à vous tous et que vive la musique libre !
health @ Savannah: GNU Health Hospital Management patchset 4.4.1 released
Dear community
GNU Health Hospital Management 4.4.1 has been released!
Priority : High
Table of Contents
- About GNU Health Patchsets
- Updating your system with the GNU Health 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.4.1.tar.gz)
Updating your system with the GNU Health control Center
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://docs.gnuhealth.org/his/techguide/administration/controlcenter.html )
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.4.0, 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.4.1: None
Now follow the general instructions at
https://docs.gnuhealth.org/his/techguide/administration/controlcenter.html
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
- Issue #15: readfp on setup.py no longer supported since python 3.12 https://codeberg.org/gnuhealth/his/issues/15
- Issue #33: health orthanc: Errors on imaging request when worklist template set on imaging test type https://codeberg.org/gnuhealth/his/issues/33
For detailed information about each issue, you can visit :
https://codeberg.org/gnuhealth/his/issues
For detailed information you can read about Patches and Patchsets
Happy hacking!
Pixelorama, a powerful and accessible open-source pixel art tool v1.0 is out now
#gnu #linux #opensource #foss #art
"I love good pixel art, and so it's nice to see more tools becoming available for game developers, especially when they're open source too. Pixelorama version 1.0 is out now after 5 years in development. Another fun tool made with Godot Engine!
The 1.0 release brings with it Multiple layer blend modes, non-destructive effects per layer, a new curve tool, an extension explorer system, you can import and export video files, a basic command line interface and much more."
Found something cool for anyone who's a fan of those old SGI workstations from way back in the day:
The MaXX Interactive Desktop
#gnu #linux #tech #foss
"MaXXdesktop is a true re-implementation of the "SGI Desktop" with the added benefits of using a modern software stack of highly tuned loosely-coupled components delivering maximum performance and stability while using as little resources as possible. We believe that high performance computing and energy friendly are not mutually exclusive. What if you could run applications in a smarter, greener and sustainable way? MaXXdesktop aims at improving just that, do more with less."
No hardware failsafe system?
"If it's on fire, it's a hardware problem"
"The objective of electronics is to keep the smoke IN the wires"
Operating systems & software aside, there's no excuse for operating commercial machinery that don't have #OSHA required failsafes even if it's just for operator/employee safety. If the software was calling for increasing temperature because a sensor was saying 0 degrees, that's on the sensor, not the software.
Software that operates with proper machinery with failsafes would be monitoring sensor status AND failsafe status such that temperature increase would be called for ONLY...
IF (sensor=less than setpoint) AND (failsafe not tripped) THEN increase temperature ELSE shutdown with error message.
♲ 𝕕𝕚𝕒𝕟𝕖𝕒 🏳️⚧️🦋 - 2024-07-29 23:10:53 GMT
I want to tell a story. This is the story why I started using #Linux. And why I had no Microsoft products in my house since.That year was 1997. Computers on the manufacturing floor at work were mostly open hardware Z80 controlled GE/Fanuc PLC's... or PC's running a several kilobyte assembly language program connected to parallel port I/O boards. And that older stuff worked like a top 24/7/365 unless the power went out or someone accidentally blasted the steam seals near the desktop computer. They were controlling large production lines long as football fields.
Then some engineer who I will never forgive decided to rewrite all the production machine systems in Visual Basic for Windows 95. Windows and other proprietary systems were crashing like crazy. Remember, this is when Windows didn't use memory page protection and was filled with kernel bugs. It was unreal. If a machine had to be restarted, the production had to be restarted and that made a lot of scrap. There were about 30 active production lines running at one time, limited to the 1.6 megawatt agreement with the utilities. If all the Windows machines crashed, it took about 80,000 pounds of raw materials to restart the production lines. Forklifts would be filling up the dumpster on the back dock.
Every night at midnight, proprietary software known as BackupExec would start at midnight. After about half an hour, the load average would increase on the Oracle database and crash it. Every production machine would routinely push the production report and would crash the entire production line if it wasn't there to sync. The whole plant would shut down shortly after midnight, every night. After a week, this got old, fast.
One night, I had a life changing event with a Windows machine. An operator called on the radio that a plastic extruder was on fire. It was a 330,000 kilowatt PVC extruder and the Microsoft Visual Basic computer was showing zero degrees on every heat zone. Obviously with the fire from the barrel heaters, it was at least several hundred degrees. A few moments later was a loud explosion and the plant floor went dark with chlorine gas. I could see light to the right of me and that's where I ran. When smoke cleared, I could see the extruder barrel had shot the thousand pound head across the plant floor like a canon. Fortunately I was only several feet away from being in front of it, so I lived. Visual Basic had an interesting feature where malfunctions like that happened a lot.
That week, a copy of Redhat Linux 4.1 arrived in the mail. I installed it on my new laptop. It was crazy fast. It did everything I wanted. I compiled the kernel. I compiled everything. It could play mp3 music. And it was reliable. It was all fun and games until some years after the IPO. Google did the same thing. I would soon learn we had a term for this. #enshitification
So this is why I love free open source software and despise walled gardens of software companies. I remember #RMS on #UseNet was a bit crazy then, but he made the #GNU software license that made this possible.
That's my Linux story. And how #Microsoft almost killed me. Other people have #Microsoft horror stories, but this one was mine.
I want to tell a story. This is the story why I started using #Linux. And why I had no Microsoft products in my house since.
That year was 1997. Computers on the manufacturing floor at work were mostly open hardware Z80 controlled GE/Fanuc PLC's... or PC's running a several kilobyte assembly language program connected to parallel port I/O boards. And that older stuff worked like a top 24/7/365 unless the power went out or someone accidentally blasted the steam seals near the desktop computer. They were controlling large production lines long as football fields.
Then some engineer who I will never forgive decided to rewrite all the production machine systems in Visual Basic for Windows 95. Windows and other proprietary systems were crashing like crazy. Remember, this is when Windows didn't use memory page protection and was filled with kernel bugs. It was unreal. If a machine had to be restarted, the production had to be restarted and that made a lot of scrap. There were about 30 active production lines running at one time, limited to the 1.6 megawatt agreement with the utilities. If all the Windows machines crashed, it took about 80,000 pounds of raw materials to restart the production lines. Forklifts would be filling up the dumpster on the back dock.
Every night at midnight, proprietary software known as BackupExec would start at midnight. After about half an hour, the load average would increase on the Oracle database and crash it. Every production machine would routinely push the production report and would crash the entire production line if it wasn't there to sync. The whole plant would shut down shortly after midnight, every night. After a week, this got old, fast.
One night, I had a life changing event with a Windows machine. An operator called on the radio that a plastic extruder was on fire. It was a 330,000 kilowatt PVC extruder and the Microsoft Visual Basic computer was showing zero degrees on every heat zone. Obviously with the fire from the barrel heaters, it was at least several hundred degrees. A few moments later was a loud explosion and the plant floor went dark with chlorine gas. I could see light to the right of me and that's where I ran. When smoke cleared, I could see the extruder barrel had shot the thousand pound head across the plant floor like a canon. Fortunately I was only several feet away from being in front of it, so I lived. Visual Basic had an interesting feature where malfunctions like that happened a lot.
That week, a copy of Redhat Linux 4.1 arrived in the mail. I installed it on my new laptop. It was crazy fast. It did everything I wanted. I compiled the kernel. I compiled everything. It could play mp3 music. And it was reliable. It was all fun and games until some years after the IPO. Google did the same thing. I would soon learn we had a term for this. #enshitification
So this is why I love free open source software and despise walled gardens of software companies. I remember #RMS on #UseNet was a bit crazy then, but he made the #GNU software license that made this possible.
That's my Linux story. And how #Microsoft almost killed me. Other people have #Microsoft horror stories, but this one was mine.