Are you planning to carve up different partitions on that one disk? You'll want to create a partition just for /home. And you could make 2-3 other partitions in anticipation of installing different distros.
Work carefully! Double-check the partition layout with 'lsblk' to make sure you don't install a distro to the wrong location.
Yes. That's exactly what I'm asking about, along with the recommended size and formatting for 2-3 distro installs.
i also mentioned that you can and should make a dedicated partition for /home :)
also, pretty much all of the distros i recommended have the option to "try" and in the live system you have Gnome Disks which is practically identical to the one in macOS
i recommend using it to slice up the disk although gparted can be better in some regards.
all distro and home partition just use ext4, don't be tempted to use btrfs, even though it's getting better you can have issues with it
also, in fact you can probably even use merely 100gb of space for each distro, rather than 200. i only recommend 200 in case you do end up wanting to install a lot of apps via dpkg or pacman or whatever
I usually install 2-4 web browsers, a bunch of messaging apps, an office sweet, gimp, and a bunch bunch of smaller, dedicated programs for specific oddities (like messing with the rgb leds on a keyboard).
I do want to start running more nostr-focused stuff. I really have no clue what I need for that, though. Local relay stuff?
yeah, probably you only need to give 100gb for each distro then.
running local relays, idk...
i know it's quite easy to do with realy but browsers block access to localhost which can be a huge pain and most web apps that allow local relay access won't let you point it at an IP address or domain name.
i had a bit of a disagreement with hzrd149 over this subject, pointing out that the browsers block this and even with what should be allowing it in the app config in the browser it wouldn't do it. being able to designate an arbitrary address for your "cache" relay would be really handy.
especially because if you set up a wireguard vpn and reverse proxy on a VPS other people can read and post to it (my relay on wss://realy.mleku.dev was being used automagically by other people, including you, because of the magic of outbox model). if the client would let me set a relay as my cache in this way i could have a second one on my machine that just does caching for my app, it would make loading old events a lot faster
Reading is not my first language. ; ) I fully endorse your advice.
