From: "Adam T. Bowen" <adamb@agitate.org.uk>
To: linux-admin@vger.kernel.org
Subject: Re: tar & samba file systems
Date: Fri, 16 Sep 2005 09:35:50 +0100 [thread overview]
Message-ID: <432A83E6.1070609@agitate.org.uk> (raw)
In-Reply-To: <0481A62A3E95A044AC20A1A45899645C06B02EF4@glc-mail-1.tessco.com>
Hi,
I have had similar behaviour from tar before when using -l (aka
--one-file-system). It was because I was doing something like:
tar -lcvf local_files.tar *
in /. The * of course is expanded to all the filenames in the directory
causing the command to look like:
tar -lcvf local_files.tar etc bin boot home ...
So even though, say, home is mounted on another partition to /, I am
stating the name of home on the command line and so it is included. Any
other non-local file systems encountered whilst traversing the
directories given will not be followed of course. Anyway, the solution
is to do:
tar -lcvf local_files.tar .
or just name the directories you want.
Hope that helps.
Adam
Callahan, Tom wrote:
> Or you can use --exclude to specify directories/files not to be backed
> up....
>
> Tom Callahan
>
> -----Original Message-----
> From: linux-admin-owner@vger.kernel.org
> [mailto:linux-admin-owner@vger.kernel.org] On Behalf Of jason
> Sent: Thursday, September 15, 2005 11:45 AM
> To: Luca Ferrari
> Cc: linux-admin@vger.kernel.org
> Subject: Re: tar & samba file systems
>
> --one-file-system and then just specify the mounts that you want to backup.
> ala /boot / /home
>
next prev parent reply other threads:[~2005-09-16 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 16:18 tar & samba file systems Callahan, Tom
2005-09-16 8:35 ` Adam T. Bowen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-15 16:03 Luca Ferrari
2005-09-15 15:45 ` jason
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=432A83E6.1070609@agitate.org.uk \
--to=adamb@agitate.org.uk \
--cc=linux-admin@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).