dconf can also be configured with text files (with a format similar to ‘.ini’ files), although enabling this support isn’t trivial, and it’s not the most well documented feature.
I also used to run a ”lobotomized” Gnome, but TBH I found it easier in the long run to start from a minimal base.
It gives you a lot of convenience, auto updates, and dependencies. While it is nice being up to date by checking the git and making it by yourself it is much more convenient to have a package manager for it when you have many Make packages
When does it hang? If it’s after you log into your user, you could try to instead when on the login screen open a shell by pressing Ctrl + Alt + F2, uninstall Nvidia drivers and install mesa drivers. Or maybe at least investigate further.
yeah it hangs way before the login screen. It basically hangs immediately after exiting GRUB and goes directly to a flashing cursor.
elltee explained it above.. MX Linux’s stable distribution is on kernel 5.10 and I need kernel 6.x (part of their advanced hardware support release) to get AMD RDNA3 drivers. So I’ll most likely be doing a full reinstall unless you know how to replace kernels in place.
I have no idea what MX is but maybe you could just compile your own? It’s not that hard. If you’re going to wipe the system anyway, it’s an opportunity to mess around a little and learn
Just remember to
backup old kernel AND initrd
have a rescue usb in case it completely stops booting up
choose modules that are used for your hard drive and filesystem as built into the kernel, just in case
you should be able to copy the CONFIG of the old kernel in the repo and use it (as the wiki proposes)
Not sure I’m feeling adventurous enough to be compiling my own kernel at this stage in the game. I might do that for some of my homelab machines as an experiment but my main computer really needs to be drop-in and go with full stability.
You should be able to boot into runlevel 1 easily and upgrade the kernel using the steps someone else already mentioned. No reason to reinstall the entire system.
The point is that you want management, easy ways to create images, backups, move container between hosts, orchestration, network management and sometimes not only container but also virtual machines. LXD does it all very well and if you don’t want those resources you might as well use systemd-nspawn.
They’ve taken over Proxmox. Not sure if you’re following but they have now a WebUI and the entire solution is magnitudes better than the crap Proxmox has been offering.
Oh, bullshit. The minimal interface that Ubuntu offers isn’t even a pimple on the Proxmox front end, and doesn’t touch the filesystem, clustering abilities and backup solution that’s the equivalent of Veeam IMO.
There you are, calling bullshit on my post while deleting your own where you clearly demonstrated close to no experience with LXD and its clustering capabilities. lol
The minimal interface that Ubuntu offers
Once again your ineptitude is palpable. Ubuntu doesn’t offer anything, the WebUI is a part of LXD.
And yes LXD’s WebUI released “yesterday” is objectively better than Proxmox and it does touch storage and clustering.
I haven’t been following, but that’s actually good to hear, proxmox needs a better ui.
LXD, I suppose for the migration, but for any more complex orchestration I think you’ve moving to k8s or something more serious, LXD just has an odd “not enough but too much” feature set for me, I like things either push-button, or let me do it, this is kind of both.
for any more complex orchestration I think you’ve moving to k8s or something more serious
I guess it depends in your use case. If you’re taking about “regular” applications LXD/LXC might not be your best fit. LXD/LXC seem to very good for the more low level infraestruture related solutions. In contrast, whatever is typically deployed with k8s that is mostly immutable very reproducible and kind of runs at a very high level.
LXD is more about what might power that “higher level” layer, more about mutable containers, virtual machines and very complex stacks that you can’t deploy with docker most of the time. As excepted people with those needs greatly leverage cloud-init and Ansible in order to get the reproducibility and the automated deployment capabilities that the Docker “crowd” usually likes.
I do that with lxd, but I have written ansible playbooks (almost like dockerfile? ) to automate the lxd containers. You could probably write some automation for scaling as well, but not something I’ve done, I have just opted for high availability with ceph & keepalived. Whatever works for your use case :) I do use some docker, but this is still nested inside lxd…
I also do playbooks to deploy stuff some stuff with LXD, but my end users only like Docker so, I kind of setup the infrastructure that allows them to deploy Docker on top of LXD containers that are deployed using Ansible.
I kind of wish I had played with ROMs and stuff earlier. I still like the idea, but I don't use it because I use mobile payments so much that it would be a PITA not to have that working.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.