Absolutely in favour, the non-free blobs are a persistent thorn in my side. I myself have always been tempted to replace all the fedora and debian templates with alpine or OpenBSD to get smaller VMs (and without systemd), built as many things as unikernels as possible (e.g. the MirageOS firewall), and I’d love if X11 got replaced with Wayland (that one is hard, the X11 modifications are kind of the core of what Qubes provides).
Yes and no. Buying a RiscV CPU has the same issues as buying an arm or x86_64, and building one from discrete components (which is absolutelt feasible, there’s multiple people that have done it) still means you might recreate some subtle and deliberate flaw in the spec (How sure are you there is none? That is the whole question). And trusting a FLOSS BIOS over a proprietary one is just accepting a different trust level/anchor. My whole point was that ultimately you cannot perfectly trust anything you haven’t designed and built yourself (and even that depends on this reality not being a malicious simulation; I am being serious), so you’ll need to consciously decide what trade-offs, if any, you’re willing to make.
Ultimately, you need to build your own CPU (and everything else) from discrete components (assuming the universe is not a malicious simulation, of course) and bootstrap on it by writing you first assembler in machine code (You ought to come up with everything from scratch, any exisiting designs might have subtle deliberate vulnerabilities). The actual question is at which point you’re willing to risk a compromised supply chain, i.e. how far does your, quite warranted, paranoia go.
What am I supposed to do?
Learning to write a problem description that is remotely intelligible would be a start. What Distro are you on? What are you trying to accomplish? What have you tried? What error occurs (error messages or what expectations you have that are not met), etc.
My downvote stays; That is an absolutely atrocious title for it.
Not everyone enjoys the same things and that’s ok. I’d rather rip out my own fingernails than spend any time with “ai chat” shrug
The counting systems were always bullshit. Different people and at different times have wildly different speech tempo. What you can do is trying to find your rhythm by actually saying a word repeatedly as fast as you can without mispronouncing and counting how often you can do that in a minute; That’ll give you a fairly accurate measure you can use.
I personally favour Alpine Linux for its minimalism, but Devuan or Debian are fine, and more familiar choices, too. Depending on what you intend to run, especially appliance-like things, OpenBSD might be a good alternative.
I’m another fellow barefoot-indoors-and-minimal-sole-whenever-possible-without-causing-a-ruckus and, yeah, ruckus happens weirdly often…
You get thrown into Jail as an “anti-social element” (There’s an important distinction between “unable to work” and “unwilling to work”, both meaning “work” as in “contributing labor to the well-being of your fellow humans”). Also: You clearly don’t know anything about socialism beyond right-wing delusions.
I’ve always enjoyed the thought of a couple cats cooperating to take on a cow lke the raptors in jurassic park, only much closer to the actual size of raptors =^_^=
No shit. “More” is technically correct. “A metric fuckton more” conveys the appropriate scale. It’s not like systemd added a handful small features, it has subsumed nearly everything between kernel and userland. (Note that proponents usually point this out as a good thing; It’s uncontested, you just seem blissfully unaware)
Have you considered that we don’t think any of those are “good points” worthy of comment?
Nope, but “more” doesn’t adequately capture the scale of it. Given that you talk about a predecessor (singular) I presume systems programming is not your specialty?
Ahem, it does a ton more than merely “initiate booting” (logging, time, user management, device management, the list is long and it is really hard to find a piece of basic system functionality it hasn’t subsumed), please don’t spread misinformation.
Come on, that’s pure ragebait… It’s not like it"s hard to search for all the different reasons… https://nosystemd.org/ collects a few in semi-coherent form. The short answer is: It combines a lot of previously independent systems responsibilities under one umbrella organization that holds decidedly strong opinions and is not exactly open to criticism.
I agree, but then I’m one of those really hardcore libre-software-only nutcases ;-)
EDIT: Though, to be fair, the Trident Missiles they carry are US-made, too, so…
https://www.popularmechanics.com/military/weapons/a19061/britains-doomsday-subs-run-windows-xp/
(Though, of course, that’s alledgedly simplifying a lot to make it more click-bait-y: https://ukdefencejournal.org.uk/no-trident-doesnt-run-windows-xp/ )
Nice April 1st. I mean that’d be almost as ridiculous as running nuclear subs on Windows, right? Long EOL’d versions at that, eh?
rustles papers
Oh.
I personally go with QubesOS which uses VMs to compartmentalize. It doesn’t reduce the risk of a supply chain attack itself (fedora & debian by default), but if your VMs only contain the bare minimum for a given task the risk of having a compromised package installed is lower than in a full-featured system and any compromise is also contained to that VM.