From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Oliver <oliver@wilmskamp.dyndns.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File corrupting bug in kernel 2.2.19 as well as 2.2.20 ?
Date: 30 May 2002 13:05:21 +0100 [thread overview]
Message-ID: <1022760321.9255.347.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <200205301233.59618.oliver@wilmskamp.dyndns.org>
On Thu, 2002-05-30 at 11:33, Oliver wrote:
> files seemed to be corrupted (e.g. /etc/apache/httpd.conf,
> /var/lib/dpkg/available and others). those files had some parts replaced
> with ...^@^@^@^@^@... stuff, which are zero-bytes (0x00) (again: there
> were only some parts REPLACED in these files, the filelength had NOT
> changed). thats not too funny for a running server as you can imagine ;)
16 or 32 byte long chunks ?
.
next prev parent reply other threads:[~2002-05-30 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 10:33 Oliver
2002-05-30 12:05 ` Alan Cox [this message]
2002-05-30 12:49 ` Oliver Wegner
2002-05-30 10:43 Oliver Wegner
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=1022760321.9255.347.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@wilmskamp.dyndns.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®