JohnPhilpin
JohnPhilpin

GAH - whatever I do :-(

Not Alone

|
Embed
Progress spinner
derekpeden
derekpeden

@JohnPhilpin oh I never update on day one

|
Embed
Progress spinner
hutaffe
hutaffe

@JohnPhilpin you get the full beta developer experience, isn’t it great? I had to wait 4 days for the first beta to even get downloaded, and then two more after it just sat there doing nothing 😅 Good Luck 🍀

|
Embed
Progress spinner
adders
adders

@derekpeden And today you couldn't even if you wanted to… 😇

|
Embed
Progress spinner
derekpeden
derekpeden

@adders I was referring to 10.15

|
Embed
Progress spinner
adders
adders

@derekpeden Indeed. And given the state of Apple's servers right now, it might hold true for that, too…

|
Embed
Progress spinner
In reply to
JohnPhilpin
JohnPhilpin

A Public Service Announcement

VLogg writes about what to do in case of a failed Big Sur install - because it appears that once it has failed, it needs to be flushed.

They write:

After trying out a few options, here are the steps that worked.

Option #1

Reboot your Mac, while holding the CMD + R keys Launch Disk Utility Chose the Machintosh HD disk from the list Click on First Aid and hit the Run button Once it’s complete, choose Done and close Close the Mac or Shutdown completely (This is important, a reboot doesn’t work) When it’s back up, go to System Updates and it should continue the download from where it left off (For us it went back to 2.4 GB even though previously it completed up to 5.4 GB)

Option #2 (Since option #1 worked, we couldn’t fully test this method)

Launch terminal Enter this command and hit enter $ softwareupdate –fetch-full-installer –full-installer-version 11.0.1 This triggered new software updates as well in another machine where unfortunately Big Sur, not supported

confirming that I thought option one was a bit of a long winded hassle - so went straight to option 2. It worked.

This is my first MicroBlog post from a Big Sur Mac.

|
Embed
Progress spinner
fabio
fabio

@JohnPhilpin how's stability?

|
Embed
Progress spinner
fgtech
fgtech

@bix It appears to be a reply from where I’m reading in the micro.blog iOS app.

|
Embed
Progress spinner
fgtech
fgtech

@bix Yeah, I think that’s something that changed along the way; maybe an implementation detail that shifted.

|
Embed
Progress spinner
JohnPhilpin
JohnPhilpin

@bix i replied to my own thread - but just removed the @johnphilpin at the beginning - so it is really a reply - just doesn't look like that.

I sometimes do the opposite - as in start a new thread with @johnphilpin - and it appears in the timeline - but doesn’t get routed into twitter et al

|
Embed
Progress spinner
JohnPhilpin
JohnPhilpin

@fabio so far so good - but earlu days:-) 17 app updates immediately after !

|
Embed
Progress spinner
JohnPhilpin
JohnPhilpin

@bix so long as it is a reply - ie inside a conversation - killing the @ at the beginning has been around a loooong time

|
Embed
Progress spinner
JohnPhilpin
JohnPhilpin

@derekpeden you obviously have such an exciting life you don’t need to throw caution to the wind once a year :-)

|
Embed
Progress spinner
JohnPhilpin
JohnPhilpin

@adders i got it on day one - in the end

|
Embed
Progress spinner
JohnPhilpin
JohnPhilpin

@derekpeden 😂

|
Embed
Progress spinner