www/want.html - view

Return to want.html CVS log

Up to [local] / www

File: [local] / www / want.html (download) (as text)

Revision 1.1118, Tue Apr 30 09:06:01 2024 UTC (4 weeks ago) by florian
Branch: MAIN
Changes since 1.1117: +2 -0 lines

I give up, this sagemcom cpe provided by my ISP is just too broken
to work on DHCPv6-PD. It hands out a prefix delegation exactly once,
any change in DHCPv6 options and it requires a factory reset. Changing
the duid, that's right, factory reset. If rapid commit is enabled it
hands out a prefix but forgets about it? And without rapid commit it
hands out a prefix but does not properly route to it, instead it
issues neighbour solicitations so we'd need to implement and ND proxy.

This is all too much trouble for an initial implementation.

<!doctype html>
<html lang=en>
<meta charset=utf-8>

<title>OpenBSD: Hardware Wanted</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://www.openbsd.org/want.html">

<style>
h3, h4 {
	color: var(--red);
}
</style>

<h2 id=OpenBSD>
<a href="index.html">
<i>Open</i><b>BSD</b></a>
Hardware Wanted
</h2>

<hr>

<p>
The following list outlines hardware that the OpenBSD project could use.
There are a number of reasons why developers need hardware, and it is important
to first of all realize these reasons:

<ul>
<li>To support a specific device, normally one which is more rare or new.
<li>To be part of their development environment.
<li>Some types of machines may be different in some way
    (i.e. big-endian or unsigned-char) and ensure that developers
    write code more carefully.
<li>That said, space or power may be at a premium for some people.
</ul>

<p>
If you do not own these devices, but want to help us, we recommend you
search on <a href="https://www.ebay.com">eBay</a> for the devices.  If
you do the bidding and then get the device shipped to us, it really
helps us.  It is better if developers develop, and skip the bidding process,
since any time saved can be spent on improving OpenBSD instead.

<p>
If it is clear which specific developer should be contacted, please do
so directly.  Otherwise contact <a href="mailto:deraadt@openbsd.org">Theo de Raadt</a>
who will pass on the message to whichever developers are in need.

<p>
Please be very clear as to where you are located!!  For larger items this
can be very important.

<hr>

<h3>General device requirements</h3>

<p>
We try to spread these types of devices around our development community.

<ul>
<li>Laptops.  These die often enough that as a group our needier
    developers need help replacing about 2-3 per year.
<li>Apple Mac powerpc equipment.
<li>HP J6750 machines (J6700 is the second best choice).
<li>Faster &amp; smaller sparc64 machines, for instance 1U rack mount
    machines.  It is important to spread sparc64 around the development
    community, since it is the most strict platform for detecting non-portable
    or buggy code.
<li>Any amd64 or faster i386 hardware which comes available.
<li>We generally do not need older and "very common" ISA/PCI equipment, since
    our developers will generally have gotten their hands on these in the
    past.
</ul>

<h3>Specific platform requests by our developers</h3>

<ul>
<!--
	Please (un)comment the relevant platform for your request.
-->

<!-- <li><i>alpha:</i> -->
<!-- <li><i>amd64:</i> -->
<!-- <li><i>arm64:</i> -->
<!-- <li><i>armv7:</i> -->
<li><i>sparc64:</i>
  <ul>
    <li>CPU activation keys for M10-1 servers. Contact claudio@openbsd.org.
  </ul>
<!-- <li><i>landisk:</i> -->
<!-- <li><i>luna88k:</i> -->
<!-- <li><i>macppc:</i> -->
<!-- <li><i>octeon:</i> -->
<!-- <li><i>Miscellaneous:</i> -->
<!-- <li>Nothing at the moment. -->
</ul>

<!-- <h3>Specific cards needed by our developers</h3> -->

<h3>Specific devices and equipment needed by our developers</h3>

<ul>
  <li>A &quot;FRITZ!Box 6660 Cable&quot; router is needed in the Netherlands
    for work on DHCPv6-PD. Contact florian@openbsd.org.
</ul>