Linked by Thom Holwerda on Thu 3rd May 2012 21:26 UTC, submitted by PhilJ
Thread beginning with comment 516971
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
don't throw so much hw at OpenBSD...
by sergio on Fri 4th May 2012 03:34
in reply to "RE: Comment by marcp"
Throw better hardware at it - that's what the "big guys" with the pockets full of money typically do. :-)
I love OpenBSD and its rock solid simplicity but It's not an ideal OS for big servers.
IMHO OpenBSD is perfect for embedded solutions, firewalls, log servers and other small footprint and very focused tasks (running on small hardware or VMs).
For bigger generalistic projects FreeBSD and GNU/Linux are better options.
RE: don't throw so much hw at OpenBSD...
by dbolgheroni on Fri 4th May 2012 14:14
in reply to "don't throw so much hw at OpenBSD..."






Member since:
2006-10-08
I think you might be trapped into an understanding problem here. Allow me to explain:
OpenBSD organizes "additional software" by its ports collection (similar to what the other BSDs do). There is "the OS" (which is OpenBSD) and there is "additional applications". Those are managed by maintainers and typically ported over from Linux land. Especially in GUI applications you can see that they are quite Linux-centric and may work better "over there". The internationalisation and localisation is a workiing field for the original developers and port maintainers, not the OpenBSD "OS team". The OS can only provide "highest level" selection mechanisms, typically by environmental variables and their control mechanisms. Just to mention a few: There is $LANG, and there are $LC_* for a fine-grained control (LC_ALL, LC_MESSAGES, LC_COLLATE or LC_TIME, just to name a few) which control both language and character set, whereas $LANG only controls language and has a "strange priority relationship" to the other ones.
See the FAQ 10.20 "Character sets and localization":
http://www.openbsd.org/faq/faq10.html#locales
More details can be found in the login.conf manpage:
http://www.openbsd.org/cgi-bin/man.cgi?query=login.conf&sektion=5
Much more details about the language control variables (even though taken from FreeBSD):
http://www.freebsd.org/cgi/man.cgi?query=environ&sektion=7
Additional info:
http://pubs.opengroup.org/onlinepubs/7908799/xbd/envvar.html
It's up to the GUI programs to properly honor the environmental settings (and not overriding them with their own defaults), and it's up to their developers to implement the translation texts properly.
Believe me - I know enough about the problem of bad, missing and partial translation. In Germany, english error messages and the ability not to select "Deutsch" at the very first step of an OS installation is the main reason to drop powerful and versatile systems like OpenBSD. Note that this also covers Linux! In the past, I always experienced Gnome to have a better translation than KDE, for example. But that has nothing to do with the actual OS they're running on. People tend to forget this fact.
I'm using english-only Unix and Linux systems myself (primarily FreeBSD, OpenBSD and Solaris), as I prefer the clear english texts over the sloppy, partially wrong and ugly-looking german translations. The only exception I'm willing to admit is OpenOffice. :-)
You have just learned that those are not developed by the OpenBSD team. :-)
OpenBSD forces coders to be more careful than other Unix or Linux systems may do. Just as an example, if cc -Wall shows anything, the program should be worked on until no more warnings appear. Especially memory management is (due to security reasons) seen as an important aspect. Sloppy coding, compile warnings and runtime messages sadly seem to be typical. They appear more often on systems software is ported to (e. g. more often on OpenBSD than on native Linux).
Throw better hardware at it - that's what the "big guys" with the pockets full of money typically do. :-)