From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <37d35879ea536afaa22cde6b7162f023@yyc.orthanc.ca>
References: <fe41879c1001121439t3b23fd3btc912dad79aeb8419@mail.gmail.com>
	<37d35879ea536afaa22cde6b7162f023@yyc.orthanc.ca>
Date: Wed, 13 Jan 2010 00:56:01 -0800
Message-ID: <fe41879c1001130056w729785cfp52de5edff6a25599@mail.gmail.com>
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Ken Fileserver problem
Topicbox-Message-UUID: be330198-ead5-11e9-9d60-3106f5b1d025

On Tue, Jan 12, 2010 at 2:50 PM, Lyndon Nerenberg (VE6BBM/VE7TFX)
<lyndon@orthanc.ca> wrote:
> So is it worth it to try to nail down a driver that can talk to at
> least some of the on-motherboard NVRAM present on today's crop of
> x86/amd64 motherboards?

Our mileages vary: I don't see the problem in my floppy or a 9fat partition
carrying a little more data (i.e., one more file). Also, considering
the input of
time on such a project and the usefulness of its output, I'd not encourage
it.

> There is anecdotal evidence of past individual success. =A0Even an
> experimental collection of these driver bits would be interesting to
> play with.

But for yourself, it seems you've answered your own question.


Best,
ak