From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Kalogirou Subject: Re: ELKS not runnable.... (once again) Date: 17 May 2002 00:53:12 +0300 Sender: linux-8086-owner@vger.kernel.org Message-ID: <1021584842.484.2.camel@cool> References: Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: List-Id: Content-Type: text/plain; charset="iso-8859-7" To: Riley Williams Cc: Linux-8086 =D4=E7=ED =D0=E5=EC, 16-05-2002 =F3=F4=E9=F2 12:40, =EF/=E7 Riley Willi= ams =DD=E3=F1=E1=F8=E5: > Hi Harry. >=20 > >> After syncing with the CVS tree, I can't run the system. >=20 > > 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. >=20 > I've just double-checked the above by doing... >=20 > mkdir X > cd X > cvs get -r elks-0_1_0 elks > cd elks > make defconfig > make dep > make Image >=20 > ...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 !!! >=20 > 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: >=20 > 1. The kernel image included on the floppy boots fine. >=20 > 2. Replacing it with the 0.1.0 kernel image compiled using the > above sequence results in a disk that fails to boot. >=20 > 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? >=20 > As I stated previously, I'm in for Dental Sedation Surgery at lunchti= me > 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 t= hey > can come up with as this definitely needs sorting out. >=20 > Best wishes from Riley. >=20 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 th= e 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" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html