<aclass="reference"href="http://www.openbsd.com">OpenBSD</a><aclass="footnote-reference"href="#id5"id="id6"name="id6">[2]</a> as the underlying kernel, userland, and libc. <aclass="reference"href="http://www.openbsd.com">OpenBSD</a><aclass="footnote-reference"href="#id5"id="id7"name="id7">[2]</a> supports a

110

variety of different architectures, so, in principle, we would need a new

111

<em>openbsd-arch</em> keyword for each supported architecture. In fact, the

eventually like to support the option of &quot;mixing-and-matching&quot;

114

GNU/*BSD/whatever userlands and libcs irrespective of the underlying kernel.

115

(<aclass="reference"href="http://www.debian.org">Debian</a><aclass="footnote-reference"href="#id10"id="id11"name="id11">[4]</a>, for example has a similar BSD <aclass="reference"href="http://www.debian.org/ports/netbsd/">project</a><aclass="footnote-reference"href="#id12"id="id13"name="id13">[5]</a>, except that they have

116

replaced the BSD userland with a GNU userland.) The net result is that we