That is my point, they have tried and failed completely before when their main product was windows licenses. Now, linux is incredibly important to their azure business, they wouldn't want to potentially cause detriment to that and is far more important to them than windows licenses.
Also why would we have to rip out systemd, even if they tried to claim ownership of it and make it proprietary, it could be forked from before the license change and we would keep on going like nothing happened.
people keep saying this, but what is their extinguish plan? how could they realistically extinguish linux? it’s not a company they can buy, or even a single thing they can ruin.
can you give examples of some? Not trying to bd sarcastic, i do just want to see what alternatives are doing.
We are talking about the non consensual circumcision of infants. Of course if an adult wants one done, they should be allowed to go do it, or if it is actually deemed medically necessary. 99% of these circumcisions are not though in the US. That's what needs to be banned.
Except its not even, at least for christians. Its actually even considered a sin for catholics. https://catholicism.org/ad-rem-no-283.html
It became popular in the US because it was thought that it would stop people from masturbating. That’s why its an American thing and not a religious vs non religious thing (except for jewish people).
Immutable isnt really the best word for these distros. Its why fedora is changing the name to atomic, as in changes made to the system are done atomically like git. This also means changes can be rolled back just as easily as they were made.
The trick was to install VSCodium from the Toolbox
Another option you can try that I use is the dev containers extension which allows you to move your workspace to different containers from within vscode. I will say however, i have tried many times to get it working in vscodium and have been unsuccessful and it only seems to work in vscode proper.
With fedora atomic, lets say i wanted to try out kde desktop for a while. i would first pin my current build so i can roll back to it if i dont end liking kde with
$ sudo ostree admin pin 0
Then i would rebase to the kde branch with
$ rpm-ostree rebase fedora:fedora/39/x86_64/kinoite
Then just reboot. That’s literally it and i would have a kde system with all my layered packages and i could roll back to my old system at anytime.
all changes in etc are snapshotted with each update so you could just roll back to your previous version and it would fix it.
I assume you meant you messed up permissions in your home directory, and yes that is pretty much the only place you can permanently mess something up with silverblue.
honestly i feel exactly the opposite, I don’t think it’s really necessary for servers as tools like ansible are already well established in that space. Plus most servers are VMs these days which can be snapshotted easily. Also, lot of these “immutable distros” require a reboot to apply changes which is non ideal in a server, but a non issue for desktop as you can shut it down when you go to sleep.
I run fedora atomic on my desktop and laptop because i never have to worry about my system getting into a broken state, I can always roll back or even spot the problem and fix it before i reboot to apply the change. I know a lot of people say you can accomplish the same thing with btrfs snapshots, but that requires extra thought and effort on my part, where fedora atomic it happens automatically with every update.
what issues have you had with libvirt and windows? Once you get the windows drivers installed, it works pretty much the same as other solutions. only thing thats still a pain in the ass still is shared folders.
Its certainly easier to read than most old init scripts and I can see why some distros and openbsd would pick it over systemd for more control. I'm not likely to pick a distro that uses it anytime soon, but i can see why some do.