4 ms·
It now looks as though it might be Google Chrome. Whoooops. https://mrmacintosh.com/google-chrome-keystone-is-modifying-var-symlink-on-non-sip-macs-causing-boo
by theclaw 7y ago
It now looks as though it might be Google Chrome. Whoooops.
https://mrmacintosh.com/google-chrome-keystone-is-modifying-var-symlink-on-non-sip-macs-causing-boot-issues/ https://mrmacintosh.com/google-chrome-keystone-is-modifying-...
e: hn discussion here: https://news.ycombinator.com/item?id=21064663 https://news.ycombinator.com/item?id=21064663
- holy_city 7y agoI can't wait for the post mortem, I wasn't expecting anything with Avid/PACE but if it's Google's problem then maybe we'll get info. I work in this space (and am a casual user in the space) and I really want to know why /private/var was getting unlinked through a normal update and why Avid got pinged for it.
- ratww 7y ago> why Avid got pinged for it I think that was just because it was Avid users discovered it on the FB group[1]. I thought it was cool of their CEO to talk to the community, despite no evidence of it being their fault. [1] https://www.facebook.com/groups/mediacomposer/permalink/10158340050634460/ https://www.facebook.com/groups/mediacomposer/permalink/1015...