Living under the tyranny of those who took your land, destroyed your cultural heritage and then swept your suffering and the death of your loved ones under the rug, using terrorism as some sort of justification? This is something you’ll have to clear with the native Americans and Inuits, even some other nomadic people.
Like again, I alluded to the Roma people (or Gypsy’s) for a reason. A broken folk, subjected under Romania (even though it has nothing to do with Roma folk), the “gypsies” lost their land in the North of India. Ever since, they’ve wandered as a people without ancestral lands, and that is a huge problem for not only the psyche, but also the culture has been subverted, destroyed and is but a husk of it’s former self.
This is why the technical definition of genocide has moved beyond body count.
I’m guessing you’re gonna say that there is no genocide if not all or most of the people are killed, because then their people have survived. But, genocide also incorporates cultural genocide. Today the day definitions are one and the same. Destroying someone’s culture and history also qualities, like during slavery.
The methods employed in genocide includes the methods of colonialism, persecution, subversion and the destructions of farms, Mosques, churches, hospitals, libraries, monuments, etc. Anything to persecute, harass and destroy someone.
Take for instance “the gypsies”. A people in diaspora from a nation state that doesn’t exist, roaming Europe forever, with no land to call their own.
That’s the fate the Israeli state wants for Palestine. It is still technically genocide.
Let me put it like this: it’s about learning curve. Arch is relatively easy to begin with, but NixOS gets much easier the more nix you learn.
What do I mean about that? Imagine having to patch something, which can be the thing. On arch you’d have to replace a package, which could lead to issues and conflicts, whereas NixOS gives you the option to keep two or even more versions of the same library, because it does not rely on your traditional UNIX path.
But with this super power comes a catch. You have to learn a programming language and learn how the nix store operates, which is a pretty high learning curve. Also, NixOS suffers from a governance issue and going by the documentation is like shooting in the dark.
That being said, the best manual for NixOS is GitHub, searching for anything and filtering by the nix language. You’ll see a ton of varying systems, be they workstations or servers.
And no matter what all the warnings say, no, flakes aren’t EXPERIMENTAL or UNSTABLE, but rather CONTENTIOUS internally. Again: I love NixOS, but they gotta fix their governance issues.
It’s still the best way of identifying animals and human bodies thank you very much. This is why 1/10 conspiratorial privacy advocates advise against going to the dentist. That’s Gary. He’s kookoo for cocoapuffs and also has really bad teeth.
Okay, folks. NixOS needs your help. No bull. I’m talking documenters, designers, coders, package maintainers. Why? Because the NixOS community has a lot on it’s plate right now.
Like I can understand why flakes haven’t become standardised, why it’s still marked as unstable, even though it’s pretty much feature complete, and that’s because nix is a complex environment builder and the current contributes are taxed to the max.
But what is nix?
Nix’s job is to create reproducible environments where you can put any library, any service, any application. It does this through compile time flags and modifying ELF headers to isolate applications on a system to their own, exclusive UNIX path. These are linked together as clojures, or a dependency graphs, that can share libraries, applications and services intetchangably with each othet, or use another version or patched version without causing any dependency conflicts.
You can fire up pretty much whatever you want and it will be reproducible elsewhere. It’s like if you took a package manager, build environments, as well as VMs and micro services and make them kiss.
You can spin up a nix environment on any supported system and expect it to run 1:1. This however breeds complexity and there’s a lack of NixOS contributors.
If only you spin up a nix environment on a VM or use it to replace your current build systems (because nix can use several build systems in one single environment), and then contribute back with some changes to nixpkgs, then you are helping to bring about the most powerful deployment tool since kubernetes.
No joke. Check out how you can contribute, because at the end of the day learning nix is gaining a new superpower.
Well technically, if you’re using BTRFS, you might want to check out subvolumes. Here’s my subvolume setup:
Subvolume 1, named @ (root subvol)
Subvolume 2, named @home (/home subvol)
Subvolume 3, named @srv (/srv subvol)
Subvolume 4, named @opt (/opt subvol)
Subvolume 5, named @swap (which is - you guessed it - the swap subvol)
You then set up fstab to reflect each of the subvolumes, using the subvol= option. Here’s the kicker: they are all in one partition. Yes, even the swap. Though caveat, swap still has to be a swapfile, but in its own separate subvolume. Don’t ask me why, it’s just the way to do it.
The great thing about subvolumes is that it doesn’t do any size provisioning, unless specified by the user. All subvolumes share the space available within the partition. This means you won’t have to do any soul searching when setting up the partitions regarding use of space.
This also means that if I want to nuke and pave, I only need run a BTRFS command on my @ subvolume (which contains /usr, /share, /bin), because it won’t be touching the contents of @home, @srv, or @opt. What’s extra cool here is that I’ll lose 0% FS metadata or permission setup, since you’re technically just disassociating some blocks from a subvolume. You’re not really “formatting”… which is neat as hell.
The only extra partitions I have is the EFI partition and an EXT4 partition for the /boot folder since I use LUKS2.