[PLUG] Backup over network...

[Michael C. Robinson]

On Sat, 2010-05-15 at 19:15 -0700, drew wymore wrote:
> On Sat, May 15, 2010 at 7:00 PM, Someone <plug_1 at robinson-west.com> wrote:
> > My dad has one of those fancy quad core 64 bit Windows 7 laptops.  I
> > have a Pentium III optimized LFS system which I can back up Windows and
> > Linux systems with as long as the computer is a Pentium III or IV.  Will
> > a Pentium III Linux kernel boot a quad core computer???
> >
> > I am using dd to dump entire hard drives, this is space intensive though
> > and I end up backing up fragmentation.  Is there a better way that is as
> > powerful as hard drive imaging?  Using dd is brute forcing the problem,
> > but this is a safe way to back a system up.
> >
> > If I need a 64 bit Linux kernel and a 64 bit optimized NFS mountable
> > Linux filesystem, how do I produce those on a 32 bit computer?  Is it
> > possible to produce an Apple G3 compatible Linux system on a PIII based
> > Linux server?  How about network booting a PC164 Alpha system?
> >
> > In general, I'm curious how to trick the Linux kernel source into
> > compiling on one computer for a totally different kind of computer.
> >
> > _______________________________________________
> > PLUG mailing list
> > PLUG at lists.pdxlinux.org
> > http://lists.pdxlinux.org/mailman/listinfo/plug
> >
> 
> No offense meant by using lmgtfy

What does lmgtfy mean?  

I want to be able to include my Dad's laptop in my network based backup
system which is made up of a network bootable Linux system and a large
backup area.  For obvious reasons, installing Linux on my Dad's laptop
even just to export that installation to a server is not a realistic
option.

Short of talking Dad into buying a second internal hard drive for his
computer and taking the Windows 7 drive out temporarily so I can install
64 bit Linux, how am I going to put together a 64 bit Linux system
without a 64 bit quad core computer?  I'm sure I'm not the only person
who cannot realistically buy a quad core computer just to facilitate
installing 64 bit Linux to it to then export that system over a network.
What if I had a really expensive mainframe computer with Windows on it
and I couldn't justify buying another one just in case?  Heterogeneous
Linux/Windows networks are common where the difficulty of getting all
the machines backed up is nothing new.

This problem isn't so far out where I would appreciate it if people
wouldn't resort to vague and probably colorful metaphors.