I have been using the same Arch installation for about 8 years. The initial installation/configuration is the only time consuming part. Actual day-to-day usage is extremely easy.
Maybe this is no longer the case but I previously used Ubuntu and it was actually much more annoying in comparison, especially when upgrading between major revisions or needing to track down sources/PPAs for packages not in the main repos. Or just when you want something more up-to-date than what they’re currently shipping.
The rolling release model + the AUR saves so much time and prevents a lot of headaches.
It isn’t just you, it failed on me enough times that I’ll never touch it again. I either manually install raw Arch, or use EndeavourOS instead for a “lazy” install.
You know how I know I've gotten better at using linux?
I saw the command and read it and figured out what it was although I've never been exposed to a fork bomb before in my life.
I was like okay, this is an empty function that calls itself and then pipes itself back into itself? What the hell is going on?
I will say that whoever invented this is definitely getting fucked by roko's basilisk, though. The minute they thought of this it was too late for them.
99.999% of that function’s effectiveness is that unix shell, being the ancient dinosaur it is, not just allows : as a function name but also uses the exact same declaration syntax for symbol and alphanumeric functions:
i’m gonna get crucified for giving apple a single benefit of a doubt but i think there are just as many windows users who “fear technology” as mac ones. think of all the grandparents running shitty dollar store pcs. mac is only a walled sandbox until you turn off the safeguards, then you can see exactly as much dumb back-end shit as you can on windows
I think this is sdvice on what you should do, not what people actually do. This would be why there is such a big industry for windows tech support. Tldr: Windows: Be afraid, very afraid.
Yes, you can. But the usual setup is to have a file system root that is nothing but subvolumes, which you can then use and mount basically as if they were independent partitions. But when you don't create a root subvolume for your system root first, you install the system directly on the file system root alongside created subvolumes. This tends to get messy as strictly speaking the file system root is a subvolume, too. So now you have that with your system installed and all other subvolumes nested inside it.
Yes. Usually the OS installer takes care of creating a root and home subvolume. Except Arch and similar barebones installer have instructions in the wiki.
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 😔.
If you want to you can just create a new subvolume, mount it temporarily and move all your files from root to there. Then you need to figure out how to make the new subvolume your root directory upon boot and you are 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.
That’s only to backup/rollback the root though, right? If one’s looking to backup - say - their home dir, they can just recreate the home as a subvolume without reinstalling the system. Or am I mistaken?
Snapper also uses btrfs subvolumes to create snapshots, so if you did create them during your installation process, nothing to worry about.
I don’t remember if there is a way to create them after the installation, neither if it’s a tough process tho. I used to simply reinstall when I messed up with the subvolumes.
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.
linuxmemes
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.