public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Backing up entire system with tar
Date: Mon, 12 Nov 2001 00:33:58 -0500	[thread overview]
Message-ID: <001601c16b3b$a12b5a60$20128fd1@enterprise> (raw)
In-Reply-To: <000c01c16b2d$bd3a4ee0$7f7ef59b@essex.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

Hi, I use a dos/Windows program called Image cast which does the job nicely.
It makes an image of your drive as it is, and then can be sent to another computer on the network, to another partition, or be burned onto a cd.
Haven't tried it with ext3, but it works good with ext2.

  ----- Original Message ----- 
  From: Saqib Shaikh 
  To: speakup@braille.uwo.ca ; blinux-newbie@braille.uwo.ca 
  Sent: Sunday, November 11, 2001 10:54 PM
  Subject: Backing up entire system with tar


  Hi,

  I keep on finding myself wanting to play with new things etc.  Instead of having to reinstall my system ever time I end up breaking something (sorry, I'm a perfectionist who feels my system must be perfect!), can I just back up my entire system with tar.

  The first question is: what is the syntax for this?

  Secondly, where will the tar file go.  What I mean is, if the command were:
  tar cf /* ./backup.tar
  then won't the program get into a loop since I'm backing up the current directory, but also continually writing data to this directory?  Equally, if I mount a second partition under /mnt and save the tar file to /mnt/backup.tar won't it try and backup the mounted partition also?

  I'd be greatful if anyone has the answer to my question.

  Thanks, Saqib


[-- Attachment #2: Type: text/html, Size: 3078 bytes --]

  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Saqib Shaikh
 ` Thomas Ward [this message]
   ` Saqib Shaikh
 ` Kerry Hoath
   ` Jason
 Dawes, Stephen

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='001601c16b3b$a12b5a60$20128fd1@enterprise' \
    --to=tward@bright.net \
    --cc=speakup@braille.uwo.ca \
    /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).