Any setup where the kernels aren't stored on the btrfs root does not give bootable timeshift snapshots. This includes UKI.
moonpiedumplings
joined 2 years ago
Dunno why this is downvoted, this is unironically a last resort of mine. I don't want to maintain a fork of grub but if it comes down to it, I may do something similar to this except the sed trick doesn't seem to work anymore.
EDIT: sed trick does work. I just forgot to install grub with --disable-shim-lock.
My goal was to install openstack on my server, using kolla-ansible, one of the automatic installers. It officially supported debian 11. I would have had to upgrade when the openstack packagers switched over to 12.
But it also officially supported Rocky Linux 9, which goes eol in like 7 years.
I am building a homelab for during college (4 years) and I don't really feel like doing a release upgrade (ie: debian 11 to 12) in the middle of schooling or over a break when i wanna relax and just chill. Debian offers 2 years of support official, and like 4 extended (unluckily, the times didn't align so if I picked debian I would have to upgrade during college),and Rocky/alma offer 4 years official and like 8 extended.
I might be wrong (on phone rn), I recommend checking https://endoflife.date
Big difference, big enough that this factor is the singular reason companies go with them. Not having to do release upgrades as frequently means less maintenance, means less costly.
If you are using kde, then this feature is right in the settings menu. I have caps lock bound to compose. I dunno about other DE's.
The issue people have with snaps isn't the containerization or the bundles, but the proprietary backend. There is no way to point the snaps at a different store other than the one canonical controls. Canonicals forcing snaps on people pisses a lot of people off because it's a blatant power grab, an attempt to get people dependent on something they have control over in a microsoft-esque move. Flatpaks and docker don't have that issue.
Definitely the clipboard manager. On kde, it's klipper. This is actually such an underrated piece of software that I can't live without. Windows has one too, but they added their's a little after all the linux desktop environments got one by default.
Because it's not their responsibility to add a feature people primarily use on servers to an installer built for desktop usage. Because there installer isn't bad, it's loved exactly for the ability to automate it. Because their installer works, and it doesn't take a lot of manpower. According to debian salsa, it basically only receives translations and package updates, some of that automated.
Why have the debian devs go off and add support a whole another installer (by support I mean actually attempt to add features to it) when they have a perfectly nice, working installer? The devs have more important things to do.
Not automatable. The default debiam installer has a feature called preseeding, where you point it to a website serving a preseed file (and you can do this with automated commands input by qemu or vnc), and it gets a recipe on how to install the system.
Open issue: https://github.com/calamares/calamares/issues/508
Well damn, I guess fraud must be a lot more widespread than I thought. Because no one seems to get punished for this behavior. Just recently, Lockpick, a tool for getting Nintendo Switch roms off a physical device, was dmca'd, and the person who filed the complaint admitted to doing so on twitter. They received no punishment.
I think it's likely that this is a similar case.
Isn't that what copyright/patent trolls are? People who lodge complaints on the behalf of others, regardless of whether or not the original owner of the intellectual property actually cares, or in some cases, even is legally allowed to do so? If it's the original owner, then it's usually just considered to be protecting property.
My important data is backed up to several usb drives, and kept in sync between two computers via syncthing. Soon I will back it up to my college's box cloud, using rclone's crypt feature.
But this isn't about data. This is about me being able to tinker without worry, breaking down to even the lowest level of my system. In addition to that, I don't want to have to waste time manually restoring a system snapshot/backup, as I will soon be busy with other things like classes. I want a one step process.