3 ms·

This wasn't a question about having a functional webserver or not. It was a conscious decision against running code without reading it first. The "run but don't

by stsp 12y ago

This wasn't a question about having a functional webserver or not. It was a conscious decision against running code without reading it first. The "run but don't read" strategy belongs into ports, not base. Hence nginx moved to ports. Forking nginx was actually discussed when a proposed nginx update diff was too large for proper review. Tons of complex regex parsing code was added with nobody willing to go through it all in detail. The forking option was quickly dismissed. The tipping point happened when someone (reyk?) pointed out that relayd had most of the guts of a complete web server anyway, including OpenBSD-style privsep which has to be bolted on to virtually all software imported from elsewhere, including nginx. It took about a week from that discussion happening to having a relayd-based functional and peer-reviewed web server in base (+ a couple of months of shaking out a few bugs and adding minor features).

jimktrains2 12y ago
> he "run but don't read" strategy belongs into ports, not base. Hence nginx moved to ports. Why is there a webserver in base?
- jquast 12y ago
  For the same reason the other 20+ net-daemons are: http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/etc/rc.conf?content-type=text/plain http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/etc/... With OpenBSD, you can actually avoid the ports tree all together and still play a critical role in your infrastructure. If you're going to distribute a system that doesn't do much of anything on its own, and delegate the responsibility of security (and choice!) to "the ports tree" you're not doing any better than Linux or FreeBSD.
  - jimktrains2 12y ago
    The majority of users are not serving static pages, so unless they bundle their own JDK, Python, PHP, Ruby installs you have to go to the ports tree anyway?
- currysausage 12y ago
  The FAQ has the canonical answer: Why is a web server included? It isn't needed by many people! Because the developers want it. [1] [1] http://www.openbsd.org/faq/faq1.html#HowAbout http://www.openbsd.org/faq/faq1.html#HowAbout

by stsp 12y ago

jimktrains2 12y ago

> he "run but don't read" strategy belongs into ports, not base. Hence nginx moved to ports. Why is there a webserver in base?

jquast 12y ago
For the same reason the other 20+ net-daemons are: http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/etc/rc.conf?content-type=text/plain http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/etc/... With OpenBSD, you can actually avoid the ports tree all together and still play a critical role in your infrastructure. If you're going to distribute a system that doesn't do much of anything on its own, and delegate the responsibility of security (and choice!) to "the ports tree" you're not doing any better than Linux or FreeBSD.
- jimktrains2 12y ago
  The majority of users are not serving static pages, so unless they bundle their own JDK, Python, PHP, Ruby installs you have to go to the ports tree anyway?
currysausage 12y ago
The FAQ has the canonical answer: Why is a web server included? It isn't needed by many people! Because the developers want it. [1] [1] http://www.openbsd.org/faq/faq1.html#HowAbout http://www.openbsd.org/faq/faq1.html#HowAbout