> Not sure what you mean by "throughout the system" -- it's case-by-case. > If you see a copyright with the OpenBSD.org email address, you keep > that, per the license. If your end result is clearly not OpenBSD and > something is referring to the overall product, you SHOULD change it, > since the overall product isn't OpenBSD anymore.
Okay, I'll change the name. What I'm wondering is, which mentions of the OpenBSD name should I change? For example, you said before that the OpenBSD name may not be removed from the license headers of source files. So far, I can see that I would have to change the default motd, the installation scripts, Theo's welcome root mail and xdm. Is there anything that I have missed? > What isn't in the license: support your product, don't send people to > the OpenBSD mail lists for support. You may not be violating the > license, but we'll be very unhappy with you, and we'll let people know. > If you find a problem that comes from OpenBSD, replicate it on OpenBSD > and report that. Good point about the mailing lists. I'll get people to contact me for support first, then I'll confirm that the problem still exists in OpenBSD and finally I'll ask the OpenBSD mailing lists if I can't solve the problem myself. > But again...if you have any questions, hire a lawyer. It isn't hard to > do right. Isn't hard to do wrong, either... Advice on the 'net is > cheap and often wrong. :) I doubt that hiring a lawyer would be necessary. I fully intend to comply with OpenBSD's policies, and from reading the mailing lists about past situations like this, it appears that OpenBSD is not likely to sue me if I make a good faith mistake, only if I refuse to correct it. :P
