Re: Speedtouchconf-28-01-2004.tar.gz

[Bob Proulx]

Alan Jones wrote:
> I have been attempting to configure the Alcatel Speedtouch 330 for Suse
> 9.0 Pro but having no success. I continually get K Archiver crashed
> Singal 11 ( Sigsegv ) bug in application. I seem to get the down load
> into the root directory but when I try to open it I get no such
> Directory.

Wow.  Not sure how to react here.  I have no idea what the "Alcatel
Speedtouch 330" is or why you are asking about it here.  You will have
to contact someone associated with that program or project.  Whatever
it is.  That question is a really out in the weeds for this list.

> I have attached the answers I get in root directory, can you help.
> [...]
> linux:~ # mv ././alcaudsl.sys./speedtouchconf-28-01-2004.tar.gz
> mv: missing file argument
> Try `mv --help' for more information.
> linux:~ # mv --help
> Usage: mv [OPTION]... SOURCE DEST
>   or:  mv [OPTION]... SOURCE... DIRECTORY
>   or:  mv [OPTION]... --target-directory=DIRECTORY SOURCE...
> [...]
> Report bugs to <address@hidden>.

The bug-coreutils list is for bugs and discussion of the GNU
coreutils.  Those are programs like 'mv' which are the very basic
utilities.  The 'mv' problem we can help with.  The 'mv' command takes
two or more arguments.  The first is the file or directory to be
moved.  The second or last argument is the place to move it to.  You
only typed in one argument in the above command.  You need two or
more.  This is described in the online documentation.

> linux:~ # tar speedtouchconf-28-91-2004.tar.gz
> tar: Old option `f' requires an argument.
> Try `tar --help' for more information.
> linux:~ # tar -xvzf speedtouchconf-28-01-2004.tar.gz
> tar: speedtouchconf-28-01-2004.tar.gz: Cannot read: Is a directory
> tar: At beginning of tape, quitting now
> tar: Error is not recoverable: exiting now
> 
> gzip: stdin: unexpected end of file
> tar: Child returned status 2
> tar: Error exit delayed from previous errors

I guess if the tar package had placed a bug reporting address there
then they would have gotten a bug report too?  In this case you the
tarfile is not a tarfile.  Probably by some invalid use of the mv
command and so tar can't read it.

Good Luck!

Bob