From: "Iruatã Souza" <iru.muzgo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] OT: how do 9fans backup their Mac(book)?
Date: Sun, 2 Oct 2011 09:38:21 -0300 [thread overview]
Message-ID: <CABJnqBQxhUNDj_QHm7FyfKR8K-7W5aX+vt+wObCqzqGv=Zx9Ew@mail.gmail.com> (raw)
In-Reply-To: <4E87D563.7070304@gmail.com>
On Sun, Oct 2, 2011 at 12:07 AM, steve jenkin <stevej098@gmail.com> wrote:
> erik quanstrom wrote on 2/10/11 1:37 PM:
>> it's all block storage.
>>
>
> Nope.
> In the same way that RAM is finely differentiated with many
> incompatibilities & 'gotchas'.
> It's not "all memory".
>
> Go away and actually *do* the thing you are suggesting, then tell us how
> you went.
>
> Get 3-4 macbooks. Preferably a range of machines: old to new.
> Get 8-12 replacement drives, differing ages, capacities and types.
>
> Do your "just pull the drive out and copy it" multiple times on each
> machine.
> To be valid, you have to swap drives between machines and have then work
> properly.
> No cheating, fully reconstruct machines between tests.
> Wearing out screws/fittings is a classic weakness on single-assembly
> designs.
>
> Quicker solution:
> point us to a web-page where your suggestion is done, even once.
> Bonus for a webpage where someone does exactly what you're suggesting,
> multiple machines, many drive types.
>
> --
> Steve Jenkin, Info Tech, Systems and Design Specialist.
> 0412 786 915 (+61 412 786 915)
> PO Box 48, Kippax ACT 2615, AUSTRALIA
>
> stevej098@gmail.com http://members.tip.net.au/~sjenkin
>
>
>
you know so much, and yet you failed to read that this is not a mac list.
next prev parent reply other threads:[~2011-10-02 12:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 15:19 Axel Belinfante
2011-09-30 15:53 ` Anthony Sorace
2011-09-30 17:43 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-09-30 17:59 ` erik quanstrom
2011-09-30 19:21 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-09-30 19:42 ` erik quanstrom
2011-09-30 19:45 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-09-30 19:53 ` erik quanstrom
2011-10-01 8:21 ` Anthony Sorace
2011-10-01 15:14 ` Ethan Grammatikidis
2011-10-01 15:24 ` erik quanstrom
2011-10-01 15:48 ` Ethan Grammatikidis
2011-10-01 16:49 ` Venkatesh Srinivas
2011-10-01 18:21 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-10-01 18:29 ` Anthony Sorace
2011-10-02 15:26 ` Ethan Grammatikidis
2011-11-03 20:54 ` Michaelian Ennis
[not found] ` <CAAQydVjZ42C-GTEFT7E2t=dCQ35fvHzqjSYx9a3o+8v+5D1vfA@mail.gmail.c>
2011-11-03 20:57 ` erik quanstrom
2011-11-01 18:15 ` smiley
2011-11-01 18:57 ` Anthony Sorace
2011-09-30 19:50 ` Latchesar Ionkov
2011-10-01 15:21 ` Ethan Grammatikidis
2011-09-30 20:01 ` Francisco J Ballesteros
2011-09-30 21:15 ` Bakul Shah
2011-10-01 17:22 ` John Stalker
2011-10-02 0:35 ` steve jenkin
2011-10-02 1:28 ` erik quanstrom
2011-10-02 2:28 ` steve jenkin
2011-10-02 2:37 ` erik quanstrom
2011-10-02 3:07 ` steve jenkin
2011-10-02 12:38 ` Iruatã Souza [this message]
2011-10-03 3:57 ` steve jenkin
2011-10-03 4:02 ` erik quanstrom
2011-10-02 13:30 ` Salman Aljammaz
2011-10-03 3:47 ` steve jenkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABJnqBQxhUNDj_QHm7FyfKR8K-7W5aX+vt+wObCqzqGv=Zx9Ew@mail.gmail.com' \
--to=iru.muzgo@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).