That's what I would expect when I get started scripting the setup myself. If I don't do it then using a sensible, community decided default would be better than doing something without investigating. Would you agree?
That's what I would expect when I get started scripting the setup myself. If I don't do it then using a sensible, community decided default would be better than doing something without investigating. Would you agree?
My familiarity with grub and the UEFI boot-process was really limited. The beginner's guide and the rest of the Arch wiki are extremely useful, and I was able to get everything set up, but it did take several hours.
Then, a couple of weeks later, my system broke with a kernel update. I hadn't properly set up my fstab to point /boot to the correct partition, so I had a separate /boot directory in the same partition as my root system... stupid on my part.
It was a bit of a pain to fix, because I couldn't boot into the system. I ended up using the USB installer that I had setup Arch with. Now things seem to be running fine again (except that recently "suspend" and "hibernate" randomly disappeared from the shutdown options in my Cinnamon DE... weird).
But yeah, Arch forces you to learn the things that you can just overlook on something like Ubuntu. I takes time, but at least you learn how to fix them when they break. I've shot myself in the foot a few times, but it's been with a BB gun instead of a shotgun.