2 ms·
> More likely is that if you boot Linux, a driver bug will cause data corruption. We've had some reports of filesystem issues, though as I said the kernel tree
by rvz 5y ago
> More likely is that if you boot Linux, a driver bug will cause data corruption. We've had some reports of filesystem issues, though as I said the kernel tree situation is haphazard right now, so we'll see if they still happen once we put together a tree with properly vetted patches :)
Well that is another notable risk isn't it? If something goes wrong on the filesystem level (since you admitted it) then the worst case is that the OS and your important files become corrupted some how and it is back to recovery once again, if not then they will use Apple Configurator which requires another Mac.
Regardless, I would most certainly use another machine to test this, hence why I said 'use at your own risk', especially when the installation script is pre-alpha.
What is wrong with such a disclaimer?
- zamadatix 5y agoDo you really care if Linux corrupts its apfs container on machine 2 instead of machine 1? Just don't go mounting your macOS apfs container and it's no different. Regardless I think most of the problem was with defaulting to fear mongering, particularly at the warranty, rather than gaining an understanding of what the risks are before making recommending action to avoid said risks.
- rvz 5y agoHow is it fear-mongering to say 'Use at your own risk' for installing an OS that is not fully supported and even the installation script is in pre-alpha? Fine for those who have a spare M1 machine but the added risk comes when it is their only machine with important work and files on it. Do you want to be liable when someone tries this script out and somehow ends up losing their important work because of those recently admitted 'filesystem issues' on the only machine they have? That is my point and why I said: "I would most certainly use another machine to test this" I don't see lots of general users racing to install this right now, since they probably know that it is still incomplete with lots of bugs and is still unusable. Unless you want to install it right now on your work machine with important files perhaps? If not then wait.
- marcan_42 5y agoYou can DFU these machines from Linux with idevicerestore, no need for Apple Configurator.
- rvz 5y agoCan you fully restore them right now officially with idevicerestore on all M1 Macs even if they are on either Windows or Linux? Is there any source for this? Is that functionality in idevicerestore ready to use instead of using Apple Configurator?
- marcan_42 5y agoI don't know about Windows, but it runs on Linux, yes, and it works on at least the M1 Mac Mini. See: https://github.com/libimobiledevice/idevicerestore/pull/406 https://github.com/libimobiledevice/idevicerestore/pull/406 There's some bug with the laptops, but it should be easy to fix once someone takes a good look at it. I might spend some time on that; I definitely want idevicerestore to be in good shape before we start encouraging more wide usage of Asahi. (https://github.com/libimobiledevice/idevicerestore/issues/411 https://github.com/libimobiledevice/idevicerestore/issues/41...)