Jorge de la Fuente
Hi, thanks for everything. I am comparing the installation in BTRFS of Manjaro Architec versus Artix and I see that Artix only creates 2 Subvolumes: “@” and “@home”, Architec creates 4 subvolumes: @, @cache, @home @snapshots this seems to have been implemented as a Improvement in Manjaro Architec, according to read here https://is.gd/5XsFGL can it be implemented in Artix?
I am definetely not an authority to speak on the issue, I have only tried BTRFS on a test installation and while I did not have any problems with it I read so many horror stories that I gave up and returned to ext4 safety. I recently read that RedHat is giving up support for BTRFS and will no longer offer it. One explanation I read was that if you use BTRFS and take snapshots of the system while you are testing to remove and escape from systemd people will start more and more attempting it. I don’t know why anyone would run RH and try to escape systemd.
Also, I believe that Artix is following structurally Arch, not Manjaro. It is alsmost a false statement to say Artix is Manjaro OpenRC as it is not. Manjaro has made a name for itself for taking Arch and splitting things up in 2-3 services, daemons, and giving systemd plenty to do and regulate. In your case it seems there are clear advantages to do so but on the specifics I can not help you much. Is it as easy as making separate partitions, all BTRFS, and mapping /cache and /snapshots directories through /etc/fstab into them, in order to be able to back-them-up easier? I know that arch-manjaro mounting of volumes is slightly different than other linux (debian related). You have to make actual directories, mount the volumes to those directories, and make an fstab entry/ies to match. mount /dev/sdc45 /snapshots …. or something along those lines. Again my experience with btrfs is limited.