-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sun, Oracle save Microsoftâs Pink after Danger data disaster
,----[ Quote ]
| âIt will take several days to actually get
| the database back up,â the source noted,
| echoing earlier reports that indicated that
| it took 6 days just to create a normal full
| backup of the data. The time and storage
| resources involved in backing up the
| tremendous amount of data were cited as the
| reason why Microsoftâs Roz Ho reportedly
| instructed Danger employees to proceed with
| work without the full backup in place over
| their objections, after sources say she was
| assured by Hitachi that a full backup was
| not necessary.
|
| Salvaging the damaged data storage without a
| real backup in place takes even longer, the
| Sun storage expert explained. âThe first
| thing to do is wheel in a big pile of new
| disk space, and copy the individual disks so
| there is a raw backup. This is like making a
| copy of a jigsaw puzzle one piece at a time.
| Then they would assemble the puzzle using
| the copied pieces, in case any pieces need
| to be re-made from the original.
`----
http://www.roughlydrafted.com/2009/10/21/sun-oracle-save-microsofts-pink-after-danger-data-disaster/
Reasons I Believe the Community Should Support the Oracle-Sun Deal
,----[ Quote ]
| Monty Widenius has posted a press release,
| urging Oracle to sell MySQL to a third
| party, and there is a link to the materials
| that he and Florian Mueller, who is working
| with him, provided to the EU Commission,
| which appears to have influenced it to delay
| approval. I've been reading all I can find
| on this topic, and I'd like to tell you why
| I think the community should support the
| Oracle deal. The most important reason is
| that opponents are trashing the GPL [PDF]
| and calling it a source of "infection" in
| their FUD submission to the EU Commission.
|
| [...]
|
| Update: I see Matt Asay has jumped on board
| the antiGPL FUD too. Folks, there is no
| difference between Sun owning MySQL and
| Oracle, as far as forking rights. Duh. What
| is this? An elaborate Microsoft production
| by proxy?
|
| [...]
|
| Get the picture? He makes a list of who
| would have the money to buy MySQL. Guess who
| is number one on the list? Microsoft.
`----
http://www.groklaw.net/article.php?story=20091021164738392
Recent:
Microsoft's Sidekick restoration turns into farce
,----[ Quote ]
| Microsoft played spot the difference over the
| weekend with statements on Saturday and Sunday
| that hinted at âsteady progressâ for the
| recovery of data its Danger subsidiary lost for
| many Sidekick customers.
|
| [...]
|
| The fallout was huge and Microsoft scurried to
| paint a more optimistic picture for Dangerâs
| unhappy customers, at the same time some punters
| threatened legal action against Redmond and T-
| Mobile.
`----
http://www.theregister.co.uk/2009/10/19/microsoft_danger_sidekick_where_art_thou_data/
Document: Microsoft, T-Mobile sued over Sidekick data outage
,----[ Quote ]
| Here's a copy of one (PDF, 21 pages), filed on
| behalf of Maureen Thompson, a Georgia resident who
| experienced a "complete and catastrophic loss of
| all data on her daughter's Sidekick." The suit
| claims that the architecture of Danger's Sidekick
| data system contributed significantly to the
| problem.
`----
http://www.techflash.com/seattle/2009/10/full_text_suit_against_microsoft_t-mobile_over_sidekick.html?ana=from_rss
Sidekick users share their horror stories
,----[ Quote ]
| Now it seems that all my information may be lost for good. It's
| infuriating. Especially when they could have been more precise in
| their text messages and let us users know what actions may be damaging
| to the livelihood of our stored data!!
|
| I hope you continue to investigate this issue. And I am keeping my
| ears open for any legal action being taken against T-mobile/MS/Danger
| for this horrible oversight.
`----
http://news.cnet.com/8301-13860_3-10372826-56.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkrgagAACgkQU4xAY3RXLo6yCwCeMzK2TIa7CQWPzXotgI8LDcpw
Jx0AoIIvkEARApOqZP4mPwUvdsgfbD03
=b4Of
-----END PGP SIGNATURE-----
|
|
