to be absolutely clear: alpine is *not* switching to systemd or implementing a 'systemd compatibility layer'.
-
to be absolutely clear: alpine is *not* switching to systemd or implementing a 'systemd compatibility layer'.
https://www.linuxjournal.com/content/alpine-linux-experiments-systemd-compatibility-while-keeping-its-lightweight-identity is literally AI slop
@ariadne lmfao the hoax generators be generating hoaxes -
R relay@relay.mycrowd.ca shared this topic
-
to be absolutely clear: alpine is *not* switching to systemd or implementing a 'systemd compatibility layer'.
https://www.linuxjournal.com/content/alpine-linux-experiments-systemd-compatibility-while-keeping-its-lightweight-identity is literally AI slop
@ariadne
Linux Urinal also slopped out an article that misrepresented Loss32 (project for running Wine as the primary desktop environment, 'cause it's easier and more helpful than making endless Wine frontends) as just another "modern Linux for 32-bit notebooks"-project.
I hope @hikari is as disappointed as I am -
to be absolutely clear: alpine is *not* switching to systemd or implementing a 'systemd compatibility layer'.
https://www.linuxjournal.com/content/alpine-linux-experiments-systemd-compatibility-while-keeping-its-lightweight-identity is literally AI slop
@ariadne I'm glad to hear it
I was looking for a tidier and more focussed disti some time ago, and looking more closely I should probably have chosen Alpine -
@ariadne Yeah, it's probably going to happen with something particularly dumb too. I can already see it coming...
-
@techokami @neal @ariadne Take a look at the "About Us" page, no mention of the current people. The listed-as-former staff last contributed around 2019...
-
@ariadne
Linux Urinal also slopped out an article that misrepresented Loss32 (project for running Wine as the primary desktop environment, 'cause it's easier and more helpful than making endless Wine frontends) as just another "modern Linux for 32-bit notebooks"-project.
I hope @hikari is as disappointed as I am@moses_izumi @ariadne do link the article to remind me?
-
@moses_izumi @ariadne do link the article to remind me?
-
a lightweight operating system built from scratch with one goal in mind — giving old and low-resource computers a new lease on life
Loss32 began as a personal project by a group of open-source enthusiasts frustrated with how quickly modern software has moved past older machines.
The name Loss32 stems from its focus on “losing” unnecessary bloat — keeping only what’s essential — and the fact that it targets 32-bit and low-resource systems that many other distros are abandoning.
is this entire thing an AI hallucination? it's genuinely unbelievably bad, there's basically no relation whatsoever to anything I wrote on loss32.org
-
@techokami @neal @ariadne Take a look at the "About Us" page, no mention of the current people. The listed-as-former staff last contributed around 2019...
-
to be absolutely clear: alpine is *not* switching to systemd or implementing a 'systemd compatibility layer'.
https://www.linuxjournal.com/content/alpine-linux-experiments-systemd-compatibility-while-keeping-its-lightweight-identity is literally AI slop
@ariadne Shocking title plus AI slop is a recipe for clicks nowadays. Its just tabloids for the internet.
-
@techokami @neal @ariadne Either that, or this new fellow is doing a Jordan Breeding on a defunct site. Maybe somewhere in the middle.
-
a lightweight operating system built from scratch with one goal in mind — giving old and low-resource computers a new lease on life
Loss32 began as a personal project by a group of open-source enthusiasts frustrated with how quickly modern software has moved past older machines.
The name Loss32 stems from its focus on “losing” unnecessary bloat — keeping only what’s essential — and the fact that it targets 32-bit and low-resource systems that many other distros are abandoning.
is this entire thing an AI hallucination? it's genuinely unbelievably bad, there's basically no relation whatsoever to anything I wrote on loss32.org
@moses_izumi @hikari I see "George" has done it again!
-
@ariadne Woho! Thanks for considering using udev in Alpine! It was the thing which forced me to return to Arch, while I would prefer to use Alpine. I've tried to use mdev + libudev-zero but it had a lot of quirks, so I switched to eudev but it had problems with mounting encrypted USB drives and some other quirks, so I tried to just use mount, but while on (some?) BSDs you can allow mount without root when user have permissions for both a device and a mount point, Linux does not.
Almost everything depends on libudev…
@aelspire Alpine already uses a udev implementation, eudev which is basically compatible with libudev.
-
@aelspire Alpine already uses a udev implementation, eudev which is basically compatible with libudev.
@ariadne Yes, I'm aware of it and tried to use it, but not everything is working. In my case mounting LUKS-encrypted USB drive from Thunar sidebar was not working, and I have almost all my USB drives encrypted. I also remember some quirks with my graphic tablet (Wacom Bamboo) but I'm not sure if those were eudev fault.
-
@ariadne Yeah, it's probably going to happen with something particularly dumb too. I can already see it coming...
-
R relay@relay.an.exchange shared this topic
-
@ariadne linuxjournal is slop too now?
@hexaheximal@mstdn.social @ariadne@treehouse.systems banned by lobste.rs 9 months ago so not even a recent thing
-
eudev exists, at least today, primarily because there's a vocal subset of people who get extremely angry if a package name or file on disk includes the word "systemd" in it, and will not consent to running a udev implementation if any internal filename happens to be /usr/lib/systemd
These people literally configure their package manager to silently delete any files from ANY package matching the glob `*systemd*`. Prank tip: write a program including "systemdetails.py".
-
eudev exists, at least today, primarily because there's a vocal subset of people who get extremely angry if a package name or file on disk includes the word "systemd" in it, and will not consent to running a udev implementation if any internal filename happens to be /usr/lib/systemd
These people literally configure their package manager to silently delete any files from ANY package matching the glob `*systemd*`. Prank tip: write a program including "systemdetails.py".
Also relevant, Gentoo dropped eudev a year and a half ago on the grounds that it serves no purpose given systemd-utils can install standalone udev, and eudev was unmaintained and broken and did not in fact provide the library APIs which software compiled against, due to its being unmaintained:
Nonetheless, Gentoo still proudly supports non-systemd installs.
-
to be absolutely clear: alpine is *not* switching to systemd or implementing a 'systemd compatibility layer'.
https://www.linuxjournal.com/content/alpine-linux-experiments-systemd-compatibility-while-keeping-its-lightweight-identity is literally AI slop
-
Also relevant, Gentoo dropped eudev a year and a half ago on the grounds that it serves no purpose given systemd-utils can install standalone udev, and eudev was unmaintained and broken and did not in fact provide the library APIs which software compiled against, due to its being unmaintained:
Nonetheless, Gentoo still proudly supports non-systemd installs.
@eschwartz @zyx @ariadne oh man maybe i should switch back to gentoo
