the error is: $ tar jtvf elks-20060515.tar.bz2 > /dev/null tar: This does not look like a tar archive tar: Skipping to next header tar: Error exit delayed from previous errors --francois On Mon, May 15, 2006 at 03:42:28PM +0100, Hans wrote: > From: Hans <hans64@xxxxxxxxxx> > To: Jody <jbruchon@xxxxxxxxx> > Cc: ELKS <linux-8086@xxxxxxxxxxxxxxx> > Subject: Re: New ELKS snapshot release > X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on cecilia > X-Spam-Level: > X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham > version=3.1.0 > Reply-To: Hans <hans64@xxxxxxxxxx> > X-Mailing-List: linux-8086@xxxxxxxxxxxxxxx > > I don't know, I checked the tar help file but can't seem to find a command > to display the error. If todo is the last file in the list then perhaps > this is a bogus error message from bzip2 to tar? > > Hans > www.ht-lab.,com > > ----- Original Message ----- > From: "Jody" <jbruchon@xxxxxxxxx> > To: <unlisted-recipients:>; <no To-header on input> > Cc: "ELKS" <linux-8086@xxxxxxxxxxxxxxx> > Sent: Monday, May 15, 2006 3:22 PM > Subject: Re: New ELKS snapshot release > > > But what's the actual error? > > Hans wrote: > >I also get an error when I extract it under Cygwin, > > > >tar jxvf elks-20060515.tar.bz2 > >.... > >elksnet/screen/screen.1 > >elksnet/screen/screen.c > >elksnet/screen/screen.h > >elksnet/screen/SharFile.Headers > >elksnet/todo > >tar: Error exit delayed from previous errors > > > >Hans > >www.ht-lab.com > > > > > >----- Original Message ----- From: "Vojte(ch S?zel" <vsazel@xxxxxxxx> > >To: <unlisted-recipients:>; <no To-header on input> > >Cc: "ELKS" <linux-8086@xxxxxxxxxxxxxxx> > >Sent: Monday, May 15, 2006 9:31 AM > >Subject: Re: New ELKS snapshot release > > > > > >>Hi! > >> > >>I've tried to unpack .tar.bz2 file, but it seems damaged. > >>Some files have been extracted but I don't know if it's all of them. > >>I have also tried to download it again, but it doesn't seem to be a > >>download error. > >> > >>Vojtech Sazel > >> > >> > >>Jody napsal(a): > >> > >>>Greetings to all you ELKSers out there. > >>> > >>>A new snapshot of the current ELKS development tree is now available at > >>>the usual place: > >>> > >>>http://compsolutions.ath.cx:88/elks/ > >>> > >>>The release is dated 2006-05-15 and contains a batch of patches from the > >>>eternally busy Tom McCabe (thanks again!) that fix a lot of build > >>>problems. It's getting about time for the C gurus to hop back in and > >>>start actually hacking on the code, wouldn't you think? > >>> > >>>If I knew C, I'd do it, but I don't, and I'm in the middle of planning a > >>>business venture, so I'm up to my ears in work at the moment. I've got > >>>just enough time to maintain these releases and tie up loose ends. Don't > >>>worry! ELKS will remain actively maintained no matter how busy I get, > >>>so keep patches and reports rolling in. > >>> > >>>Happy hacking! > >>> > >>>Jody Bruchon > >>>- > >>>To unsubscribe from this list: send the line "unsubscribe linux-8086" in > >>>the body of a message to majordomo@xxxxxxxxxxxxxxx > >>>More majordomo info at http://vger.kernel.org/majordomo-info.html > >>> > >>> > >>> > >>> > >>> > >> > >>- > >>To unsubscribe from this list: send the line "unsubscribe linux-8086" in > >>the body of a message to majordomo@xxxxxxxxxxxxxxx > >>More majordomo info at http://vger.kernel.org/majordomo-info.html > >> > > > > > >- > >To unsubscribe from this list: send the line "unsubscribe linux-8086" in > >the body of a message to majordomo@xxxxxxxxxxxxxxx > >More majordomo info at http://vger.kernel.org/majordomo-info.html > > > - > To unsubscribe from this list: send the line "unsubscribe linux-8086" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > - > To unsubscribe from this list: send the line "unsubscribe linux-8086" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
