Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!apple!snorkelwacker.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!jik From: jik@athena.mit.edu (Jonathan I. Kamens) Newsgroups: comp.unix.internals Subject: Re: more uses for mode 000 (was: Summary: What SUID, SGID...) Message-ID: <1991Feb11.233340.19804@athena.mit.edu> Date: 11 Feb 91 23:33:40 GMT References: <1991Feb4.124123.25558@gpu.utcs.utoronto.ca> Sender: news@athena.mit.edu (News system) Organization: Massachusetts Institute of Technology Lines: 21 In article , clark@cme.nist.gov (Steve Clark) writes: |> Ooops. I made a mistaken generalization, it seems. Since Gnu tar |> does the obvious thing with the `-' filename after -X, I assumed SunOS |> tar and, by extension, others would as well (and a rather unconscious |> assumption it was, I might add). I was wrong. I hope this doesn't |> set off two more weeks of "my tar does[n't]" messages ... Um, I wasn't just talking about feeding names to the -X option via stdin. I was talking about the -X option in general. BSD 4.3, Ultrix 3.1 and A/UX all seem to be lacking this option. For those of you who are curious about what we're talking about here and don't have a -X option on their version of tar :-), what it does is reads a list of regular expressions from the specified file and ignore and files which match any of those regular expressions. -- Jonathan Kamens USnail: MIT Project Athena 11 Ashford Terrace jik@Athena.MIT.EDU Allston, MA 02134 Office: 617-253-8085 Home: 617-782-0710