public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joerg.Schilling@fokus.fraunhofer.de (Joerg Schilling)
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Best way to copy /* ?
Date: Wed, 29 Dec 2010 00:36:29 +0100	[thread overview]
Message-ID: <4d1a747d.b9ziR/SWhk1oijOR%Joerg.Schilling@fokus.fraunhofer.de> (raw)
In-Reply-To: <20101228223353.3dc949d8@digimed.co.uk>

Neil Bothwick <neil@digimed.co.uk> wrote:

> On Tue, 28 Dec 2010 17:26:16 +0100, Joerg Schilling wrote:
>
> > > 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.
>
> You are right. I was referring to the --one-file-system, which I thought
> had -l as the short option, but apparently not. Or has that changed in
> the last couple of years?

Tar did not change it's behavior with respect to -l during the past 31 years.

On Linux, there is frequently gtar installed as tar and gtar is not respecting 
standards. Gtar in previous times was e.g. in conflict with the standard 
regarding to -l. Aprox. 10 years ago, I files a bug report against gtar for 
this standard deviation and it seems that they fixed this bug.

Jörg

-- 
 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de                (uni)  
       joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily



  parent reply	other threads:[~2010-12-28 23:38 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
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 [this message]
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=4d1a747d.b9ziR/SWhk1oijOR%Joerg.Schilling@fokus.fraunhofer.de \
    --to=joerg.schilling@fokus.fraunhofer.de \
    --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