I had heard about it on a Quidsup video and from a guy on Gab who was running it.
Burned the ISO to a 4GB USB stick and booted it up.
Did I ever tell you how much I hated Gnome? My dislike was renewed and strengthened.
Antergos is well constructed but the ISO comes with Gnome as the default.
I inserted a 16GB USB stick and installed Antergos to it selecting KDE as the DE and using Btrfs as the fs for /.
When I booted up I was disappointed. The @ and @home roots for Btrfs were not present. When running btrfs-find-root it pointed me at /var/lib/machines.
So, how do I get my preferred btrfs file system structure? One method is explained here.
http://blog.fabio.mancinelli.me/2012..._on_BTRFS.html
All of that in order to create @ and @home at the root of the btrfs file system, something Ubuntu, Kubuntu and Neon do automatically when you chose btrfs as the file system for / during the install.
Antergos did leave me a little going away present ... despite my careful avoidance of my sda @ sdc drives, on which my main installation resides .... it corrupted my boot loader. So, I had to chroot proc and run grub-update to recover it. For good measure I rolled back to my most recent snapshot. Everything came up fine and Antergos is just a bad memory.
Burned the ISO to a 4GB USB stick and booted it up.
Did I ever tell you how much I hated Gnome? My dislike was renewed and strengthened.
Antergos is well constructed but the ISO comes with Gnome as the default.
I inserted a 16GB USB stick and installed Antergos to it selecting KDE as the DE and using Btrfs as the fs for /.
When I booted up I was disappointed. The @ and @home roots for Btrfs were not present. When running btrfs-find-root it pointed me at /var/lib/machines.
So, how do I get my preferred btrfs file system structure? One method is explained here.
http://blog.fabio.mancinelli.me/2012..._on_BTRFS.html
All of that in order to create @ and @home at the root of the btrfs file system, something Ubuntu, Kubuntu and Neon do automatically when you chose btrfs as the file system for / during the install.
Antergos did leave me a little going away present ... despite my careful avoidance of my sda @ sdc drives, on which my main installation resides .... it corrupted my boot loader. So, I had to chroot proc and run grub-update to recover it. For good measure I rolled back to my most recent snapshot. Everything came up fine and Antergos is just a bad memory.
Comment