From: Mike Gorse <mgorse@mgorse.dhs.org>
To: blinux-list@redhat.com
Subject: Re: Imaging the hard drive?
Date: Tue, 19 Mar 2002 09:20:00 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0203190917410.8968-100000@mgorse.dhs.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0203180952470.2581-100000@toccata.rednote.net>
Janina, I am not sure that that would work well for what he wants to do.
I would not trust dd to make an image of a file system for the purpose of
transporting it to another computer which may have a different hard disk
and a Linux partition of a different size. Tar should work well, however,
so long as you pass it parameters to exclude anything that you do not want
copied (ie, /proc).
-- Michael Gorse / AIM:linvortex / http://mgorse.home.dhs.org --
On Mon, 18 Mar 2002, Janina Sajka wrote:
> Imaging in linux is the easiest imaging you will ever do.
>
> Use the dd command partition by partition as follows:
>
k
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Octavian Rasnita
` Janina Sajka
` Mike Gorse [this message]
` Willem van der Walt<vdwaltw@health.gov.za>
` Janina Sajka
` Jude DaShiell
` John
` Anders Holmberg
` Peter Toneby
` Anders Holmberg
` Peter Toneby
` Octavian Rasnita
` Anders Holmberg
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=Pine.LNX.4.44.0203190917410.8968-100000@mgorse.dhs.org \
--to=mgorse@mgorse.dhs.org \
--cc=blinux-list@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).