Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
The Almighty Buck Operating Systems Software BSD

NetBSD Makes Plea for 'Cold, Hard Cash' 34

Posted by timothy from the capitalist-running-dogs dept.
daria42 writes "NetBSD has e-mailed its user community asking for donations. "There are many upgrades we'd like to make to the NetBSD project infrastructure," said the e-mail, "but which we cannot make because, to be blunt, our project is poor. Not poor in innovation nor poor in developer resources nor poor in features -- poor in cold, hard cash, the kind we need to buy hardware that would let us better serve our users." The e-mail pointed out while sister projects OpenBSD and FreeBSD had received tens or hundreds of thousands of dollars in donations, NetBSD had up until now been embarrassed to ask its users for money."
This discussion has been archived. No new comments can be posted.

NetBSD Makes Plea for 'Cold, Hard Cash' More

NetBSD Makes Plea for 'Cold, Hard Cash'

Comments Filter:

  • Dupe! (Score:5, Informative)

    by dorward ( 129628 ) on Tuesday June 14, 2005 @07:15AM (#12811484) Homepage Journal

    We know already [slashdot.org]

  • I donated, what about you? (Score:5, Insightful)

    by plcurechax ( 247883 ) on Tuesday June 14, 2005 @08:39AM (#12812050) Homepage
    While I don't use NetBSD directly, I am confident that I have benefited from the NetBSD project.

    I've already donated $20.00 US, and if 2 in 1000 slashdot readers did the same, they would met their goal and we won't see this story again.
    • www.microsoft.com

      We're all confident that you guys have benefitted from NetBSD as well. I, for one, am no longer interested in the public continuing to fund R&D for the most wealthy company in the world.
      • www.microsoft.com

        We're all confident that you guys have benefitted from NetBSD

        I'm not with Microsoft. I don't know of any NetBSD code in microsoft, of course there is some BSD code in Microsoft's products (tcp/ip stack), at least there was once upon a time.
      • Why not? A lot of companies use GPL software on their websites to run services and make boatloads of profit. How many Fortune 500 companies have benefited from Linux internally? Or GCC? Or numerous other GPLed software which, because they don't distribute it, they haven't provided source code?

        I guess you can take the exclusionist approach or maybe consider that one project's advances will help the whole industry, both commercial and non-commercial without regards to any particular political ideology.
      • Comment removed based on user account deletion
    • Donating money might well fix the problem, but I'm pretty confident that we'll get the story again until the end of time.

      Slashdot should fund this by offering subscribers the ability to block dupes for an extra $2/month, and sending the proceeeds to NetBSD. Of course, we'd probably get articles about that new feature every 2-4 weeks...

    • Re:I donated, what about you? (Score:1, Funny)

      by Anonymous Coward
      they'd get a little more if 1 in 500 donated

  • OK, OK (Score:4, Funny)

    by FullMetalAlchemist ( 811118 ) on Tuesday June 14, 2005 @08:50AM (#12812201)
    OK, OK... I _will_ donate again... :-P

    Thank you Slashdot, dupes in the BSD section; well, at least they post news twise as often.

  • Just like public radio (Score:4, Funny)

    by Intron ( 870560 ) on Tuesday June 14, 2005 @01:10PM (#12815433)
    This story is just like those NPR pledge drives that keep coming around again, asking for money.

  • Trouble is, the VAX port is going nowhere (Score:2, Interesting)

    by Anonymous Coward
    The GCC compiler has recently dropped support for the VAX architecture, so unfortunately, I'm stuck at the current version and probably will stay there until 2038.

    (and no, don't mod me as "funny"...I have a bunch of VAX systems and I run NetBSD on them)

    TDz.

    • Re:Trouble is, the VAX port is going nowhere (Score:1, Interesting)

      by Anonymous Coward
      I am unfamiliar with all this, my understanding is the VAX is an old arch and isn't that fast the cases also look fair big from a couple of googles.

      In terms of cubic centimeter volume of the cases and power consumption - what are *your* personal reasons for still having a "bunch of VAX systems". Nostaligia?

      I mean, I am serious, if you can get a A64 3000+ to outperform them (I dunno if it can, but I assume so, moores law vs how old they are) and put it in a nice case and have low power consumption at a ver
      • The reason is stability. VAX machines are stable beyond belief. They just plain last. They might not be the most powerful computers per watt, but for applications where reliability and extreme uptimes are required, you go with a VAX.

        Indeed, I'd hate to see a Pentium 4 desktop used for any mission critical function. What do you do when the CPU fan dies and the system shuts down (assuming it doesn't melt, like some AMD CPUs), and now the core temperature of your local nuclear power plant isn't being monitore

        • Re:Stability, reliability, quality. (Score:1, Insightful)

          by Anonymous Coward
          "What do you do when the CPU fan dies and the system shuts down"

          I take three of those Pentium 4 "desktops" in redundancy so I'm even better than you with your single point of failure no matter how VAX is it.
          • Redundancy doesn't solve the problem of inherent low quality. Great, now you've got four systems which have a high probability of failure, in addition to the added complexity of handling off responsibilities when a failure does occur. In your effort to remove a single point of failure, you have instead introduced many more such failure points!
            • Redundancy doesn't make the individual low quality systems any more reliable, but it does help out the reliability of the system as a whole.

              Let's say you have a server which is 90% reliable (or unavailable 10% of the time).

              If you have two such servers working in redundant cluster, then you will only have an outage when both servers are down (p(failure) = 0.1 * 0.1 = 0.01). In other words, you've gone to 99% availability.

              By adding a third server, you go to 99.9% availability (etc).

              Clustering *does* add

        • I'd hate to see a Pentium 4 desktop used for any mission critical function.

          In general, when you pay extra for server-rated x86 hardware compared to desktop hardware, you're getting a case designed for rack mounting and better airflow, and you're getting more reliable fans.

          What do you do when the CPU fan dies and the system shuts down

          When the fan dies on an Intel Pentium 4 processor, the thermal diode kicks in and cuts the CPU down to 50 percent utilization, making passive cooling safe. Or you can

          • Indeed, server-quality x86 hardware is a slight improvement. But it still offers reliability and durability nowhere near that of true VAX technology. There are still unfortunate quality problems to deal with, even if the airflow is slightly better.

            Clustered solutions only serve to bring in more points of failure than single, extremely reliable solutions. Now you have to guarantee that the hand-off code and hardware is reliable. Soon enough you'll need to introduce redundancy there. And then you'll need to
        • Nuclear power plants dont use VAXen to control reactors.
        • There are definitely ways of making a farm of x86 servers very reliable - see google, for instance.
    • So, there is a VAX sitting on the floor of the Computer Club's room at my college (and a bunch in a rack too), which is there for people to work on independant maintenance of GCC. I think that it is running either NetBSD 1.6.2 or NetBSD 2.0, and has open access for people who work on NetBSD/vax and GCC/vax. The info about the vaxen for the guy who maintains them is at vaxpower.org [vaxpower.org].
    • I just asked one of the maintainers and he said that a.out support has been dropped, but that vax support itself has not been dropped.

  • Diversification is needed (Score:5, Funny)

    by suitepotato ( 863945 ) on Tuesday June 14, 2005 @04:08PM (#12817478)
    They should convince hot naked chicks to wear BSD demon temporary tattoos and then sell the pics. Instant hit with geeks. Money comes in.
    • Seriously though, I bet some sexy PG pics on t-shirts and coffee mugs, sold via something like Cafe Press might work. A hot babe with one of those skimpy little halloween costumes that get trotted out on halloween should do the trick -- little satin horns, red bikini, tail, pitchfork, and a smile.

      There is apparently no shortage of sexy she-devil costumes [google.com].

      If NetBSD doesn't jump on this chance, some other open source project will, undoubtedly.
  • I think that giving to a charity or good cause such as the NetBSD project is an excellent way to spend some money. I donated blood to the Red Cross for the victims of the earthquake because it was something that needed to be done. NetBSD has served its thousands of users for years. I think that we should all pitch in a little to help them out.

  • Seriously tho (Score:3, Interesting)

    by william_w_bush ( 817571 ) on Saturday June 18, 2005 @06:13PM (#12853303)
    If you have are an admin, or your company uses linux or anything please donate. So much of the cross-architecture, and device driver support for the BSD's and linux comes from NetBSD you'd be surprised. I gave 50 just cause I remember back in the day when they were the only group to support my old SGI Indigo2, and they still lead in most wierd architecture support.

    If you have a wierd or rare architecture they probably support it, or have something that can be hacked to work, and that kind of resourcefulness is why we aren't all running windows 3.3, TPM Borg edition.
    • Do you have examples of specifically which cross architecture and device drivers in Linux come from NetBSD?

      The only drivers I'm aware of that came directly from BSD are the ncr53c8xx driver and aic7xxx. And those came from FreeBSD.

      Some code in various drivers were written after peeking at BSD driver code, but the same goes for BSD peeking at linux driver code.

      And AFAIK none of the cross architecture code in Linux is taken from NetBSD. If you have specific examples I'd be interested to see it.

      FWIW it loo

Slashdot Top Deals

To be awake is to be alive. -- Henry David Thoreau, in "Walden"

Close