I think it's pretty likely they are since they gave a talk at Code BEAM Europe 2025: https://www.youtube.com/watch?v=tC435RGwRCI
> https://github.com/zabbly/incus/issues/89#issuecomment-30764... > I mean sure, it's the UI component only, and not on the lxc repo but the Zabbly one, and maybe they treat things widely differently depending. This one…
Can you substantiate this? The only time this held, vaguely to my recollection, true was prior to Incus 0.4 where both were cherry picking from each other but neither were upstream of each other
There is .NET support for FreeBSD but it is relatively recent; FreshPorts lists it as added in January 2024. See: - https://www.freshports.org/lang/dotnet/ - https://wiki.freebsd.org/.NET -…
This is deliberate misinformation. You can easily see that versions prior to Beta 1.8 were obfuscated just by downloading the .jar for the older versions on minecraft.wiki. You can even view some of the old MCP mappings…
According to another message chain, this is also in part related to/influenced by Dockyard no longer funding Elixir projects [1]. Also that the next evolution of "LVN" is likely not going to be Elixir based going by [2]…
This looks more like a wrapper over Qemu/KVM
I think things are swinging back the other way if I have understood the more recent PVHv2 stuff correctly.
This has been one personal pet peeve with the documentation surrounding Incus. As a stack, Incus has been exceptional, it has largely replaced Proxmox and Podman Quadlets for me. For context, I homelab so I cannot…
Linux Containers, or LXC, came before Docker and OCI standardization. As the others have mentioned, Incus is the community fork led by former members of the LXD team.
I think you could also add Xen to that list. IIRC, the old Xen PV mode was purely paravirtualized without using any hardware extensions.
In the context of Incus, they are the same. Incus and LXC internally use umoci to manipulate the OCI tarball to conform to how LXC runs containers. See: - https://umo.ci/ -…
No worries on that front, I expect that fun fact to be just a minor setback but I'm still pretty dead set on making my personal infrastructure declarative, reproducible, and anti-hysteresis.
I wasn't aware NixOS prunes EOL kernels, thanks for letting me know; this throws a bit of wrench/damper in my personal machine plans.
That's a fair point and I don't disagree. I guess my main point of contention was the implication that either a) ZFS wasn't stable on anything non-LTS or b) the Linux kernels themselves were unstable outside of a LTS.…
12th gen and newer had some form of SR-IOV support in the i915 driver, but I'm not sure whether or not Intel fully upstreamed that. Here's a project that, iirc, backported and made a DKMS for from Intel's tree:…
I think this would depend on Virtio-GPU Native Context which, if I recall correctly from the qemu-devel mailing list, is the next natural progression from Virtio-GPU Vulkan Edit: Can't substantiate further, but this is…
Then look back to 2.2.6, it supported up to 6.10. A far cry from only supporting only up to 6.6 so I'm not seeing where they were going with with their initial statement until they define what they mean by stable.…
What do you mean by stable? 2.2.7 supports the 6.12 kernel if I'm not mistaken
Virtio-GPU Venus is similar to Virgl except it passes through Vulkan commands rather than OpenGL
Most likely they did not adjust +P which bumps the max process limit
Sorry for the segue, but how your team's experience with C# on VSCode? Any recommendations for plugins? I've heard of a lot of people recommend Rider but not much, aside from neonsunset, talk about VSCode.
To be pedantic for a moment... > You can't use Go to write a kernel ... Not a production kernel, but MIT did use Go to "study the performance trade-offs of using a high-level language with garbage collection to…
The article is talking about ChromeOS merging to an Android base. Ninja edit: this article should clarify some things: https://blog.chromium.org/2024/06/building-faster-smarter-ch...
It's possible your previous knowledge was based on HiPE, which to my understanding was kind of sucky. The new JIT in Erlang/OTP 26 is called BeamASM and is based upon asmjit
I think it's pretty likely they are since they gave a talk at Code BEAM Europe 2025: https://www.youtube.com/watch?v=tC435RGwRCI
> https://github.com/zabbly/incus/issues/89#issuecomment-30764... > I mean sure, it's the UI component only, and not on the lxc repo but the Zabbly one, and maybe they treat things widely differently depending. This one…
Can you substantiate this? The only time this held, vaguely to my recollection, true was prior to Incus 0.4 where both were cherry picking from each other but neither were upstream of each other
There is .NET support for FreeBSD but it is relatively recent; FreshPorts lists it as added in January 2024. See: - https://www.freshports.org/lang/dotnet/ - https://wiki.freebsd.org/.NET -…
This is deliberate misinformation. You can easily see that versions prior to Beta 1.8 were obfuscated just by downloading the .jar for the older versions on minecraft.wiki. You can even view some of the old MCP mappings…
According to another message chain, this is also in part related to/influenced by Dockyard no longer funding Elixir projects [1]. Also that the next evolution of "LVN" is likely not going to be Elixir based going by [2]…
This looks more like a wrapper over Qemu/KVM
I think things are swinging back the other way if I have understood the more recent PVHv2 stuff correctly.
This has been one personal pet peeve with the documentation surrounding Incus. As a stack, Incus has been exceptional, it has largely replaced Proxmox and Podman Quadlets for me. For context, I homelab so I cannot…
Linux Containers, or LXC, came before Docker and OCI standardization. As the others have mentioned, Incus is the community fork led by former members of the LXD team.
I think you could also add Xen to that list. IIRC, the old Xen PV mode was purely paravirtualized without using any hardware extensions.
In the context of Incus, they are the same. Incus and LXC internally use umoci to manipulate the OCI tarball to conform to how LXC runs containers. See: - https://umo.ci/ -…
No worries on that front, I expect that fun fact to be just a minor setback but I'm still pretty dead set on making my personal infrastructure declarative, reproducible, and anti-hysteresis.
I wasn't aware NixOS prunes EOL kernels, thanks for letting me know; this throws a bit of wrench/damper in my personal machine plans.
That's a fair point and I don't disagree. I guess my main point of contention was the implication that either a) ZFS wasn't stable on anything non-LTS or b) the Linux kernels themselves were unstable outside of a LTS.…
12th gen and newer had some form of SR-IOV support in the i915 driver, but I'm not sure whether or not Intel fully upstreamed that. Here's a project that, iirc, backported and made a DKMS for from Intel's tree:…
I think this would depend on Virtio-GPU Native Context which, if I recall correctly from the qemu-devel mailing list, is the next natural progression from Virtio-GPU Vulkan Edit: Can't substantiate further, but this is…
Then look back to 2.2.6, it supported up to 6.10. A far cry from only supporting only up to 6.6 so I'm not seeing where they were going with with their initial statement until they define what they mean by stable.…
What do you mean by stable? 2.2.7 supports the 6.12 kernel if I'm not mistaken
Virtio-GPU Venus is similar to Virgl except it passes through Vulkan commands rather than OpenGL
Most likely they did not adjust +P which bumps the max process limit
Sorry for the segue, but how your team's experience with C# on VSCode? Any recommendations for plugins? I've heard of a lot of people recommend Rider but not much, aside from neonsunset, talk about VSCode.
To be pedantic for a moment... > You can't use Go to write a kernel ... Not a production kernel, but MIT did use Go to "study the performance trade-offs of using a high-level language with garbage collection to…
The article is talking about ChromeOS merging to an Android base. Ninja edit: this article should clarify some things: https://blog.chromium.org/2024/06/building-faster-smarter-ch...
It's possible your previous knowledge was based on HiPE, which to my understanding was kind of sucky. The new JIT in Erlang/OTP 26 is called BeamASM and is based upon asmjit