From: Jody Bruchon <jody@jodybruchon.com>
To: linux-8086@vger.kernel.org
Subject: elksfs removed from ELKS kernel; EMS memory needed
Date: Fri, 17 Feb 2012 00:39:22 -0500 [thread overview]
Message-ID: <4F3DE80A.1030508@jodybruchon.com> (raw)
Upon close examination of a "diff" between the filesystems "minix" and
"elksfs" I have concluded that elksfs is merely a clone of minix, with
changes for the new name but nothing of real value. This effectively
means that the minix filesystem was included in entirety in the ELKS
kernel source TWICE. There seems to be zero documentation specifying the
layout of elksfs, and zero tools that create one, thus to me it is quite
clear that elksfs never came to actually exist. I have removed it and
pushed the removal to Git, reducing the total ELKS kernel code by 75 KiB
and removing some unnecessary configuration options.
Next on the chopping block: everything that depends on CONFIG_NOT_NOW is
potentially vaporware and/or bloat, though some of it looks potentially
useful. I've acquired the LIM EMS 4.0 specification from:
http://www.arl.wustl.edu/~lockwood/class/cs306/class-resources/gpe/limems41.doc.html
And I would like to develop support for expanded memory, possibly tying
into the swap subsystem. Does anyone on the list have some hardware with
EMS memory for testing?
Jody Bruchon
next reply other threads:[~2012-02-17 5:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 5:39 Jody Bruchon [this message]
2012-02-17 7:12 ` elksfs removed from ELKS kernel; EMS memory needed Kirn Gill
[not found] <jXCVB0ylFfhQ.p6tLq6MJ@posti.saunalahti.fi>
2012-02-17 9:35 ` Kirn Gill
2012-02-17 14:35 ` David Given
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=4F3DE80A.1030508@jodybruchon.com \
--to=jody@jodybruchon.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).