From: Neil Holmes <neil.holmes@zoom.co.uk>
To: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Elks DIstribution Edition (EDE) Update
Date: 24 Jun 2002 07:25:55 +0100 [thread overview]
Message-ID: <1024899956.1696.26.camel@nhthinkpad> (raw)
Just to keep everyone updated. Pascal's BootKit is now up and running
and the working version of "EDE" that I have now installs and boots with
this. Excellent work Pascal. Many thanks. For those who may not be
aware, Pascals Bootkit works like a kind of a mini version of Lilo. I
now have test platforms that allow selection of o/s to kick off. i.e.
DOS or ELKS being the main one but it works fine with a Linux selection
too.
I have not uploaded this version yet as it does not "boot and run". I
will plug it all back together when the issues described below are
resolved.
The work I am doing at the moment involves automating the building of
the BootKit menu while EDE is installing. I have been having some
problems with partype though. This is the tool that enables me to
identify partition types and, therfore, construct the BootKit menu. If
anyone else has experiences with partype please relay. I have been
discussing this with Riley and am currently trying to get to the bottom
of the issue. There seems to be occasions when partype will error when
seeking a partition. Even if that partition type is present.I am freely
recreating this on my 286 test bed. I haven't been able to recreate
under DOSEMU.
The other key issue that is outstanding is the "ansi-isation" of the knl
command that will allow me to set the root partition while the EDE
install is running.
The install shell that I have in test at the moment has been built with
resolution of both the above issues expected. I have, though, been
experimenting with an install set that contains multiple kernels for
different root locations because I am expecting the knl issue to take
some time to resolve.
Final point is that I have only looked at working with a single hard
drive (bda1-bda4). I don't anticipate significant issues with a second
hard drive but I am not looking at it yet.
I am, as ever, greatful for all the support and assistance that I
receive. Particularly to Riley and Pascal who have put up with my
pestering !
I'll keep you posted.
Have fun.
Neil
reply other threads:[~2002-06-24 6:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1024899956.1696.26.camel@nhthinkpad \
--to=neil.holmes@zoom.co.uk \
--cc=linux-8086@vger.kernel.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