Subject: Re: Embedded NetBSD on M$ Windows?
To: NetBSD-current Discussion List <current-users@NetBSD.ORG>
From: gabriel rosenkoetter <>
List: current-users
Date: 10/29/2001 17:27:50
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 29, 2001 at 04:26:21PM -0500, Greg A. Woods wrote:
> However it seems you've ignored the larger issue of future
> maintainability here.  I thought John Nemeth explained fairly clearly
> that any M$ Windows device driver can define a new device name and that
> they can appear anywhere within the NTFS filesystem hiararchy.

But only under extreme, non-standard circumstances. The environment
Todd is aiming for has Cygwin and not much else installed. That
build environment can easily be tailored so that no weird device
drivers are installed, but can NOT be tailored so that aux doesn't
get to be a special name, since that's a part of the base windows

I feel certain that Todd (and the rest of the NetBSD developers
involved) really do understand your concern and really did consider
it, and chose to make this change. No one is asking that we account
for some random device driver (even one that's popularly installed),
just that we account for the basic Windows environment since several
NetBSD developers (note that I don't think anyone employed by Wasabi
has said anything about Wasabi clients paying specifically for this,
btw) would like to cross-build in this environemnt.

I assure you that you've made enough of a flap that nobody will
forget your point, not even those too nauseated to keep reading by
the third or fourth reply.

Please, please, please let it drop.

       ~ g r @

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see