NetBSD 8.0 Released (netbsd.org)
Slashdot reader fisted quotes NetBSD.org: The NetBSD Project is pleased to announce NetBSD 8.0, the sixteenth major release of the NetBSD operating system.
This release brings stability improvements, hundreds of bug fixes, and many new features. Some highlights of the NetBSD 8.0 release are:
— USB stack rework, USB3 support added.
— In-kernel audio mixer (audio_system(9)).
— Reproducible builds
— PaX MPROTECT (W^X) memory protection enforced by default
— PaX ASLR enabled by default
— Position independent executables by default
[...]
NetBSD is free. All of the code is under non-restrictive licenses, and may be used without paying royalties to anyone.
This release brings stability improvements, hundreds of bug fixes, and many new features. Some highlights of the NetBSD 8.0 release are:
— USB stack rework, USB3 support added.
— In-kernel audio mixer (audio_system(9)).
— Reproducible builds
— PaX MPROTECT (W^X) memory protection enforced by default
— PaX ASLR enabled by default
— Position independent executables by default
[...]
NetBSD is free. All of the code is under non-restrictive licenses, and may be used without paying royalties to anyone.
I remember using NetBSD and FreeBSD back in the day for my first web servers. Good stuff. The only thing I use it for now is my NAS.
Nothing at all wrong with NetBSD. Runs on about everything. Been using it off and on since 1998. I prefer OpenBSD because it works better on laptops generally and has pf as a native program, but NetBSD is outstanding for embedded work and actually ran and runs some stuff for the space program. A phenomenal OS for small stuff.
I ran it forever in the 1990s and into the late 2000s. Super stable and it's so nice having a bare OS adding in only the things you need.
Only the State obtains its revenue by coercion. - Murray Rothbard
I continue to be impressed by NetBSD's multiplatform support. Even as Linux has retreated from older architectures, NetBSD keeps support alive.
...a Beowulf cluster of NetBSD 8.0s running?
I was curious since I'd never heard of this problem before (or even had a clue of what the problem was about). I was led to this blog post, which is quite interesting. The issue is having the same source tree always build an identical cdrom. On the surface it sounds simple, but a surprising amount of work was needed to make it happen, all detailed in the blog post. I can't help but admire the obsessive perfectionism that won't leave the problem alone until it is completely resolved.
Stop posting spam about your software. Your post has nothing to do with the topic of this article, which is the release of NetBSD 8.0. You deserve to be modded down. Spam like this is a big part of why you have so many problems with other users of this site. Also, I don't see any reason why you couldn't already run your software on NetBSD and FreeBSD, since they have Linux binary compatibility. OpenBSD used to as well, though I don't believe it does any longer. Also, if you really want your software to be used by BSD users, you'd be better off releasing it as an open source tool and maintaining it in the ports collection.
Also, there are open source alternatives to your software such as Steven Black's hosts file software that seems to do exactly the same thing your software does. Also, Steven Black's software is written in Python and is cross-platform, so there's no need to maintain separate versions for Windows, Linux, and MacOS. The documentation suggests that software could run provide the same functionality on iOS and Android. It could run on *BSD right now without any difficulty. The fact that this software is cross-platform and open source seems to provide substantial advantages over yours.
A hosts-based blacklist may be a useful component for securing a system, including a *BSD system. However, there are high-quality, open source, cross-platform solutions that already exist. If you want to implement a hosts-based blacklist on *BSD, I suggest taking a look at the software I linked to.
NetBSD just received USB 3.0 support just now?
I had to check that. FreeBSD has had it since 2011.
Kriston
Rather than actually addressing the issues I raised in my post, you've turned to personal attacks almost instantly. Part of your post is pretty damn incomprehensible. However, I can honestly say I've never moderated any of your posts, either up or down. Your post is offtopic and it is spam, so I feel no sympathy for you that it will probably be modded to -1.
However, I'm going to focus on the technical issues.
1) You've bragged that you have the second largest hosts file in existence, blocking every ad server there is. While the part about blocking every ad server seems dubious, there's another issue. The software I linked to aims to limit the size of the hosts file in order to maintain performance. That's why hphosts isn't included. If your file is as large as you claim, surely that adversely affects performance.
2) Why do you even need a separate *BSD version? This just doesn't make sense. As I pointed out, many of the BSDs already have binary compatibility with Linux. If all you're doing is writing a file to /etc/hosts, why would you need a separate *BSD version at all? NetBSD and FreeBSD have binary compatibility with Linux, so shouldn't your closed source software already run under Linux?
3) Alternatively, why not open the source to your software and maintain it as part of the ports collection? That's a really nice feature of the BSDs, and would likely increase the use of your software.
4) Why is your software better than what I linked to in my previous post? The functionality seems to be the same, except that the software I linked to is open source and already cross-platform. You've claimed the GUI is an advantage of your software, but I disagree. It would probably be better to run the software as a daemon or a cron job, possibly with an optional GUI frontend. Rather than hurling personal attacks as you've opted to do, perhaps you should explain why your software is an improvement over what's already been released.
What does USB3 have to do with gaming?
Normally, I don't respond to ACs, but...it just so happens that in the late '90s/early '00s, I was working at Intel and attended a Linux Summit at the mothership.
ESR, Linus Himself, etc. were there and I had the chance to talk with Linus at the end of the talks and we discussed this very issue.
I posited that the GPL license, which "forces" changes to be available vs the BSD license which "allows" changes to be available, would - ultimately - cause the Linux ecosystem to grow more rapidly than the BSD side.
He disagreed, but with no vehemence, and I suspect that he somewhat agreed, but didn't want to push that aspect of it.
He and ESR both gave really compelling talks - great experience!
Nobody needs an Unix-like system without systemd anymore.
It is official; Netcraft confirms: NetBSD is dying
One more crippling bombshell hit the already bleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. NetBSD is the most endangered of them all, having lost 93% of its core developers.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that NetBSD has steadily declined in market share. NetBSD is very sick and its long term survival prospects are very dim. If NetBSD is to survive at all it will be among OS dilettante dabblers. NetBSD continues to decay. Nothing short of a cockeyed miracle could save NetBSD from its fate at this point in time. For all practical purposes, NetBSD is dead.
Fact: NetBSD is dead
For some reason, this article is under linux.slashdot.org rather than bsd.slashdot.org. How come?
True, but APK is losing his fucking mind right now.
I've noticed in the past week that quite a few folks have taken the time to write him meaningful replies, possibly because no-one wants blood on their hands when the guy goes completely over the edge and jumps off a bridge.
Yes APK, everyone of these posts that is critical of you is from the same fucking person. Different styles, different wording, different grammar, different posting pattern. But every fucking one is from the same person. Actually it seems more likely that you are the one who is fucking nuts and paranoid. Just because you spend every waking hour trying to spam slashdot with your bullshit engine as much a possible doesn't mean everyone else does. Maybe you can tell us all about your zuckerberg theories instead.
Reproducible builds is a highlight? OMG. That really worries me that at this stage in the game that's a highlight. RedHat was doing that with Linux over two decades ago. Hell, even Microsoft has been doing that for years.