Btrfs can mostly fo everything you would normaly use LVN or raid for natively.
Btrfs raid0 lets you combine any number of differently sized drives into one (just without the speed boost of traditional raid0 because with flexible drive sizes data is not symmetrical striped). And btrfs raid1 keeps every data duplicated, again with flexible number and sizes of drive (also with metadata on every drive).
The sytemd hooks (instead of the traditional busybox ones) then manage the one other task you use LVM for: unlocking multiple partitons (for example multiple raid partitons and swap) with just one password. Because the systemd encrypt function tries unlooking all luks partitions it finds with the first password provided and only asks for passwords for each partition if that doesn't work.
PS: btrfs subvolumes are already flexible in size and don't need predefined sizes. So the only things that need to be created separately are non-btrfs stuff like the efi system partition or a physical swap (which you can also skip by using a swap file instead of a partition).
The main trash you accumulate are config files in you home directory because they stay after the package is uninstalled. And they just sit there not hurting anybody.
Which btw is the reason many people ended up with Archlinux... after the x-th time looking up some configuration issues on another distro and landing there.
I think it's not a newbie but a general user issue. I have learned to recognize the linux newbies for whom Arch is a good fit over time... just by watching which people distro hop until landing with Archlinux.
PS: And among the typical distro hoppers is really a big chunk of them... because for a lot of them distro hopping is just a symptom of wanting to make the mandatory big system upgrades every few years at best worth it by trying something new. Those should actually get a rolling distro as a recommendation much earlier.
Yes, you are missing the fact that it's mostly not people making Archlinux their personality, but people making meme'ing about "Archlinux users" their personality. For the vast majority it's just an OS.
They are written but don't replace something in the read-only OS. They are just overlayed, so once removed the original is still there. How they do it differs. There are actual overlay filesystems for the job, or some use btrfs where all subvolumes behave mostly like virtual partitions (and copies of a subvolume only take space for changes of the original).
An immutable OS is fixed and mounted non-writable. Every update you get, every program you install is handled on top of it via containers or filesystem overlays so the underlying OS is untouched.
Basically the same concept you know from smartphones or other devices with a "reset to factory settings" function. No matter how hard you screw up your system, you can always reset to the base OS, either by granulary deactivating things installed on top, or by a reset to the working base OS.
Good thing is the kind of people making decisions based on buzzword-bongo filled PR campaigns like Crowdstrike's are already forcing their IT to use Windows anyway.
It's the other way around. All those PCs are bluescreening at boot. So that prevents fixing the system remotely and on a large scale. Now poor IT guys have to fix evey single one by hand.
But they don't. I mean call for him to step back, not having a plan (which they probably also don't have).
This is a massive campaign of media bullshitting (like in this case where you can try to find that statement from Obama, when in reality the best you will get is that someone said someone else told them that Obama had said this in private...). I guess a shitshow incarnate as Trump would just fit today's media operation of enragement farming and doom scrolling much better and who would ever look further than to their next bottom line.
Dual booting with Windows is always a pain, because Windows likes to nuke and replace your boot menu.
The safest bet is keep Windows strictly separated: You create a 2nd efi system partition on your second drive with linux, use a boot loader there and then set everything up to start that as default. And then you configure the boot loader to chainload windows from it's own ESP on disk one. This way Windows is oblivious about linux systems it might try to damage. And you can then set the boot loader menu to a default or to default to the last system booted. (2 separate ESPs on on disk might work, but that is not supported by UEFI, so it depends on your hardware's implementation if they are recognized or if it just stops after having found the first...).
I would assume what you did was install the Linux boot loader (efi file) as the default like removable drives do (so grub's efi file installed as esp/EFI/BOOT/BOOT64.efi which is the default for removably drives to take priority; done via grub-install with the --removable flag, some installations might use this by default...)
Yeah, why would you try to actually solve a problem instead of just applying a band-aid that the next administration can rip of again (by incresing the size of the court again)?
Zen Kernel is the opposite of "optimized for gaming".
It was once the default kernel for out-of-the-box gaming simply because it had fsync patches integrated. But since fsync is in the normal kernel for quite some time now zen is obsolete for that purpose.
I mean it's still an okay choice for any desktop environment but it is definitely not optimized for gaming as it sacrifices throughput and is more tailored to multitasking of a lot of smaller things running to provide a snappy desktop experience.
Ooops @ Ooops @feddit.org Posts 0Comments 180Joined 1 yr. ago
Btrfs can mostly fo everything you would normaly use LVN or raid for natively.
Btrfs raid0 lets you combine any number of differently sized drives into one (just without the speed boost of traditional raid0 because with flexible drive sizes data is not symmetrical striped). And btrfs raid1 keeps every data duplicated, again with flexible number and sizes of drive (also with metadata on every drive).
The sytemd hooks (instead of the traditional busybox ones) then manage the one other task you use LVM for: unlocking multiple partitons (for example multiple raid partitons and swap) with just one password. Because the systemd encrypt function tries unlooking all luks partitions it finds with the first password provided and only asks for passwords for each partition if that doesn't work.
PS: btrfs subvolumes are already flexible in size and don't need predefined sizes. So the only things that need to be created separately are non-btrfs stuff like the efi system partition or a physical swap (which you can also skip by using a swap file instead of a partition).