Re: tar problem

On Sun, 09 Jun 2024 19:12:52 +0000, Robert Heller wrote:

At Sun, 09 Jun 2024 18:22:38 +0100 Richard Kettlewell
<invalid@invalid.invalid> wrote:
 
 

db <dieterhansbritz@gmail.com> writes:

I like to make life easy so I wrote a one-line script for extracting
the contents of a tar file. I copied it into the /bin directory so I
can run it from anywhere.
I tried it out in a test directory where I had it, and where there is
a small test tar file. Here is the dialogue from running it, using
both the local script and the one in /bin:
>
~/tartest> ls tarx  test.tar.gz ~/tartest> cat tarx tar -xf $1.tar.gz
~/tartest> cat ~/bin/tarx tar -xf $1.tar.gz ~/tartest> ./tarx test
~/tartest> ls tarx  test  test.tar.gz ~/tartest> del -r test
~/tartest> tarx test tar (child): test: Cannot open: No such file or
directory tar (child): Error is not recoverable: exiting now tar:
Child returned status 2 tar: Error is not recoverable: exiting now
>
Why doesn't it work from bin/ ?

 
What does 'which tarx' show?  Does it show /bin/tarx?
 
Note: you should *never* put random programs in /bin (or even /usr/bin).
 The only programs/files in these directories should be ones installed
by your package management system.  /bin is reserved for core / early
boot programs and others would be in /usr/bin.
 
Locally provided programs should be in either /usr/local/bin or /opt/bin
(depending on your file system usage philosiphy).  These directories
can/should be added to your $PATH.  *Personally* provided programs
should be in $HOME/bin, and this directory can be added to your $PATH as
well.
 
 

Probably /bin/tarx isn't the same as ./tarx. What does
  cat /bin/tarx
show?
>

I already showed that, the two cat.. statements.

Be that as it may, but this works with other single-line
scripts I use. E.g. inside the directory Newstuff/ i just
typed in

~/Newstuff> mvindex

which moves a newly generated file called index.htm into another
directory. The command sits in ~/bin, as seen here
~/Newstuff> more ~/bin/mvindex
mv index.htm ~/homepage/pages/

And that worked.
Ar well, the easy way out is simply to plant the tarx script
in the two tar file directories I have, and run it with ./

--
db