From: jliddle@rs6000.cmp.ilstu.edu (Jean Liddle) Subject: Re: Where to find ln? Date: Tue, 07 Jul 1992 01:54:09 GMT
In article <1992Jul7.001630.8308@muddcs.claremont.edu> jwinstea@jarthur.claremont.edu (Jim Winstead Jr.) writes:
>
> [my comments on being able to extract *.tar.Z files removed]
>
>I don't follow you here - you don't need mtools to read *.tar.Z files,
>simply do this:
>
> uncompress < foo.tar.Z | tar zv
>
>Things will work fine from there. You can also redirect a device
>(like /dev/fd0) into uncompress if you want.
First, many, many thanks for all the input on my two questions.
Changing ownership of passwd to root:root did indeed fix things.
I was also (moderately) successful in extracting a *.tar.Z file
from /dev/fd0 (whos audodetect now works for me! yeah!) using
the following command
# uncompress < /dev/fd0 | tar xv
however, the extraction ended with the message:
"broken pipe"
I then tried the following, to creat a *.tar file on my hard drive:
# uncompress < /dev/fd0 > fileutl32.tar
which resulted in ...
general protection: 0000
EIP: 000f:03C10855
EFLAGS: 00013206
fs: 0017
base: 1C000000, limit 04000000
stack: 00000400 00000001 03C288F4 03BFFB94
Pid: 34, process nr: 7
89 38 83 7d 00 00 74 09 8b 45
segmentation fault (core dumped)
I assume this is becouse uncompress has reached the end of the tar file and
beyond it. My question is - does this affect the extraction of the last
file? Tar was unable to extract fileutl32.tar after the process had ended,
but /usr/man1/touch.1 (the last file from the fileutils *.tar.Z file to be
extracted using the pipe) appears ok.
I am wondering because I plan on using this approach for (re)installing
GCC 2.2.2 and installing x-windows, and don't want to end up posting
inane questions about problems resulting from faulty file extractions.
Thanks for any insights!
Jean.
-- Jean Liddle | == Bill Clinton for President == Computer Science, Illinois State University | e-mail: jliddle@ilstu.edu | - Carol Mosley Braun for Senat -