Hacker News Reader

Hacker News

Comment by bob_theslob646 | Hacker News Reader

Parent Full thread

bob_theslob646

>Let’s recap the week of Apple software problems:

- macOS High Sierra critical flaw with root admin access

- macOS High Sierra update released, but breaks file sharing

- iOS 11 crashing on some iPhones due to a date bug

- macOS High Sierra fix not installing correctly on some systems

-iOS 11.2 released early to fix iPhone crash bug

Yeah I would say that is a pretty bad week

View on HN

Don’t forget console being spammed with hundreds of “Month 13” messages a second!

Thanks for the heads up. I wonder what will happen first, Apple releases a fix or the logs fill up my disk?

That's what that was! I was up late last night trying to debug my app because of this.

Yup something to do with mdworker IIRC.

The transition to APFS also went flawlessly, above and beyond anyone's expectations.

Really? That transition introduced “store encryption password in plaintext, as password hint” - http://mashable.com/2017/10/06/high-sierra-password-fix-appl...

AFPS has serious performance issues:

https://macperformanceguide.com/blog/2017/20171124_2015-macO...

Apparently, apple won't implement apfs for people on spinning rust so I can't get it on an iMac which made upgrading to high sierra easier. How did it go for people on macbooks?

Nor for RAID drives, whatever the substrate... except that by virtue of my participation in the beta programme, my Mac's RAID-0 array was converted before they decided to change track, and now after I wiped my system to restart anew I have literally no way of getting my system back to the initial state it was in.

You can convert those disks, they don’t do it automatically though. Diskutility has a convert option.

That's a dumb idea, the file system is designed for flash memory, not spinning disks.

flawlessly - for iOS users only.

They also released 10.13.1, which undid the patch for the root login issue.

That's basically this point

> - macOS High Sierra fix not installing correctly on some system

But 10.13.1 has been out for a while, the root issue only resurfaces if you upgrade from 10.13 -> 10.13.1 after the patch is automatically installed.

Oops, my bad then, I misinterpreted the news yesterday about that. Do they at least prompt you to reapply the patch after updating?

10.13.1 was released more than a month ago.

Reply on news.ycombinator.com