From: "Neil Holmes" <neil.holmes@zoom.co.uk>
To: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Elks Distribution Edition - 0.0.3
Date: Tue, 28 May 2002 11:40:04 +0100 [thread overview]
Message-ID: <DDENIOHFNLNMCGGDFDPCGEOOCDAA.neil.holmes@zoom.co.uk> (raw)
I have put up version 0.0.3 which addresses (hopefully finally for now) the
device creation issues using the MAKEDEV script from the 0.1.0 kernel
root/boot disk.
I have also done a little bit of tidying up on the messages displayed during
the install.
For disk one, being as I intend to dump it from the distribution in due
course, it will not really change at all on any version. I have changed some
of the text but functionally it is exactly the same as in all previous
releases so you can save yourselves a couple of minutes and not produce a
new disk 1 ! Just use the one you have already.
Michael McConnell has found that their seems to be a problem in using the
Distribution Edition in Bochs. I have never used Bochs before and am
currently trying to set up Bochs 1.4 to look into this. I am assuming that
the problem is likely to relate to the bootloader, that I am currently
using, in some way being as on all other platforms that I have tried thus
far (with a 1.44 Mb floppy drive), I have had no problems.
Assuming nothing drastic comes up, I will leave 0.0.3 as the latest version
for a little while now.
My desirables for the next release include :-
- A single floppy disk
- No requirement to "login" to start the install
- A tidier completion of the script
(try taking the floppy out before you hit return for reboot if you don't
know what I mean here !!!)
- Different Disk Image Formats !!!
And if I can
- Begin to introduce a method for package installation
Have Fun
Neil
reply other threads:[~2002-05-28 10:40 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=DDENIOHFNLNMCGGDFDPCGEOOCDAA.neil.holmes@zoom.co.uk \
--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