News for hackers. Stuff that matters.
Re:Upgrading to Mac OS X 10.10 Yosemite as a Developer by podsnap on Friday October 17, 2014 @12:42PM (#8471838)
I had 32k files using up 8GB in /usr/local, and the time spent on "2 minutes remaining" was about 45 minutes. In retrospect, I'm happy that I didn't waste any time on special preparations. One thing I learned is that the ⌘L log window blocks progression from restore to the next reboot; I lost about 15 minutes that way.
Re:Upgrading to Mac OS X 10.10 Yosemite as a Developer by podsnap on Saturday October 18, 2014 @09:16AM (#8475266)
Sorry, 32k was the result of `ls -lR /usr/local | wc -l` and then typing on a keyboard with a broken 4. To be much more precise, `find /usr/local -type f | wc -l` is 243185, while (including directories and links) `find /usr/local | wc -l` is 274709.
Re:Upgrading to Mac OS X 10.10 Yosemite as a Developer by bratsche on Friday October 17, 2014 @05:17PM (#8473428)
45 minutes, another lost 15 minutes... wow, you're install went fast! Everyone else seems to be having multiple-hours long installs. :)
Re:Upgrading to Mac OS X 10.10 Yosemite as a Developer by podsnap on Friday October 17, 2014 @07:02PM (#8473881)
It was multi-hour altogether, but the lying about two minutes remaining only took 45 minutes.
Re:Upgrading to Mac OS X 10.10 Yosemite as a Developer by jlindley on Friday October 17, 2014 @01:43PM (#8472244)
I'll add that note. People with problems tended have >100k or more files.
Re:Upgrading to Mac OS X 10.10 Yosemite as a Developer by podsnap on Saturday October 18, 2014 @09:27AM (#8475278)
See my reply above. A more accurate count on a keyboard with working keys is 243185. I'm starting to wonder whether the /usr/local-related delay is naturally about an hour, but vastly increased - sometimes catastrophically - by having the log window open. Just a theory.
Re:Upgrading to Mac OS X 10.10 Yosemite as a Developer by jlindley on Saturday October 18, 2014 @12:42PM (#8475693)
I've gotten messages from people who didn't even know how to open the log viewer until hours into the process, so it's just a highly variable delay depending on individual circumstances.