If I were to publish anything under the FDL, I would rely upon the fact that there is *one*FDL - the one I decided to use, not a modified version 'John Smith' came up with.
You are suggesting to allow anybody to relicense the work of others - which is unacceptable. If I wanted to do that, I'd put the document in the Public Domain. The FDL is about protecting the intellectual property of the author, and therefore must not be modified in its basic sense.
A. Line-by-line security audit of *everything* that goes on the CD.
Not completely true!
Only the OpenBSD OS and a portion of the Ports & Packages that are on the CD are audited. The majority of the Ports are just that: working Ports of the respective Software. Just want to make sure that people (new to OpenBSD) installing third party software (like Ports) are not left alone with a false believe of security.:) However, running insecure software on a secure OS could potentionally reduce the effect, but it remains dangerous, nevertheless.
Major Kudos to the OpenBSD team - a job very well done!
Slashdot Mirror
Red Hat release numbers indicate the version of the C library (for binary-compatibility) - like so:
Doing so would render the license itself useless!
If I were to publish anything under the FDL, I would rely upon the fact that there is *one* FDL - the one I decided to use, not a modified version 'John Smith' came up with.
You are suggesting to allow anybody to relicense the work of others - which is unacceptable. If I wanted to do that, I'd put the document in the Public Domain. The FDL is about protecting the intellectual property of the author, and therefore must not be modified in its basic sense.
Not completely true!
Only the OpenBSD OS and a portion of the Ports & Packages that are on the CD are audited. The majority of the Ports are just that: working Ports of the respective Software. Just want to make sure that people (new to OpenBSD) installing third party software (like Ports) are not left alone with a false believe of security. :)
However, running insecure software on a secure OS could potentionally reduce the effect, but it remains dangerous, nevertheless.
Major Kudos to the OpenBSD team - a job very well done!