Joke’s on you, user has virtualized windows ME.
But on a serious note, doesn’t that simply kill the virtual machine with a useless amount of load? What is different on MacOS? As in: couldn’t I do the same with any virtual machine independently of the host OS?
Not familiar with MacOS at all but I wouldn’t be surprised if Apple just doesn’t respect the VM and has some “safeguard” intervention mechanic…
mount --bind
warning: do not attempt if linux is your actual OS, this shit is for virtual macbros ONLY
Why not? A VM is a VM. You can remove root in there just fine?
didn’t let me remove root. i ran the command with
sudoand it just kept saying “can’t remove root”. i’m using UTM on macOS tahoeyou can maybe use strace to find where this text is coming from, btw.
i’ve been a macbro for 8 years but i just got into linux, what…two days ago? so i don’t know any of the lingo. but i just googled strace,looks like it’s good for debugging shit. neat! i try to do as much as i can from the terminal as possible
if it just says that and doesn’t do anything, there’s some extra safety added, maybe in sudo or the shell.
otherwise, it can’t remove “/”, because it’s a mount point in use. the point is that the recursive switch removes all subdirs, which are not mount points, leaving just empty disks an a handful dirs behind.
after i ran it, none of my commands worked. well of course they didn’t work, everything but root got wiped, so goodbye /usr/bin and all that
I did that on purpose once to test Timeshift’s restore. I had to boot to a live image to run the restoration, but it worked great! Very impressed.
Only applies if the Timeshift directory is not in the removed path.


