Deutsch English Français Italiano |
<wwvv82d8ffg.fsf@LkoBDZeT.terraraq.uk> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!news.gegeweb.eu!gegeweb.org!nntp.terraraq.uk!.POSTED.tunnel.sfere.anjou.terraraq.org.uk!not-for-mail From: Richard Kettlewell <invalid@invalid.invalid> Newsgroups: comp.os.linux.misc Subject: Re: tar problem Date: Thu, 13 Jun 2024 08:33:55 +0100 Organization: terraraq NNTP server Message-ID: <wwvv82d8ffg.fsf@LkoBDZeT.terraraq.uk> References: <v44em0$3i8j8$1@dont-email.me> <wwvo78auj35.fsf@LkoBDZeT.terraraq.uk> <F_OdnckCE_opY_j7nZ2dnZfqn_udnZ2d@giganews.com> <v46oc6$dn9v$1@dont-email.me> <v46ruq$etuo$1@dont-email.me> <lcp7qiF3bnqU2@mid.individual.net> <v47v3e$etuo$2@dont-email.me> <lcpeisF3bnrU1@mid.individual.net> <v492gj$vdjv$1@dont-email.me> <v4a08d$1573l$1@dont-email.me> <v4c4sj$1ld54$2@dont-email.me> <ygar0d2qf6z.fsf@akutech.de> <wwvikyeq8eh.fsf@LkoBDZeT.terraraq.uk> <VoicnQSLGKrIk_f7nZ2dnZfqn_qdnZ2d@giganews.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: innmantic.terraraq.uk; posting-host="tunnel.sfere.anjou.terraraq.org.uk:172.17.207.6"; logging-data="69822"; mail-complaints-to="usenet@innmantic.terraraq.uk" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) Cancel-Lock: sha1:FCS2E8gbeGxmxw84QRMSoTeoTj8= X-Face: h[Hh-7npe<<b4/eW[]sat,I3O`t8A`(ej.H!F4\8|;ih)`7{@:A~/j1}gTt4e7-n*F?.Rl^ F<\{jehn7.KrO{!7=:(@J~]<.[{>v9!1<qZY,{EJxg6?Er4Y7Ng2\Ft>Z&W?r\c.!4DXH5PWpga"ha +r0NzP?vnz:e/knOY)PI- X-Boydie: NO Bytes: 2707 Lines: 25 Robert Heller <heller@deepsoft.com> writes: > Richard Kettlewell <invalid@invalid.invalid> wrote: >> 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. I think you need to review the first post in the thread. They already have a working script, all they need to do is run it instead of the broken one; that is what they are having troble with. Knowing the difference between the two scripts won’t help at all. > Note the lack of "#!/bin/bash" at the start of the file could also be > causing problems. Again I think you need to review the first post in the thread. This would not cause the problem that’s actually on display. -- https://www.greenend.org.uk/rjk/