Awww man, thanks ☺️.
Good thing I love fiish, it's my default shell 😉.
0x4E4F
joined 2 years ago
Yes, you can just set it to mount a, let's say @home, subvolume to /home and that's that, done.
I know how to do that, you set the subvolume as the default one, thus, when mounting, if no options are passed, it always mounts that subvolume as root.
But, you have to disable that. Sure, I set it during install, cuz installers are stupid (if you tell it to install in /@, it will most probably moan), but disable it after first run (set the real root as the default subvol, i.e. mount point) and just add subvol mount options in fstab.
It's just extra steps I have to do now 😒, that's why the rant.
I need it because of Timeshift, it works with subvolumes only.
Yes, you can, but now I have to move the entire install to a subvolume, risking borking the install 😒.
Yeah, that should work, thanks 👍.
I just do lspci and install the adequate firmware 😂.
Timeshift works only with BTRFS subvolumes, thus, if you wanna have backups (snapshots), you have to have subvolumes and not install in the root of a BTRFS filesystem 😔.
Yes, if it's on 5 to 10 year old hardware.
Yep, been in the same boat 😂. Was an LTS fan for a long long time till I realized... this shit ain't worth it 😂.
Everthing there is out there in 99% of the cases compiles against latest libraries. And well, LTS is just... lagging behind 🤷. So, you solve one lib dependcy and then, bam, another one pops up... OK, solved that one, bam, another one 😒... it just gets frustrating to compile stuff on LTS.
And then you get all sorts of errors from the package manager cuz you did the unthinkable - install latest libs on an LTS distro.
LTS is good for one thing only nowadays - servers.
Why not use LAN instead?
Yeah, but Timeshift uses the Ubuntu style subvolume naming, @ for root, @home for /home, so you have to create them that way, otherwise, it won't work. It can work if you tell it to ignore home, but checks for @ as root on start up.