public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Best way to copy /* ?
Date: Tue, 28 Dec 2010 18:41:59 +0000	[thread overview]
Message-ID: <201012281842.13216.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4d1a0fa8.TVuQcBiVBzUKO5TQ%Joerg.Schilling@fokus.fraunhofer.de>

[-- Attachment #1: Type: Text/Plain, Size: 924 bytes --]

On Tuesday 28 December 2010 16:26:16 Joerg Schilling wrote:
> Neil Bothwick <neil@digimed.co.uk> wrote:
> > On Tue, 28 Dec 2010 00:02:31 -0500, Mike Edenfield wrote:
> > > tar -C /old cpf - | tar -C /new xvpf -
> > > 
> > > You'll probably not want to do the entire / in a single go,
> > > since /proc, /sys, and /dev (at least) should be skipped.
> > 
> > Which can be done with the -l option.
> 
> You are mistaken: The -l option causes tar to warn if not all hars links to
> a file could not be resolved.

I often use this with a LiveCD:

cd /home
tar --exclude File1 --exclude Dir1 -lcpvSf - . | (cd /mnt/new_partition; tar -
xpvf - )

or something like this with star:

star -copy -p -xdot -xattr -H=exustar -sparse -M -C /home . /mnt/new_partition

(You can use -V -pat=File1 to exclude files or directories with star, use the 
-M option to avoid following mount points).
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-12-28 18:43 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 15:20 [gentoo-user] Best way to copy /* ? Marc Blumentritt
2010-12-27 15:20 ` Etaoin Shrdlu
2010-12-27 16:37   ` Neil Bothwick
2010-12-27 16:52     ` Mark Knecht
2010-12-27 17:05       ` [gentoo-user] " Remy Blank
2010-12-27 20:26         ` Marc Blumentritt
2010-12-27 21:23           ` Remy Blank
2010-12-28  8:56             ` Marc Blumentritt
2010-12-28  9:18               ` Remy Blank
2010-12-28 10:49                 ` Neil Bothwick
2010-12-27 15:30 ` [gentoo-user] " ich bins
2010-12-27 15:34 ` [gentoo-user] " Lubos Kolouch
2010-12-27 15:41 ` [gentoo-user] " Jarry
2010-12-27 15:47 ` Dale
2010-12-29 17:03   ` Peter Humphrey
2010-12-29 17:14     ` Maciej Grela
2010-12-29 17:43       ` Paul Hartman
2010-12-29 17:50     ` Alex Schuster
2010-12-29 18:30       ` Peter Humphrey
2010-12-29 18:41         ` Alex Schuster
2010-12-29 19:16           ` Mick
2010-12-29 20:24             ` Stefan G. Weichinger
2010-12-27 17:27 ` Volker Armin Hemmann
2010-12-27 17:38   ` Mark Knecht
2010-12-27 17:51     ` Volker Armin Hemmann
2010-12-27 18:01       ` Mark Knecht
2010-12-27 17:45   ` Dale
2010-12-27 18:45     ` Neil Bothwick
2010-12-27 21:35       ` Dale
2010-12-28  5:02 ` Mike Edenfield
2010-12-28 13:20   ` Alex Schuster
2010-12-28 13:32   ` Neil Bothwick
2010-12-28 16:26     ` Joerg Schilling
2010-12-28 18:41       ` Mick [this message]
2010-12-29 15:38         ` Joerg Schilling
2010-12-29 16:17           ` Mick
2010-12-28 22:33       ` Neil Bothwick
2010-12-28 23:16         ` Mick
2010-12-28 23:36         ` Joerg Schilling
2010-12-29  0:51           ` Alex Schuster
2010-12-28 23:08       ` Alex Schuster
2010-12-29 14:40 ` [gentoo-user] Re: Best way to copy /* ? [SOLVED] Marc Blumentritt

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=201012281842.13216.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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