 |
Add
Remote Backup Services to your existing business, or start
a profitable Internet-based online backup service for
a high profit recurring revenue stream.
Click here for more info. |
WPW IT Dicsussion Posts |
US
Backs Microsoft In Antitrust Fight
Microsoft has long complained that antitrust regulators
with the European Union have been holding back information
related to the investigation, and US...
DW and DB connections?
I am trying to set up Dreamweaver to work with my
DB. I am using the phpdev build of PHP, MySQL and
Apache, and for the life of me I cannot figure out
what I...
Internet
Explorer Mystery
Not sure if this is the right place to post this
question, but I was wondering if anyone can tell
me what the following means: When I enter my url
into IE as...
|
|
|
Top Web News |
Microsoft
Virtually Supporting Linux
The Windows maker announced at the LinuxWorld Conference
& Expo it would make the Microsoft Virtual Server
2005 R2 available at no charge to customers.
Google Subpoena Just “Tip Of the Iceberg”
The US Department of Justice harassed more than
the major search engines for information to support
its case for the Child Online Protection Act.
A
Legal RSS Feed?
Law.com released its own RSS reader on Monday, named
NewsPoint. A free download, the application will
come with preloaded content from Law.com and the
Law.com...
|
|
|
04.05.06
Tar Wild Card Interpretation
 By
A.P. Lawrence
I had this email earlier this week:
I am trying to restore a file "\GL050". I can see it on the tape listing,
but I can't get edge to find it. I have tried listing it the
following ways: ./usr1/file/\\GL050
./usr1/file/\GL050
And I've tried it in quotes. I also put the file path in a filelist and tried to use edge that way. It just will not find it. Note that she is using Microlite Edge, but that's really unimportant: you can observe the problem with tar.
$ cd /tmp
$ mkdir foo
$ touch "foo/\\filewithbackslash"
$ ls foo
\filewithbackslash
$ tar cvf test.tar foo
foo/
foo/\\filewithbackslash
We know have a tar file (test.tar) containing the problem file. Let's try restoring it as she did:
$ tar xvf test.tar foo/\\filewithbackslash
tar: foo/\filewithbackslash: Not found in archive
tar: Error exit delayed from previous errors
$ tar xvf test.tar "foo/\\filewithbackslash"
tar: foo/\filewithbackslash: Not found in archive
tar: Error exit delayed from previous errors
Our wildcards look like they should work:
Add
Remote Backup Services to your existing business, or start
a profitable Internet-based online backup service for
a high profit recurring revenue stream.
Click here for more info. |
|
$ echo "foo/\\filewithbackslash"
foo/\filewithbackslash
$ echo foo/\\filewithbackslash
foo/\filewithbackslash
At this point you may be saying "Are you crazy? Both those tar's work - with or without the quotes!"
And someone else would retort "Are YOU nuts?? No they don't!"
Who is nuts or not nuts has to be decided by some other method. Whether or not your tar happily works or complains as shown above simply depends upon how it handles wildcards and whether or not it gets to see them.
The complaining tar above identifies itself as "(GNU tar) 1.14" and was executed on Mac OS X 10.4.5. A non-complaining tar on a RedHat Linux systems says that it is "(GNU tar) 1.13.25".
Isn't that odd: the newer version seems to work "incorrectly". There's an interesting section of the "info tar" for the 1.13.25 version:
Click
to read the full article.
About the Author:
A.P. Lawrence provides SCO
Unix and Linux consulting services.
|
