From: Björn Stenberg <bjorn@haxx.se>
To: John <john@imining.com.tw>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Fail to add TCP/IP stack package
Date: Fri, 02 Mar 2001 02:30:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.30.0103021128320.28430-100000@pm1.contactor.se> (raw)
In-Reply-To: <NDBBKMEDOKEJKFEDGCLOEEGECEAA.john@imining.com.tw>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
John wrote:
> extracting pkgadd.db:
> /usr/bin/tar:Skipping to next header
> /usr/bin/tar:Skipping to next header
It looks like your tar file is corrupted. Download it again and make sure
you use binary transmission without any conversion or filtering.
/Björn
next prev parent reply other threads:[~2001-03-02 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 1:25 John
2001-03-02 2:30 ` Björn Stenberg [this message]
2001-03-02 7:10 ` Lewin A.R.W. Edwards
2001-03-02 7:15 ` Jonathan Larmour
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=Pine.GSO.4.30.0103021128320.28430-100000@pm1.contactor.se \
--to=bjorn@haxx.se \
--cc=ecos-discuss@sources.redhat.com \
--cc=john@imining.com.tw \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).