The major version number used to be 1 and the minor number used to indicate a major release. For example, 1.5 and 1.6 were major releases. There was also a third number that was used for fixing bugs, like service packs, 1.6.2 for example.
SMP will never go to 1.6 branch. You have to wait for 2.0 or use current. If you don't like to build current you can download it from releng.netbsd.org.
The reason why such annual reports aren't more common is because they occur once a year. If they were to become more common they would cease to be annual.
Maybe it's vague to say "gnu tools", however, all BSDs use GNU toolchain, that means, cc, as, ld, c++,... stuff required to compile stuff. Of course they might also use other programs from GNU like diff, grep, awk, but I think they could be easily replaced.
Me too, I'm using Mozilla and I'm pretty happy with it so I did not switch to *bird. I like it all integrated. Can't wait to test that about:about thing!
It's too american because they are raising a flag together. I think it's better if people don't consider NetBSD an american software project because developers are all over the world.
The major version number used to be 1 and the minor number used to indicate a major release. For example, 1.5 and 1.6 were major releases. There was also a third number that was used for fixing bugs, like service packs, 1.6.2 for example.
Yes, but if you don't distribute GPL'd code (the library), you aren't bound by GPL.
The problem is of course, that include files are GPL'ed so your program becomes GPL'd even if you don't distribute any of the GPL'd library code
The solution: rewrite your own header files ;)
Could someone type "uname -a" and send results!
It was Bill Sommerfeld. Get the facts straight ;)
Does this mean that OpenBSD's packet filter don't make it to 2.0? Well, I don't worry much because some one will surely port it later.
I'm going to use Firehose, from now on....
SMP will never go to 1.6 branch. You have to wait for 2.0 or use current. If you don't like to build current you can download it from releng.netbsd.org.
The reason why such annual reports aren't more common is because they occur once a year. If they were to become more common they would cease to be annual.
Maybe it's vague to say "gnu tools", however, all BSDs use GNU toolchain, that means, cc, as, ld, c++, ... stuff required to compile stuff. Of course they might also use other programs from GNU like diff, grep, awk, but I think they could be easily replaced.
Me too, I'm using Mozilla and I'm pretty happy with it so I did not switch to *bird. I like it all integrated. Can't wait to test that about:about thing!
It's too american because they are raising a flag together. I think it's better if people don't consider NetBSD an american software project because developers are all over the world.
LOL, you make ML syntax look even more weird than it is!