-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 06 Nov 2002 21:59:56 -0600
begin steve rader <[EMAIL PROTECTED]> spewed forth:
> > > begin steve rader <[EMAIL PROTECTED]> spewed forth:
> > > Here's another reason to avoid dd'ing whole partitions: since
> > > it copies the actual file system, it forces the destination
> > > file system to be exactly the same size as the source.
> > >
> > > In other words, if you dd a 2 gig file system into a 4 gig
> > > partition then you end up with a 2 gig file system (and thus
> > > 2 gig of disk space "disappears!")
> > >
> > > I now think Roger Oberholtzer is right:
> > >
> > > cd source; find . -depth -print0 | cpio --null -pvd destination
> > >
> > > appears to be the best choice for copying directory trees and
> > > file systems.
>
> > From: "David A. Bandel"
> > you'll want to avoid copying /proc and probably even /tmp. Look
> > around because there might be others you won't want to copy. Just be
> > sure to exclude them.
True -- think of /proc like a window into the kernel.
Perhaps I misunderstand how you're doing this, but if the filesystem is
running, while these files and directories are ephemeral and don't exist
on disk, they can be copied. If they are restored onto a filesystem at
the very minimum they'll take up space, but restored onto a running
filesystem they can crash the system or at least produce some very
interesting results. I've never tried copying them then booting into the
filesystem they were copied to so I have no idea what the outcome would
be.
Ciao,
David A. Bandel
- --
Focus on the dream, not the competition.
-- Nemesis Racing Team motto
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9ykbQ3uVcotqGMQcRApHnAKCeYgOqLOPt5D1CdZ6H4wB4EeOZAgCfTTQn
Uu/u5J0T+d89Z8Oxs2yQtxc=
=kQYG
-----END PGP SIGNATURE-----
_______________________________________________
Linux-users mailing list
[EMAIL PROTECTED]
Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
