Open Source Software Community - it's about ethics in Code of Conducts

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
General Emílio Médici said:
Well, time to make the switch to Artix.
Click to expand...
I was considering Cachy, EndeavourOS or just straight Debian but after watching SystemD bend the knee to toothless legislation, I might actually consider Artix as a daily driver.
WielkiWapiesz2137 said:
When it comes to artix init system the one that i recomend the most is runit due to it being very simple by design.
Click to expand...
How inconvenient is using runit/openRC compared to SystemD for a daily driver? Do either grant any major improvements?
 
Fuck, I just got real comfy on Arch. Do I really need to go back to Artix? I hate having to enable/disable services without SystemD.
Molokroid said:
How inconvenient is using runit compared to SystemD for a daily driver?
Click to expand...
It works until it doesn't and you have to troubleshoot why it doesn't work or worse yet, manually script services for runit. It may not be a big deal to some of the autists here but I'm retarded and it was the main reason I switched to Arch after years of running Artix.
 
Molokroid said:
How inconvenient is using runit/openRC compared to SystemD for a daily driver? Do either grant any major improvements?
Click to expand...
On artix it is no different as they got all the services ported. However with overwhelming probability 3rd party services wont be shipping runit files thankfully however writing them is dead easy. The advantage of runit is mostly boot time the disadvantage is that it doesn't handle dependencies. I have been running Artix with runit for around 2 years with no problems on my thinkpad.
 
skunt said:
It's the 'boiling the frog' metaphor.
Click to expand...
It's a meme for good reason.

NFS readers were sold under the selling point of "paying with your phone", only to become a passport scanner. Fingerprint scanner? To replace passwords. This age verification thing will essentially all sooner or later converge to a way that you got zero anonymity on hardware level.
 
Gonna try out Alpine Linux again on my server. I rejected it previously because of the whole musl bullshit, but since most of the programs are run in containers anyways, that might be OK.
 
Sneedmason said:
Fingerprint scanner? To replace passwords. This age verification thing will essentially all sooner or later converge to a way that you got zero anonymity on hardware level.
Click to expand...
There's also no such thing as "age verification" as the age never gets verified. It's either age declaration, identity declaration, or identity verification. Only once they've verified your identity can someone actually "verify" your age, but it sounds way less intrusive to say that than it actually is. They're playing evil games with words to conflate these ideas and make them more palatable to the public as they force it down.
 
General Zigger said:
s6? (never heard of this)
Click to expand...
Think of s6 as being the maximum-autism init system. The init system structure has been aggressively decomposed into a set of tools for process supervision. You'll probably hit more rough edges, but it's also a lot more "bare-metal" and operates with incredibly low requirements.

From its webpage, https://skarnet.org/software/s6/index.html

s6 is a small suite of programs for UNIX, designed to allow process supervision (a.k.a service supervision), in the line of daemontools and runit, as well as various operations on processes and daemons. It is meant to be a toolbox for low-level process and service administration, providing different sets of independent tools that can be used within or without the framework, and that can be assembled together to achieve powerful functionality with a very small amount of code.
Examples of things you can do by assembling together several programs provided by s6 - besides process supervision:
  • syslogd functionality, using much less resources than the traditional syslogd.
  • Reliable service readiness notification, which is the basis for service dependency management.
  • Controlled privileged gain as with sudo, without using any suid programs.
  • The useful parts of socket activation[1] without having to change application code or link servers against any specific library, and without having to switch to any specific init system.
The s6 documentation tries to be complete and self-contained; however, if you have never heard of process supervision before, you might be confused at first. See the related resources section below for pointers to more resources, and earlier approaches to process supervision that might help you understand the basics.
Click to expand...

Now, I'm happy on Gentoo, but when I try Artix, I usually use the s6 builds. Haven't noticed breakage at all yet, but I haven't really pushed it at all either.
 
Question, are they going to have a thing where sites that legitimately need your real age (like your bank) will file a fraud report if your computer's copy of your birthday doesn't match the one in their records?
 
Runit/s6/OpenRC and Pipewire is the best way to Lennart Poettring proof your system because he wrote systemd and pulseaudio. He also accused Ubuntu of not implementing the latter correctly during adoption, but some people think that he wrote it like shit. The more we push ourselves away from systemd, the better Linux will be. Then again, the bootlickers of Linux will fellate Poettring while not knowing that he works for Microsoft.
 
Betonhaus said:
Question, are they going to have a thing where sites that legitimately need your real age (like your bank) will file a fraud report if your computer's copy of your birthday doesn't match the one in their records?
Click to expand...
Under the laws in question your computer isn't storing your birthday, just an age range (<13, 13-<16, 16-<18, or 18+). However, I could see some retard thinking they need to generate a Suspicious Activity Report because the age-range asserted by your browser/their app doesn't match what they have on-file for you.
 
REGENDarySumanai said:
Pipewire
Click to expand...
Eh.

I think what is needed is a complete scrapping of all these frameworks currently built over alsa. We just need to start fresh, and hopefully end up with something that works well.
REGENDarySumanai said:
Runit/s6/OpenRC and Pipewire is the best way to Lennart Poettring proof your system because he wrote systemd and pulseaudio
Click to expand...
Seeing as most people using pipewire are running pipewire-pulse, I don't know if I would say it's completely Poettring proofed.

With pipewire, they've just moved to something else that handles things in the same way on some level. They are using pulse, they are using jack, etc.


On the topic of init systems. Open-rc does tend to work decently well. It's actually slower to boot than sysyemd not that it matters much, just something to note. Unless you enable parallel boot, but I don't recommend that unless you are competent enough to handle the breakages that happen because the services are starting out of order (you need to add that to their depends section to make sure x service only starts once y service has started).

I think dinit is a very good service manager/init. It's as fast or faster than runit, and handles a lot of stuff pretty well. Also it has first class support for turnstile which can be used along with seatd to replace elogind if you take the time to set it up (which is fairly easy).

Runit is nice too. Also fast, it's simpler in what it does. You will need to look up how things are handles, and I recommend having a basic understanding of shell scripting if you plan to write services (not entirely necessary but it will help a lot).
 
prollyanotherlurker said:
I think what is needed is a complete scrapping of all these frameworks currently built over alsa. We just need to start fresh, and hopefully end up with something that works well.
Click to expand...
I do agree with this, but considering that pulseaudio has been used for so long that stopgaps have to be used to make it works with successors makes this a big errand.
 
REGENDarySumanai said:
The man who ruined Linux. The anti-systemd movement needs to be a movement against him. Runit and Pipewire forever.
Click to expand...
Calling him that is just channeling everyone else's sins through him like he's open source hitler. The efforts of commercializing linux are an industry wide process, and they've been going on for decades now even before pottering (Linus is a part of that BTW)
 
You must log in or register to reply here.
Back
Top Bottom