> apt/dnf scripts run on packages a maintainer signed and a distro gatekept
Unfortunately apt/dnf isn't much better here because random tutorials online suggest people add random repositories where the creator of any repository effectively has root access to anyone machine that adds it as a remote.
It's the exact same problem when random tutorials (and official pages) recommend to do a curl "URL" | bash to install something. Every time that I see it, I look it suspicious.
Actually, it depends on the Windows scheduler settings. On Windows Server, the default is to kill the foreground process (on the assumption that it is just a management app rather than a critical server component).
In either case, Windows tries a lot of things to avoid killing processes. Which at least in a desktop setting is an infinitely better approach than random beheadings without warning.
yeah. a lot of the issue with Linux's approach is that until recently, the kernel was the one making the choice, and it doesn't know which processes matter. The part Linus does a lot better if not getting to oom in the first place (and with the newish compressed ram stuff is getting even better)
There is no more succinct way to describe a Zionist than by using the word Zionist. To assume anyone who says "Zionist" means "Jew" is to make an unnecessary leap in bad faith.
A lot of people shout 'Free Palestine' before doing some vigilante violence (shooting in DC, firebombing I'm Boulder), so wouldn't that make security officials jumpy?
The whataboutism of Israel being more 'evil' doesn't mitigate the security threat.
I don't know about the other user, but I hear both shouted. So... the same?
Don't make this about party politics. The politics here is about if you're allowed to have a dumb SSID. IDGAF if that's "Fuck Gaza" or "Fuck Israel" or "Cheney shot a man then made him apologize" or "Obama is a Muslim".
We're talking about restricting the names of SSIDs that aren't in the category of "I'm going to blow up this plane". Seriously, this whole conversation is fucking dumb because people are acting on partisan politics and not on what's actually happening. I need a fucking beer, or 10
Eh, most Nazis that use the words interchangeably really do use them interchangeably. Like, they'll talk about the Jews controlling everything in one sentence and say it's Zionists pushing cultural Marxism or whatever the next.
You realize that calling everyone who criticizes an ongoing genocide an antisemite isn't workable, right?
There's zero proof it's an intentional backdoor, it's just FUD spread by the exploit author which is probably not helping his case and may be reason for his ban.
Microsoft doesn't need to put in a backdoor on disk because they can make payloads that'll pass the TPM and not need a single trace on the disk.
Why would it not be? Microslop doesn't need to make such a backdoor, but it's still a lot more convenient to make one generic backdoor than many signed ones.
I've noticed a trend that the same people who complain systemd does too much also have a strong affinity for the X server... with it's built in print server!
> Maybe systemd should have been an API + a spec instead of an unportable implementation.
There's nothing really stopping other init systems from implementing it's unit spec, some hobby ones have done so.
In the case of GNOME, KDE etc depending on it, the reason mainly boils down to "we could implement our own manager for handling desktop daemons etc or just get systemd to do it for us"
But why would they do so? That makes no objective sense.
Systemd never was "merely" only an init system. And it makes no sense for init systems to grow to systemd-size either, in order to solve non-init related issues.
> In the case of GNOME, KDE etc depending on it, the reason mainly boils down to "we could implement our own manager for handling desktop daemons etc or just get systemd to do it for us"
That's not quite true. GNOME always was close to systemd devs due to funding. KDE was less close, but even within KDE some people lobbied for it such as dave edmunson or however you spell the name, and "me-needs-a-donate-daemon" Nate, who you are not allowed to critisize on #kde reddit. But I agree that they could simplify some code by depending on systemd. Of course this now means that KDE is sold in a dead-lock with systemd. I wonder if I can still use konsole without systemd. I tend to use iceWM since it is so much faster than KDE or GNOME, but when konsole depends on systemd I may indeed need to switch to another terminal. That will be painful though, but there is no stopping systemd - it infects and taints.
I mean yeah, it doesn't aim to be a "cross-platform compilation/building system" so of course dependencies is up to you to solve, AFAIK AppImage only aims to solve packaging itself, not what goes into that package.
Unfortunately apt/dnf isn't much better here because random tutorials online suggest people add random repositories where the creator of any repository effectively has root access to anyone machine that adds it as a remote.
reply