Very Computer

I'm attempting to install Netserva, a mini-distribution based on Debian.  
http://netserva.com
(yes, the lack of WWW matters)

Since it only comes in a tarred/bzipped directory tree, I installed a minimal
installation of Caldera OpenLinux 2.3 (as a backup, and to install Netserva)
on /dev/hda2, and left the /dev/hda1 partition free, clear, and formatted
ext2.

I succeeded in getting the .tbz file onto my Linux machine, and onto
/dev/hda1.  I attempted to untar it as described on the website, but it
didn't work.  Apparently, Caldera OpenLinux didn't come with (or wasn't
installed in the minimal installation) bzip2.  I got that off of the
internet, and dumped it into /bin.  Copied it to bunzip2 as well.  I
uncompressed the archive, netserva-base1-20010223.tbz leaving me with
netserva-base1-20010223.tar.  I tried to untar this by using tar -xvf
netserva-base1-20010223.tar.  Files whizzed by, and several messages about
not being able to link to files because the file didn't exist (?).  The last
few lines before it dumped me to bash were:

sbin/mli-tool
sbin/resize2fs
floppy/
cdrom/
initrd/
tar: Error exit delayed from previous errors

Anyone have any ideas?

Thanks alot,
Ian Trider

 -----  Posted via NewsOne.Net: Free (anonymous) Usenet News via the Web  -----
  http://newsone.net/ -- Free reading and anonymous posting to 60,000+ groups
   NewsOne.Net prohibits users from posting spam.  If this or other posts

Quote:>I uncompressed the archive, netserva-base1-20010223.tbz leaving me with
>netserva-base1-20010223.tar.  I tried to untar this by using tar -xvf
>netserva-base1-20010223.tar.  Files whizzed by, and several messages about
>not being able to link to files because the file didn't exist (?).  The
last
>few lines before it dumped me to bash were:

>sbin/mli-tool
>sbin/resize2fs
>floppy/
>cdrom/
>initrd/
>tar: Error exit delayed from previous errors

>Anyone have any ideas?

It seems that these files constitutes a complete system and thus "expects"
to be untarred from the root-directory which may account for the errors you
saw, if you untarred the files in a subdirectory.

To actually get a better look at the error messages, try the command "tar
xvf netserva-base1-20010223.tar 2>&1 | less" -- now you can page through the
messages and hopefully see what went wrong. Beware though that the filenames
(from the "v" option) may not be synchronised to the error messages as the
system uses different buffers for stdout (ordinary messages) and stderr
(error messages).

  /TRY