Question: how do I respond to this problem report? After submitting the
problem, I joined this list and "listened in" upon a couple of folks
attempting to solve my problem!! (Pretty cool.) Needless to say, I now have
an LC3 as a file server (I'm very happy).

Anyway, I would be glad to be a tester for lc3 kernels (with and without
FPU). (Unfortunately, I'm an applications guy... device drivers and such are
just not my cup of tea.) How do I answer this query (just in case someone is
waiting on an action from me)?

brian

----- Original Message -----
From: bhowar - Brian Howard <bhowar@acxiom.com>
To: <bhowar@gte.net>
Sent: Monday, March 06, 2000 8:45 AM
Subject: FW: Reminder of 1 NetBSD Problem Report


>
>
> -----Original Message-----
> From: gnats@netbsd.org [mailto:gnats@netbsd.org]
> Sent: Sunday, March 05, 2000 7:07 AM
> To: bhowar@acxiom.com
> Subject: Reminder of 1 NetBSD Problem Report
>
>
> This is an infrequent reminder that there is 1 Problem Report
> (PR) of yours in the NetBSD GNATS database in "feedback" state.
>
> Problem Reports in this state require additional information
> before they can be resolved. Most often, this is information
> required from the user who submitted the Problem Report in the
> first place; occasionally, information is required from some
> other source to resolve the reported problem.
>
> To see a summary of the whole PR database, please see
>
> http://www.NetBSD.org/Gnats/
>
> If you wish to perform an arbitrary query on the database, please see
>
> http://www.NetBSD.org/Misc/query-pr.html
>
> For additional helpful documentation, please see
>
> http://www.NetBSD.org/Misc/pr-hints.html
> http://www.NetBSD.org/Misc/pr-fields.html
> http://www.NetBSD.org/Misc/pr-states.html
>
> Please examine the full text and history of the Problem Report
> listed below by following the given URL with a web browser.
> The audit trail of action will be at the bottom of each report,
> and should list what information is required to solve the problem
> and close the report.
>
> ______________________________________________________________
>
> port-mac68k/7040 - critical low priority sw-bug
> Sonic (sn0) Ethernet driver hangs LC3 when accessed through ifconfig
> http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=7040