On Sep 30, 2011, at 13:59, erik quanstrom quans...@labs.coraid.com wrote:
backup:
1. power down mac. remove hard drive.
2. stuff drive as one gigantic file into venti.
restore:
1. copy your backup onto drive
2. install hard drive. power up mac.
In principal, that's roughly what
if you (slash) could just grab the atazz binary
(ftp://ftp.quanstro.net/other/8.atazz)
and send me the output of
echo 'identify device' | 8.atazz -r [2=] /dev/sdE0 /tmp/somefile
that would be great. thanks!
Here you go. Again, sdE0 is the old drive, sdE1 is the new one.
slash
On Sat Oct 1 06:37:52 EDT 2011, slash.9f...@gmail.com wrote:
if you (slash) could just grab the atazz binary
(ftp://ftp.quanstro.net/other/8.atazz)
and send me the output of
echo 'identify device' | 8.atazz -r [2=] /dev/sdE0 /tmp/somefile
that would be great. thanks!
Here
On Fri, 30 Sep 2011 13:59:00 -0400
erik quanstrom quans...@labs.coraid.com wrote:
backup:
1. power down mac. remove hard drive.
2. stuff drive as one gigantic file into venti.
restore:
1. copy your backup onto drive
2. install hard drive. power up mac.
ROFL! What I guess you don't
On Fri, 30 Sep 2011 13:50:23 -0600
Latchesar Ionkov lu...@ionkov.net wrote:
At work, I use Time Machine to a Linux server.
You can do this? I tried to use a second internal drive for Time
Machine but it claimed Cannot find wifi and refused to proceed. (O.o)
This was with Leopard; maybe it only
echo 'identify device' | 8.atazz -r /dev/sdE0 /tmp/somefile
would be better
Here goes.
sdE0.out
Description: Binary data
sdE1.out
Description: Binary data
erik quanstrom quans...@labs.coraid.com wrote:
backup:
1. power down mac. remove hard drive.
2. stuff drive as one gigantic file into venti.
restore:
1. copy your backup onto drive
2. install hard drive. power up mac.
ROFL! What I guess you don't know is you can more or
since i don't have one of these drives, i wrote a little
program to dig into the ident block.
a small aside. ata disks have two sector sizes. (groan.)
there's the logical sector size and the physical sector size.
by default they are both 512. the ears drive sets the
set logical sector size to
i forgot the interesting part of the program output
word 106 6003 [valid=1]
multiple log/phys? 1
log/phys 8
logical sector size 0 [valid=0]
the logical sector size is by default 512, so the fact
the logical sector size is invalid means it's 512.
- erik
When my home directory is less than 2 gigabytes in size, I use
dump9660 from Plan 9 port (or a standalone relative).
Otherwise I rsync my home to a DragonFly BSD system and take a HAMMER snapshot.
-- vs
Just curious what 9fans use, for home and/or work, to backup their macs.
At work everything is FreeBSD and backups are not my worry.
At home I use rsync to keep a copy of my home directory at work,
and just reinstall everything else. So far I've had to do that
once. Huge files which can be
ROFL! What I guess you don't know is you can more or less do this
without disassembling the Mac. Boot the Mac with the right keys pressed
(I forget which) and it will emulate a Firewire drive.
ROFL! What you don't know is (most) Macs no longer have Firewire
interfaces.
On Oct 1, 2011, at 14:21 , Lyndon Nerenberg (VE6BBM/VE7TFX) wrote:
What you don't know is (most) Macs no longer have Firewire interfaces.
This works again with the newest Macs with Thunderbolt.
Lest this just be even further off topic, the relevant point here is that beyond
erik's unless your
Dear all,
the dealine for IWP9 WIP is here, but we encourage
everyone with WIP to submit to IWP9. We will still wait
a few days for WIP submissions.
hth
1. I liked the distinction noted between 'backups' and 'archives'.
2. Cloning a drive is of limited use on any system.
Isn't future proof, doesn't scale, doesn't allow for disk size
changes or hardware changes.
Is a necessary part of an Admin Toolkit, but only for very
particular
2. Cloning a drive is of limited use on any system.
Isn't future proof, doesn't scale, doesn't allow for disk size
changes or hardware changes.
Is a necessary part of an Admin Toolkit, but only for very
particular situations.
really?
what do you mean by doesn't allow for hardware
w.r.t. Disk Cloning.
you are conflating multiple issues:
- hardware disk imaging
- managing NAS appliances
- handling VM images
I agree with you.
Cloning drives in low-end NAS appliances is quick, simple and effective.
I had a lot of fun a year ago documenting how to clone config and data
You are right that cloning disk *images* is an essential part of
using/managing VM's.
Don't conflate that with cloning physical disks.
why not? this reminds me of the mem $x ... with a computer.
i think we've gotten to the point where we keep hearing $x ... with v12n.
and why make such a big
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.
19 matches
Mail list logo
