This list archive was started on 11/4/93.
Here are some quick descriptions of the NetBSD mailing lists:
(clicking on the mailing-list name will take you to the archive of the mailing list on ftp.iastate.edu. The info file in each directory will list each file, and the last date it covers)
This list exists to inform people of changes to the NetBSD-current tree that will affect them. Everyone running NetBSD-current is encouraged to subscribe and listen. Don't send mail to here, this list is writeable only by people modifying the -current source tree.
This is a forum for all people using an up-to-date version of the NetBSD-current source tree. It is a good forum for talking about ``gotchas'' in the tree. Since the -current tree is a quickly moving target, please confirm any problems with the latest tree before posting.
Mailing list for people actively developing or interested in the development of ports of NetBSD to machines with m68k-family CPUs.
For "top-secret-hush-hush" kernel hacker types of discussion about MacBSD.
For general questions/answers/debate/help with MacBSD.
This mailing list is where you can discuss bugs in the latest release of NetBSD. Bugs in the current sources are *not* appropriate for this list.
This mailing list is where you can ask for help with the latest release of NetBSD.
This list is for people working on or generally interested in ports of NetBSD.
This is a forum for all people using NetBSD in any form. Since a very large number of people receive this, please keep the technical content high.
People working on the NetBSD/hp300 port.
People working on the NetBSD/i386 port.
People who want to see the m68k ports merged, such that they run one binary executable type.
People working on the NetBSD/pmax (DECstation) port.
People working on the NetBSD/sparc port.
People working on the NetBSD/sun3 port.
This list is for those who are interested in getting a commit message for every change committed to the NetBSD source tree.
People who are working on the install process.
Generic kernel issues like defining interfaces that "work".
People who are working things like multicast support, protocols, and drivers.
People who are doing ports, have recently done ports, or should be convinced to do them for/with us.
Non kernel issues. Things like Posix conformance of binaries, compilation environment, and fixing standard utilities.