From: Harry Kalogirou <harkal@gmx.net>
To: Riley Williams <rhw@InfraDead.Org>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: ELKS not runnable.... (once again)
Date: 17 May 2002 17:10:01 +0300 [thread overview]
Message-ID: <1021644561.21840.3.camel@cool> (raw)
In-Reply-To: <Pine.LNX.4.21.0205162338390.12716-100000@Consulate.UFP.CX>
Την Παρ, 17-05-2002 στις 01:42, ο/η Riley Williams έγραψε:
s.
>
> I don't understand it either. All I can be sure of is that th version
> produced by `cvs get -r elks-0_1_0 elks` has exactly the same problem,
> but the one produced by `cvs get -D 'Apr 30 12:00:00 2002' elks` does
> not, so the problem lies somewhere between those two versions.
>
Why should we compare 0.1.0 with an older one? Concentrate on this facts
1) The bioshd block device fails because the FS tells it to read some
_wild_ sector.
2) Replacing the minix FS sources in the current source code with the
ones from the 0.1.0, fixes the problem.
3) The changes in the minix FS are very dangerous and require care.
Harry
-
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:[~2002-05-17 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 17:31 ELKS not runnable.... (once again) Harry Kalogirou
2002-05-15 18:46 ` pauln
2002-05-15 19:30 ` Harry Kalogirou
2002-05-17 20:15 ` ELKS not runnable.... (other thing) Stefan de Konink
2002-05-17 19:40 ` Harry Kalogirou
2002-05-15 21:25 ` ELKS not runnable.... (once again) Riley Williams
2002-05-15 23:11 ` Riley Williams
2002-05-16 9:40 ` Riley Williams
2002-05-16 21:53 ` Harry Kalogirou
2002-05-16 22:42 ` Riley Williams
2002-05-16 22:47 ` Dan Olson
2002-05-17 14:10 ` Harry Kalogirou [this message]
2002-05-17 17:59 ` Riley Williams
2002-05-17 19:28 ` Harry Kalogirou
2002-05-16 9:52 ` Harry Kalogirou
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=1021644561.21840.3.camel@cool \
--to=harkal@gmx.net \
--cc=linux-8086@vger.kernel.org \
--cc=rhw@InfraDead.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