From: "jamesc@reliant-data.com" <jamesc@reliant-data.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Moving linux system to another partition
Date: Fri, 08 Jun 2007 19:43:21 -0500 [thread overview]
Message-ID: <52650.1181349801@reliant-data.com> (raw)
On Fri Jun 8 18:25 , Albert Hopkins <marduk@gentoo.org> sent:
>On Fri, 2007-06-08 at 19:01 -0500, jamesc@reliant-data.com wrote:
>> On Fri Jun 8 16:38 , Dale dalek@exceedtech.net> sent:
>
>>
>> Yeah, that's me, I do exactly the same until you issue the cp command where I do:
>> $>cd /mnt/oldstuff && tar cvjpf /pathtosomewhere/mystuff.tbz ./
>> and then extract to the new directory. I do this out of habit mostly and, yes,
>> it is a useless step unless you want to store a copy somewhere for whatever
reason...
>>
>> --James
>
>The one thing I mentioned is that I actually pipe tar to tar (tar -c ...
>| tar -x ...) which seems even more useless, but as I said I'm used to
>doing some things out of habit. Then I thought about why: the '-a' flag
>is not available on all *nices... I believe it's a GNU extension. So I
>probably got used to using the tar trick on a non-GNU system and got
>used to it because it works whether I'm using Linux or not. But if
>you're on a Linux system (that has rsync installed) then rsync is
>probably the nicer option. It's got even more options than GNU's cp. I
>actually 'alias cp="rsync"' on my Gentoo systems.
Ha. This is a good day. I have to laugh at myself for not utilizing rsync more;
for the last few years I've just been using rsync to backup/restore my /home and
key config files to my fileserver (while at home). Never even considered using
it for local operations. Nice. I have the habit, also, of using the most basic
stuff since I'm usually on all manner of UNIX{like} boxes during the day.
Thanks,
--James
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2007-06-09 0:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 0:43 jamesc [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-09 0:18 [gentoo-user] Moving linux system to another partition jamesc
2007-06-09 0:01 jamesc
2007-06-09 0:25 ` Albert Hopkins
2007-06-09 8:14 ` Florian Philipp
2007-06-08 16:52 burlingk
2007-06-08 16:40 burlingk
2007-06-08 15:05 Aleksey Kunitskiy
2007-06-08 15:18 ` Hemmann, Volker Armin
2007-06-08 15:48 ` Alan McKinnon
2007-06-08 15:59 ` Albert Hopkins
2007-06-08 16:21 ` Aleksey Kunitskiy
2007-06-08 16:43 ` Tim Allingham
2007-06-08 18:52 ` Hans-Werner Hilse
2007-06-09 18:25 ` Tim Allingham
2007-06-11 7:24 ` Mick
2007-06-11 8:58 ` Hans-Werner Hilse
2007-06-11 15:18 ` Randy Barlow
2007-06-11 14:54 ` Alan McKinnon
2007-06-11 15:00 ` Hans-Werner Hilse
2007-06-08 22:38 ` Dale
[not found] ` <200706081839.07324.alexey.kv@gmail.com>
2007-06-08 15:59 ` Mauro Faccenda
2007-06-08 15:54 ` Albert Hopkins
2007-06-08 16:01 ` Mauro Faccenda
2007-06-08 18:09 ` Benno Schulenberg
2007-06-09 8:45 ` Vladimir Rusinov
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=52650.1181349801@reliant-data.com \
--to=jamesc@reliant-data.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