Richard Stallman Talks Red Hat, AI, and Ethical Software Licenses at GNU Birthday Event

We should stop calling ChatGPT and other generative AI software “artificial intelligence,” according to Stallman, because “there’s nothing intelligent about them.”

The post Richard Stallman Talks Red Hat, AI, and Ethical Software Licenses at GNU Birthday Event appeared first on FOSS Force.



Source: FOSS Force – Richard Stallman Talks Red Hat, AI, and Ethical Software Licenses at GNU Birthday Event

How to Install TIG Stack (Telegraf, InfluxDB, and Grafana) on Rocky Linux

The TIG (Telegraf, InfluxDB and Grafana) Stack is an acronym for a platform of open-source tools to make the collection, storage, graphing and alerting of system metrics easier. You can monitor and visualize metrics such as memory, disk space, logged-in users, system load, swap usage, uptime, running processes etc. from one place.

Source: LXer – How to Install TIG Stack (Telegraf, InfluxDB, and Grafana) on Rocky Linux

Vulnerable Arm GPU drivers under active exploitation (ars technica)

Ars technica reports
on an Arm advisory
regarding exploitable vulnerabilities in a number of
its GPU drivers.

The most prevalent platform affected by the vulnerability is
Google’s line of Pixels, which are one of the only Android models
to receive security updates on a timely basis. Google patched
Pixels in its September update against the vulnerability, which is
tracked as CVE-2023-4211.

As the article notes, the story on fixes for other devices is less clear.

Source: LWN.net – Vulnerable Arm GPU drivers under active exploitation (ars technica)

[$] Revisiting the kernel's preemption model, part 2

In last week’s episode, a need to preempt
kernel code that is executing long-running instructions led to a deeper
reexamination of how the kernel handles preemption. There are a number of
supported preemption modes, varying from “none” (kernel code is never
preemptible) to realtime (where the kernel is almost always preemptible).
Making better use of the kernel’s preemption machinery looked like a
possible solution to the immediate problem, but it seems that there are
better options in store. In short, kernel developers would like to give
the scheduler complete control over CPU-scheduling decisions.

Source: LWN.net – [$] Revisiting the kernel’s preemption model, part 2