MidnightBSD 0.1 is now available. It includes several software packages such as ksh, sudo, OpenNTPD, gcc 3.4.4, BIND 9.3.4 (plus patch), and others in the base system. "MidnightBSD is a desktop operating system for x86 compatible, and soon amd64 compatible architectures. It was originally based on FreeBSD 6.1 Beta. The goal of the project is to create a BSD with ease of use and simplicity in mind."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-09-27
Umm, I was talking about the licensing issue, not security. My point is, If you include a proprietary program in your system, you can't take anything from its code, period. If you include GPL'd programs, in the *worst* case you can't take anything from its code and you have to treat it as if it were proprietary. You can argue that GPL'd code is more risky than BSD-licensed code, regarding licensing issues, but not more risky than proprietary code, except in the sense that proprietary code is not *risky*, it's worst-case from the beginning.
Member since:2006-01-14
Ah, that is a little more clear. I totally agree with your statement. I'm personally not a huge fan of the GPL and would prefer not to use anything that is licensed such. Obviously this would be quite an impossible task though. I know that someone brought up the ideas of browsers, which is a big one but there are other more pressing issues, such as a compiler.
Member since:
2006-01-14
I believe that person was talking about the licensing issue and not the security of the code. There are many pieces of GPL code that are both created with security in mind and increase security on a given system. The issue he was trying to make is that GPL code can completely change the licensing model which BSD systems prefer to use. While GPL is great and has its place, we prefer BSD code in our system whenever possible. Personally, I would stay away from all proprietary drivers...