Yesterday (Tuesday 28 February), Amazon Web Services, suffered a significant
outage.
Among the services impacted was GitHub.
AWS's S3 outage was so bad Amazon couldn't get into its own dashboard to warn
the world
https://www.theregister.co.uk/2017/03/01/aws_s3_outage/
Things were apparently
On Mar 1, 2017, at 11:42, William H. Magill wrote:
>
> Yesterday (Tuesday 28 February), Amazon Web Services, suffered a significant
> outage.
>
> Among the services impacted was GitHub.
Yes, that's correct. The MacPorts 2.4.1 installers on GitHub could not be
accessed during that time. The fil
> On Feb 28, 2017, at 9:54 PM, Ryan Schmidt wrote:
>
> I've just used Migration Assistant to migrate from one Sierra system to
> another. Since both systems are the same macOS version, I wasn't planning on
> following the Migration instructions in the wiki. (I was planning on
> rebuilding gmp,
On Wed, Mar 1, 2017 at 12:54 AM, Ryan Schmidt
wrote:
> I've just used Migration Assistant to migrate from one Sierra system to
> another. Since both systems are the same macOS version, I wasn't planning
> on following the Migration instructions in the wiki. (I was planning on
> rebuilding gmp, si
> On Mar 1, 2017, at 14:45, Jeremy Lavergne wrote:
>
> On 03/01/2017 12:54 AM, Ryan Schmidt wrote:
>> I've just used Migration Assistant to migrate from one Sierra system to
>> another. Since both systems are the same macOS version, I wasn't planning on
>> following the Migration instructions
> On Mar 1, 2017, at 17:09, Brandon Allbery wrote:
>
>
> On Wed, Mar 1, 2017 at 12:54 AM, Ryan Schmidt wrote:
> I've just used Migration Assistant to migrate from one Sierra system to
> another. Since both systems are the same macOS version, I wasn't planning on
> following the Migration ins
On Wed, Mar 1, 2017 at 6:10 PM, Ryan Schmidt
wrote:
> I'm not talking about an unusual case. I'm talking about the completely
> normal case that I expect all users will undergo when moving to a new
> computer: complete the setup assistant and use it to transfer data from
> their old computer. If
> On Mar 1, 2017, at 17:34, Brandon Allbery wrote:
>
>
> On Wed, Mar 1, 2017 at 6:10 PM, Ryan Schmidt wrote:
> I'm not talking about an unusual case. I'm talking about the completely
> normal case that I expect all users will undergo when moving to a new
> computer: complete the setup assist
> On Mar 1, 2017, at 17:07, Bradley Giesbrecht wrote:
>
>> On Feb 28, 2017, at 9:54 PM, Ryan Schmidt wrote:
>>
>> I've just used Migration Assistant to migrate from one Sierra system to
>> another. Since both systems are the same macOS version, I wasn't planning on
>> following the Migration
Yeah, I've never used the migration assistant since it has always caused me
heartache, but I bet we have a lot of users that do. It's an interesting
case. We should at least come up with advice as to how to get rid of all
this crap and start fresh.
—Mark
___
Mark E. Anderson
I think the "best" course of action for you is to delete all the users and
then follow the migration instructions. But yeah, there has to be some way
to undo this damage programmatically.
—Mark
___
Mark E. Anderson
On Wed, Mar 1, 2017 at 6:39 PM, Ryan Schmidt
wrote:
>
> > O
> On Mar 1, 2017, at 3:39 PM, Ryan Schmidt wrote:
>
>> On Mar 1, 2017, at 17:07, Bradley Giesbrecht wrote:
>>
>>> On Feb 28, 2017, at 9:54 PM, Ryan Schmidt wrote:
>>>
>>> I've just used Migration Assistant to migrate from one Sierra system to
>>> another. Since both systems are the same macO
On Mar 1, 2017, at 18:04, Mark Anderson wrote:
>
> I think the "best" course of action for you is to delete all the users and
> then follow the migration instructions. But yeah, there has to be some way to
> undo this damage programmatically.
I don't believe following the migration instruction
On Wed, Mar 1, 2017 at 7:13 PM, Ryan Schmidt
wrote:
> I don't believe following the migration instructions will do anything
> useful. It's for moving to a different CPU or OS version; I'm not doing
> either.
In fact only one change is needed: you do some of the early steps on the
origin system
> On Mar 1, 2017, at 4:13 PM, Ryan Schmidt wrote:
>
> On Mar 1, 2017, at 18:04, Mark Anderson wrote:
>>
>> I think the "best" course of action for you is to delete all the users and
>> then follow the migration instructions. But yeah, there has to be some way
>> to undo this damage programmat
15 matches
Mail list logo
