×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

NetBSD 4.0 Has Been Released

ScuttleMonkey posted more than 6 years ago | from the so-long-and-thanks-for-all-the-stacks dept.

Operating Systems 121

ci4 writes to tell us that NetBSD 4.0 has been released and has been dedicated to the memory of Jun-Ichiro "itojun" Hagino. "Itojun was a member of the KAME project, which provided IPv6 and IPsec support; he was also a member of the NetBSD core team (the technical management for the project), and one of the Security Officers. Due to Itojun's efforts, NetBSD was the first open source operating system with a production ready IPv6 networking stack, which was included in the base system before many people knew what IPv6 was. We are grateful to have known and worked with Itojun, and we know that he will be missed. This release is therefore dedicated, with thanks, to his memory."

cancel ×
This is a preview of your comment

No Comment Title Entered

Anonymous Coward 1 minute ago

No Comment Entered

121 comments

SLASHDOT SUX0RZ (-1, Troll)

Anonymous Coward | more than 6 years ago | (#21753792)

_0_
\''\
'=o='
.|!|
.| |
download Mass Effect for linux here [goatse.ch]

Some actual information (3, Informative)

Anonymous Coward | more than 6 years ago | (#21753918)

Major achievements in NetBSD 4.0 include support for version 3 of the Xen virtual machine monitor, Bluetooth, many new device drivers and embedded platforms based on ARM, PowerPC and MIPS CPUs. New network services include iSCSI target (server) code and an implementation of the Common Address Redundancy Protocol. Also, system security was further enhanced with restrictions of mprotect(2) to enforce W^X policies, the Kernel Authorization framework, and improvements of the Veriexec file integrity subsystem, which can be used to harden the system against trojan horses and virus attacks.

Holy Shit. (0)

Anonymous Coward | more than 6 years ago | (#21753840)

Sad to hear about itojun. This is the first time i've heard of this news.
Anyone know how he passed away?

Re:Holy Shit. (-1, Troll)

morgan_greywolf (835522) | more than 6 years ago | (#21753978)

Sad to hear about itojun. This is the first time i've heard of this news.
Anyone know how he passed away?
I heard he caught something from BSD, which, as Netcraft confirms, is dying.

Re:Holy Shit. (2, Insightful)

trybywrench (584843) | more than 6 years ago | (#21754018)

Sad to hear about itojun. This is the first time i've heard of this news. Anyone know how he passed away?

yeah you'd think that would be in the summary.

I knew nothing of him but rest in peace and thanks for all the hard work

Re:Holy Shit. (3, Interesting)

Anonymous Coward | more than 6 years ago | (#21754160)

http://www.itojun.org/resume.html [itojun.org] ... too many activies to summarize from my limited head.

Re:Holy Shit. (0)

Anonymous Coward | more than 6 years ago | (#21754318)

http://www.itojun.org/resume.html ... too many activies to summarize from my limited head.

Impressive! Are they sure it wasn't Karoshi [wikipedia.org]?

Re:Holy Shit. (1, Insightful)

Anonymous Coward | more than 6 years ago | (#21756074)

It could be that that nobody outside his family knows, but more likely I think the cause of death is being kept quiet. People have been asking since he died ... alway met with curious silence on the issue. I think at the point, the respectful thing to do is not to ask.

Google Cache Reveals Cause of Death (2, Informative)

h4ck7h3p14n37 (926070) | more than 6 years ago | (#21757614)

I did a little digging and determined that it was almost certainly suicide. I found two blog posts from a google search on Itojun and noticed that the Google cache version was dated one day prior to the date listed on the blog posts. I then discovered that you can actually retrieve old text from the Google cache version of a page by tweaking your search query over and over. I determined that the two bloggers had deleted paragraphs from each of their posts talking about the cause of death, Itojun's mental health problems and his recent decent into depression.

To see what I'm talking about, check these search results [google.com] and then compare the page that's being linked. You'll notice it's dated the 31st and the paragraph from the search results has been deleted. If you then perform queries using text from the search result snippet you can reveal more and more of the deleted text. For example, like this [google.com].

I'm a bit conflicted about posting the cause of death since multiple people took the trouble to attempt to delete that information from public view, but I figure that people will find this technique at recovering deleted information quite useful. I have recovered the complete text from each blog post, but am not going to post that information. If you care that much, you can figure it out for yourself.

Re:Google Cache Reveals Cause of Death (0, Insightful)

Anonymous Coward | more than 5 years ago | (#21759644)

It probably is because of the cultural taboo's about suicide , both western and possibly japanese.

It's sad that suicide is seen as shameful instead of bringing attention to mental illness , especially depression and how it affects people. I suffer from double depression so I know how hard it can be and it's something I've had to confront and face about my illness. I've had differing reactions to it over the years. It's sad to lose another person to the horrible illness of depression. It's such a hard illness to battle since it saps your will.

I've tried to be open about my depression in my life so people who haven't experienced it, can begin to understand it. So others who experience it can be more open without the shame and when those who haven't experienced it they can be open about it too. Hopefully this will help save some people from suicide.

RIP Itojun

Re:Google Cache Reveals Cause of Death (0)

jd (1658) | more than 5 years ago | (#21759698)

If that is the case - and I've no reason to question your investigative technique - then this was not only tragic but probably needless. Depression isn't always treatable, but in many cases it is, provided it is spotted quickly enough, the doctors get the meds (if any) correct fast enough (it's a complex process), provided the person is assisted as necessary in keeping with the regimen, and provided the person gets additional assistance in figuring out what (if anything) external is triggering or worsening the condition.

Hey, that's no small deal, but it can be done and is done. Those who have chronic, clinical depression and have both neutralized it in the short-term and are working to minimize or eliminate the underlying factors in the long-term deserve medals of honor. It's hard work and it's often expensive work. It is, nonetheless, doable work.

It is wrong to blame anyone who kills themselves. It is also wrong to blame those who might have ben able to step in. It is, however, entirely appropriate to ask how things could have gone so far and what factors - including perhaps cultural - that led to this outcome rather than another.

Science and technology have far too many tragic heros - people who have contributed much but died far too young for whatever reason. It is not the fault of their subject - science isn't toxic - but if we merely cry for the individuals and then do nothing different, all we will end up with is more people, exceptional extraordinary people, dying far too young, with far too much to still offer the world. (Not that anyone dying young is good, but there is a qualitative difference when it's someone who is working to make some sort of difference. There aren't many of them.)

Re:Holy Shit. (3, Informative)

Anonymous Coward | more than 6 years ago | (#21754020)

Responding to my own post, apparently he was fighting a long illness and did not make it. Gathered from comments at undeadly [undeadly.org].
See also http://www.wide.ad.jp/news/press/20071031-itojun-e.html [wide.ad.jp]

Jeez. The guy was a good guy. Very upset that he is no longer with the community. RIP.

Re:Holy Shit. (0)

Anonymous Coward | more than 5 years ago | (#21759588)

Half true. He committed suicide -- he suffered from depression.

Re:Holy Shit. (0)

Anonymous Coward | more than 6 years ago | (#21754172)

He put too much power into the Kame-hame-ha.

Yes! (5, Funny)

angryfirelord (1082111) | more than 6 years ago | (#21753856)

Time to upgrade my toaster!

Re:Yes! (-1, Troll)

workdeville (1166127) | more than 6 years ago | (#21753900)

Let's face it. Not only is BSD dying, its lead developers are too.

Re:Yes! (-1, Flamebait)

angryfirelord (1082111) | more than 6 years ago | (#21754146)

Well, not really. True, a lot of the developers have left the three major projects (FreeBSD lost 93% of its core developers), but I wouldn't say it's dying. If a package or new driver is developed in one BSD, it usually gets ported to the other two. For example, OpenBSD started pf and NetBSD helped FreeBSD with its alpha port. (correct me if I'm wrong)
Oh, and to show you what I mean: http://video.google.com/videoplay?docid=7833143728685685343&q=BSd+is+dying&total=5&start=0&num=10&so=0&type=search&plindex=0 [google.com]
http://www.freebsd.org/advocacy/myths.html [freebsd.org]

Re:Yes! (4, Funny)

TheRaven64 (641858) | more than 6 years ago | (#21754248)

FreeBSD lost 93% of its core developers
Do you have any kind of source for that? The FreeBSD core team consists of 9 people, so losing 92% of them would mean losing 8.37 of them, which doesn't really make sense.

Re:Yes! (2, Insightful)

ByOhTek (1181381) | more than 6 years ago | (#21754400)

or it once had 128 or 129 devs...

*shrug* Given the way the last two releases have progressed, and the fact that it's been a while since the releases have been anywhere remotely on schedule, it wouldn't surprise me if they took a huge dev hit.

Personally, I don't care how popular my OS is, as long as it gets the job done, and does it well. So for for me, FreeBSD does that.

Re:Yes! (1)

timeOday (582209) | more than 6 years ago | (#21754584)

Well, since the issue of popularity (and probably an ensuing flame war) are inevitable, I might as well ask what advantages NetBSD kernel has over the Linux kernel (meaning the Linus tree)?

Re:Yes! (1)

TheRaven64 (641858) | more than 6 years ago | (#21754626)

If you're only counting Linus' tree then the most obvious benefit NetBSD has over Linux is Xen support (domU and dom0). That's not really a fair comparison though; comparing NetBSD to something like Fedora would make more sense.

Re:Yes! (1)

arivanov (12034) | more than 6 years ago | (#21755134)

Easier to port onto a toaster :-)

On a more serious note it tends to be more stable on the more obscure architectures. Its internal guts are also considerably cleaner so it is easier to get going on various specialised platforms.

It is more of "it ain't fancy, but it works and does exactly what it says on the tin" philosophy compared to Linux.

I always keep a tree around (and a freebsd one) for a reference so I can look up how some things are implemented at the low level. You cannot do that with linux (or god forbid Slowarez) without arming yourself with a couple of aspirins and a bottle of vodka.

Re:Yes! (2, Informative)

TheRaven64 (641858) | more than 6 years ago | (#21756014)

I always keep a tree around (and a freebsd one) for a reference so I can look up how some things are implemented at the low level. You cannot do that with linux (or god forbid Slowarez) without arming yourself with a couple of aspirins and a bottle of vodka.
I'd agree with Linux, but the Solaris code is often very, very clean. The parts I've looked at have been close to OpenBSD standard, which is the most readable kernel I've come across.

Re:Yes! (0)

Anonymous Coward | more than 5 years ago | (#21762030)

Are you serious? You're also the one who made the completely unsubstantiated claim that NetBSD is more portable than Linux (which I refuted and you had no answer to). So you seem like a troll.

So, what evidence do you have to back up this new claim? Here's something interesting. Both Solaris and Linux are recently implementing NUMA text replication. This is what the diff looks like for Solaris:

http://hg.genunix.org/onnv-gate.hg/rev/1b5c93035912 [genunix.org]
  28 files changed, 2508 insertions(+), 314 deletions(-)

And this is what the Linux one looks like:

http://marc.info/?l=linux-kernel&m=118552585814804&w=2 [marc.info]
18 files changed, 812 insertions(+), 61 deletions(-)

So the Linux implementation is like 1/3 the size and touches 50% fewer files.

So, why is it that you say Solaris is cleaner than Linux? I doubt you've even read the code.

Re:Yes! (2, Interesting)

mi (197448) | more than 5 years ago | (#21762500)

I'd agree with Linux, but the Solaris code is often very, very clean.

Solaris kernel may be clean. Solaris' user-space programs, however, are a disaster. For example, even in the most-modern Solaris 10:

  • awk could still complain about "input line too long"
  • vi which would allow multiple editing sessions of the same file and, also, complain about "screen too wide"
  • the castrated /bin/sh (no wonder, Sun's own scripts use /bin/ksh!)
  • find, which does not have the -print0
  • make that can't parallelize jobs
  • no out-of-the-box locate
  • ftp-client has no line-history/editing
  • etc., etc., etc.

Maybe, all of these utilities have a really clean source, of course. Cleanliness is not sufficient, however — it is merely required. The common solution to the above-listed problems is to install GNU versions of the utilities — which brings in all that ugly-but-functional code we are complaining about... It is also done differently by every sysadmin, so portable scripts can't rely on it...

If you want out-of-the-box functionality and clean source code, you want a BSD operating system. Be that Net, Open, Free, or DragonFlyBSD. Or even MacOS.

Re:Yes! (0)

Anonymous Coward | more than 5 years ago | (#21763372)

it's not a kernel, it's an operating system.

checkout a copy and read LINT if you want to see device driver support.

Re:Yes! (1)

syntaxeater (1070272) | more than 6 years ago | (#21754814)

This might be slightly OT, but since you seem to be the only one on this article not posting flamebait/troll responses and are experienced with FreeBSD - do you have any good resources/links you can share? Maybe recommend a book or two? I downloaded the iso's from FreeBSD.org a few weeks ago. I also read through the beginner's guide and some of the doc. Everything sounds good so far, and I plan on continuing to move to FreeBSD despite what's been said.

Re:Yes! (1)

sremick (91371) | more than 6 years ago | (#21755068)

The 2nd edition of Michael Lucas' "Absolute FreeBSD" just came out. I haven't had a chance to go through the 2nd edition though, but the 1st ed was very good. This would make it the most-up-to-date FreeBSD book currently available. Other older ones I can recommend are FreeBSD Unleashed, The Complete FreeBSD, and FreeBSD: The Complete Reference.

Re:Yes! (4, Informative)

ByOhTek (1181381) | more than 6 years ago | (#21755186)

I was nervous to - I had so many Linux users tell me how bad it was, that it was harder to use and learn than Linux, etc.

I found it wasn't the case. The more you have experience coding and building from source in Linux, the better off you'll be, but here goes:

(1) I didn't buy any books or anything, I had a friend who was into FreeBSD tell me about it. She gave me a few hints and tips on how to start and what to avoid. She said I should try it since I'd rather use Windows than Linux, and it'd be nicer for me to use a FOSS OS if I could. I listened, and tried, and was hooked on the OS within a day of installing it.

So the best resource you can have is a friend who knows what he or she is doing (or at least has a bit more of a clue than you).

(2) The handbook is your friend. under /usr/share/doc/en/books/handbook/index.html is the system documentation. You can look at it on the freebsd website under the handbook section. It is actually EXTREMELY useful, and fairly well written/comprehensive. Unless you are looking for VPN stuff, they you're sporked.

(3) The Mailing list and it's archives are invaluable. Don't worry, the people there don't eat babies or penguins (if they did, I wouldn't use the OS, I have a friend who I love to hang out with who'd never speak to me again if I talked to people who ate penguins!). Actually they are a friendly and easy going bunch. They don't like people picking on them for their OS choice, but they don't mind people preferring different OSes. If you have a question, let them know your background when you ask, so they can better tailor the advice. You'll be asked to read some stuff, but they'll tell you what you need to read, and not just give you a blind RTFM. Heck, one user recently said he wanted to migrate to Linux, and asked which distro would be easiest for a FreeBSD user, no flames came.

(4) The errors are typically useful, and if you read them, they'll point you to a file or directory that's a problem. Using that you can figure out if something needs to be edited, deleted, etc. When making packages, if something is described as "marked" (ex. "Marked as broken on AMD64", or described as "conflicts", it is the packages make file, and you may need to modify that (or find another package that does the same thing, usually there are hints, but not always). You can sometimes find documentation related to these files either in the man pages for the program that uses them, or with the file name itself. Sometimes the error messages will actually tell you what to type or give you options on what to do to fix the problem - they don't fix it automatically because they'd assume you'd rather chose the fix option rather than have the choice made for you.

More practical (basically the advice my friend gave me, aside from the location of the handbook):

1. Until you are confident in your ability to get your system up to the poing of getting a web browser out to the internet from a fresh install (read: have done it at least once), only install freebsd if you have a system you can access the internet from, preferrably while running freebsd (i.e. install FreeBSD to a virtual machine, or on a spare computer).

2. I've found that the non-minimal installs tend to be a bit confused in their setup. I just do a minimal install, and install everything else manually. Read up on the section about partitioning your disk, FreeBSD does this in an odd manner, and you'll want to be familiar with it.
2.1. Ports - Compiling your own stuff
2.1.1. Familiarize with "csup", under /usr/share/examples you'll not run this often, but it updates your ports tree. typically you just type "csup -g -L 2 [path to supfile]", there's a sample supfile in the /usr/doc/examples directory somewhere, probably in a csup or cvsup directory, and the man page is fairly useful. In fact, most BSD man pages are (weird). They usually have good examples.
2.1.2. to build a package, go to /usr/ports, find the package within there (may need to csup first), and then go to the package directory (to find a package try 'make search key="package"' in there). In the directory of the package type 'make install' (this will install everything in any directory below, so make sure it is only in that directory. ex: if you do this in /usr/ports/shell, it will make and install every shell, this usually has bad results).
2.1.3. I'd suggest setting the environmental variable "BATCH" to "yes" initially, so it doesn't prompt you for configuration, until you are comfortable with everything.
2.1.4. Later you'll learn about the portupgrade utility, and that might help you out a bit too.
2.2. Packages - let someone else compile it.
2.2.1. Get the package name (usually can be obtained from the ports tree, /usr/ports, if you've csuped and have the full ports tree), and type 'pkg_add -r [PACKAGE NAME]', ex 'pkg_add -r bash' would be one of my first moves. The '-r' tells it to download the package if there isn't a copy available on system. This should also fetch dependancies.

Sorry, a bit OT/TMI, but I figure it's good to start with the basics. That's a bit more than I had to go on, but hopefully it'll be enough to let you make your own decision on if FreeBSD is right for you, or if you want something else.

Re:Yes! (1)

syntaxeater (1070272) | more than 6 years ago | (#21755418)

Good info - thanks.

A friend would have been helpful. Unfortunately, everyone I know (work with) now-a-days is Windows/Mac. I'm venturing into this one alone I'm afraid.

One last quick question. How complicated is it to get into port development? One of the driving factors for reaching out is hobby development. I've been stuck doing vb.net for 4 years now (pays the bills...) and miss my days with C. If I were to shoot myself in the lower body; am I more likely to lose a toe, foot or leg?

Re:Yes! (1)

ByOhTek (1181381) | more than 6 years ago | (#21755638)

I've not done much ports development (read any), but with the helpfulness of the mailing lists (and they are nice, even I'll admit I ask some pretty inane questions, and they are never rude), and what I've seen in the documentation, developing ports (applications) is not hard unless the original application (if you are porting and not writing from scratch) isn't well written.

Porting the entire OS, if that's what you mean, I dunno, I've never done that :-)
I stick with i386 and AMD64.

Re:Yes! (1)

syntaxeater (1070272) | more than 6 years ago | (#21755744)

Oh no, that's not what I mean. I just meant basic application development (ie. Hello World, Snake Game, etc.) from scratch. I'll check out the mailing list and look into a couple of the books that have been suggested by others here.

Thanks all.

Re:Yes! (1)

ByOhTek (1181381) | more than 6 years ago | (#21755984)

Oh, you can access any language.

Once that is done, there's a fairly simple process to get it into the ports tree (if it's distribution worthy), someone usually makes sure it isn't obscenely bug ridden and will compile, at which point it is out to the public.

Though the ability to compile may eventually be lost over time (see: boson)

Re:Yes! (1)

coryking (104614) | more than 6 years ago | (#21759278)

I see what you are asking. Okay... think like this:

1) You are writing an application that will run on unix. This means make; ./configure; make install. This means writing code that doesn't assume a specific compiler (people targeting linux are notorious for assuming gcc exists). This means you are distributing a source code tarball that looks and works just like all the other source code tarballs you are used to working with.
2) You happen to be offering it to FreeBSD users with a port. Ports are nothing but scripts that know how to interact with your make file. They are makefiles that script how to interact with a package's makefiles. The port makefile says "here is where to download the source code, here is how to unpack it, here is a list of everything that gets installed, here is how to call ./configure, here are the arguments for ./configure, here are some patches, and here is where I want you to install it"

Take a look at the ports tree. There are some doozies in there like apache, perl or php so avoid them at first. Look at how some silly app is installed via a port and copy it for now. If you are writing a language library (like a CPAN module) make sure to see how others install CPAN modules, same with PEAR modules.

Make sure to read the porters handbook [freebsd.org] too! On FreeBSD, there is actually good documentation to work with so enjoy your new OS :-)

Remember, you aren't writing a program for freebsd. You are writing a program for unix, and you are writing a wrapper to install it on freebsd.

Good luck!

Re:Yes! (1)

coryking (104614) | more than 6 years ago | (#21758904)

Allow me to state that all of the port maintainers I've interacted with are very friendly and helpful. I've had some of my ports and port patches sucked into the mainline ports tree in under 24 hours.

I love FreeBSD. It is a great community that values stability over flashiness and features. Everything is documented as a man page, and if you get lost, FreeBSD.org is your portal (as apposed to linux, where the question "where do I even start" is a big one).

My only fear is that people try to turn FreeBSD into something that competes with linux "for the desktop". As far as I'm concerned, FreeBSD is the perfect OS for a server and trying to "go for the desktop" can only load it up with baggage for graphics, sound and other things that doesn't matter for servers.

So, my ebay rating for FreeBSD?
A+++++++++++++++ Would use Again!

Re:Yes! (1)

ByOhTek (1181381) | more than 5 years ago | (#21763614)

Except the ports tree makes it a perfectly acceptable desktop.

x11/kde*, x11/gnome*, x11-wm/xfce4, editors/open-office*, emulators/wine*, www/firefox*, audio/*xmms*, multimedia/*(xmms|ogle|mplayer|vlc)*

That pretty much covers a nice desktop right there

Re:Yes! (1)

Brandybuck (704397) | more than 6 years ago | (#21756096)

I'm not sure what you mean by "port development", but in terms of learning programming, Unix is the way to go.

All the tools you need are included in FreeBSD. Get some familiarity with the command line and shell, and learn a good non-GUI text editor like vi or emacs. GUI editors are great, but being able to edit a file over an ssh connection is an invaluable skill. The other tools you need, like make, gcc, etc., are included in the basic install.

FreeBSD has a programming book included. Really! It's called "FreeBSD Developers' Handbook", and it's online at . It's also installed along with FreeBSD. Some of the stuff is specific to FreeBSD, but there's a lot in it that's general to C programming on any Unix platform. Once you are comfortable with the command line and a good text editor, start going through this handbook.

Re:Yes! (1)

TheRaven64 (641858) | more than 6 years ago | (#21756148)

A few things I'd add:
  • You say 'Read up on the section about partitioning your disk, FreeBSD does this in an odd manner, and you'll want to be familiar with it.' This highlights an important difference between BSD and Linux. Linux tries to look like the most common operating system on the platform in question. On x86, this means that it uses the DOS partition scheme and system call convention. BSDs tend to try to make every machine look the same. Understanding this difference in philosophy will help a lot of things make sense.
  • The recommended way of updating the ports tree is now portsnap, not csup (actually, it was never csup; csup was written after portsnap). Doing 'portsnap fetch update' will grab the latest version of the ports tree without any configuration files being needed.
  • Install portupgrade. It is much, much easier to use for installing and updating packages than doing everything with the ports tree manually. I'd also recommend portaudit if the machine is Internet-facing or multiuser.

Re:Yes! (0)

Anonymous Coward | more than 6 years ago | (#21757846)

I was nervous to -

To what? Clue me in here.

Re:Yes! (1)

Liquid Len (739188) | more than 5 years ago | (#21762240)

Thanks for the info. Just out of sheer curiosity, what sparked your decision to migrate from Linux to BSD ?

Re:Yes! (1)

ByOhTek (1181381) | more than 5 years ago | (#21763574)

Actually, it was from Windows to BSD. Linux never made me feel it was worth migrating to. It always took more time to install applications not set up with the base system, and administrate it than to actually get stuff done. With FreeBSD, I got into the hang of things quickly, and found that in a week, with the documentation and useful error messages it gave, I could do more with FreeBSD than I could with my previous years on Linux when I had to use it.

Re:Yes! (4, Insightful)

coryking (104614) | more than 5 years ago | (#21759412)

You'll love it here. We are chill.

The folk behind FreeBSD are all just professional people trying to get real work done. You will not find your next religion when you use FreeBSD. Nor will you find saints who preach to you about how you should and should not use your computer. Nor will you find people telling you how you should and should not value your labor.

We dont give a shit if you like Vista. We dont care make FreeBSD work with your Windows Server. We dont care if you embed FreeBSD in your Tivo or Playstation. We are more than happy if you take our code and use it in your TCP/IP stack. Seriously. Take our code! No strings attached!

And hey, we all have to eat here in FreeBSD-land and so do you! We don't care if you make money from what comes out of your brain. Many of us are programmers whose livelihood depends on selling the value of our brain. We dont preach to you about the evils of intellectual property. If you sell software, the more power to you! If you become the next Microsoft, sweet!

And at the end of the day, FreeBSD works. It is the most boring OS you'll ever find. It is about as exciting as your water heater. And that is the best part about it.

Re:Yes! (3, Funny)

eclectro (227083) | more than 6 years ago | (#21756086)

so losing 92% of them would mean losing 8.37 of them, which doesn't really make sense.
It does if you make him get a haircut and shave.

Quality vs. quantity (1)

mi (197448) | more than 5 years ago | (#21763012)

The FreeBSD core team consists of 9 people, so losing 92% of them would mean losing 8.37 of them, which doesn't really make sense.

The loss of a single man — Matt Dillon [wikipedia.org], who went on to found DragonFlyBSD [dragonflybsd.org] — was devastating. He is not only quite bright, but also energetic and somehow able to devote a lot of time to the open-source software development.

His being expelled — over an exasperated comment in a cvs-commit — was highly unfortunate in my not-so-humble opinion...

Holy crap, they've removed Sendmail... (4, Interesting)

Saint Aardvark (159009) | more than 6 years ago | (#21753868)

...and replaced it with Postfix. Sendmail's still available from pkgsrc, but it's no longer the default. Man, never thought I'd see the day when one of the BSDs finally did this...

Re:Holy crap, they've removed Sendmail... (2, Insightful)

morgan_greywolf (835522) | more than 6 years ago | (#21754036)

'bout frickin' time!

Look, the rest of the world has moved on to Postfix, which is much smaller and less bloated than sendmail, easier to configure, and, most importantly, a ton more secure.

Why have the BSDs taken so long to realize this simple fact of life?

1. I've used Postfix on NetBSD since 2000 or so (-1, Flamebait)

Anonymous Coward | more than 6 years ago | (#21754232)

2. Your posts suck. Choke on a cursed greased meatstick.

Re:1. I've used Postfix on NetBSD since 2000 or so (2, Interesting)

morgan_greywolf (835522) | more than 6 years ago | (#21754390)

1. Good for you. I'm talking about what comes installed by default, not what you can install yourself after the fact. And, yes, it matters, because people, even experienced, seasoned, veteran administrators are likely to use what's installed by default rather than install something extra manually. It's usually the path of least resistance.

2. I'm sorry you don't like my posts. I tend to make a lot of jokes with heavy, sarcastic humor and it's one of those things that either people love or they hate. Most of my funny posts get moderated either up to +5, Funny, or down to -1, Troll or Flamebait. One man's humour is another man's troll. Go figure. *shrug* On my more serious posts, I say exactly what I think. You don't like it? Disagree with me? Okay, I don't care. I think it's more important to say you what you really think than it is to say something that's popular and/or likely to be modded up.

Re:Holy crap, they've removed Sendmail... (3, Informative)

Just Some Guy (3352) | more than 6 years ago | (#21754984)

Why have the BSDs taken so long to realize this simple fact of life?

Well, in the case of OpenBSD, it's because they've gone over the Sendmail code with a fine-toothed comb and patched up any problems they found along the way. It's pretty well vetted by people who care intensely about such things. Therefore, replacing Sendmail with anything else would be a case of the devil you know being better than the devil you don't.

Re:Holy crap, they've removed Sendmail... (1)

Fweeky (41046) | more than 6 years ago | (#21757440)

Why have the BSDs taken so long to realize this simple fact of life?
Well, *I* think the colour of the bikeshed should be exim^Wblue!

Or maybe the base system should just not come with an MTA. Keep that stuff in ports where it belongs.

Re:Holy crap, they've removed Sendmail... (1)

MavEtJu (241979) | more than 6 years ago | (#21758906)

Or maybe the base system should just not come with an MTA. Keep that stuff in ports where it belongs.

You need something to deliver your daily/weekly/monthly run logs, cron output, alerts etc to the right person.

But as you know, installing GREEN!^Wpostfix from the ports collection is hardly rocket science if you take all the default settings, plus that it can be updated without having to worry that an system upgrade will put everything back to an ancient version.

Re:Holy crap, they've removed Sendmail... (2, Interesting)

Anonymous Coward | more than 6 years ago | (#21754060)

...and replaced it with Postfix. Sendmail's still available from pkgsrc, but it's no longer the default. Man, never thought I'd see the day when one of the BSDs finally did this...

As a reference, sendmail is still good. But given the lack of desire of the maintainers of sendmail to be more proactive in anti-spam and further development of SMTP, many people have switched to Postfix. I view this as a highly progressive move.

I switched my systems to postfix last year. Love it. Even though I mastered the sendmail.cf/mc so my understanding of sendmail, above average even in complex routing and multiple domains/rewriting. I am not looking back, postini is superior.

Leave it to where the intelligence is, BSD is far from dead because of contributions that "itojun" Hagino and others make. It is why other OSes follow and do not lead.

----
MS: You say you run Windows?
Tech: Yep, sure do, X-Windows.

Walmart (-1, Offtopic)

Anonymous Coward | more than 6 years ago | (#21753870)

You recommended Walmart? ::shudder::

Your money is like your vote. You should only give it to the people you'd like to have it.

Walmart has done as much to advance the conservative agenda in America as any Congressman or Senator has, yet people who would never vote for the right-wing facists queue up every day to give their money to one.

Re:Walmart (0, Offtopic)

ericrost (1049312) | more than 6 years ago | (#21754226)

Yes, but do you feel target, best buy, circuit city, or any of the other corporate fascist masters we can choose are better in any material way? We must choose to live either on the grid or off.

If you're on the grid, people who you don't like are getting your money. Think BP/Shell/Texaco or your local monopolistic power company are filled with joyful liberals? Think the local water/sewage/waste disposal companies are your best friend?

Life is full of choices. Sometimes its what you can get, not who you're giving it to that is the deciding factor.

Re:Walmart (1)

Brandybuck (704397) | more than 6 years ago | (#21756230)

If you're on the grid, people who you don't like are getting your money.

Why should I care? As long as I give my money to them voluntarily through uncoerced economic transactions, it's not longer my money, it's theirs. I gave it to them. On the other hand, if I dislike them so much that I have to rant on Slashdot about it, then I shouldn't be doing business with them to begin with. As the doctor says, if it hurts to do that then don't do that!

Re:Walmart (1)

ericrost (1049312) | more than 6 years ago | (#21757066)

Yes, but is it uncoerced if the item you're buying is a necessity and you have no other choice because of a government protected monopoly?

Re:Walmart (1)

Brandybuck (704397) | more than 5 years ago | (#21760308)

I am against all government protected monopolies. I am also against any government privileges given to businesses. In such situation the economic transaction itself may not be coerced, but others in the economy definitely are. If a business can't compete without the heavy handed fist of government helping them, then they need to get out and make room for someone else who can.

Major Changes Between 3.0 and 4.0 (5, Informative)

NeoManyon (953080) | more than 6 years ago | (#21753928)

Major achievements in NetBSD 4.0 include support for version 3 of the Xen virtual machine monitor, Bluetooth, many new device drivers and embedded platforms based on ARM, PowerPC and MIPS CPUs. New network services include iSCSI target (server) code and an implementation of the Common Address Redundancy Protocol. Also, system security was further enhanced with restrictions of mprotect(2) to enforce W^X policies, the Kernel Authorization framework, and improvements of the Veriexec file integrity subsystem, which can be used to harden the system against trojan horses and virus attacks. Please read below for a list of changes in NetBSD 4.0.

http://www.netbsd.org/releases/formal-4/NetBSD-4.0.html [netbsd.org]

Major Changes Between 3.0 and 4.0

The complete list of changes can be found in the CHANGES and CHANGES-4.0 files in the top level directory of the NetBSD 4.0 release tree. Some highlights include:
Networking

        * agr(4): new pseudo-device driver for link level aggregation.
        * IPv6 support was extended with an RFC 3542-compliant API and added for gre(4) tunnels and the tun(4) device.
        * An NDIS-wrapper was added to use Windows binary drivers on the i386 platform, see ndiscvt(8).
        * The IPv4 source-address selection policy can be set from a number of algorithms. See "IPSRCSEL" in options(4) and in_getifa(9).
        * Imported wpa_supplicant(8) and wpa_cli(8). Utilities to connect and handle aspects of 802.11 WPA networks.
        * Imported hostapd(8). An authenticator for IEEE 802.11 networks.
        * carp(4): imported Common Address Redundancy Protocol to allow multiple hosts to share a set of IP addresses for high availability / redundancy, from OpenBSD.
        * ALTQ support for the PF packet filter.
        * etherip(4): new EtherIP tunneling device. It's able to tunnel Ethernet traffic over IPv4 and IPv6 using the EtherIP protocol specified in RFC 3378.
        * ftpd(8) can now run in standalone mode, instead of from inetd(8).
        * tftp(1) now has support for multicast TFTP operation in open-loop mode, server is in progress.
        * tcp(4): added support for RFC 3465 Appropriate Byte Counting (ABC) and Explicit Congestion Notification as defined in RFC 3168.

File systems

        * scan_ffs(8), scan_lfs(8): utilities to find FFSv1/v2 and LFS partitions to recover lost disklabels on disks and image files.
        * tmpfs: added a new memory-based file system aimed at replacing mfs. Contrary to mfs, it is not based on a disk file system, so it is more efficient both in overall memory consumption and speed. See mount_tmpfs(8).
        * Added UDF support for optical media and block devices, see mount_udf(8). Read-only for now.
        * NFS export list handling was changed to be filesystem independent.
        * LFS: lots of stability improvements and new cleaner daemon. It is now also possible to use LFS as root filesystem.
        * vnd(4): the vnode disk driver can be used on filesystems such as smbfs and tmpfs.
        * Support for System V Boot File System was added, see newfs_sysvbfs(8) and mount_sysvbfs(8).

Drivers

        *

            Audio:
                    o Support for new models on drivers such as Intel ICH8/6300ESB, NVIDIA nForce 3/4, etc.
                    o Added support for AC'97 modems.
                    o auich(4): added support to handle the AC'97 modem as audio device, enabled with the kernel option "AUICH_ATTACH_MODEM".
                    o azalia(4): added support for S/PDIF.

        *

            Hardware Monitors:
                    o amdpm(4): added support for the i2c bus on the AMD-8111 used on many Opteron motherboards and for the Analog Devices ADT7464 hardware monitor chip.
                    o adt7467c(4): new driver for Analog Devices ADT7467 and ADM1030 hardware monitor chips.
                    o ipmi(4): new driver for motherboards implementing the Intelligent Platform Management Interface 1.5 or 2.0, from OpenBSD.
                    o it(4): new driver for iTE 8705F/8712F and SiS 950 hardware monitors.
                    o The lm(4) driver was rewritten and support for more chips was added, for example for Winbond W83627HF, W83627THF, W83627DHG and Asus AS99127F.
                    o owtemp(4): new driver for the 1-Wire temperature sensors.
                    o tmp121temp(4): new driver for the Texas Instruments TMP121 temperature sensor.
                    o ug(4): new driver for Abit uGuru hardware monitor found on newer Abit motherboards.

        *

            Miscellaneous:
                    o geodewdog(4): new AMD Geode SC1100 Watchdog Timer driver.
                    o gscpcib(4): new AMD Geode SC1100 PCI-ISA bridge that provides support for the GPIO interface.

        *

            Networking:
                    o ath(4): updated HALs with support for WiSOC (AR531x) and 32bit SPARC.
                    o bge(4): added support for the following chips: BCM5753, BCM5753M, BCM5715, BCM5754, BCM5755 and BCM5787. Numerous improvements and bugfixes were made too.
                    o kse(4): new driver for Micrel KSZ8842/8841 PCI network cards.
                    o msk(4): new driver for Marvell Yukon 2 GigE PCI network cards, from OpenBSD.
                    o nfe(4): new driver for NVIDIA nForce Ethernet network cards, from OpenBSD.
                    o ral(4): new 802.11 driver for PCI/Cardbus Ralink RT2500, RT2501, RT2600, RT2661 and RT2500 USB chipsets, from OpenBSD.
                    o rum(4): new 802.11 driver for USB Ralink RT2501 and RT2601 chipsets, from OpenBSD.
                    o sip(4): now works on sparc64.
                    o tlp(4): added support for ASIX AX88140A and AX88141.
                    o vr(4): added support for the VIA Rhine III.
                    o wm(4): added support for i8003, ICH8, ICH9 and others. Support for IPv6 Rx TCP/UDP Checksum Offloading and more.
                    o wpi(4): new driver for Intel PRO/Wireless 3945ABG PCI 802.11 network cards, from OpenBSD.

        *

            Security:
                    o glxsb(4): new driver for the AMD Geode LX AES Security Block that provides random numbers and AES acceleration, from OpenBSD.

        *

            Power Management:
                    o Support for Intel Speedstep SMI on PIIX4 PCI-ISA for i386.
                    o Support for AMD PowerNow and Cool'n'Quiet Technology on K7 and K8 CPUs (both in 32 and 64 bit mode), including Athlon Mobile, Athlon64, Opteron or X2. See options(4) for more information.
                    o Support for more Enhanced Speedstep CPUs, including VIA C7/Eden and Intel Core Solo/Duo/Duo2. See options(4) for more information.
                    o The Enhanced Speedstep and PowerNow drivers were modified to be able to be scaled in all CPUs available, saving power on SMP systems.

        *

            Storage:
                    o ahcisata(4): new driver for AHCI 1.0 and 1.1 compliant SATA controllers.
                    o ataraid(4): added support to handle Adaptec HostRAID and VIA V-Tech software RAID.
                    o ciss(4): new driver for HP/Compaq 5th+ generation Smart ARRAY controllers, from OpenBSD.
                    o fdc(4): added support for SBus based sparc64 machines and fixed formatting on sparc.
                    o gcscide(4): new driver for the AMD Geode CS5535 Companion Device IDE controller.
                    o jmide(4): new driver for JMicron Technology JMB36x PCIe to SATA II/PATA controllers.
                    o mfi(4): new driver for LSI Logic and Dell MegaRAID SAS controllers, from OpenBSD.
                    o mpt(4): added support for newer SAS and similar devices.
                    o njata(4): new driver for Workbit NinjaATA-32 CardBus IDE controller.
                    o pdcsata(4): added support for the Promise PDC20775, PDC20771, PDC40518, PDC40718 and some bugfixes.
                    o piixide(4): added support for some ICH8/ICH8-M/ICH9 IDE and SATA controllers.
                    o svwsata(4): new driver for Serverworks K2 SATA controllers, from OpenBSD.
                    o viaide(4) added support for the VIA VT8237A SATA controller and AMD CS5536 Companion Device IDE Controller.

        *

            USB:
                    o ucycom(4): new driver for Cypress microcontroller based serial devices.
                    o uipaq(4): new driver for the iPAQ devices.
                    o uslsa(4): new driver for Silicon Labs CP210x series serial adapters.
                    o utoppy(4): new driver for the Topfield TF5000PVR range of digital video recorders.

Platforms

        *

            i386:
                    o Added support for the for Multiboot specification. This means much improved support for loading the kernel by GRUB, including passing in parameters to the kernel.
                    o Added the unichromefb framebuffer driver that supports the VIA Unichrome Graphics adapter.
                    o vesafb(4): added new framebuffer driver that supports VESA BIOS (VBE) 2.0 extensions and up.
                    o Added ability to boot from the cd9660 file system to the BIOS bootloader. This adds the ability to load much bigger kernels and the option of selecting different kernels at boot time.

        * evbarm: new platform support for Arcom Viper PXA255-based single board, Atmark Techno Armadillo-9 and Armadillo-210, Certance CP-3100, Linksys NSLU2 (a.k.a. "Slug") and I-O DATA HDL-G Giga LANDISK NAS devices.
        * evbmips: added support for Alchemy Au1550 processors, DBAu1550 boards, Alchemy Au15XX PCI host, (OMS-AL400/128) and Atheros AR5312 SoC.
        * New port ews4800mips: NEC's MIPS based EWS4800 workstations.
        * cobalt: added support for booting off raidframe RAID1 mirrors.
        * hpcmips: added the teliosio(4) driver for the Sharp Telios LCD screen and Battery unit.
        * New port landisk: port to the SH4 processor based NAS appliances, supporting models by I-O DATA (USL-5P, HDL-U, HDL-AV, HDL-W and HDLM-U series, SuperTank LAN Tank, UHDL-160U and UHDL-300U) and Plextor PX-EH16L, PX-EH25L and PX-EH40L.
        * macppc: this port has gained support to use accelerated wsdisplay drivers by default (if possible), and uses the appropriate driver rather than the Generic Open Firmware Framebuffer.
        * prep: this port has been modernized, and support for five additional machines has been added, among them the IBM 7024-E20 and 7025-F30 models and Motorola Powerstack E1. Additionally, sysinst support was added, and the bootloader process was improved, allowing easy installation and upgrade to future releases.
        * sparc: added support for booting off raidframe RAID1 mirrors.
        * Xen: support for Xen3 domU and dom0 (Unprivileged domain and domain 0), including support for hardware virtualization on CPUs that support it.

Kernel subsystems

        * Improved Firewire (IEEE1394) support imported from FreeBSD.
        * The midi(4) framework got a complete overhaul for better support of Active Sensing and improved handling of tempo and timebase changes.
        *

            Added a Bluetooth protocol stack including:
                    o hardware drivers: ubt(4) for USB controllers, and bt3c(4) for the 3Com Bluetooth PC-Card.
                    o socket based access to the HCI, L2CAP, RFCOMM and SCO protocols.
                    o pseudo drivers for integrating services on remote Bluetooth devices such as Keyboards, Mice and SCO Audio into the NetBSD device framework.

            See bluetooth(4), bthset(1) and btpin(1).
        * Imported the bio(4) framework from OpenBSD, to query/control block hardware RAID device controllers. Currently supporting the mfi(4) driver.
        * Kernel uses stateful read-ahead algorithm.
        * dkctl(8) can be used to switch buffer queuing strategies on the fly on wd(4) disks, see also bufq(9).
        * fileassoc(9) is used by Veriexec, it adds in-kernel and file-system independent file meta-data association interface.
        * firmload(9): an API for loading firmware images used by various hardware devices.
        * gpio(4): imported General Purpose I/O framework from OpenBSD.
        * onewire(4): imported Dallas Semiconductor 1-wire bus framework from OpenBSD.
        * The proplib(3) protocol was added for sending property lists to/from the kernel using ioctls.
        * spi(4): new SPI (Serial Peripherial Interface) framework.
        * timecounter(9) adds a new time-keeping infrastructure along with NTP API 4 nanokernel implementation. Almost all platforms were changed to support this API.
        * Start of 32bit-Linux-emulation for amd64 (COMPAT_LINUX32).
        * wscons(4) console driver supports splash screens, scrolling, progress bar for kernel and boot messages.

Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue.
Security

        * The FAST_IPSEC IPsec implementation was extended to use hardware acceleration for IPv6, in addition to the hardware accelerated IPv4 that was available before. See fast_ipsec(4) for more information.
        * mprotect(2) got restrictions to enforce W^X policies, from PaX. See options(4), sysctl(3), and paxctl(1).
        * GCC 4's support for stack smashing protection (SSP) was enabled by adding libssp, see security(8).
        *

            The kernel authorization framework kauth(9) was added, replacing the traditional BSD credential management and privileged operation access control with an abstract layer, allowing the implementation of various security models either as part of the NetBSD distribution or as third-party LKMs.

            NetBSD's kernel authorization is a hybrid clean-room implementation of a similar interface developed by Apple, extending its capabilities and combining concepts of credential inheritance control.

Userland

        *

            3rd party software updates:
                    o BIND 9.4.1-P1
                    o OpenSSL 0.9.8e
                    o CVS 1.11.22
                    o OpenSSH 4.4
                    o gettext 0.14.4
                    o PF from OpenBSD 3.7
                    o (n)awk 20050424
                    o Postfix 2.4.5
                    o am-utils 6.1.3
                    o file 4.21
                    o zlib 1.2.3
                    o GNU binutils 2.16.1
                    o GNU groff 1.19.2
                    o IPFilter 4.1.23
                    o GNU gcc 4.1.2 prerelease
                    o GNU gdb 6.5 (some architectures)
                    o NTP 4.2.4p2
                    o pppd 2.4.4

        * cdplay(1): added digital transfer mode support.
        * cksum(1) can now verify checksums.
        * csplit(1): new utility that splits a file into pieces. From FreeBSD/OpenBSD.
        * identd(1): added support for forwarding ident queries and receiving of proxied ident queries.
        * getent(1): added support for the ethers database.
        * gkermit(1): new program for transferring files using the Kermit protocol.
        * mail(1): added support for Mime and multi-character set handling, command line editing and completion.
        * utoppya(1): new utility to interface to the utoppy(4) driver.
        * init(8): added support for running multi-user in a chroot() environment. Allows / file system on e.g., cgd(4), vnd(4) or ccd(4) volumes.
        * gpt(8): new GUID partition table maintenance utility, from FreeBSD.
        * iSCSI target (server) code added, see iscsi-target(8); Initiator (client) code is underway.
        * lockstat(8): new command to display a summary of kernel locking events recorded over the lifetime of a called program.
        * ofctl(8): new command to display the OpenPROM or OpenFirmware device tree for the macppc, shark and sparc64.
        *

            Various utilities to support Bluetooth were added:
                    o btconfig(8) for controller configuration.
                    o btdevctl(8) to manage pseudo devices relating to remote services.
                    o bthcid(8) and btpin(1) for authenticating radio connections.
                    o sdpd(8) for providing service discovery to remote devices.
                    o sdpquery(1) for querying services on remote devices.
                    o rfcomm_sppd(1) to access remote services over RFCOMM via stdio or pty.
                    o bthset(1) for making connections to Bluetooth headsets.

Besides this list, there have also been innumerable bug fixes and other miscellaneous enhancements of course.

Re:Major Changes Between 3.0 and 4.0 (5, Funny)

Anonymous Coward | more than 6 years ago | (#21753980)

Major achievements in NetBSD 4.0 include support for version 3 of the Xen virtual machine monitor...

Ah, so it does run Linux. I was going to ask.

Re:Major Changes Between 3.0 and 4.0 (2, Informative)

TheRaven64 (641858) | more than 6 years ago | (#21754362)

The new bluetooth stack from NetBSD has now been ported to DragonFly BSD and OpenBSD, so others benefit from this work, not just those running NetBSD. Looking through the new features list, I see a lot of things that I recognise from both OpenBSD and FreeBSD, so the sharing goes both ways.

NetBSD is, I believe, the second kernel to officially support running as a Xen 3 Domain 0 guest. Both Solaris and NetBSD have been able to do this in prerelease versions for quite a few months, but I believe NetBSD is the first to release it officially. (The first kernel overall was Linux, although the Xen patches are still not in the main kernel.org tree).

Re:Major Changes Between 3.0 and 4.0 (1)

demon (1039) | more than 6 years ago | (#21755312)

Does it support PAE this time? I'm not seeing anything in the release notes, so I'm guessing the answer is "no"; unfortunately if it doesn't, that makes it (still) useless to me. I'd love to run NetBSD in a Xen domU, but all my production Xen hosts use PAE - 4 GB on a VM host box is just not enough, and NetBSD's continued dogged insistence that PAE is an ugly hack (yes, it is, but that's *beside* the point) is getting really obnoxious. I'd just go with the x86_64 Xen kernel, except that they don't even have an x86_64 Xen-enabled kernel yet...

Re:Major Changes Between 3.0 and 4.0 (1)

dgatwood (11270) | more than 6 years ago | (#21754796)

...many new device drivers and embedded platforms based on ARM, PowerPC and MIPS CPUs.

Translation: now it really does run on your toaster... and your refrigerator.

Re:Major Changes Between 3.0 and 4.0 (1, Interesting)

Anonymous Coward | more than 6 years ago | (#21758256)

Am I the only one that read this and thought, "hmmm, should have just said, 'imported OpenBSD.' Since really, a huge number of the items are from OpenBSD." It really caught me off guard that so much of what is listed here is just imported from OpenBSD, did an OpenBSD developer write the list, and just downplay the in-NetBSD developed stuff? And if you're going to import OpenBSD stuff, why not get a recent PF version, 3.7 is what, two releases a year, we're on 4.2 now, so two and a half years old. A two and a half year old version of PF? I mean, every release should see an update to PF to keep it on par with OpenBSD's version.

Oh Boy! (5, Funny)

Anonymous Coward | more than 6 years ago | (#21754002)

An OS that supports more platforms than it has users.

Re:Oh Boy! (0)

Anonymous Coward | more than 6 years ago | (#21754622)

LMAO.
That beats the "And all 12 users are rejoicing!" post I was planning. Nicely done.

Re:Oh Boy! (1)

filterban (916724) | more than 6 years ago | (#21754634)

NetBSD is a great OS. I've used it since version 2 and it really has improved dramatically. I've found it to be very, very useful in resurrecting old hardware, and it also runs great on current platforms, too.

NetBSD's support of so many hardware architectures speaks something about how it's designed, if you ask me. No other OS I know of supports even 1/2 as many architectures as NetBSD.

Re:Oh Boy! (1)

99BottlesOfBeerInMyF (813746) | more than 6 years ago | (#21754868)

Oh Boy! An OS that supports more platforms than it has users.

Oh Boy! Another user that doesn't know what OS's he's using. If your firewall isn't running NetBSD, and your gateway router isn't, and you don't own any appliances that run NetBSD, the chances are your internet packets, at least are making their way through one or more NetBSD boxes. NetBSD has plenty of users, it's just most of them don't know they are users because they use NetBSD systems as black boxes.

Re:Oh Boy! (1)

MrWeelson (948337) | more than 6 years ago | (#21756058)

Viewing websites that use Apache doesn't mean I'm an Apache user. The only soft/hardware I use are those directly under my control, my XP PC, my Linux PC, my router and so on.

Re:Oh Boy! (1)

onefriedrice (1171917) | more than 5 years ago | (#21761340)

I think it's quite apparent from the context he was using that he meant user in the sense that you are using the OS, which is accurate whether you made the black box or not. If you're using the router (or whatever), you are using NetBSD in the sense of the word that he used. Either way, it also becomes quite obvious that _somebody_ is using NetBSD, and as it turns out (like the GP pointed out), many people are using NetBSD, in the traditional sense.

Re:Oh Boy! (1)

shnizep (1192389) | more than 6 years ago | (#21756648)

On top of that I've noticed NetBSD running on iSCSI SAN hardware :) *cough* EqualLogic, which is damn reliable, and who knows else what hardware.

Netcraft is dead (2, Funny)

Anonymous Coward | more than 6 years ago | (#21754076)

this new release of NetBSD confirms it.

Netcraft confirms: *BSD is dying (-1, Redundant)

Anonymous Coward | more than 6 years ago | (#21754136)

It is official; Netcraft confirms: *BSD is dying

One more crippling bombshell hit the already beleaguered *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 [samag.com] in the recent Sys Admin comprehensive networking test.

You don't need to be a Kreskin [amdest.com] 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.

FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

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 *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

Fact: *BSD is dying

Both users (-1)

Anonymous Coward | more than 6 years ago | (#21754174)

I'm sure both of NetBSD's users are happy now... oh, wait, one of them died...

Since wide user base seems to be your preferred (4, Funny)

ByOhTek (1181381) | more than 6 years ago | (#21754212)

metric in OS worth...

How are you liking your Windows install? Just curious.

Re:Since wide user base seems to be your preferred (3, Funny)

Monsuco (998964) | more than 6 years ago | (#21754312)

How are you liking your Windows install? Just curious.
Ugh, mines horrible, it lets in a draft and the screen fell out. Next time I will just get a contractor.

Re:Since wide user base seems to be your preferred (1)

Kadin2048 (468275) | more than 5 years ago | (#21762126)

Well, I don't know why you'd want one in the first place; it's not like you get much of a view in that mine.

Elegy for *BSD (-1)

Anonymous Coward | more than 6 years ago | (#21754294)

Elegy For *BSD

I am a *BSD user
and I try hard to be brave
That is a tall order
*BSD's foot is in the grave.

I tap at my toy keyboard
and whistle a happy tune
but keeping happy's so hard,
*BSD died so soon.

Each day I wake and softly sob
Nightfall finds me crying
Not only am I a zit faced slob
but *BSD is dying.

Had something to say about IPv6 (0, Redundant)

Seismologist (617169) | more than 6 years ago | (#21754376)

I had something cleaver an witty to say about "production ready IPv6 networking stack" note for the BSD 4.0 release, but it has escaped me. Thus, I'll let others do that for me...

OpenBSD (2, Informative)

cachimaster (127194) | more than 6 years ago | (#21754512)

If i'm not mistaken, the OpenBSD 4.2 release was also dedicated to Jun-Ichiro "itojun" Hagino, it was a big loss for the BSDs.

A *BSD Xmas Carol (0, Funny)

Anonymous Coward | more than 6 years ago | (#21759088)

"Spirit," said Scrooge, with an interest he had never felt before, "tell me if *BSD will live."

"I see a vacant seat," replied the Ghost, "in the poor chimney-corner, and a crutch without an owner, carefully preserved. If these shadows remain unaltered by the Future, *BSD will die."

"No, no," said Scrooge. "Oh, no, kind Spirit! say it will be spared."

"If these shadows remain unaltered by the Future, none other of my race," returned the Ghost, "will find him here. What then? If it be like to die, it had better do it, and decrease the surplus operating system population."

Scrooge hung his head to hear his own words quoted by the Spirit, and was overcome with penitence and grief. It was sad to see any operating system die, even one so obviously flawed and useless as *BSD.

God bless us, every one.
Load More Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Sign up for Slashdot Newsletters
Create a Slashdot Account

Loading...