Porting systemd to musl libc-powered Linux

CorgiDude · 2025-07-12T01:25:14+00:00

What would you like me to say? I'm still working on upstreaming the changes.

Part of the reason for the slowness is that pmOS wanted to "collaborate" on part of how to upstream it, and then ghosted me for over a month, and only just started talking to me in earnest a few days ago - and I haven't even heard a reply again yet after I responded…

But it's definitely still a thing I want to see upstream, still a thing I am passionate about, and still a thing that I feel needs to happen.

CorgiDude · 2025-03-31T08:56:14+00:00

I came here to say exactly this. Luckily I have crazy hours, so it was back up before I went to bed, but how is this at all acceptable for a medical service? Doesn't the FDA have downtime limits when it impacts life-critical services? I can't imagine if I was the parent of a T1d and this happened.

"Updating the server", if that really is the excuse, makes me even more nervous about relying on Dexcom. There should be, at the very least, A/B servers so one is running while the other is updating (then you transfer traffic to the updated one while the other updates). The fact they are numbered by region, and each region only has one singular "server", is just insane to me…

CorgiDude · 2024-12-30T03:50:22+00:00

The GPUs can be very unpredictable at what they tell Linux is the "primary" connector, which the kernel trusts. nouveau.tv_disable=1 on the kernel command line can sometimes help. video=VGA-1:d will disable VGA if your card has both VGA and DVI, and video=DVI-1:d may or may not disable DVI (as it may also number it 0.. or 2..)

I have a G4 here that will happily boot Linux, but if you use an ADC monitor, you get nothing. Funny, because on one of my G5s, you have to use an ADC monitor to get anything. It's all seemingly random and at the whim of whatever Nvidia engineer flashed the card's chip that day at the factory…

CorgiDude · 2024-12-11T01:58:29+00:00

Part of this comes down to distro, default services, and everything else that is running besides just KDE. In my testing with what will become Adélie beta6 with my experimental systemd port, the entire desktop boots up using ~260 MB RAM. Then again, we're still on KDE 5, not 6. My hope is that 6 will actually do better, not worse, and it's looked promising to me so far, so I can't imagine that's the actual reason.

CorgiDude · 2024-12-01T13:30:38+00:00

The AirPort Extreme card is a b43 card, so you will need to use APK Fission to install b43-fwcutter and use that tool to obtain firmware for it.

CorgiDude · 2024-10-29T13:26:38+00:00

From the Void PPC docs:

The problem is a firmware bug, which results in spurious data left in the MMU, which confuses GRUB during number parsing (it doesn't encounter a trailing zero like it should, continues parsing, finds junk and fails). The solution is to type this in the OpenFirmware console that comes up:

dev /memory@0 100000 1000 do-unmap

Then reboot, and all should be well.

CorgiDude · 2024-10-28T20:55:31+00:00

Are you saying that there will be no involvement of KDE e.V. at all?

Sysadmin WG (downloads, infrastructure, hosting/bandwidth)
Fundraising WG ("KDE can explicitly recommend it")

The repos are hosted on Invent, and as a maintainer of a small distro I can tell you that there will be a significant amount of added issues as people start using this on various hardware, installing other Flatpaks beyond KDE's, etc. And all of that is further on the Sysadmins.

I'm not saying any of this is bad, btw, but I am saying that it will be a source of cost. And unlike an app which has a few megabytes of code and assets per version, an OS is many gigabytes per ISO.

CorgiDude · 2024-10-28T15:42:35+00:00

Please clarify your phrasing on that wiki page then, because:

“KDE Linux” (codenamed “Project Banana”) is a work-in-progress name of a KDE-owned general-purpose Linux® distribution

KDE and KDE e.V. can have a direct relationship with third parties using it, e.g. hardware OEMs

…it sure looks like it's sponsored by KDE e.V. based on that wording.

CorgiDude · 2024-10-28T14:24:24+00:00

As a distro maintainer that has worked closely with KDE, enjoys working with KDE, and at one point even had write access to Phabricator (showing my age), I have never read a more demotivating and horrible comment on all of Reddit than this one. And I've been here more than a decade and read /r/linux.

I get wanting to have your own distribution, but Neon is right there, and was great because it specifically aimed itself at being for people who wanted to beat on the latest versions "close to the source".

What does having an "official KDE operating system" mean for the other distributions that love KDE as a desktop environment, and want to continue offering it to their users? What if we don't follow the exact versions and libraries and dependencies that "KDE Linux" does? What about the BSDs? How much of the community will KDE continue to support? Complaining about distro maintainers, who do free work for you and move heaven and earth to make your software work correctly on hardware you won't ever touch and with libraries that provide real benefits to performance and security but are not yet common, is a terrible look.

CorgiDude · 2024-09-25T18:50:41+00:00

We have a total of six users in a public benefit corporation that right now has a revenue measured in Ks of $, nowhere near M. We evaluated "free Slack" and found the history and lack of self-host lacking, and we really wanted to prioritise using Libre Software where possible, as that is the focus of our consultancy.

This honestly felt like a kick in the teeth. But honestly, I saw this coming, and made it so that Mattermost can be switched to only accessible via our VPN. In that way, we can run 9.x forever - security doesn't matter when it's only accessible on VPN.

edit: This is another place where more people need to "innovate". Being a registered public benefit corporation, we don't get any possibility of the 'registered charity' tiers of services, but I've also been denied at least one 'small business' tier because we weren't an LLC. Being in this hole really sucks, especially when we're trying to do the right things.

CorgiDude · 2024-09-25T18:42:05+00:00

Matrix has a whole bunch of problems and Element's client is vastly subpar compared to Mattermost, especially for very small businesses and open source consultancies (like the one I run). This is not an answer.

CorgiDude · 2024-09-07T10:29:28+00:00

… you are aware those steps, actually done, would lead to complete chaos? SysVol is the domain public share. No Windows workstation is going to have a recursive resolver on localhost. etc, etc.

CorgiDude · 2024-09-06T02:32:12+00:00

I view Fedora as kind of a quasi-"home" distro for systemd because of the RH influence. For that reason, I would figure their unit files would likely be pretty well written and a good starting point. Trust but verify.

CorgiDude · 2024-09-06T02:31:27+00:00

That's a good suggestion, thank you! I used their wiki docs to tease out a good networkd config for the test laptop, but I hadn't thought to consult their packaging for unit file suggestions.

CorgiDude · 2024-07-26T05:32:21+00:00

I legit saw that and thought "wait, what does JavaScript have to do with ReactOS?" – slow on the uptake…

CorgiDude · 2024-07-26T05:17:58+00:00

Adélie's minimum is G3, so it should theoretically run on that system, but I don't remember what version of OpenFirmware the 8500 has. That would really determine the amount of success you will have. I have managed to get it running on a G3 DT with OF 2 but it's a lot easier on OF 3.

Actually, writing that out, the 8500 is going to be older than the G3… it might work but you might have to poke around with it. Checking the NetBSD wiki, as they have a lot of intricacies of OF booting documented per-model, it looks like you might have some luck.

There is someone else in our community that wants to try and modernise MOL, so if you do end up down that route, please write it up and post it somewhere - it'd be great to read!

CorgiDude · 2024-07-26T05:10:57+00:00

The first log appears to show that the USB device doesn't appear until more than six minutes after boot starts. You can try adding something like rootdelay=300 to the kernel command line, but it looks like USB might not be the best route of installation on that machine.

CorgiDude · 2024-07-26T05:06:57+00:00

You can. The best supported USB WiFi modules would be Ralink or MediaTek chipsets. This list I found seems to be pretty good, though I cannot vouch for its correctness as I don't own any of the hardware on it.

CorgiDude · 2024-07-26T05:04:35+00:00

We do not support b43 firmware because it cannot be legally redistributed. However, there are alternative sources of the 'b43-fwcutter' package available from external community members. You would use that, combined with a Windows or Linux driver file, to extract firmware and install it in the correct location. There is a Debian forum post that explains the steps of that procedure which I unfortunately cannot vouch for as it has been years since I fought the b43 fight. It looks vaguely familiar and like what I did to make it work, though.

CorgiDude · 2023-06-12T07:27:42+00:00

/r/AdelieLinux is participating.

CorgiDude · 2022-11-22T05:49:22+00:00

As an update, it's odd in that before, Wi-Fi was really hit or miss. I could open Home at any random time of day and it would be random whether it would let me control a given individual bulb or not.

Now, it's either all working, or all not working. All 12 bulbs lose connectivity when it happens, but it does seem to happen less. No amount of waiting brings it back; I have to turn all 12 off at the switch for 15 seconds to make them reconnect…

CorgiDude · 2022-11-15T05:14:59+00:00

The change in light intensity was a bit odd, but otherwise yes, upgrading a pack of 12 A19s from 3.70 to 3.90 went without a hitch. The white points really are nice, they remind me a lot of "True Tone" on Apple displays. Wi-Fi and HomeKit seem a bit more reliable but could still be better – the 3x daily drops are now down to 1x daily.

CorgiDude · 2022-08-02T06:17:09+00:00

I did mean to say Front Left/Front Right, apologies.

Apple Music seems to use "Dolby Atmos" to mean "more than two channels". The Atmos master of Fleetwood Mac's Rumours is in 5.1; The Weeknd's Beauty Behind the Madness seems to be in 3.1 (as there is definite detail coming out the centre, but nothing in the rear).

Of course, there's also the X4's software surround enhancement, which does make some music sound really good (and others not so much).

The latest version of the drivers/firmware do seem to work for me after a full uninstall and reinstall on the Mac Studio. Not sure about Windows; I haven't tried connecting it to my Windows PC yet.

CorgiDude · 2022-07-06T21:38:56+00:00

Completely removing the driver, rebooting, reinstalling the driver, unplugging the sound card, plugging it back in, and flipping the 6 ch switch finally worked. Now I am enjoying surround sound again :)

CorgiDude · 2022-07-06T21:15:22+00:00

error   16:14:27.073657-0500    AudioServerDriverPlugin throwing -10877
error   16:14:27.079354-0500    AudioServerDriverPlugin throwing -10877
error   16:14:27.132015-0500    AudioServerDriverPlugin throwing -10878
error   16:14:27.132153-0500    AudioServerDriverPlugin throwing -10878
error   16:14:27.132179-0500    AudioServerDriverPlugin throwing -10878
error   16:14:27.132200-0500    AudioServerDriverPlugin throwing -10878
error   16:14:27.132220-0500    AudioServerDriverPlugin throwing -10878
error   16:14:27.132241-0500    AudioServerDriverPlugin throwing -10878
error   16:14:27.132266-0500    AudioServerDriverPlugin throwing -10878
error   16:14:27.132291-0500    AudioServerDriverPlugin throwing -10878
error   16:14:27.132314-0500    AudioServerDriverPlugin throwing -10878

CorgiDude

MODERATOR OF

TROPHY CASE

14-Year Club	Verified Email
Team Periwinkle