From: Jody <jbruchon@nc.rr.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: New ELKS snapshot release
Date: Mon, 15 May 2006 10:22:08 -0400 [thread overview]
Message-ID: <44688E90.70504@nc.rr.com> (raw)
In-Reply-To: <040301c67828$f2c17ef0$6602a8c0@dionysus>
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@atlas.cz>
> To: <unlisted-recipients:>; <no To-header on input>
> Cc: "ELKS" <linux-8086@vger.kernel.org>
> 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@vger.kernel.org
>>> 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@vger.kernel.org
>> 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@vger.kernel.org
> 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-05-15 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 5:18 New ELKS snapshot release Jody
2006-05-15 8:31 ` Vojte(ch Sázel
2006-05-15 14:05 ` Hans
2006-05-15 14:22 ` Jody [this message]
2006-05-15 14:42 ` Hans
2006-05-15 15:18 ` Vikas Kumar
2006-05-15 15:26 ` Hans
2006-05-15 15:33 ` David Given
2006-05-15 16:09 ` Hans
2006-05-15 19:53 ` Tom McCabe
2006-05-15 20:04 ` Tom McCabe
2006-05-16 4:50 ` Jody
2006-05-17 13:26 ` Francois Gurin
2006-05-17 13:30 ` Jody
2006-05-15 19:54 ` Tom McCabe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44688E90.70504@nc.rr.com \
--to=jbruchon@nc.rr.com \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.