The normal and recommended Proxmox file structure is what you’ve after running rm -rf /. Just move to Incus (LXD) and be done with it.

Incus provides a unified experience to deal with both LXC containers and VMs. If you’re running a modern version of Proxmox then you’re already running LXC containers so why not move to Incus that is made by the same people? Why keep dragging all of the Proxmox overhead and potencial issues?

Incus is free can be installed on any clean Debian system with little to no overhead and on the release of Debian 13 it will be included on the repositories. Another interesting advantage of Incus is that you can move containers and VMs between hosts with different base kernels and Linux distros.

Read more here: https://tadeubento.com/2024/replace-proxmox-with-incus-lxd/

KISS

Debian is KISS. Grab it and use, no need to overcomplicate things.

• https://systemd.io/
• https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/using_systemd_unit_files_to_customize_and_optimize_your_system/assembly_working-with-systemd-unit-files_working-with-systemd#con_introduction-to-unit-files_assembly_working-with-systemd-unit-files
• https://www.freedesktop.org/software/systemd/man/latest/
• https://tadeubento.com/2023/systemd-hidden-gems-for-a-better-linux/

Systemd does a lot of stuff I guess it is easier to just lean based on what comes up / you need. There isn’t a single path.

For those who want to keep macOS due to some reason: https://github.com/blueboxd/chromium-legacy

It could be an amazing change that results in much more progress for hardware acceleration on guests of various types (since that is what vmware is good at) in kvm…

Yeah but VMware was good. And I’m not seeing Broadcom investing into porting the “proprietary goodness” of VMware into KVM. I just see then looking at KVM and saying “that’s good enough” and seeing it a cost reduction measure.

I’ve questions about this.

People are talking about it like it is the greatest thing ever, however, isn’t this yet another result of the Broadcom acquisition? After firing a bunch of people , now this. Maybe they just don’t want to maintain the “existing proprietary virtualization code” so they’re moving to KVM. Less costs, less people.

Like what?

Windows 10 Enterprise with a ton of group polices applied, no issues ever. The Windows Terminal app is really good.

Love it 😂

It’s not “my hardware” it is that everyone talks about Linux desktop yet nobody puts any effort into going into the tablet market that is where Linux can have a real advantage (because ARM + full desktop OS experience) and get a large user base.

Instead of wasting time on supporting bullshit hardware that almost nobody owns and will be forgotten in about 6 months, what about placing some effort into real hardware that real people want to use like tablets? Fucks sake.

Update: just to make it clear, I own no hardware of that type, it’s not “doesn’t work on my hardware” type of situation. It is that everyone likes to talks about Linux desktop (including Canonical) yet nobody puts any effort into going into the tablet market that is where Linux can have a real advantage (because ARM + full desktop OS experience) and get a real user base.

AirPods work so… how much more proprietary can you get? :P

Yeah, it may be less customizable but at least is fast and error free (unlike NextCloud)

Yeah, Incus FTW!!

The thing with Ubuntu / Canonical isn’t that it doesn’t work, it is that they’ve bad policies and by using their stuff you’re making yourself vulnerable to something akin to what happened with VMWare ESXi or with CentOS licensing - they may change their mind at some point and you’ll be left with a pile of machines and little to no time to move to other solution.

For starters Ubuntu is the only serious and corporate-backed distribution to ever release a major version on the website and have the ISO installer broken for a few days.

Ubuntu’s kernel is also a dumpster fire of hacks waiting for someone upstream to implement things properly so they can backport them and ditch their own implementations. We’ve seen this multiple times, shiftfs vs VFS idmap shifting is a great example of the issue.

Canonical has contributing to open-source for a long time, but have you heard about what happened with LXD/LXC? LXC was made with significant investments, primarily from IBM and Canonical. LXD was later developed as an independent project under the Linux Containers umbrella, also funded by Canonical. Everything seemed to be progressing well until last year when Canonical announced that LXD would no longer remain an independent project. They removed it from the Linux Containers project and brought it under in-house development.

They effectively took control of the codebase, changed repositories, relicensed previous contributions under a more restrictive license. To complicate matters, they required all contributors to sign a contract with new limitations and impositions. This shift has caused concerns, but most importantly LXD became essentially a closed-off in-house project of Canonical.

Some people may be annoyed at Snaps as well but I won’t get into that.

Will they learn how to apply padding to stuff this time?

vbox is easy until it starts saying vt-d isn’t enabled and refuses to start when it fact it is.

Maybe it can be installed in Debian 12 now without much trouble…

Yeah, all for security. I’ve been “complaining” about this for a while. :)

Tldr; Ubuntu clones a macOS feature (from 2019) that actually makes sense.