Path: utzoo!attcan!uunet!mcvax!unido!sbsvax!greim
From: greim@sbsvax.UUCP (Michael Greim)
Newsgroups: comp.unix.wizards
Subject: Re: relative pathname question!
Summary: (none)
Message-ID: <605@sbsvax.UUCP>
Date: 22 Aug 88 09:07:04 GMT
References: <1670003@hpcilzb.HP.COM< <5762@super.upenn.edu< <5103@rpp386.UUCP< <20437@watmath.waterloo.edu<
Organization: Universitaet des Saarlandes, Saarbruecken, West Germany
Lines: 32

In article <20437@watmath.waterloo.edu<, sahayman@watmath.waterloo.edu (Steve Hayman) writes:
< Sorry to leap into this discussion so late.  Anyway, in 
< article <591@sbsvax.UUCP< greim@sbsvax.UUCP suggests
< using a little filter program to remove leading /'s from
< tar pathnames: (i.e.  filter <the-tape | tar xf -)
< 
[stuff deleted]
< Good idea, but isn't that kind of dangerous?  What happens when you have
< a data file that happens to have a '/' and a '\0' in those
< positions?    You don't want those moved around, you only
< want to diddle tar header blocks.
Yes, I wondered about that too. But I decided to worry about it only
after something went wrong. Nothing has so far.
I just tested the behaviour. Yes, it is wrong. Maybe I was just lucky
so far :-)
< 
< A program to do this safely really needs to know a little more
< about tar-format - fiddle the header blocks only, not the
< data blocks.   I think I have a version that will do that,
< I'll send it off to comp.sources.misc.
Ok. Am waiting for it.
< 
< ..Steve Hayman
	-mg
-- 
UUCP:  ...!uunet!unido!sbsvax!greim   | Michael T. Greim
       or greim@sbsvax.UUCP           | Universitaet des Saarlandes
CSNET: greim%sbsvax.uucp@Germany.CSnet| FB 10 - Informatik (Dept. of CS)
ARPA:  greim%sbsvax.uucp@uunet.UU.NET | Bau 36, Im Stadtwald 15
voice: +49 681 302 2434               | D-6600 Saarbruecken 11, West Germany

# include <disclaimers/std.h>