you don’t need a micro kernel to install medules, nor to make a crash in certain module don’t bring the kernel down, you program it isolated, they don’t do that now because it’s unecessary, but android do that, and there’s work being doing in that way https://www.phoronix.com/news/Ubuntu-Rust-Scheduler-Micro
the thing is that it’s harder todo that, that’s why no one does, but not impossible, you also need to give the kernel the foundation to support that
to be fair, fedora downloads and apply the update before reboot, windows download, apply and then reboot, that’s why it take so much time
nah, you can have micro-kernel features on linux, but you can’t have monolithc kernel features on microkernel, there’s zero arguments in favor of a micro kernel, except being a novel project
flatpak has dedub, so no
distrobox?, i also installed nix and works perfectly
put flatpak in your PATH and you can youse the app name like normal
But, I may be wrong, please, tell us how exactly a move to systemd has benefited companies enough that it would make the effort and expense to make a distro move to sytemd, let alone a majority of distros, worth it.
you’re putting to much thought in something that even the guy who you’re asking didn’t
that’s some high ammount of copium from someone that never made a distro
you can run a command using run0 it’s only elevating that commads, sometimes it’s needed to login as root, it’s life
Idk he’s just a hot take merchant basically. He has a particular hate-boner for distros that don’t use systemd as the default init system like void and gentoo (usually these are troll tweets as opposed to commit messages though).
shut up, wtf that has todo with the commit, people who don’t use systemd it’s not going to complain about the color of something that they don’t use
exactly lol
no? it an alias to systemd-run, you can call an alias bloated
but with only 1/20 of it’s capabilities lmao
the pid1 part is wrong, only the systemd-init run in pid1, in it’s own process, own binary etc, it’s sole purpose is being an init system, after that it start the rest of the system, including the others systemd binaries
the rest is perfect thanks!, in the lennart he made a comparation with ssh were you “forward the commad to run as root”, i think it’s a good analogy
. run0 does it in a better way which I do not understand.
it does that in a “ssh like” that i read in the blog, they foward your commands, they don’t elevate your user, they also use polkit for security intead of sudoers
run0 uses systemd-run i don’t remember you can use that directly
ok them go suffer alone in your 2004 distro that can’t update bash because it break the 400 scripts that it use to boot lmao
bro thinking a chromecast OS gonna run in google servers 💀, micro kernels has their utility in embedded system, we know, saying that they are replacement for monolithic kernel is dumb, also companies can’t do different/hacks project anymore?