Fuck off, Jussi. Serious problems like the one that fellow's network administrator pinged him for should not sit unsolved. It affects the rest of us. Those problem stepchild packages are problems in and of themselves, as is the platform it runs on. The time to condone sloppy practices and attitudes is long over, if there ever was such a time.
Even in Ports, there is a selection of packages that would allow him to set up content management not tied to any specific proprietary formats, protocols or systems. http://www.openbsd.org/4.6_packages/i386/cmsmadesimple-1.5.3.tgz-long.html http://www.openbsd.org/4.6_packages/i386/tikiwiki-2.2.tgz-long.html http://www.openbsd.org/4.6_packages/i386/drupal-6.12.tgz-long.html http://www.openbsd.org/4.6_packages/i386/plone-3.0.6p1.tgz-long.html Even though they run on OpenBSD, they allow clients to connect from any platform, unlike the bad example. Even simpler, there's OpenAFS or Samba in Ports, to go with Apache in Base: http://www.openbsd.org/4.6_packages/i386/openafs-1.4.7p9.tgz-long.html http://www.openbsd.org/4.6_packages/i386/samba-3.0.34p1.tgz-long.html Its wrong in allowing a mess on your LAN does, more so because it means that the rest of us net users should have to cover it. Because of dipshits using and defending broken protocols, broken formats and broken services, any project that is oriented towards proper design, security, standards, cross platform development and open source has a harder time of it. Taking a more proactive stance on security and go after the problem systems and those that spread them, or give backtalk about wanting to allow them. If you are too good for Ports, then there are more packages that will operate safely and provide reliable service to clients: http://lenya.apache.org/ http://www.joomla.org/ http://www.opencms.org/ http://zope2.zope.org/ There are plenty more that work well. /Lars
