LXD now re-licensed and under a CLA
LXD now re-licensed and under a CLA
stgraber.org
LXD now re-licensed and under a CLA | Stéphane Graber's website
Blog post from LXC's project lead
27 comments
-
-
I just see a problem here:
I perfectly understand, approve and back this move, however I’ve a question about the current state of things and specifically Debian 12 users. Debian includes LXD LTS 5.0.2 on their repositories and that version will be still be around after 2024/05 and trying to use the image server. Debian won’t likely change stable to include Incus until 2025, what’s the suggested path here?
https://discuss.linuxcontainers.org/t/important-notice-for-lxd-users-image-server/18479/9
-
Fucking Canonical at it again.
-
Do people actually use LXD in production? All hosting services I've seen use LXC and not LXD for containers, as do UIs like Proxmox and Unraid, and you don't have to use Snap for LXC.
-
-
I though it was being relicensed under agpl?
-
I though it was being relicensed under agpl?
The answer is in the submitted blog post.
-
It's both
-
-
-
Red Hat kills X11
I mean Red Hat does bad things, but is switching to Wayland a bad thing?
-
Well let's see
- Doesn't work with nvidia, the leading vendor of graphics cards
- Drops support for a huge set of diverse window managers and applications
- Reimplements X11 functionality over shitbus, an incomprehensible nightmare
- sandboxing security designed to enable Windows/Android like apps where users run random proprietary malware
- Promoted for purely idiotic reasons like like "circular windows"
I could go on...
-
-
Of all the reasons you could have chosen for Red Hat you chose "they killed a dead corpse"?
X11 was already dead, it isn't getting updated, and its maintenance is gonna end eventually. Sure Wayland still has issues but once it's ready for widespread use (which it is, save maybe for gaming on PCs with like 6GBs of RAM) the jump is unavoidable. In fact by doing this they got more people to work on fixing the issues in Wayland
-
Wayland on its own may be ready but you can't build a whole desktop with just Wayland. The rest of the stack needs time to catch up.^(*) And no, not everybody is willing to use KDE and restrict themselves to whatever combination of elements happens to work right now.
^(*) Because the bright people who did this decided they needed to throw the baby out with the bathwater on X. They couldn't possibly find a way to ditch only the obsolete parts and fix the problems and maintain compatibility as much as possible. No, everything had to be rewritten from scratch.
So here we are 15 years later, with another 5 or so to go until the whole Linux desktop ecosystem will be thoroughly redone.
-
-
Red Hat kills X11
So does Valve. Valve and Red Hat are the driving forces behind the recent HDR advancements.
-
Yes, but I can still play steam, any Valve game and atm any Linux steam game on X11.
I don't hate Wayland as a project, I just don't like Wayland as it current state. Give me better stability, better support with multiple monitors and a compositor with more customization, and I'll be happy.
But, in my opinion, Wayland is by design opinionated. Some ideas are good, such as the security model, some are both good and bad, such as the Compositor VS Server+WM debate (both good systems in my opinion), some are just bad (no unified screen management option; obviously there are LOTS of protocol extension, but not all are supporting everywhere)
So, imo, WayLand just needs a stable, (really) customizable Compositor with all useful extensions and designed to put other components together; I'm still on my X11+awesomewm+rofi+polybar, and I want a customizable, stable and module approach on Wayland.
-
Yes, but I can still play steam, any Valve game and atm any Linux steam game on X11.
I don't hate Wayland as a project, I just don't like Wayland as it current state. Give me better stability, better support with multiple monitors and a compositor with more customization, and I'll be happy.
But, in my opinion, Wayland is by design opinionated. Some ideas are good, such as the security model, some are both good and bad, such as the Compositor VS Server+WM debate (both good systems in my opinion), some are just bad (no unified screen management option; obviously there are LOTS of protocol extension, but not all are supporting everywhere)
So, imo, WayLand just needs a stable, (really) customizable Compositor with all useful extensions and designed to put other components together; I'm still on my X11+awesomewm+rofi+polybar, and I want a customizable, stable and module approach on Wayland.
-
-
-
I hate Red Hat as much as anyone, but X11 is dying even without them.
-
red hat is the one maintening x11 lol, it only working right now because of them
-
27 comments
Thank heavens for Incus.
The issue here is that this will stall the development of LXD/Incus. Two separate projects running in different directions no future feature parity and potentially less features in Incus than in LXD.
Currently LXC Incus is more active than Canonical LXD.