Cons: You’ve spent a bunch of time installing OSes you might not like, and you have to set everything back up again. Also if you didn’t back up your data you’re probably going to delete it.
Do you value time fucking around with your computer, or are you happy with how it works currently?
Also distro hop in a VM first, you’re probably not going to like most other things, or it might not be worth the time to migrate all your shit over to it if you find something you like more.
Unless its NixOS or something like silver blue or QubesOS they’re all basically the same. If you want to mess about try some different ones in a VM or on a live CD or USB. That way you still have your daily driver working when you need it
Can you install MacOS by Zorin™ on something else? I suppose there’s a source repository somewhere and you can always compile it if you really want it…
Im pretty happy with KDE Fedora (though constant updates make me anxious something breaks every reboot, lol) but if I had to change I would probably check out LMDE (Linux Mint Debian Ed). I’m not really a fan of Cinnamon/Mate but I’d give it another go …
I am on a very strange situation, Wayland for me still quite buggy, but my x11 session only render about half of the red subpixels on my display, so wayland it is
All Canonical contributions have been relicensed and are now under AGPLv3. Community contributions remain under Apache 2.0.
So they can happily port over code from the Incus fork but Incus cannot import the code without changing the license first. It’s meant to be a one-way street. Typical Canonical.
In short incus has Apache 2.0 copyright licene that states:
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole
While AGPL v3.0 that Canonical just adopted states:
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
. . .
You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy …
Meaning if incus uses any part of Canonicals source their code can’t be licenced under Apache but rather AGPL v3.0, which pulls any other derivative of incus.
Projects which choose BSD/Apache type licences do so fully in the knowledge that their code may be incorporated into projects with different licences. That’s literally the point: it’s considered a feature of the licence. These projects are explicitly OK with their code going proprietary, for example. If they weren’t OK with it, they’d use a GPL-type copyleft licence instead, as that’s conversely the literal point of those licences.
Being mad about your Apache code being incorporated into a GPL project would make no sense, and certainly wouldn’t garner any sympathy from most people in the FOSS community.
Its not a one way street but this makes more libre thing. Canonical didnt make it proprietary to create a one way street but made it more libre by adopting AGPL license which gives users more rights to the code
Its not a one way street but this makes more libre thing. Canonical didnt make it proprietary to create a one way street but made it more libre by adopting AGPL license which gives users more rights to the code
Why is there still a CLA that allows them and only them to sell proprietary versions then? Don’t fall for Canonical’s PR bullshit.
Look, I’m usually first in line to shit on Canonical, but I can’t get mad at them adopting AGPL. This is objectively the best license for server software. Incus should also switch to AGPL for all Canonical code, and seek to have contributors license their code as AGPL as well.
I will however point out the hypocrisy and inconsistency of it, because the Snap server is still proprietary after all of this time. If this is their “standard for server-side code” then apply it to Snaps or quit lying to us.
They would have used a license like SSPL or the newer BSL for that. AGPL keeps it open.
No, the copyright owner can sell proprietary versions however they like. Outside contributions are required to sign Canonical’s CLA. Read github.com/canonical/lxd/blob/…/CONTRIBUTING.md#l… before making claims.
I don’t understand how AGPL allows Canonical to make and sell proprietary copies of this software without violating their license. That’s the only way your scenario could happen. If you’re aware of a situation where a company can do this, I’d love to learn.
I don’t understand how AGPL allows Canonical to make and sell proprietary copies of this software without violating their license. That’s the only way your scenario could happen.
“To release a nonfree program is always ethically tainted, but legally there is no obstacle to your doing this. If you are the copyright holder for the code, you can release it under various different non-exclusive licenses at various times. […] the GPL is a license from the developer for others to use, distribute and change the program. The developer itself is not bound by it, so no matter what the developer does, this is not a “violation” of the GPL.”
It requires that you make available the full source code to anyone who you give binaries too (like the GPL), but also requires you make available that source to users of the software over a network. So, someone could not make a proprietary fork of AGPL software to sell exclusively as a service. In order to provide that service you have to also be willing to provide the source, including changes, which would allow users to then choose to run that service themselves instead of being forced to pay the provider.
The full details are complex but I’ll give you the basic gist. The original GPL licenses essentially say that if you give somebody the compiled binary, they are legally entitled to have the source code as well, along with the rights to modify and redistribute it so long as they too follow the same rules. It creates a system where code flows down freely like water.
However, this doesn’t apply if you don’t give them the binary. For example, taking an open source GPL-licensed project and running it on a server instead. The GPL doesn’t apply, so you can modify it and do whatever, and you aren’t required to share the source code if other people access it because that’s not specified in the GPL.
The AGPL was created to address this. It adds a stipulation that if you give people access to the software on a remote system, they are still entitled to the source code and all the same rights to modify and redistribute it. Code now flows freely again, and all is well.
The only “issue” is that the GPL/AGPL are only one-way compatible with the Apache/MIT/BSD/etc licenses. These licenses put minimal requirements on code sharing, so it’s completely fine to add their code to GPL projects. But themselves, they aren’t up to GPL requirements, so GPL code can’t be added to Apache projects.
If it really has rebooted, it could be some graphics driver issue causing it to freeze up. I had stuff like that on Nvidia graphics back in the day. Linux will reboot itself after a while if it freezes.
EndeavourOS is an arch-based distro that “just works”. I put it on a new machine recently, and the installer manages to let you pick a desktop environment, and still manages to be user friendly.
Nobara (wayland/gnome) + NVIDIA 2080ti, screen and projector dual setup = never add any issues. I’m a noob, came to linux 6 months ago. I’m really curious about why so many people are having problems with Wayland and NVIDIA but my system basically worked out of the box. I guess I was lucky?
Honestly, I tried Plasma on my friend’s 2-in-1 laptop and it’s pretty great with gestures and touch. I haven’t tried gnome but I can definitely recommend plasma.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.