interesting.
i did:
mknod /dev/loop22 b 7 0
dd of=/tmp/archive if=/dev/zero bs=1024 count=65536
/sbin/losetup /dev/loop21 /tmp/archive
mkdir /archive
/sbin/mkfs /dev/loop22
mount /dev/loop22 /archive
cp -r /etc /archive
unmount /archive
cd /tmp
gzip archive
# it was just over a meg, gzipped
# ftp'd it to another machine..
# mknod'd, gunzipped, mounted
I knew it worked as emergency swap. but, backup could be a cinch.
I could make a set of backup files, one for each backup period.
operate on them as I would a standard partition, gzip and write
them to tape or cd.
am I missing some important part of the equation? is there something wrong with
my logic, do people already do this kinda thing all the time? do people not do
it because of something I'm missing?
On Wed, Aug 22, 2001 at 03:46:15PM -0700, Christopher Maujean wrote:
> Does anyone know how much of a performance hit one would take using a dd'd file
> via the loop device? is there any performance hit?
>
> ReverendTrance
>
>
> --
>
> Christopher Maujean IT Director Premierelink Communications
> [EMAIL PROTECTED] www.premierelink.com
> ----------------------------------------------------------------------
> GnuPg/PGP: 0x5DE74D38
> Fingerprint: 91D4 09FE 18D0 27C1 A857 0E45 F8A4 7858 5DE7 4D38
--
Christopher Maujean IT Director Premierelink Communications
[EMAIL PROTECTED] www.premierelink.com
----------------------------------------------------------------------
GnuPg/PGP: 0x5DE74D38
Fingerprint: 91D4 09FE 18D0 27C1 A857 0E45 F8A4 7858 5DE7 4D38
