❌

Vue normale

Reçu avant avant-hier

Linux Presentation Day 2025

✇LinuxFr.org : les dépêches
Par :montpellibre · Benoît Sibaud
16 mai 2025 à 09:31

Pour la 7ᵉ année consécutive Montpel’libre annonce la Linux Presentation Day pour la France et l’Afrique, des événements autour du 18 mai 2025 seront organisés pour montrer et démontrer et peut-être même pour certaines et certains « démonstrer » ou plus prosaïquement démystifier, que l’installation et l’utilisation de GNU/Linux n’est pas si compliquée que cela et même à la porter de tous.

Cette année encore Montpel’libre vous présente Linux Presentation Day (ou LPD) relayé par la GULL Academy. Cet événement est l’occasion de découvrir Linux et les logiciels libres. Un grand nombre de groupes d’utilisateurs de Linux (GUL) et/ou Logiciels Libres (GULL) du monde, ainsi que des entreprises et des universités, organisent chaque année, à la même période, des rencontres afin de présenter GNU/Linux et plus largement les Logiciels Libres.

Grâce à la mobilisation exceptionnelle des GUL, chaque année, cette manifestation est une réussite.

Linux Presentation Day (ou LPD) est un événement à grande échelle qui a pour but de promouvoir Linux et les logiciels libres auprès du grand public.

L’idée d’organiser un événement de manière synchronisée sur l’ensemble de l’Europe a été initiée par le groupe d’utilisatrices et d’utilisateurs de Linux berlinois (BeLUG), afin de faire connaître et découvrir Linux et les logiciels libres à un large public et d’éveiller l’attention des médias.

Des présentations, voire l’installation de plusieurs distributions GNU/Linux seront possibles, ainsi que des démonstrations et mini ateliers peuvent être organisés ou toute sorte de manifestation qui feront la part belle au système d’exploitation GNU/Linux.
Alors, à vos agendas ! Le prochain Linux Presentation Day aura lieu autour du 18 mai, mais plus largement sur tout le mois de mai, en Afrique et en France, mais bien sûr partout ailleurs.

Si vous avez des propositions, merci de les indiquer !

Ainsi, nous vous proposons d’inscrire sur cet espace, les activités de votre structure sur les présentations de GNU/Linux qui auront lieu lors du mois de mai. Pour les inscriptions sur l’Agenda du Libre, pensez bien à taguer votre événement avec « linux-presentation-day » (NdM: linux_presentation_day pour LinuxFr.org)
Inscription de votre événement sur framaforms.

Photo d'un événement

Commentaires : voir le flux Atom ouvrir dans le navigateur

La prochaine console Zotac tournera bien sous Linux

✇MiniMachines.net
Par :Pierre Lecourt
14 mai 2025 à 08:14

C’est bien un processeur Strix Point qui sera à bord de la prochaine console portable de Zotac, un AMD Ryzen AI 9 HX 370. On le sait depuis janvier. Cette seconde version de la console Zotac Gaming Zone doit sortir à une date encore indéterminée et cache toujours bien des secrets. Une partie du voile concernant son système d’exploitation a été levée.

Zotac est en effet au travail pour présenter au public un système d’exploitation maison. Une version très retravaillée de la distribution Linux Manjaro. Un choix un peu étrange de la part de Zotac que j’ai du mal à expliquer. Valve propose SteamOS exactement pour ce type de produit que sont les ConsolesPC. Je n’ai pas idée de la qualité des contrats qui lient les différents fabricants à Valve pour obtenir le droit d’employer cette distribution particulière, mais on peut imaginer qu’il s’agit d’une solution d’engagement classique. Pourquoi choisir un développement indépendant qui sera couteux à produire ? Est-ce lié à des engagements avec d’autres produits chez Microsoft ? Est-ce que Zotac veut avoir les coudées franches pour faire précisément ce qu’il veut avec sa nouvelle minimachine ?

Quoi qu’il en soit, Zotac insiste sur un développement parfaitement taillé pour sa console autour de Manjaro. On se doute que derrière cette façade, on retrouvera un univers tournant sous la brique Open Source qu’est Proton pour assurer une compatibilité avec les jeux Windows, mais rien d’autre des motivations du fabricant. 

La nouvelle solution proposera un écran 7 pouces en 120 Hz, de la mémoire LPDDR5x, un stockage non détaillé sur un port M.2 2280 en NVMe PCIe 4.0 et elle embarquera une batterie de 48.5 Wh qui ne précise pas d’autonomie. On retrouvera à bord un module Wi-Fi6e et Bluetooth 5.2. L’interface de jeu devrait être très classique et semblable à celle de la première version. La puce AMD Strix Point apportera évidemment plus de muscles à l’ensemble sans que l’on sache vraiment son impact sur la batterie embarquée. La connectique annoncée serait composée de deux ports USB4, un jack audio combo 3.5 mm et un lecteur de carte MicroSDXC.

Aparté : Avec un peu de recul, ce genre d’annonce est très intéressant à suivre. Il était absolument impensable il y a encore quelques années qu’un constructeur annonce une sortie d’un produit « PC » sous autre chose que Windows. L’évolution proposée par le travail de Valve et l’offre Proton a réellement bousculé la donne.

La prochaine console Zotac tournera bien sous Linux © MiniMachines.net. 2025

I Want to Love Linux. It Doesn’t Love Me Back: Post 2 – The Audio Stack Is a Crime Scene — fireborn

✇Liens en vrac de sebsauvage
12 mai 2025 à 14:35
Jusqu'à l'arrivée de PipeWire, la gestion de l'audio sous Linux c'était le bordel.
Maintenant PipeWire fonctionne à merveille !... sauf que beaucoup d'applications dialoguent toujours avec PulseAudio. Il y a donc une interface PulseAudio-PipeWire, et tout ne marche pas à merveille.
(Permalink)

Security Researchers Create Proof-of-Concept Program that Evades Linux Syscall-Watching Antivirus

✇Slashdot
Par :EditorDavid
4 mai 2025 à 14:34
Slashdot reader Mirnotoriety shared this report from the Register: A proof-of-concept program has been released to demonstrate a so-called monitoring "blind spot" in how some Linux antivirus and other endpoint protection tools use the kernel's io_uring interface. That interface allows applications to make IO requests without using traditional system calls [to enhance performance by enabling asynchronous I/O operations between user space and the Linux kernel through shared ring buffers]. That's a problem for security tools that rely on syscall monitoring to detect threats... [which] may miss changes that are instead going through the io_uring queues. To demonstrate this, security shop ARMO built a proof-of-concept named Curing that lives entirely through io_uring. Because it avoids system calls, the program apparently went undetected by tools including Falco, Tetragon, and Microsoft Defender in their default configurations. ARMO claimed this is a "major blind spot" in the Linux security stack... "Not many companies are using it but you don't need to be using it for an attacker to use it as enabled by default in most Linux systems, potentially tens of thousands of servers," ARMO's CEO Shauli Rozen told The Register. "If you're not using io_uring then disable it, but that's not always easy with cloud vendors."

Read more of this story at Slashdot.

Linus Torvalds Expresses His Hatred For Case-Insensitive File-Systems

✇Slashdot
Par :EditorDavid
27 avril 2025 à 07:34
Some patches for Linux 6.15-rc4 (updating the kernel driver for the Bcachefs file system) triggered some "straight-to-the-point wisdom" from Linus Torvalds about case-insensitive filesystems, reports Phoronix. Bcachefs developer Kent Overstreet started the conversation, explaining how some buggy patches for their case-insensitive file and folder support were upstreamed into the Bcachefs kernel driver nearly two years ago: When I was discussing with the developer who did the implementation, I noted that fstests should already have tests. However, it seems I neglected to tell him to make sure the tests actually run... It is _not_ enough to simply rely on the automated tests. You have to have eyes on what your code is doing. Overstreet added "There's a story behind the case insensitive directory fixes, and lessons to be learned." To which Torvalds replied.... "No." "The only lesson to be learned is that filesystem people never learn." Torvalds: Case-insensitive names are horribly wrong, and you shouldn't have done them at all. The problem wasn't the lack of testing, the problem was implementing it in the first place. The problem is then compounded by "trying to do it right", and in the process doing it horrible wrong indeed, because "right" doesn't exist, but trying to will make random bytes have very magical meaning. And btw, the tests are all completely broken anyway. Last I saw, they didn't actually test for all the really interesting cases — the ones that cause security issues in user land. Security issues like "user space checked that the filename didn't match some security-sensitive pattern". And then the shit-for-brains filesystem ends up matching that pattern *anyway*, because the people who do case insensitivity *INVARIABLY* do things like ignore non-printing characters, so now "case insensitive" also means "insensitive to other things too".... Dammit. Case sensitivity is a BUG. The fact that filesystem people *still* think it's a feature, I cannot understand. It's like they revere the old FAT filesystem _so_ much that they have to recreate it — badly. And this led to a very lively back-and-forth discussion. Slashdot's summary of the highlights:

Read more of this story at Slashdot.

ArcoLinux Lead Steps Down After Eight Years

✇Slashdot
Par :EditorDavid
20 avril 2025 à 15:34
"The time has come for me to step away," ArcoLinux lead Erik Dubois posted last week. ("After eight years of dedication to the ArcoLinux project and the broader Linux community...") 'Learn, have fun, and enjoy' was our motto for the past eight years — and I really had fun doing all this," Dubois says in a video version of his farewell post. "And if we reflect back on this teaching and the building and promoting of Linux, it was fun. But the time has come for me to step away..." Over its eight years ArcoLinux "accomplished several important milestones," reports Linux magazine, "such as creating over 5,000 educational videos; the creation of ArcoInstall; the Carli education project; the Arch Linux Calamares Installer (ALCI); the ArcoPlasma, ArcoNet, ArcroPro, and Ariser variants; and much more." According to Dubois, they weren't just creating a distribution but a mindset. Dubois says that the code will remain online so others can learn from, fork, or remix the distro. He also indicated that ArcoLinux will supply users with a transition package to help them convert their existing ArcoLinux systems to Arch Linux. That package will remove ArcoLinux branding, replace pacman.conf with an Arch and Chaotic-AUR focused config file, and change the arcolinux-mirrorlist to a single source. It's FOSS News describes ArcoLinux as one of those "user-friendly Arch-based distros that give you a bleeding-edge experience." The reasoning behind this move, as shared by Erik, is his advancing age and him realizing that he doesn't have the same level of mental focus or stamina he used to have before. He has found himself making small mistakes, the kind that can negatively affect a major undertaking like this... Come July 1, 2025, the transition period will end, marking a stop to all development, including the deactivation of the ArcoLinux social media handles. The Telegram and Discord communities will stay a bit longer but will close up eventually. "I want to leave ArcoLinux while it's still strong, and while I can look back with pride at everything we've accomplished together," Dubois says in their post...

Read more of this story at Slashdot.

Proxmox Virtual Environment 8.4 est disponible

✇LinuxFr.org : les dépêches
Par :haeda · Xavier Teyssier · Benoît Sibaud · bobble bubble
14 avril 2025 à 14:55

Proxmox Server Solutions GmbH a publié la version 8.4 de sa plate-forme de virtualisation libre Proxmox Virtual Environment (VE). Proxmox VE est sous licence GNU Affero GPLv3. Proxmox Server Solutions propose un support d’entreprise à partir de 115 € par an et par processeur.

Principales nouveautés de la version 8.4

  • Migration à chaud avec des dispositifs médiés :
    Les dispositifs médiés permettent de partitionner les ressources matérielles physiques en plusieurs dispositifs virtuels. Il est désormais possible de migrer des machines virtuelles (VM) en cours d’exécution utilisant des dispositifs médiés, tels que les vGPU NVIDIA.

  • API pour les solutions de sauvegarde tierces :
    Proxmox VE propose une API qui simplifie le développement de plug-ins par les fournisseurs de solutions de sauvegarde externes. Ces solutions de sauvegarde tierces peuvent désormais implémenter directement des fonctionnalités de sauvegarde et de restauration dans Proxmox VE, tout en tirant parti de fonctionnalités avancées.

  • Passage direct de répertoires via Virtiofs :
    La version 8.4 offre la possibilité de partager des fichiers et des répertoires directement entre un hôte et les machines virtuelles (VM) exécutées sur cet hôte. Cette fonctionnalité est rendue possible par virtiofs, qui permet aux machines virtuelles d’accéder aux fichiers et répertoires de l’hôte sans surcharger le système de fichiers réseau. Les systèmes invités Linux modernes sont dotés de la prise en charge native de virtiofs, tandis que pour les invités Windows, l'utilisation de cette fonctionnalité nécessite un logiciel supplémentaire.

  • Mises à jour de tous les composants libres :
    Proxmox VE 8.4 est basé sur Debian 12.10 (“Bookworm”), mais utilise par défaut le noyau Linux 6.8.12. Cette version de Proxmox VE inclut des mises à jour vers les dernières versions des principales technologies open source pour les environnements virtuels, telles que QEMU 9.2.0, LXC 6.0.0. La solution est livrée avec ZFS 2.2.7 et Ceph Squid 19.2.1.

D’autres améliorations incluent un mécanisme de filtrage de sauvegarde plus robuste, des améliorations de la pile SDN (réseau défini par logiciel), et de nouvelles options dans l’installateur ISO.

Commentaires : voir le flux Atom ouvrir dans le navigateur

Fedora Targets 99% Package Reproducibility by October

✇Slashdot
Par :msmash
11 avril 2025 à 22:30
Fedora has proposed a major change for its upcoming version 43 release that aims to achieve 99% package reproducibility, addressing growing concerns about supply-chain security. According to the change proposal announced March 31, Fedora has already reached 90% reproducibility through infrastructure changes including "clamping" file modification times and implementing a Rust-based "add-determinism" tool that standardizes metadata. The remaining 10% will require individual package maintainer involvement, treating reproducibility failures as bugs. The effort will use a public instance of rebuilderd to independently verify that binary packages can be reproduced from source code. Unlike Debian's bit-by-bit reproducibility definition, Fedora allows differences in package signatures and some metadata while requiring identical payloads. The initiative follows similar efforts by Debian and openSUSE, and comes amid heightened focus on supply-chain security after the recent XZ backdoor incident.

Read more of this story at Slashdot.

Forget 'Snow Sequoia'. Now I'm Cheering for Better Linux Hardware

✇Slashdot
Par :EditorDavid
6 avril 2025 à 16:34
It was long-time Slashdot reader uninet who argued "Apple Needs a Snow Sequoia." (That is, Apple needs an upgrade to MacOS Sequoia that's like it's earlier "Snow Leopard" upgrade to "Leopard" OS — an upgrade that's "all about how little it added and how much it took away".) "My recent column on Apple's declining software quality hit a nerve..." he writes in a follow-up. "So why do any of us put up with software that grows increasingly buggy?" "One word: hardware. And that's where I'd love to see someone help Linux take the next step." Apple knows how to turn out very good quality pieces of hardware and, for many purposes, stands alone. That's been largely true for the last couple of decades. The half-decade of Apple Silicon has cemented this position. At any price point Apple contends, Macs, iPads and iPhones are either without peers or at the top of the market in build quality and processing power... [I]f only there were hardware that was as good and worked together as well as Apple's, jumping ship to Linux would be awfully attractive at this juncture... For Apple aficionados troubled by the state of MacOS, the modern GNOME desktop on Linux beckons as a more faithful implementation of the ideals of MacOS than current MacOS does. GNOME is painstakingly consistent across its different apps and exudes the minimalist philosophy with which Apple's hardware shines... Now is a perfect moment for a modern Linux push to take that wind back. What it needs, though, is to solve its remaining weakness on the hardware side. One of the giants of electronics manufacturing, tired of being stuck between the Microsoft and Apple ecosystems, would only need to decide to commit the resources necessary to solve the hardware puzzle... ChromeOS has grown to the extent it does because there is hardware designed for it. Take that and carry it further by making it good hardware utilizing the best Linux software and you'd have something disruptive... Initially, the hardware could be "good enough" for the software, much as Apple's software today is merely "good enough" for the hardware. Iterating from there could lead to a genuine third way of computing. They titled their piece, "I Want a Better Mac, so I'm Cheering for a Better Linux." (Wondering if Dell or Sony could be the one to supply that good hardware...) "I say this not as someone who thinks Linux will ever dominate the personal computing world, but as someone who wants to see a spark of creativity and push beyond mediocrity in it again. "Apple needs a real competitor, one alternatives such as GNOME on Linux could actually be, if only the hardware rose to the occasion."

Read more of this story at Slashdot.

An Interactive-Speed Linux Computer Made of Only 3 8-Pin Chips

✇Slashdot
Par :BeauHD
5 avril 2025 à 00:20
Software engineer and longtime Slashdot reader, Dmitry Grinberg (dmitrygr), shares a recent project they've been working on: "an interactive-speed Linux on a tiny board you can easily build with only 3 8-pin chips": There was a time when one could order a kit and assemble a computer at home. It would do just about what a contemporary store-bought computer could do. That time is long gone. Modern computers are made of hundreds of huge complex chips with no public datasheets and many hundreds of watts of power supplied to them over complex power delivery topologies. It does not help that modern operating systems require gigabytes of RAM, terabytes of storage, and always-on internet connectivity to properly spy on you. But what if one tried to fit a modern computer into a kit that could be easily assembled at home? What if the kit only had three chips, each with only 8 pins? Can it be done? Yes. The system runs a custom MIPS emulator written in ARMv6 assembly and includes a custom bootloader that supports firmware updates via FAT16-formatted SD cards. Clever pin-sharing hacks allow all components (RAM, SD, serial I/O) to work despite the 6 usable I/O pins. Overclocked to up to 150MHz, the board boots into a full Linux shell in about a minute and performs at ~1.65MHz MIPS-equivalent speed. It's not fast, writes Dmitry, but it's fully functional -- you can edit files, compile code, and even install Debian packages. A kit may be made available if a partner is found.

Read more of this story at Slashdot.

Linus Torvalds Gently Criticizes Build-Slowing Testing Code Left in Linux 6.15-rc1

✇Slashdot
Par :EditorDavid
31 mars 2025 à 04:34
"The big set of open-source graphics driver updates for Linux 6.15 have been merged," writes Phoronix, "but Linux creator Linus Torvalds isn't particularly happy with the pull request." The new "hdrtest" code is for the Intel Xe kernel driver and is around trying to help ensure the Direct Rendering Manager header files are self-contained and pass kernel-doc tests — basic maintenance checks on the included DRM header files to ensure they are all in good shape. But Torvalds accused the code of not only slowing down the full-kernel builds, but also leaving behind "random" files for dependencies "that then make the source tree nasty," reports Tom's Hardware: While Torvalds was disturbed by the code that was impacting the latest Linux kernel, beginning his post with a "Grr," he remained precise in his objections to it. "I did the pull, resolved the (trivial) conflicts, but I notice that this ended up containing the disgusting 'hdrtest' crap that (a) slows down the build because it's done for a regular allmodconfig build rather than be some simple thing that you guys can run as needed (b) also leaves random 'hdrtest' turds around in the include directories," he wrote. Torvalds went on to state that he had previously complained about this issue, and inquired why the hdr testing is being done as a regular part of the build. Moreover, he highlighted that the resulting 'turds' were breaking filename completion. Torvalds underlined this point — and his disgust — by stating, "this thing needs to *die*." In a shot of advice to fellow Linux developers, Torvalds said, "If you want to do that hdrtest thing, do it as part of your *own* checks. Don't make everybody else see that disgusting thing...." He then noted that he had decided to mark hdrtest as broken for now, to prevent its inclusion in regular builds. As of Saturday, all of the DRM-Next code had made it into Linux 6.15 Git, notes Phoronix. "But Linus Torvalds is expecting all this 'hdrtest' mess to be cleaned up."

Read more of this story at Slashdot.

❌