Could somebody explain in very simple terms how I might get my M1 Mac Pro to dual boot between MacOS & Linux? Is there a guide or HowTo? Or am I a few months early re mainstream Linux rollout.
This will download and execute the Asahi Linux installer. If you want to check the source ahead of time, it's on the Asahi Linux GitHub.
While functionality improves rapidly every day, it is still decently rough around the edges. However, the installer is very streamlined and it's easy to get set up and try it out.
Why not? Without looking, I assume that the script is downloading a binary and running it. What could it be doing that is more dangerous than that?
If someone wanted to do `rm -rf /` on your system, they wouldn't put it in the setup script you're piping to sh: they'd put it into the binary, making your inspection of the setup script effectively useless.
There are a few things that make shell script installers particularly dangerous, though. I don't think any are meaningful with the way people normally use computers, but they could be meaningful in the future if we improve our collective security posture:
* Shell script installers aren't digitally signed. Most OSes have pretty weak code signature schemes anyway. They're littered with root-of-trust issues that prevent a lot of OSS from being signed to begin with, and in turn, the vast majority of users (especially power users) ignore code signing warnings. But, as these problems are addressed, shell scripts will become weaker and weaker in comparison to binary packages.
* Shell script based sites can fingerprint the client and serve different content to a browser and to the "curl" command, confusing users who attempt to audit what's going to run before it's passed into the shell script command. This is a fine argument and a real problem with the "pipe to sh" approach. However, unless the user is also independently checksumming or disassembling every binary application they download, it's also a bit of a straw man.
Nice straw man. Completely unfalsifiable. I didn’t bother reading the rest.
2. Someone tells him
3. Third person chimes in “you know, it’s technically possible that they’re lying!” despite no evidence of that being the case.
Tough crowd…
(Btw, you can easily verify that the alx.sh installation method is recommended by official sources, for example here: https://asahilinux.org/2022/03/asahi-linux-alpha-release/)
The best way to share files with a proprietary system is to go through some sort of network, i.e. NAS, smb, etc.
----
If I was going to go that route, on my MacBook which is 1TB, I would probably do something like 200GB for macOS, 200GB for Linux and then a shared partition of the rest (~600GB). I'd probably make the shared partition ExFAT, or possibly un-journaled HSF+.
I think the easiest way would be to install Asahi first, pick the size you want for it (200GB in my example), then once you have that sorted, figure out how to create another partition that you will format as ExFAT/HSF+/Whatever you want. I'm sure this is possible/easiest from the macOS side of things, although I have never partitioned a drive in macOS. The Asahi installer does it from the command line in macOS, so I'm sure Disk Utility has the ability to resize and create partitions, too.
Just forget about dual booting nobody really does that.