Because we are helpful people here.
Because questions at this level wouldn’t be answered on the Arch forum.
There are tons of topics here from people who are running Arch or other Arch-based distros already. I don’t think the goal is to become a general support forum for Arch but the nature of the community is to be helpful when we can.
I understand that, but a full on install seems extensive, that’s all. I don’t mind helping, we’re all using the same repos and packages, etc. We do regularly help each other - and many of us use Arch. I use Arch. This thread feels different than our usual help thread.
We just need to keep in check. The path to hell is paved in inches, not miles (or cm/I’m for you non Americans).
Well I am truly confused now
Just for the hell of it I used the new built in Arch installer, while it didn’t set everything up as it should have, it did install Arch and allowed me to boot into arch without a DE (my choice)
Installed KDE as Endeavour does along with Nvidia drivers…and its works 
looked to see what subvolumes the installer created and it only had these
ID 258 gen 14 top level 5 path var/lib/portables
ID 259 gen 15 top level 5 path var/lib/machines
Those are created by systemd. Basically everything is just sitting in the root of the btrfs partition.
It is easy enough to create the subvolumes after the fact.
At least I know whatever the issue is it is not with my hardware or the Arch-iso
I created an @home subvolume and it shows up in root.
not checked yet myself but with Endeavour picking btrfs doesn’t show any @ subvolumes in root. Either they are hidden or you set it up yourself 
Maybe I should just not bother with Timeshift or snapper, I mean… on my nvme its just programs I will be using nothing much. All my games are on a separate 2TB SSD
You can’t see the subvolume in / because @ is mounted on / for EOS. You can see the subvolumes the EOS installer create with sudo btrfs subvolume list /
Ah explains it, since the subvolumes I made are IN root i see them but if it was mount on root obviously I couldn’t see them.
hmm since doing so pr-install give me that horrible btrfs error, can i mount @ on root somehow alone with @home for example ?
Sadly what iv learned is all pre install not post install.
Since we have discussed so many different things I am not sure what you are referring to. Are you asking how to convert the system which has the filesystem mounted on root to use @ for root instead?
If so, it is easy.
sudo btrfs subvolume snapshot / /@/etc/fstab and grub to use subvol=@Thanks @dalto I consider this post answered ^^ but I do have one question since I can’t find a decent answer elsewhere.
What is the reasoning for Endeavour creating a @cache and @log subvolume ? most forum posts and guides just do @ @home @var or @snapshots.
@cache is /var/cache - It is there so the cache is excluded from snapshots. Cache has a high rate of change and there is no good reason to include it in a snapshot.
@log is /var/log - This is excluded so that if you need to restore a snapshot you won’t overwrite your logs so can investigate if you need to.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.