I have the latest Big Sur 11.0 Beta (20A5395g) installed on an external NVMe with nothing but Big Sur on it.
When booting into it, the "Big Sur" volume/container that is exposed in Finder is read-only, and there is no Big Sur Data container, as is shown in Disk Utility. I think I remember that in prior betas the exposed "Big Sur" volume was the read-write Data container, and not the read-only System container.
As it appears right now, I can't write anything to Big Sur.
I should add that the internal NVMe of my MBP 2018 contains Catalina, and the Catalina Data container is also shown in Disk Utility, but not in Finder. Finder only shows "Catalina" which is read-write (so it's really Catalina Data), so it is doing for Catalina what I would it expect to do for Big Sur (showing Big Sur Data as "Big Sur" in Finder).
What am I misunderstanding, or what can I do to get the behavior I am expecting?
When booting into it, the "Big Sur" volume/container that is exposed in Finder is read-only, and there is no Big Sur Data container, as is shown in Disk Utility. I think I remember that in prior betas the exposed "Big Sur" volume was the read-write Data container, and not the read-only System container.
As it appears right now, I can't write anything to Big Sur.
I should add that the internal NVMe of my MBP 2018 contains Catalina, and the Catalina Data container is also shown in Disk Utility, but not in Finder. Finder only shows "Catalina" which is read-write (so it's really Catalina Data), so it is doing for Catalina what I would it expect to do for Big Sur (showing Big Sur Data as "Big Sur" in Finder).
What am I misunderstanding, or what can I do to get the behavior I am expecting?