Re: tar problem

At Wed, 12 Jun 2024 20:16:06 +0100 Richard Kettlewell <invalid@invalid.invalid> wrote:

 
Ralf Fassel <ralfixx@gmx.de> writes:

* db <dieterhansbritz@gmail.com>
| ~/bin> tarx ../tarfiles/NumNotes       
| tar (child): ../tarfiles/NumNotes: Cannot open: No such file or directory
--<snip-snip>--
| ~/bin> ls ../tarfiles/Num*
| ../tarfiles/NumNotes.tar.gz

>

| The last line proves that it's lying.
>
Why do you expect that if you tell tar to use a file named 'NumNotes'
that it should use a file named 'NumNotes.tar.gz' instead?

 
The script they quoted does "tar -xf $1.tar.gz", i.e. it adds .tar.gz.
 
Presumably the script they are actually running is different.
 

Wondering: is there a space after "$1" (eg between that and the dot). Also: is
the script file a purely ASCII text file or does it contain UTF-8 characters --
is the dot really an ASCII period character or something else that "looks"
like a period. Bash won't like it if it is not an ASCII period and won't like
white space where it does not belong. Note the lack of "#!/bin/bash" at the
start of the file could also be causing problems.

--
Robert Heller             -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software        -- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
heller@deepsoft.com       -- Webhosting Services