Quote from: asUHWEceyc on December 13, 2019, 02:32:47 PM

Quote from: jbreher on December 13, 2019, 02:30:36 AM

Quote from: jbreher on December 12, 2019, 05:59:19 AM

Quote from: Last of the V8s on December 11, 2019, 05:42:50 PM

explain

In a long shameful convoluted story, I find myself with a new tricked out MacBook Pro 16", and a Time Machine brain transplant from the last machine. Not yet fully cloned. New MBP runs only Catalina. Apple has seen fit to -- get this -- prevent users from writing to the root directory of the filesystem.

Now I need to figure out how I want to map a nearly four-decade-old directory structure to the absurd dictates of my new environ.

jojo69's hell may be different - dunno.

Good news, everyone.

While it is not really well documented, there is a workaround.

Apple has created a new type of symlink-like filesystem construct. Using this synthetic link, one can create a 'ghost link' in the root of the filesystem. This link can redirect to another place in your filesystem, like any normal symlink. It does not, however, exist on disk. It is instantiated at boot. One configures these links through an fstab-like mechanism: a new file /etc/synthetic.conf.

After creating a link using this mechanism and rebooting, my filesystem looks like it used to. I am now happily restoring over 400,000 files -- over 220GB -- from Time Machine to this new phantom filesystem location. So all my old scripts and such should work just fine.

More info at man synthetic.conf.

Why Apple's second-level support was utterly unaware of this workaround is a mystery. But there you go.

how do you feel about macos being slowly and now rapidly disfigured into a cellular phone-home applianceOS ?

Not particularly good. For the moment, however, I can still bend it to my will. And I still find it a better solution for my personal productivity machine than either Win or any *nix - both of which I use for what they are each respectively good for.