All of lore.kernel.org
 help / color / mirror / Atom feed
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 00:53:12 +0300	[thread overview]
Message-ID: <1021584842.484.2.camel@cool> (raw)
In-Reply-To: <Pine.LNX.4.21.0205160649080.12716-100000@Consulate.UFP.CX>

Την Πεμ, 16-05-2002 στις 12:40, ο/η Riley Williams έγραψε:
> Hi Harry.
> 
> >> After syncing with the CVS tree, I can't run the system.
> 
> > I've just checked, and I now get this problem by dropping the 0.1.0
> > release kernel on the current floppy image, so this isn't a recent
> > problem. I have to suspect that it's to do with other than the
> > kernel itself, so who's been patching the elkscmd package recently?
> > I haven't.
> 
> I've just double-checked the above by doing...
> 
> 	mkdir X
> 	cd X
> 	cvs get -r elks-0_1_0 elks
> 	cd elks
> 	make defconfig
> 	make dep
> 	make Image
> 
> ...and then copying the resulting kernel image to a fresh copy of the
> floppy image you released with the 0.1.0 kernel. When I boot from the
> resulting floppy, I get exactly the same problem as you reported, so
> whatever the problem is predates the 0.1.0 release !!!
> 
> I've also downloaded the images-0.1.0.zip file after following the
> download link on the ELKS website, and dropped the full3 image on a
> floppy, and I can confirm the following:
> 
>  1. The kernel image included on the floppy boots fine.
> 
>  2. Replacing it with the 0.1.0 kernel image compiled using the
>     above sequence results in a disk that fails to boot.
> 
> Basically, I have to conclude that the kernel on the 0.1.0 images is
> NOT the 0.1.0 kernel as labelled in the source tree, and that has me
> VERY worried. Can somebody please advise what is going on here?
> 
> As I stated previously, I'm in for Dental Sedation Surgery at lunchtime
> today, so I'm not likely to be in any condition to investigate this
> after that. Can somebody please look into this problem and see what they
> can come up with as this definitely needs sorting out.
> 
> Best wishes from Riley.
> 

I don't see how the things you describe can happen. On my side I just
downloaded the 0.1.0 version and reverted all the changes you did to the
minixfs. The thing booted fine. I thing it is the changes you made to
some datatypes.

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

  reply	other threads:[~2002-05-16 21:53 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 [this message]
2002-05-16 22:42       ` Riley Williams
2002-05-16 22:47         ` Dan Olson
2002-05-17 14:10         ` Harry Kalogirou
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=1021584842.484.2.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 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.