From: Ilia Menchikh <meniluha@mailru.com>
To: mandrake-russian@altlinux.ru
Subject: Re: [mdk-re] OO & ftp
Date: Thu Dec 27 22:47:01 2001
Message-ID: <20011227225030.787e8777.meniluha@mailru.com> (raw)
In-Reply-To: <20011227214248.066211e5.z_on@ukr.net>
On Thu, 27 Dec 2001 21:42:48 +0200
Avenger <z_on@ukr.net> wrote:
> > Такая вот проблема: скачал новый OOo по модему а он битый, (долго скачивал, машина висла).
> >Можно это как-нибудь исправить не скачивая заново (~80 Мb)?
>
> А известно в каких местах битый?
> Можно попытаться дотянуть битые куски.
> (когда-то так делал - много мороки)
Да bzip на него ругается. Примерно так:
$ bzip2 -d OO641C-linux-ALT2-rus.tar.bz2
bzip2: Data integrity error when decompressing.
Input file = OO641C-linux-ALT2-rus.tar.bz2, output file = OO641C-linux-ALT2-rus.tar
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to *attempt* to recover
data from undamaged sections of corrupted files.
bzip2: Deleting output file OO641C-linux-ALT2-rus.tar, if it exists.
$ bzip2 -tvv OO641C-linux-ALT2-rus.tar.bz2
OO641C-linux-ALT2-rus.tar.bz2:
[1: huff+mtf rt+rld]
[2: huff+mtf rt+rld]
<scip>
[49: huff+mtf rt+rld]data integrity (CRC) error in data
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
Я так понимаю что цифра - это какое-то место в файле, вот только 49 чего?
---
Илья
next prev parent reply other threads:[~2001-12-27 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 22:30 Ilia Menchikh
2001-12-27 22:36 ` Avenger
2001-12-27 22:47 ` Ilia Menchikh [this message]
2001-12-27 23:15 ` Avenger
2001-12-28 0:23 ` Ilia Menchikh
2001-12-28 12:34 ` Vyt
2001-12-28 16:39 ` Ilia Menchikh
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=20011227225030.787e8777.meniluha@mailru.com \
--to=meniluha@mailru.com \
--cc=mandrake-russian@altlinux.ru \
/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
ALT Linux Community general discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
public-inbox-index community
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.community
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git