#Random Linux

With the release of GNOME 49 the desktop environment has increased its dependency on the systemd project. As a result, GNOME requires more work and patching to get it to run on operating systems which do not run systemd. As one Artix developer stated: "Some of you have probably seen the blog post a few months ago about how GNOME is more strongly depending on systemd. The changes mentioned there have landed into the latest stable versions of the mentioned software (GNOME 49) and do affect us. In particular, the main culprit is the removal of the non-systemd fallback code in gnome-session. This makes it currently impossible to launch gnome-shell/mutter on a non-systemd system. A fairly straightforward patch of using elogind, like what was previously done, no longer works either.

Since we don't have the time or interest to write a new non-systemd codepath for gnome-session, this means that all support for gnome-based desktops has to be dropped. In particular, the affected packages would be gnome-session, gnome-shell, mutter, and gnome-settings-daemon. For now, the old versions are still in the repos but because there is so much intertwining between other GTK/GNOME packages, there is no guarantee they actually work and will later be removed from our repos." This change will exclude GNOME from running on the approximately 90 Linux distributions which do not run systemd by default, unless the packages are patched to work with alternative dependencies.
Click to expand...

approximately 90 Linux distributions which do not run systemd by default
Click to expand...

DistroWatch.com: Put the fun back into computing. Use Linux, BSD.

News and feature lists of Linux and BSD distributions.
distrowatch.com distrowatch.com

OUCH!
 
Cromulent said:
I'm getting up to speed with FreeBSD as I haven't used it in a long time.
Click to expand...

I've been having a play with GhostBSD and there are way too many workarounds and compromises for me to be able to use it as a daily driver.

DRM for example means jumping through hoops just to watch catchup tv.
 
What caught my attention is that freebsd still offerers legacy Nvidia drivers so i thought it might be useful for old cards, maybe i'll have another play with GhostBSD on it's next release.
 
I was going to say Alpine also, though learning to get along with musl instead of glibc can be a steep learning curve like the first time you use Arch.

Flatpaks work if you need a glibc applications but considering the size and extra overhead some people question if it's worth it on alpine as it's no longer a tiny os.
 
www.theregister.com

Russian spies pack custom malware into hidden VMs on Windows

: Curly COMrades strike again
www.theregister.com www.theregister.com
Russia's Curly COMrades is abusing Microsoft's Hyper-V hypervisor in compromised Windows machines to create a hidden Alpine Linux-based virtual machine that bypasses endpoint security tools, giving the spies long-term network access to snoop and deploy malware.

"This hidden environment, with its lightweight footprint (only 120MB disk space and 256MB memory), hosted their custom reverse shell, CurlyShell, and a reverse proxy, CurlCat," Bitdefender senior security researcher Victor Vrabie said in a Tuesday report.
Click to expand...

WOW!, that's inventive.
 

systemd Lands Experimental Support For musl libc - Phoronix

www.phoronix.com www.phoronix.com

Systemd today finally merged support for building against and using the musl libc library. This is a win for Linux distributions like postmarketOS, Alpine Linux, and others that use musl by default as their standard C library or offer it as an option.

Since September has been a pull request for experimental support for building systemd with musl libc. This requires a new version of musl with a recent patch, which has been backported to some distributions like Alpine Linux and postmarketOS, in order to use musl as an alternative to glibc.
Click to expand...

So Alpine Linux may live on with Gnome desktop yet. :)
 
Red Hat has been trying to promote its AI-powered tools lately along with tools for developing new AI technologies. This pro-AI stance has spread into the Fedora distribution where it has resulted in debates and, this week, some amusingly poor results. This past week Fedora Magazine published a guide for setting up and using an AI tool for monitoring, troubleshooting, and managing the distribution: "By enabling an LLM direct access to system information and logs, it is transformed into an active part of the investigation process when troubleshooting an issue. It empowers an LLM to directly query the system state, allowing it to help identify performance bottlenecks, and identify important log entries that might be missed by a manual review."

The demonstration went poorly with the AI giving false information, incorrectly diagnosing a network issue, and repeatedly trying to get the user to run Debian's apt package manager instead of Fedora's own dnf tool.
Click to expand...

LOL :D
 
You must log in or register to reply here.
Back
Top Bottom