>>34163I would agree especially with avoiding configuring the kernel at first.
Work within the software, not against it.
Avoid setting a separate /usr/ or FDE but a separate /var/ can be useful to avoid filling up / with caches.
(You generally will have to clear out the caches in /var/)
It's difficult to get a split-usr config to work today, and FDE is many more steps.
Pile your extra space into /home.
Clearly on my machine /efi is too large (I was unfamiliar with this so I was cautious)
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg0-root 24G 12G 11G 52% /
/dev/mapper/vg0-var 24G 4.4G 18G 20% /var
/dev/mapper/vg0-home 54G 19G 33G 36% /home
/dev/sda1 1022M 168K 1022M 1% /efi
/dev/sda2 1022M 135M 888M 14% /boot
Use the right tool for the job.
For example just use dispatch-conf to edit files if needed.
If you need to edit images install gimp, or similar, don't try to do it in the browser.
Configure an LSP if you're going to be coding.
Generally use your memory.
If you're familiar with say ext4, use that instead of btrfs or ZFS.
If you know X11 use that instead of Wayland.
If you don't know anything just check the handbook.
Maybe eventually you have good reason to try something else.
Follow the documentation completely, check the optional stuff.
For example you need network tools before you reboot.
In fact refer back to the documentation even over searching for your issues.
If you're playing an optimization game, don't optimize for install size, or ease.
Gentoo is a bad fit for this.
Focus instead on something like active running software, patches, etc.
Have fun with it, you know, but also try to make something that works.
Don't get frustrated if you make mistakes - these happen, especially in the beginning.
If somethings unworkably wrong, reboot back into the live disk and chroot back in after setting up the network.