From: "Gregg C Levine" <obiwanthejediknight@worldnet.att.net>
To: ELKS <Linux-8086@Vger.Kernel.Org>
Subject: Status of software written by Chad Page
Date: Tue, 4 Jun 2002 18:00:29 -0400 [thread overview]
Message-ID: <001c01c20c13$3e3703e0$1955580c@who> (raw)
Hello from Gregg C Levine
I've asked this question before, but so far no one's replied. So I shall ask
it again. What is the status of everything written by Chad Page? And does
anyone have an updated e-mail address for the man? I am studying his "nonix"
code from the MIT FTP site, where ELKS code used to be stored, originally.
But his address on the LSM files for a few of his original files, those
labeled "Linux-16" doesn't work. It returns the electronic mail equivalent
of addressee unknown.The reason being is that the code for his nonix project
never went past the kernel status, and I'd like to find out more about his
later attempts. For myself I think he abandoned it in favor of eventually
became our project.
Gregg C Levine obiwanthejediknight@att.net
<This signature will be replaced, pending an approval from the Jedi Council.
>
next reply other threads:[~2002-06-04 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 22:00 Gregg C Levine [this message]
2002-06-04 23:17 ` Status of software written by Chad Page Alan Cox
2002-07-24 17:47 ` Robert de Bath
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='001c01c20c13$3e3703e0$1955580c@who' \
--to=obiwanthejediknight@worldnet.att.net \
--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