Slashdot Mirror


OpenBSD SMP In The Works

Cajal writes "Four students at the University of Waterloo are working to add SMP support to OpenBSD as part of the Spinlocks project. More information is available in a story at the OpenBSD Journal's site. They expect to have an initial working MP kernel in January."

259 comments

  1. The problem with OpenBSD.. by Karamchand · · Score: 2, Offtopic

    ..is that I can never decide to buy a CD set because everytime I think wait one release, the next one will have new feature xxx included!! (Where xxx is some new pf feature, or systrace, or SMP, or....

    1. Re:The problem with OpenBSD.. by Lxy · · Score: 0, Flamebait

      Buying a copy of OpenBSD seems fundamentally flawed.

      Isn't it the OpenBSD folks who are telling people not to make ISOs because the codebase changes frequently enough? Why would you purchase a set of discs to perform multiple installs when OpenBSD developers recommend against using a static copy?

      Sure, I can understand buying copies to support OpenBSD. I buy Redhat for the same reason, it's more principle than the actual material in the box. It sounds like you're buying it to actually have a set of BSD discs. It just seems flawed to me. I'd rather grab a fresh snapshot off OpenBSD's servers each install to make sure I'm getting all the latest features.

      --

      There is no reasonable defense against an idiot with an agenda
      :wq
    2. Re:The problem with OpenBSD.. by Anonymous Coward · · Score: 0

      So, I think you can just contribute some reasonable amount of cash to the project and then download the releases and make your own CDs.

    3. Re:The problem with OpenBSD.. by jfedor · · Score: 5, Insightful

      It doesn't matter which CD set you buy, what's important is that the project gets the money.

      You can always get the latest release by FTP.

      So why don't you just buy the current release now.

      -jfedor

    4. Re:The problem with OpenBSD.. by jfedor · · Score: 5, Informative

      Isn't it the OpenBSD folks who are telling people not to make ISOs because the codebase changes frequently enough?

      No.

      Perhaps you are confused by this.

      Why would you purchase a set of discs to perform multiple installs when OpenBSD developers recommend against using a static copy?

      They don't. OpenBSD releases come at regular 6 months intervals (3.2 was a month early). That's what you should be using. You can use the snapshots or even the current CVS if you feel brave.

      Sure, I can understand buying copies to support OpenBSD. I buy Redhat for the same reason, it's more principle than the actual material in the box.

      You are correct. There's a slight difference, though, OpenBSD is not trying to turn a profit, just cover the development costs.

      -jfedor

    5. Re:The problem with OpenBSD.. by Anonymous Coward · · Score: 0

      No, you're thinking of OsbourneBSD.

    6. Re:The problem with OpenBSD.. by Anonymous Coward · · Score: 0

      Or donate!

    7. Re:The problem with OpenBSD.. by evilviper · · Score: 3, Informative

      Well, you could always donate a few bucks instead. More than that, if you buy a 3.2 CD (latest), then you get a CD with the full sources, and when 3.3 is released, all you'll need to do is update your source tree via CVS, then build it. The bandwidth used to update is rather slim.

      But on the subject, the chances are slim to none that SMP will be stable and secure enough that it will be included in the next release, so you don't need to procrastinate this time. I haven't yet heard of major improvements fore 3.3 (except the altq & pf merge) so it will be mostly bug-fixes, and performance improvements.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  2. Wow! by Jeffrey+Baker · · Score: 5, Funny

    In related news, the Egyptians are on the cusp of discovering Construction, which will allow them to build Aqueduct and Coliseum. However, this is not expected to improve the odds of their feared Chariot against invading Mechanized Infantry.

    1. Re:Wow! by Anonymous Coward · · Score: 0

      You are playing too much Age of Empires.

    2. Re:Wow! by Anonymous Coward · · Score: 0

      Please, get your games correct. That's obviously Civ III.

    3. Re:Wow! by Anonymous Coward · · Score: 0

      s/Age of Empires/Civilization/
      dolt.

    4. Re:Wow! by Anonymous Coward · · Score: 0

      you mean Civilization, dumbass

    5. Re:Wow! by ajs · · Score: 5, Insightful

      Ok, I grant your comment is funny, but I'm a Linux user (and sympathizer :) who grew up on BSD, and it really pains me to think that any OS (Solaris, Linux, HP/UX, etc) needs to be viewed as a competitor to BSD rather than a fellow citizen in the realm of UNIX and UNIX-derived OSes.

      Each has its niche, and while some of those niches wane over time (e.g. SCO, IRIX, DG/UX), others flourish (Linux, FreeBSD, Solaris) and that's a good thing. They continue to flow into the containers that they define, rather than having to attack eachother as many products do.

    6. Re:Wow! by bahwi · · Score: 1

      Why yes. OpenBSD supports FreeCiv Also. =)

    7. Re:Wow! by Anonymous Coward · · Score: 0

      Things compete. That's how the world works. If you want to whine and complain about reality, that's fine and dandy, but don't expect people to change. Just go right on whining.

      BOOOHOOOOO

    8. Re:Wow! by Anonymous Coward · · Score: 0

      So, still pissed off that your boxed was hacked last week, eh?

    9. Re:Wow! by Anonymous Coward · · Score: 0

      Except that Linux is trying to fill everyone's niche. Because of it's openness and growing popularity, I think it can eventually do it.

    10. Re:Wow! by Anonymous Coward · · Score: 0

      But the people that control Linux are not INSANE CONTROL FREEKS like the one(s) that control OpenBDS.

    11. Re:Wow! by Anonymous Coward · · Score: 0

      Slashdot needs to add a "-1 Linux Faggot" rating.

    12. Re:Wow! by Anonymous Coward · · Score: 0

      You're supposed to say the people that control GNU/Linux are not INSANE CONTROL FREEKS....

      Dumbass. Get it right.

    13. Re:Wow! by Anonymous Coward · · Score: 0

      Why is everyone saying IRIX is dying, it makes me feel alone. Hello, is anyone there.

    14. Re:Wow! by Noodlenose · · Score: 2
      Hello, is anyone there.

      Just us nerds..

    15. Re:Wow! by Anonymous Coward · · Score: 0

      Actually, the GPL is all about being an ICF.

  3. Not to be trollish.... by unterderbrucke · · Score: 0, Troll

    But most other OS have had it for a while now. Why has BSD taken so long?

    1. Re:Not to be trollish.... by Anonymous Coward · · Score: 0

      because theo is an idiot. FreeBSD and NetBSD have SMP, theo is too dumb to catch up

    2. Re:Not to be trollish.... by Anonymous Coward · · Score: 1, Interesting

      Theo and the crew were working on matters they consider more important, like making certain the existing code is robust, secure, and correct.

    3. Re:Not to be trollish.... by Tuzanor · · Score: 5, Informative
      Its OpenBSD that has "taken so long". FreeBSD has had SMP for ages now, and until very recently it better scaled than linux's. Keep in mind that NetBSD and FreeBSD forked in the early ninties and both had different priorities. FreeBSD became a stable high performance platform. It only ran on x86 (now alpha, soon to be Ultrasparc and Itanium). They eventually added SMP with other various features.

      NetBSD was more focused on portability. They were aimed at the embeded market (which Wasabi systems is in business in) where there isn't SMP. When Theo forked OpenBSD off of NetBSD they still didn't have it and it still wasn't a priority. Now there is more interest in it, especially now that SMP hardware is becoming so cheap.

    4. Re:Not to be trollish.... by Anonymous Coward · · Score: 0

      > FreeBSD has had SMP for ages now, and until very recently it better scaled than linux's

      are you smoking more of that crack again?

    5. Re:Not to be trollish.... by Anonymous Coward · · Score: 1, Informative

      FreeBSD has had SMP for ages now, and until very recently it better scaled than linux's.

      Really? The smp in FreeBSD doesn't scale anywhere unless you consider one giant global lock to be scaling to a locked up system.

      The smp in FreeBSD right now is on par with linux 2.0, which was a long time ago.

      I will metamod whoever gave this uninformed peice of shit +4 down. Please do the same.

    6. Re:Not to be trollish.... by Anonymous Coward · · Score: 0

      Yawn. I am so sick and tired of annoucements like this being treated as news. So a couple college kids are doing some hacking. BFD. SMP in Unix isn't even worthy of a Master's degree at any decent University anymore. BSD/Linux are completely uninteresting relative to Solaris and the innovation happening there.

    7. Re:Not to be trollish.... by Strog · · Score: 1

      I think by recently they meant 2.4 kernels. FreeBSD would outperform a 2.2 kernel. On paper it shouldn't but real world performance was very good. The problem is that was only on dual boxes. The design employed a giant kernel lock which meant it wouldn't scale up well on 4,8, whatever cpu systems. Sure it would run but it was quickly diminishing returns.

      FreeBSD 5.0 looks great for SMP and has a lot of potential but time will tell as it continues to mature and develop.

  4. Great news by ekrout · · Score: 4, Insightful

    And it makes for a good research project as well.

    But I ask here, as an honest interested person, why one would wait until SMP is correctly and efficiently implemented into OpenBSD when they could simply use any old recent version of Windows or Linux on SMP hardware to get symmetric multiprocessor support for a high-load server?

    I understand that Research -> Products -> Corporate $$$, but is this perhaps too little too late for OpenBSD?

    --

    If you celebrate Xmas, befriend me (538
    1. Re:Great news by bahwi · · Score: 5, Informative

      Because OpenBSD is about security, not the lastest and greatest features. Linux is about the latest and greatest features. Since the economy went south, most of the peopl working on any of the BSD's lost their jobs or were unable to continue working on the BSD's during corporate time. Where the BSD's have corporate backing and private backing, Linux is mostly private backing, i.e. people at home working on it. Again, things are changing, but everyone has their preferences. No one is going to simply give up OpenBSD to go to Linux, if they need SMP, that is the best route. But from OpenBSD's web page:

      "Only one remote hole in the default install, in more than 7 years!"

      So they all have their uses, Linux, FreeBSD, OpenBSD, and NetBSD. =) Live together, work together, don't kill each other.

    2. Re:Great news by jfedor · · Score: 4, Insightful

      But I ask here, as an honest interested person, why one would wait until SMP is correctly and efficiently implemented into OpenBSD when they could simply use any old recent version of Windows or Linux on SMP hardware to get symmetric multiprocessor support for a high-load server?

      Because you like OpenBSD and would like to help them test the SMP-enabled version so that one day it runs properly?

      What's an "old recent version of Windows", BTW? :)

      -jfedor

    3. Re:Great news by Anonymous Coward · · Score: 4, Funny

      MS-DOS - No root exploits, no patches since 1981!

    4. Re:Great news by jfedor · · Score: 5, Funny

      "Only one remote hole in the default install, in more than 7 years!"

      What puzzles me is how they jumped from "nearly 6 years" to "more than 7 years" in less than a year. :)

      -jfedor

    5. Re:Great news by Anonymous Coward · · Score: 0

      Take a look at his posting history. It's troll for "I don't know what the fuck I'm talking about, but I'll still try to cause trouble anyway." And if you like the masturbatory, self-servient attitude he displays here, you'll LOVE his webpage.

    6. Re:Great news by joib · · Score: 5, Insightful

      I'd say the main reason for Linux development continuing rapidly despite the economy is that the Linux market is orders of magnitude larger than the *BSD market, so the distro makers (and other companies who employ Linux kernel hackers) have the money to keep Linux kernel hackers employed.

    7. Re:Great news by jolan · · Score: 1

      It was corrected for accuracy.

    8. Re:Great news by Anonymous Coward · · Score: 0

      Ha ha.

    9. Re:Great news by Anonymous Coward · · Score: 1, Informative

      Because they only update that statement on their web site about twice a year.

      (You're using a sliding reference window while they are looking at an absolute reference--you saw "nearly 6 years" was because they hadn't updated the site in a while. "more than 7 years" is because they did update it recently. Overall time passed from *editing* the main page is less than a year. But the statement is correct because they are looking at the 2nd to last remote hole to figure their time.)

    10. Re:Great news by DAldredge · · Score: 1

      What about all those Kernel Devs that RedHat employees?

    11. Re:Great news by PureCreditor · · Score: 1

      SMP is hardly the "latest and greatest". SMP in OpenBSD is LONG over-due. Can't believe it took Theo THAT LONG to sort out his priorities. If OpenBSD wants it's security to do some useful work, they need to on a SMP system these days. How frequently do you still here "corporate mission-critical server with single CPU" today?

    12. Re:Great news by Null_Packet · · Score: 2

      Because they changed the criteria after a local exploit via ssh. It used to read something like 'No exploit in the default install...'. Because the new statement applies to remote exploits, the time changed.

    13. Re:Great news by evilviper · · Score: 2
      That's completely wrong.

      When I first came to OpenBSD (abround the 2.5 days), their website read something like:

      1 year without a local exploit in the default install
      3 years without a remote exploit in the default install

      They removed the first line when a couple local holes were found, and since that time there have been no changes to the style.

      The reason it has changed, is merely that they don't update it a precise intervals. They essentially stopped the clock last time they updated (I believe because of some claimed exploit near the 6 year mark that never worked out), and finally brought it up to date recently.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    14. Re:Great news by binaryDigit · · Score: 2

      Must have been typed on an original Pentium with the floating point rounding error.

  5. Maybe now.. by FuzzyMan45 · · Score: 2, Interesting

    They can increase their userbase to (hopefully) include some of the larger companies and corporations that opt to use FreeBSD because of it's SMP support and greater performance than OpenBSD. Hopefully, this modification will also include some performance modifications so it can also compete speedwise with FreeBSD.

    While security takes precedence over performance in my book, there are definitely some things that need the performance of FreeBSD.

    This is one feature i've been looking forward to playing with (not NEEDING) for a while, i can't wait to try it when it's available somewhere.

    --Fuzz

  6. Re:'ehh by Ark42 · · Score: 1

    No, I would have assumed *BSD all had SMP support too, after all, Linux and Windows support SMP... strange

  7. Sweet Mother of Blowfish by echorun · · Score: 3, Funny

    Sweet now I can have more than one fish in the box.

    --
    The human condition is to not accept the human condition.
  8. Re:in russia.... by Anonymous Coward · · Score: 0

    aww come on man, if you're gonna say it at least say it right, It's Soviet Russia

  9. It's about friggin time they did... by CoolVibe · · Score: 5, Informative
    Although, the question remains if Theo will accept these patches...

    The last time I spoke to Theo in person, he wasn't too keen on SMP. That wasn't too long ago.

    1. Re:It's about friggin time they did... by Gothmolly · · Score: 0, Troll

      Well fsck Theo, then. Seriously, you'd never run into this in Linux, because Linux has multiple working journaling filesystems - no need to fsck.
      Wait, did I just troll?

      --
      I want to delete my account but Slashdot doesn't allow it.
    2. Re:It's about friggin time they did... by aridhol · · Score: 4, Interesting
      Possibly he wasn't keen on the time investment required to implement SMP. If these guys do all the work, it may well make it in.

      OTOH, it may be that SMP code is more difficult to audit, and that this is the reason it won't make it in. Remember, SMP allows for the possibility of race conditions within the kernel itself, which would be a nightmare to validate for security.

      --
      I can't say that I don't give a fuck. I've just run out of fuck to give.
    3. Re:It's about friggin time they did... by CoolVibe · · Score: 4, Insightful
      Possibly he wasn't keen on the time investment required to implement SMP. If these guys do all the work, it may well make it in.

      It might. Even if Theo doesn't accept these patches, the patches will still be available. I just hope they keep maintaining them and keep them up to date if Theo says no for any reason.

      OTOH, it may be that SMP code is more difficult to audit, and that this is the reason it won't make it in. Remember, SMP allows for the possibility of race conditions within the kernel itself, which would be a nightmare to validate for security.

      If Theo would deny this work, it would probably be on those grounds. It was indeed one of the reasons he mentioned to me.

      The most likely place for race conditions to occur on SMP systems is with threading. I have yet to see a totally solid threading implementation that is totally devoid of race conditions of any kind wrt locking/freeing/semaphores/etc. Usually kernel developers solve most of the problems by passing one big lock around (like linux does, and FreeBSD (ever heard of Giant?))

      All in all good news that these guys are working on it indeed. My main concern is seeing this project die because it has the chance of being shot down by Theo. I really hope they persist in pushing Theo to accept it. I also hope they have a lot of patience while dealing with Theo, he's also not the easiest to get along with :)

    4. Re:It's about friggin time they did... by psxndc · · Score: 2, Interesting
      Well if worse comes to worse, they could always fork OpenBSD like Daren Reed did to include ipf. Of course then you lose the trustyworthyness of OpenBSD because it is no longer A) official or B) going under the microscope like OpenBSD does by the OpenBSD team.

      psxndc

      --

      The emacs religion: to be saved, control excess.

    5. Re:It's about friggin time they did... by Otterley · · Score: 3, Informative

      Linux has been free from most Big Kernel Lock constraints since 2.2 was released. There are very few operations left that don't use fine-grained locks.

    6. Re:It's about friggin time they did... by Anonymous Coward · · Score: 0

      Yes. Because Linus is rather well known for not accepting patches he doesn't like, think is needed, understand, etc. It occurs again and again. It's covered on /. Read up on it. Bitch at him. He's obviously affect your OS of choice.

      Instead, you bitch about someone doing this to an OS you don't even use. I must be reading /.

    7. Re:It's about friggin time they did... by Anonymous Coward · · Score: 0

      I name drop famous nerds, I am cool.

    8. Re:It's about friggin time they did... by Anonymous Coward · · Score: 0

      In the Linux world, it's recommended procedure to maintain your patch outside of the main tree until it gains a large enough userbase for Linus to bother with it.

      On the other hand, the OpenBSD people apparently live on the money from CD sales, so unofficial forks are not looked upon kindly.

    9. Re:It's about friggin time they did... by Bert64 · · Score: 2

      For all their so called security auditing, they failed to find several holes, most notably in openssh. Holes not only in older code, but holes in the new code added by the openbsd team themselves.. So you trust people who write insecure code themselves to audit existing code for security?

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    10. Re:It's about friggin time they did... by psxndc · · Score: 1
      I trust them more than I trust anyone else. Have they had holes? Sure. But they've had way less holes than anyone else.

      psxndc

      --

      The emacs religion: to be saved, control excess.

    11. Re:It's about friggin time they did... by Bert64 · · Score: 2

      Way less holes than who?
      You dont see many holes in NetBSD... VMS has even less, MacOS AmigaOS and older versions of windows/dos rarely make it into bugtraq either.
      I`m sure if you created a linux distribution with a similar set of tools to those included with openbsd, you would see a similar number of holes. You cant compare something-for-everyone redhat to a stripped down do-it-yourself system.
      Aside from that fact, i have found openbsd to be less stable and less performant than other os`s, of the relatively small number of people i know who use openbsd.. almost all of them have experienced crashes, often related to system or network load. In contrast i know far more people using freebsd, linux or solaris, and they very rarely complain of crashes, the exception being people using beta versions of the linux kernel.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    12. Re:It's about friggin time they did... by psxndc · · Score: 2
      I've been running OpenBSD for almost three years and never had a system crash. I've had Gnome crash, and Navigator crash, but never the system. Granted I've never had my SuSE system crash either, but both systems are comparable as far as stability.

      The lack of holes don't come from a stripped down total system, they come from A) a stripped down default install which uses B) carefully audited code in that install. Even with the most basic SuSE install I had packages I didn't want that had holes (the wu-ftp bug a while ago comes to mind). But that's just my experience. Expecting anything but YMMV is naive.

      psxndc

      --

      The emacs religion: to be saved, control excess.

  10. In Red China ... by Anonymous Coward · · Score: 0

    SMP tanks roll over YOU!

  11. Waterloo? by sean23007 · · Score: 0, Flamebait

    The University of Waterloo, eh? Well, knowing them, the versions of OpenBSD with SMP support will require a Windows XP activation key...

    Or maybe they figured out a way to port OpenBSd to Windows. Or something. Waterloo?

    --

    Lack of eloquence does not denote lack of intelligence, though they often coincide.
    1. Re:Waterloo? by Anonymous Coward · · Score: 0

      Oww! I felt that one! Talk about serious flamebait...


    2. Re:Waterloo? by jpmorgan · · Score: 2, Informative

      Sounds like you've got some issues, dude.

      Your comment is amusing since as a UW CS student, I don't have a Windows account. In fact, last I checked as an upper year student I'm not allowed to have Windows account, unless it's required by a specific course (statistics courses sometimes require windows accounts for matlab, for example).

      Introductory programming courses are taught on Macs and Windows boxes, but almost everybody I know participates (as time allows) in free software projects; hell, half of the people I know are Debian developers.

      So why don't you stick to things you know (i.e., nothing) and take some of this shut the fuck up.

    3. Re:Waterloo? by thirty-seven · · Score: 4, Informative
      The University of Waterloo, eh? Well, knowing them...

      Which apparently you don't.

      the versions of OpenBSD with SMP support will require a Windows XP activation key...

      Or maybe they figured out a way to port OpenBSd to Windows. Or something. Waterloo?

      I assume you're referring to the stories from several months ago about a proposed deal where UW's Computer and Electrical Engineering department would, as part of a larger research sponsorship deal with MS, agree to make C# the language used in a first year class for CompEng students. There was a huge outcry against this by most CS and CompEng students and profs. Also, note that the School of Computer Science, in the Faculty of Mathematics, had nothing to do with this deal.

      It is my impression that there are many UW students who use or contribute to Open Source projects. Profs are more than willing to make an occasional joke in class at Microsoft's expense. And most CS students (I can't speak for CompEngers) don't touch any MS products for programming projects past first year, by far preferring to use the provided unix labs.

      Do I think the CompEng department's decision regarding C# bad? Very much so. But as I understand it, this decision was made by a few key people who stretched their authority, when really they should have consulted with more people. In fact, Engineering profs have called UW administration on this decision, leading to a decision that before the MS deal can be finalized, it must be approved by "the Electrical and Computer Engineering Department Program Committee, Faculty of Engineering Admissions Committee, Faculty of Engineering Academic Committee, Faculty of Engineering Undergraduate Studies Committee, Year 1 Implementation Committee, Senate Undergraduate Council, UW Registrar's Office and the senate as required by UW policy and practice." This, in my opinion, effectively has killed the deal. See this article for more about this. [Note that the article implies that the proposed MS C# deal would have affected all first year programming classes. This is untrue: only first year CompEng classes would have been affected; CS students would have been fine.]

      The very reason that this decision was such as big deal at UW is that it goes so very much against the prevalent attitude there. And the very large amount of negative feedback they got from UW students and profs in the CompEng and CS departments should ensure that something like this doesn't happen again at UW.

      --

      Atheism is a religion to the same extent that not collecting stamps is a hobby.

    4. Re:Waterloo? by Anonymous Coward · · Score: 0


      I'm sure they're referring to the C#/Engineering debacle, which can be summed up in a simple equation:

      MS -> $ = UW Eng + C#

      But UW Eng != UW in general, so you're completely correct, the stoooopid poster should just STFU.

      But... I have an engineering co-op student who's working for me, and it's amusing to bash MS in front of him.

    5. Re:Waterloo? by thirty-seven · · Score: 1
      But UW Eng != UW in general, so you're completely correct, the stoooopid poster should just STFU.

      Exactly. I tried to make this point in my other post in this thread.

      But... I have an engineering co-op student who's working for me, and it's amusing to bash MS in front of him.

      Except that all four students working on this project are 4th year CompEng students! According to their site, they "are four University of Waterloo students who are adding Symmetric Multiprocessor (SMP) support to the OpenBSD kernel as [their] 4th year Computer Engineering Design Project."

      --

      Atheism is a religion to the same extent that not collecting stamps is a hobby.

    6. Re:Waterloo? by vorwerk · · Score: 1

      Actually, the whole C# problem has been vastly blown out of proportion.

      Myth: C# will be used in E&CE courses at UW.

      Truth: The Dept of E&CE and Microsoft were in negotiations. No more, no less. Nothing's been confirmed. Nothing's been done, other than an initial "hey, let's talk about this" discussion. (Hence the "memorandum of understanding", not the "legally binding contract saying that you have sold your souls". :)

      In fact, public outcry has really forced the Department of E&CE at Waterloo to take a step back and re-think things. As it stands now, it may not even go through.

      -kris
      MASc student
      University of Waterloo

    7. Re:Waterloo? by Anonymous Coward · · Score: 0

      whats the matter, mom and pop couldnt send you to a decent school that is even slightly recognized? Oh wait, you just could not get in so you settle for pathetic schools such as "Waterloo". Good job, keep studying and some day you will be fixing cash registers at mcdonalds!

    8. Re:Waterloo? by Ballsy · · Score: 1

      ....maybe you'll bump into each other then. You can take a smoke break while he fixes your cach register, dumb ass.

  12. come on SUN cough up the specs by zenst · · Score: 1

    We want the option of SMP on SUN kit as well. Seriously SMP is well needed seeing as most OpenBSD box's are yesterdays coperate kit. Also given intels SMP on a chip play along with Power4 dual cores on the market now that by the time they make it into your average geeks home SMP should be stable.

  13. Re:'ehh by RedLeg · · Score: 2, Informative

    You've apparently never asked Theo about this. I have several times, going back years ago, and his reply has always been either "nobody wants it", or "SMP machines are too expensive and nobody has them". And OBTW, he wasn't interested in loaner or donated hardware to do the work on.

    I guess somebody cares now....

  14. Re:'ehh by larien · · Score: 3, Informative
    It's not really all that surprising; there's a few potential pitfalls (read: race conditions) in SMP that you can get round in a uni-processor build. As OpenBSD is intended to be a secure OS, you make things simpler (and, by inference, more secure) by sticking to a single-CPU model.

    The problem is, I don't know how much of OpenBSD's kernel really relies on the assumption that it'll only ever run on one CPU and it may take some time before OpenBSD becomes as stable and secure as it needs to be.

    OpenBSD is designed for an "edge server" environment, where scalability isn't as important as security.

  15. Re:Hooray! by Anonymous Coward · · Score: 0

    If I'm not mistaken, OpenBSD has had very strong IPv6 support for years.

  16. I guess they can forget about... by Jacco+de+Leeuw · · Score: 3, Interesting
    ... ever working for Microsoft then!

    Microsoft has been raiding the University of Waterloo for programmers for years now.

    --
    -------
    Warning: Slashdot may contain traces of nuts.
    1. Re:I guess they can forget about... by dolmant_php · · Score: 3, Informative

      You are aware that Microsoft uses BSD code in Windows? Microsoft actually likes the BSD liscense, since they can use BSD code. They dislike the GPL, for obvious reasons.

    2. Re:I guess they can forget about... by Anonymous Coward · · Score: 0

      You missed the point. Microsoft is anti-competetive. Have you been living under a rock or something? They were tried in court and found guilty of acting as a monopoly, and are currently being sued by at least two states in the US.

      Now, given their competetive natures, don't you think Microsoft would frown upon a university contributing to Open Source software?? (hint: yes)

    3. Re:I guess they can forget about... by Ninja+Programmer · · Score: 2
      • Microsoft has been raiding the University of Waterloo for programmers for years now.
      Correction -- *decades*.
  17. It just goes to show by drivers · · Score: 1, Funny

    Those who don't use Linux are doomed to reimplement it... again.

    1. Re:It just goes to show by King+of+the+World · · Score: 1

      Heh heh heh...

    2. Re:It just goes to show by Citizen+of+Earth · · Score: 3, Funny

      Those who don't use Linux are doomed to reimplement it... again.

      I believe that should be: "Those who do not understand Unix are condemned to reinvent it, poorly." -- Henry Spencer

      Or maybe: "NT is a weak form of Unix like a donut is a weak form of a particle accelerator." -- MBCook

    3. Re:It just goes to show by Anonymous Coward · · Score: 0

      you stupid moron. read more, talk less.

    4. Re:It just goes to show by Anonymous Coward · · Score: 0

      you are my hero

    5. Re:It just goes to show by Jeff+Probst · · Score: 1

      you forget that linux is a unix clone, and that a clone by definition does not do anything new.

    6. Re:It just goes to show by Anonymous Coward · · Score: 0

      Yeah, like Solaris did. Damn they were stupid reimplementing ASMP before Linux was even written, pre-repeating Linux. Like VMS having full clustering support before Linux was written. Oh wait, they didn't pre-repeat Linux [yet] because Linux doesn't have anything resembling decent or even half usable clustering support. Etc, etc.

    7. Re:It just goes to show by Anonymous Coward · · Score: 0

      never let a good link go to waste:

      reading material

    8. Re:It just goes to show by Anonymous Coward · · Score: 0

      Wait, OpenBSD's code goes back much further than Linux...

    9. Re:It just goes to show by Anonymous Coward · · Score: 0


      Yeah, because Linux was the first unix... ... oh, wait... no, it wasn't.

      But it was the first with SMP... ... oh, wait... no, it wasn't.

      Those who don't understand BSD are condemned to re-implement it - poorly.

  18. Re:In The Nation Formerly Known As The CCCP... by Anonymous Coward · · Score: 0

    and for a limited time the ekrout combo is available for just $3.99 and may be super-sized for a meager 39 cents extra. standard meal includes medium size fountain soda and large fries.

  19. don't forget by Anonymous Coward · · Score: 0

    He's a fag, too.

    God hates fags.

  20. ipv6 by nestler · · Score: 2
    Yes, they are slow at implementing SMP because they don't care about SMP relative to other things.

    However, the crack about ipv6 is stupid. OpenBSD has had a working ipv6 stack for a long time (they were first OS to ship with an IPsec stack at all). Get your facts straight.

    1. Re:ipv6 by Gothmolly · · Score: 2

      IPv6 and IPSec have nothing to do with each other, you insensitive clod!

      --
      I want to delete my account but Slashdot doesn't allow it.
    2. Re:ipv6 by Cajal · · Score: 1

      Correct me if I'm wrong, but does IPv6 require IPSec? I thought that for an IPv6 stack to comply with the RFCs that it had to support IPSec.

    3. Re:ipv6 by Make · · Score: 1

      hm, I think I read somewhere that IPsec came from IPv6 and was backported to IPv4. I would google now and provide links if I didn't have to work now..

  21. In other news.... by Anonymous Coward · · Score: 0
    Microsoft announces that it is on target for working SMP support in 3q 2003.

    Yes... I suppose it IS a troll...

  22. Re:Hooray! by Daniel_Staal · · Score: 4, Informative

    They have ipv6. OpenBSD ships with ipv6 active and operating. They've been looking at/working on SMP for some time, but they (read: Theo) wants to make sure it meets the standards of the rest of the OS. SMP adds quite a few (theoretically at least) security problems to deal with, and they want to be sure those problems are fully addressed.

    --
    'Sensible' is a curse word.
  23. XP and Linux comparisons are pointless by flinxmeister · · Score: 5, Interesting

    I've been using OpenBSD in several mission critical networking roles for 3 years now, and I can safely say that I haven't needed SMP.

    The conventional wisdom that an operating system should be judged according to it's bells and whistles is what's wrong with the software industry. An OS should be judged by two things: Does it do the job I require of it, and does it do it well?

    There are many many jobs that do not require SMP. There are many many jobs being done on SMP boxes that do not require SMP. As the price of processors has diminished, SMP is just a cool thing to buy. I'd be willing to put money down saying that 75% of the SMP boxes out there aren't needed (if that was measurable).

    So, if you want to judge your OS based on features you don't need, then go for it. I use OpenBSD because it is the best choice for that particular need. If you want to assume that one OS is the Uber-OS because of the back panel of the box, then go for it. I'll assume a particular OS is best for the task at hand, and go with that.

    I'm not part of the OpenBSD project (nor do I play one on TV), but one of the central points behind it is that they don't put in things unless they are needed. So far it doesn't seem like SMP has been justified in the great scheme of things (no surprise given the actual need in the wild). I'd much rather have them working on things I'm going to be using instead of evaluating other products based on things I won't.

    1. Re:XP and Linux comparisons are pointless by RazorJ_2000 · · Score: 2

      "I've been using OpenBSD in several mission critical networking roles for 3 years now..." blah blah blah...


      What are you using it for, and how reliable is it for networking? Uptime?



      --
      pi=sigma{n:0-infinity}[(1/16)^n][(4/(8n+1))-(2/(8n +4))-(1/ (8n+5))-(1/(8n+6))]
    2. Re:XP and Linux comparisons are pointless by flinxmeister · · Score: 2, Informative

      7 production firewalls in varying degrees of importance. 6 of these guys have *never* gone down. The exception on one was one where squid had some compile issues and made the rest of the box unhappy (during implementation). This number includes one soekris box. 2 temporary firewalls where someone insists on using firewall-1 or Symantec on Solaris but doesn't have the Solaris hardware or the budget yet. One is a bridging firewall, so I don't know what they're going to do when they want to switch. To be honest, they'll probably end up keeping them. 3 Snort sensors. (2 have never crashed, uptime of over one year before massive power failure at the location). This includes 3 upgrades of snort. One crashed during some Gigabit experiments. A high volume syslog server/ftp logfile repository/mysql server. This one has been a bit flaky. Crashed twice in a one year period, 10 months between crashes. A web server that has a maximum uptime of 8 months. Could have gone longer but this location has a bad power situation. So total OpenBSD boxen for me is around 14.

    3. Re:XP and Linux comparisons are pointless by Anonymous Coward · · Score: 0

      Well according to a statistician friend of mine, 68% of all statistics are made up.

    4. Re:XP and Linux comparisons are pointless by Doomdark · · Score: 3, Interesting
      Yeah, just like Windows users were saying around '95, "who needs pre-emptive multitasking, I've never needed more than co-operative multitasking" (and Mac users until Mac Os X). Or linux users wondering why one needs a journaling file system, up until three of them get mature enough. And when the system does get what was formerly denounced as "unnecessary toy", it suddenly becomes indispensable commodity.

      Now, SMP is not necessarily something people "start needing"; you don't usually realize one day that "gee, now I really need SMP". For many things it isn't strictly required, like you say -- after all, most systems only scale up decently to 4- or perhaps 8-way systems, and common rule of thum is that you get about sqrt(num_procs) output (assuming you get enough CPU load for all processors)... and so you can same amount of work done by getting twice as fast CPU (instead of 4-way SMP system).

      However, having SMP capability as an option is a Good Thing. For servers it allows nice high-end scalability (esp. with Sun boxes, E10K and co. wouldn't rock if it wasn't their SMP-scalability coupled with kickass I/O.. but those beast scale well past 8 CPUs). For desktop systems it allows for better interactivity (especially on traditional unix[ish] system that have batch-job oriented scheduling), smoother UI.

      --
      I like paying taxes. With them I buy civilization -- Oliver Wendell Holmes
  24. Make up your mind, God! by Anonymous Coward · · Score: 0
  25. Confuscious say by Anonymous Coward · · Score: 0

    Man who spin locks safe cracker.

  26. Re:Am I reading this right? by Anonymous Coward · · Score: 0

    Still doesn't. Most BSD's don't.

  27. just to be the fourth guy to point it out by Anonymous Coward · · Score: 0

    You mean Civilization.

    Suck it, Trebek!

    1. Re:just to be the fourth guy to point it out by Anonymous Coward · · Score: 0

      Suck it long.. And suck it hard!

      BUCKFUTTER!

      Damn you and your daily doubles, you brigand!

      One day it'll be my turn, Tre-bek!

      Okay, I'm done now.

  28. Hacking on PowerBooks by scorpioX · · Score: 3, Informative

    Did anyone else notice that these four students are using PowerBooks (I assume running OS X). Check out this picture. You also have to love the reference to the cult movie Hackers.

    1. Re:Hacking on PowerBooks by Anonymous Coward · · Score: 0

      Looks to me like those 4 guys live over on Philip St just off campus. If I'm guessing correctly where they live then they should be able to lean out their window, turn their head, and then see the Math/CompSci building. Woohoo!!


    2. Re:Hacking on PowerBooks by MalleusEBHC · · Score: 2

      The one on the far left is an iBook. On the far right is a TiBook. The one at the bottom of the screen is a Pismo I believe, but I'm not sure. Can anyone verify this?

    3. Re:Hacking on PowerBooks by Mandi+Walls · · Score: 2

      RISC architecture is gonna change everything.

    4. Re:Hacking on PowerBooks by geeker · · Score: 1

      Last I heard, (since I lived in that house), it was in the student ghetto on Westmount.

      Oh, wait, Waterloo doesn't have any student ghettos.

    5. Re:Hacking on PowerBooks by singularity · · Score: 1

      It would have to be a TiBook or an iBook, since the introduction of the TiBook brought with it the correctly oriented Apple logo.

      Before that, as you were opening the laptop, the Apple logo would look correct to you. To people who saw you working on it, though, it would be upside down (the top of the logo would be closer to the hinge side)

      Too much Apple trivia for anyone person to hold...

      --
      - (c) 2018 Hank Zimmerman
    6. Re:Hacking on PowerBooks by NeuroKoan · · Score: 2

      I think the mystery machine is an iBook. It looks too thick to be a TiBook. And the color is a slight red (and I don't know *anyone* who would want to spray-paint a TiBook).

      --

      "However," replied the universe, "The fact has not created in me A sense of obligation."
    7. Re:Hacking on PowerBooks by ISWalker · · Score: 1

      You are correct sir. I own the white iBook, but shortly after the picture was taken I painted the lid blue. The laptop in the middle is an iBook with the lid painted red.

    8. Re:Hacking on PowerBooks by SN74S181 · · Score: 1

      I've always thought that the wannabe rich wear gold jewlery, the rich wear platinum jewelery, but the super-rich wear copper-plated platinum jewelry.

  29. Re:Hooray! by DA-MAN · · Score: 1

    Actually OpenBSD has had ipv6 for some time now. Kind of lame to have ipv6 (something that has yet to be implemented at any reasonable amount) before SMP (something required for servers doing just about anything but firewalling in a corp environment).

    --
    Can I get an eye poke?
    Dog House Forum
  30. Re:Hooray! by Anonymous Coward · · Score: 0

    This should help OpenBSD to die scalably.

  31. Re:Hooray! by gooser23 · · Score: 1

    Um.... OpenBSD has had ipv6 since May 19, 1999: http://www.openbsd.org/plus25.html

    And even without SMP support, you have always been able to run OpenBSD on a dual-cpu x86. I've been running it on my dual p2-233 for two years now. Sure it only uses one processor, but for the time I want to put in to configuring it, I figure a secure box on one proc is better than an unsecure box on two.

    And yes, I have checked out the other BSD projects. After trying linux for a year, I got sick of the bloat, and wanted to get as lean as possible. In my opinion, at the time OpenBSD (2.9, I think) was the cleanest.

    --
    "Dying tickles!" -- Ralph Wiggum
  32. So? by Anonymous Coward · · Score: 1, Insightful

    I see tons of negativity from the clueless as usual. *sigh*

    Hey, people? Do you know how many people *don't* need SMP, as opposed to those who do? Did you ever think that, given the number of SMP-supporting *nixes out there, OpenBSD felt like concentrating on more important things (like security) first?

    Yeah.

    Congrats, OpenBSD! (Still the only operating system to pit Daemonettes against Catgirls in pits of pudding! Hehehe. Get it? Daemonettes? Catgirls? Script Kitties? HEHEHEHEHE. Sorry. :P)

    1. Re:So? by Anonymous Coward · · Score: 0

      Congrats, OpenBSD! (Still the only operating system to pit Daemonettes against Catgirls in pits of pudding! Hehehe. Get it? Daemonettes? Catgirls? Script Kitties? HEHEHEHEHE. Sorry. :P)

      You have never been laid have you?

    2. Re:So? by Anonymous Coward · · Score: 0

      Do you know how many servers ARE SMP and that OpenBSD is supposed to be a SERVER OS? For gods sake, that's like a basic requirement.

    3. Re:So? by rosie_bhjp · · Score: 1

      SMP really isn't a big deal with firewalls, which is really where OpenBSD has its 'target market'. I think thats been said about 1000 times, but hey, I'll say it again.

      --
      A radio maverick jumps to internet only. The Future of Rock n Roll
    4. Re:So? by Anonymous Coward · · Score: 0

      You are ASSuming servers have dual processors.

    5. Re:So? by Anonymous Coward · · Score: 0

      > SMP really isn't a big deal with firewalls, which is really where OpenBSD has its 'target market'. I think thats been said about 1000 times, but hey, I'll say it again.

      Everywhere I go I see people saying OpenBSD has some sort of unstated target. Stop ASSuming.

  33. Part of the project?.. wishful thinking? by Anonymous Coward · · Score: 0

    I think its great as a school project, but that seems to be all that it is. It would be great if others gave a helping hand, and made sure the project gets "finished"(mostly working anyways) "These guys have an interesting 4th year project for CE" would be more better, or at least repel more Trolls

  34. Re:'ehh by vesamies · · Score: 1

    Smp don't have a lot of meaning because almost nobody has many processors. But people are always interested in more features. I guess if everyone buys a hyper threaded pentium 4, then smp support is essential.

  35. Re:Hooray! by bahwi · · Score: 4, Insightful


    Troll.

    OpenBSD has had IPv6 since version 2.7 out in June 2000.

    And for the record, FreeBSD has had IPv6 since March, 2000, version 4.0

    And let's not forget who brought you OpenSSH.

    SMP isn't the top priority. Giving up stability and security for the latest and greatest features are not what everyone wants. A friend of mine complained about FreeBSD not having good SMP support, I asked him if he had an SMP machine, he said "No." I hope that is enough to illustrate my point.

    Sorry to go off on this, but mod the parent down if you mod me down please. People always trounce on any of the BSD's while praising Linux here.

    Hear that? That's my karma in the toilet. Flush.

  36. A long wait... by evenprime · · Score: 5, Informative
    There's been talk of doing this since 1997. In the past there was concern about the cost of SMP hardware to develop on and also on the huge amount of time needed to do it right:
    SMP is a big deal. OpenBSD does things, and it does them RIGHT. To do SMP right, we'd need to make the kernel fully-reentrant. This means that we'd clean up the kernel I/O functions so that they don't wait on one another (that's a really dumbed-down, bad explanation of it.) By making the kernel re-entrant, we wouldn't have the problem of spinlocks (one processor waiting on the other to finish I/O, etc.) This would mean almost a COMPLETE re-write of the kernel. This would be a six+ month ordeal for quite a few coders working 40-60 hour weeks. Remember, such a huge task needs to include not only the re-writing of existing code, but checking it to make sure it works on all supported platforms without breaking all the great existing features of OpenBSD.
    That bit about doing things the Right Way is a major consideration for the OpenBSD team. In 1998 jkatz pointed out that they probably wouldn't just use the code from another BSD because they wanted to make sure that OpenBSD's solution was more scaleable.
    --

    "Weapons should be hardy rather than decorative" - Miyamoto Musashi
    I think that goes for OS's too
    1. Re:A long wait... by thirty-seven · · Score: 1

      In that case it definitely sounds like these 4 UW students aren't doing things the "Right Way", according to the core OpenBSD team's standards, anyway.

      Don't get me wrong, I'm not knocking them - this is a big and very cool undertaking that the students are doing. It's just too bad that it seems like their work won't be accepted by the OpenBSD core team.

      --

      Atheism is a religion to the same extent that not collecting stamps is a hobby.

  37. Re:In The Nation Formerly Known As The CCCP... by Anonymous Coward · · Score: 0

    Well, don't they? Forwards and backwards that means the same thing essentially. :-)

  38. Re:Am I reading this right? by Anonymous Coward · · Score: 0

    Did you expect something more from a dying OS?

  39. Very smart... by Dahan · · Score: 4, Interesting
    Good to see that they're using NetBSD as a reference for this... OpenBSD is basically a less-active branch of NetBSD from a couple years back, so it should be a pretty straightforward process to merge in the SMP stuff from NetBSD (which, like just about every other OS, has had SMP for quite some time now).

    OpenBSD is a very promising OS, and SMP support will finally let it play with the big boys in the free *nix playground :)

    1. Re:Very smart... by Anonymous Coward · · Score: 1, Informative

      OpenBSD is basically a less-active branch of NetBSD from a couple years back

      That is basically bullshit. IPv6, OpenSSH, pf, altq, ipsec and systrace all appeared in OpenBSD before NetBSD.

    2. Re:Very smart... by evilviper · · Score: 2
      OpenBSD is basically a less-active branch of NetBSD from a couple years back

      OpenBSD may have been branched from NetBSD, but there is practically no resemblance left anymore. Both, in source code and userland, there have been so many changes that the differences between Net and Open are bigger than the difference between either of them and FreeBSD.

      SMP support will finally let it play with the big boys in the free *nix playground

      OpenBSD has a very surprising acceptance. Sure, usually on routers, firewalls, gateways, VPN routers, etc., but in comparison to NetBSD, OpenBSD is doing incredibly well.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    3. Re:Very smart... by LizardKing · · Score: 4, Interesting

      OpenBSD may have been branched from NetBSD, but there is practically no resemblance left anymore. Both, in source code and userland, there have been so many changes that the differences between Net and Open are bigger than the difference between either of them and FreeBSD.

      I applaud your attempt to counter the accusation that OpenBSD is "less active" than Net, but you've got it a little wrong. The userland between the three *BSDs is very similar, and the kernels have similar subsystem layouts. Without this similarity, things like softdeps, systrace and IPv6 wouldn't have percolated so quickly into all three. Finally, note that this new OpenBSD SMP work builds on Bill Studenmunds NetBSD code.

      Chris

    4. Re:Very smart... by evilviper · · Score: 2
      you've got it a little wrong. The userland between the three *BSDs is very similar, and the kernels have similar subsystem layouts.

      You should read my post more quickly next time. I said the differences between OpenBSD and NetBSD are now larger than the differences between NetBSD and FreeBSD (or between OpenBSD and FreeBSD).
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    5. Re:Very smart... by evilviper · · Score: 2

      Correction:

      You should read my post *less* quickly next time

      OR

      You should read my post more *carefully* next time

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    6. Re:Very smart... by junyoung · · Score: 1

      Huh?! Have you ever taken a look at OpenBSD and NetBSD sources?

    7. Re:Very smart... by Anonymous Coward · · Score: 0

      perhaps he meant openbsd is most old fashoned, out of date OS.
      all unix variants (including linux, freebsd, netbsd, and all of
      commercial unix variants) have smp and unified buffer cache.
      but openbsd don't have them.
      last I've heard, some openbsd developers tried to take unified
      buffer cache from netbsd kernel (as their usual, e.g. uvm, wscons,
      cardbus support, IDE ultra DMA support, raidframe, usb support,
      nfs v3 support, this smp thing, and so on...), but they cannot
      make it work on openbsd.

  40. OS should be judged by three things by screwthemoderators · · Score: 1

    "two things: Does it do the job I require of it, and does it do it well?" In every engineering project there's cost. You can choose two of the three: Better, Faster, Cheaper. You may have forgotten this, but the accountants won't

    1. Re:OS should be judged by three things by flinxmeister · · Score: 1

      Well, if ya can't afford OpenBSD, then ya can't afford accountants.

      And in most planned growth network environments, faster IS better.

      This leaves "better". And IMHO OpenBSD is "better" for many apps.

    2. Re:OS should be judged by three things by Anonymous Coward · · Score: 0

      LOL. Nice one. ;-)

  41. Re:Openbsd by dabj.net · · Score: 2, Insightful
    The BSD that is always behind, and unsecure, they even admit their security hole PROUDLY on their homepage.
    You are correct in your statement that they proudly flaunt their securityhole. Note however the lack of plurality in that statement.
    Yes, one(1!) remote hole in the default install, in more than 7 years.
    If Microsoft could boast with this they would spend the equivalent of a small country's GNP on letting you damned well know about it.
    If Linux could boast with this then Microsoft wouldn't have that small country's GNP to spend, since everybody would be running Linux instead.

    If you by "always behind" mean that Doom 3 can't be run on OBSD then yes, you are correct on that too.

    OpenBSD was designed to be a secure server, even with default install. Adding SMP-support have never been a priority in part, I think, because of the inherent security issues that arise from such a implementation. I'm sure there are other reasons as well, none of them beeing that they never got around to implementing it.

    So are we agreed then, OpenBSD is always behind, and unsecure?

    I thought so. =)

    --
    "Education is a system of induced ignorance" / Noam Chomsky
  42. Uses of SMP? by guacamole · · Score: 2

    Which of the popular applications and uses of OpenBSD would benefit from SMP support?

    1. Re:Uses of SMP? by timeOday · · Score: 3
      Which of the popular applications and uses of OpenBSD would benefit from SMP support?
      I don't suppose anybody is running apache on it? :) But seriously, the only requirement to benefit from SMP is that you run more than one cpu-intensive process on the computer at once. Servers (like apache) usually fork a process for each client.
    2. Re:Uses of SMP? by Anonymous Coward · · Score: 0

      Fork a process for each user. Pathetic. Do the coders still rub two sticks togeather to light a fire to keep their cave warm at night too?

    3. Re:Uses of SMP? by Tuzanor · · Score: 3, Informative

      Dynamic web servering, of course. OpenBSD is also widely used as a VPN. Whilst some of the crypto cards work great a second proc. can only help. Also, firewalls for very large networks may benefit.

    4. Re:Uses of SMP? by Anonymous Coward · · Score: 0

      When it's late at night and I'm feeling tired due to coding all day long... I like to fork my arse. It gives me positive motivation to keep going forward. :)


    5. Re:Uses of SMP? by drinkypoo · · Score: 4, Informative
      In addition to what the siblings of this comment currently say: Everything that requires lots of CPU, or lots of processes running at the same time. A single thread is usually not relocated across processors, so the following is more or less true in the case where you have lots of processes of vaguely equal size and more than one processor: The number of context switches which have to be done is divided by the number of processors. That's one benefit. The other is that (in theory but not in practice of course) you can execute twice as many instructions at once. Obviously you still have operations which have to wait on things other than other instructions being retired (Though that too) which I suspect is the main reason why usable "speed" (let's say cycles for the sake of saying SOMETHING) does not tend to scale linearly with additional processors.

      Anyway anything that is relatively (or entirely) cpu-bound and involves lots of processes or threads will be sped up significantly. Also one process doesn't tend to monopolize your processor so badly.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Uses of SMP? by timeOday · · Score: 1
      Fork a process for each user. Pathetic.
      Technically what I said is a simplification. Each apache process exits only after serving N clients IIRC.

      Besides, Unix (and Linux) are very guick at creating processes. It doesn't take long and protects you from some security issues and memory leaks.

      And yes, various servers use threads instead of full processes, which will also benefit from SMP (depending on which thread library is used).

      But the point still stands, nothing very special need be done to utilize SMP, especially on a server.

    7. Re:Uses of SMP? by Anonymous Coward · · Score: 0

      Servers (like apache) usually fork a process for each client.

      That would be true of Apache 1.3. Apache 2.0 learnt how to do threading.

  43. secure server by zogger · · Score: 1

    --about time. Before I just didn't understand. I keep reading about open bsd being a server distro, very secure. Well, duh, servers are where you see multiple processors more than cheap(er) desktops. and if all it is is to be some sort of minimum home brewed gateway router thing, they can stop now, it's "done", go on to some other project.

    All in all, though, I'd say adding multiple processor support is a good thing. I wish them well, and perhaps I'll try it someday once this is more stable.

  44. Re:Hooray! by Anonymous Coward · · Score: 0

    Hi.

    Is there any reason you're posting in monospace, other than to be an eyesore?

  45. Re:Hooray! by Jeff+Probst · · Score: 1

    you are a moron. just how egotistical are you? stick to linux - unix for tools.

  46. This would be nice by QuietRiot · · Score: 5, Interesting
    I'm curious how much of a rework will be required [by the OpenBSD core developers] once these guys are done. 4 guys on a one-year project. SMP. Good luck. Will this be a patch-type thing? Will the core team accept it, or reject it outright? Will the core team use some portion of it - cleaning it up along the way, or will it take a major rewrite?

    It's strange how things like this end up changing would would have been. Do it right the first time, because if it gets adopted, and it wasn't done right, efforts will be diluted.

    I'm glad to see it's happening though. At least somebody's throwing some brainpower at it rather than waiting around for Theo & friends. (no fault to Theo, I know SMP is "in the works" - OpenBSD is secure, first and foremost. That's what I, and many others, care about most. Kudos to you and your team on this! You have a highly-regarded, ultra secure OS that has kept many cracker-types and script-kiddies at bay for many years. You have saved many people many thousands or millions of dollars with the protection your software project has provided. You have given nothing to the headache medicine providers of the IT industry.)

    One more processor for my dual-capable Sun SS20 and I'll have a grand-ole time playing with this. Just too bad it comes with only a single 10-speed ethernet port. Anybody know about S-bus fast ethernet cards?

    To these brave deveopers: Way to go! Thanks for getting the ball rolling and best of luck with your project (and dealing with the publicity! :)

    1. Re:This would be nice by SN74S181 · · Score: 1

      Anybody know about S-bus fast ethernet cards?

      They are fairly common on eBay, although not always low priced. Stay away from the earlier ones, I've had nothing but problems with my 'BigMacEthernet' (be). People hawking them on eBay generally know they're selling you a lemon. Get a HappyMeal (hme), they're good stuff.

      You can get the second processor card, for SMP hacking, real cheap on eBay. I got my second SM51 there (50 MHz sparc with 1MB of cache) for $5.

    2. Re:This would be nice by Bert64 · · Score: 1

      The openbsd claims of security are just hype to increase their cd sales.. in what way is openbsd more secure than any other os? the "Secure by default" philosophy can apply to a number of linux distributions aswell, which similarly come with no daemons enabled. openbsd code has had a number of vulnerabilities aswell, no less than any other os with a similarly small set of default tools. people compare openbsd to redhat, but dont take into account the thousands of packages redhat comes with.. install and enable a similar number of things from the ports tree and see how secure it is then..

      As for the ss20, its actually quad capable (look for ross dual hypersparc modules)... and 100mbit ethernet, even 100mb quadethernet cards are often for sale on ebay quite cheaply.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    3. Re:This would be nice by xenocyst · · Score: 1

      ahem, clearly you have no idea what doing things The Right Way is about, you should probably go do some homework before you make posts on topics you aren't qualified to post on

      --
      And, no, I should not have used the goddamn Preview mode first.
  47. Re:Am I reading this right? by merdark · · Score: 1

    Be careful what you say there. Most BSDs? What are you classifying as BSD? Most commercial unix systems like solaris are based on BSD.

    I assume of course you are talking about the free BSD operating systems. Considering there are only three, I guess two of three can constitute most. But FreeBSD has had SMP for a while already, although until 5.x it hasn't been very good.

    On the comercial side of things, most BSDs *do* have SMP. And very good SMP as well.

  48. Re:Hey! by xenode · · Score: 1

    Why isn't this posted in the BeOS section?

    I'll bite, because it has nothing to do with BeOS.

  49. Re:Hey! by teamhasnoi · · Score: 2
  50. Is it really needed? by nurb432 · · Score: 2

    Sure its cool and isnt a bad thing, but for the target market that OBSD has, is SMP really *that* important?

    --
    ---- Booth was a patriot ----
    1. Re:Is it really needed? by Anonymous Coward · · Score: 1, Funny

      but for the target market that OBSD has, is SMP really *that* important?

      I don't think so. There aren't all that many SMP 486s to begin with.

  51. In Soviet Russia... by Anonymous Coward · · Score: 0

    The Kernel spinlocks you!

  52. Re:Hooray! by Anonymous Coward · · Score: 0

    i would also like to add that if you are in any way technically inclined you can build a Linux From Scratch ( google for that ) and make it as small as you wanted. :) hell, even layout the directories as you like, GNU/Linux is kewl like that.

  53. Re:'ehh by defile · · Score: 2

    he wasn't interested in loaner or donated hardware to do the work on

    Hmm. now why didn't he say "Because SMP is insanely hard to do right and I'm not motivated enough or smart enough to get it done without making the system even more unstable. And besides we get more publicity if we encrypt swap"?

    The OpenBSD project seems filled with people who need to prove their masculinity and grab attention rather than people who want to make sound design decisions. And in addition to making technical decisions, they also follow suit politically. For example, oh, such as holding an OpenSSH vulnerability hostage to promote adoption of their privilege separation patch.

    OpenBSD has plenty of stability problems. See Dan Bernstein's downtime reports. And Bernstein is someone who wants to believe in OpenBSD but is losing patience.

    OpenBSD receives plenty of attention thanks to its loudmouthed egomaniacs. Fortunately, FreeBSD is a better, more rationally designed system. Of course the FreeBSD developers are a little resentful of Linux's attention and the GPL and have made system changes out of spite, but it's nothing as bad as what OpenBSD does on a regular basis.

    I really did want to like OpenBSD. Don't believe the hype.

  54. a bsd question by Erpo · · Score: 2

    Ok, it's oversimplification time. As I understand it, the three main flavors of BSD and their foci are:

    Free - Well-rounded BSD for popular architectures.
    Open - Ultrasecure BSD for many architectures. Lots of code auditing, but always just behind Free in some area or another.
    Net - Runs everywhere. Won't be done until it runs on toasters and wristwatches.

    I have much less experience with the BSDs than I do with the various GNU/Linux distros, so I hope someone will answer my question rather than flame in response. I've long been an advocate of reducing the number of different and nearly equal (in functionality) ways to do the same thing, regarding what I would call redundant software projects. In my view, the necessity of competition in a market for physical goods (the need to keep costs down and quality up by preventing monopolies) does not exist with OSS. If a company producing OSS decides to raise prices or slow development or include unpopular features, anyone else is free to keep using older versions at the very least or fork the project and continue development with positive goals at best. With the necessity for competition removed, a market containing multiple, redundant, competing (for mind share) OSS projects is inferior to a market containing a single, popular OSS project that satisfies a specific need. Incompatibilites crop up. The support base is divided. Developer time is divided. Skills must be learned twice. I would greatly prefer a single desktop environment (and widget set and cut 'n' paste mechanism) over the current situation. In Erpo's-the-emperor land, there is only one gnu/linux distro.

    Remember, these are just my opinions.

    My question is this: while there are a number of idealogical, license-, or ego-related reasons why maintainers of gnu/linux distros (or desktop environments, or whatever) would resist a merging of sofware or elimination of obviously inferior options (obviously inferior in the "there's 1001 gnutella clients and 99% of them suck" sense), is there the same kind of resistance in the BSD community to merging all three main flavors?

    1. Re:a bsd question by Walterk · · Score: 2, Interesting
      Here's something more compact:
      "FreeBSD has tcsh installed as /bin/csh. OpenBSD and NetBSD don't. NetBSD runs on a Cobalt Qube2. OpenBSD and FreeBSD don't. OpenBSD can encrypt swap. NetBSD and FreeBSD don't."
      Can't remember where I picked that one up.
    2. Re:a bsd question by kjd · · Score: 2, Interesting

      Three different projects with separate ideals and goals. Their code has not been "one" for a long time, but code is quite often swapped between the projects in large chunks where deemed useful and possible. Merging the three codebases is really not necessary, as they give and take each other's code as they please; and merging the focus and direction of the three projects would be plenty more difficult than the code. :)

      Also, keep in mind that these projects did used to be one. They're now three for many good reasons.

    3. Re:a bsd question by Anonymous Coward · · Score: 0

      OpenBSD forked from NetBSD, but NetBSD and FreeBSD really forked from the doomed 386BSD project. 386BSD project died because Mr. and Mrs. Jolitz weren't willing to accept contributions or influence from other BSD developers out there. So some of these jilted developers became the FreeBSD project while others became NetBSD. Early release notes by Jordan Hubbard suggest that some thought might have been given to merging NetBSD and FreeBSD, but apparently there was far less enthusiasm for that then introducing IBM microchannel support on FreeBSD. Microchannel support did finally arrive somewhere in 4.x, but I doubt many people out there are using it. Anyway, the history of the various BSD's is well documented. One has only to look at old release notes, mail archives, and cvsweb.

    4. Re:a bsd question by SN74S181 · · Score: 2, Informative

      I've long been an advocate of reducing the number of different and nearly equal (in functionality) ways to do the same thing

      I feel much the same, in a lot of ways. So I've focused on NetBSD.

      I have Sparc and Intel and various other pieces of hardware. With NetBSD I can run the same OS, built from the exact same source tree (kernal and userland, plus the packages) on it all. I've built a library of almost all the essential references for Unix, including a complete 'real' manual set from 4.3BSD (it's great to use the tutorials from the old days- I'm starting to appreciate 'ed' as a real editor after reading Kernighan's tutorials), the 'devil' BSD book (McKusick/Bostic/Karels/Quarterman), 'The Basic Kernel' 386BSD book (Jolitz and Jolitz), Bach and (of course) Tannenbaum. Throw in an assortment of O'Reilly books (the Vol 3 and 8 X11 books are especially good, along with 'Essential System Administration').. There's more than enough on my plate for me to study and learn from. I see Linux as generally growing away from it's UNIX roots, part of why as I came to like UNIX more and more I liked Linux less and less and gravitated to one of the BSDs.

      The BSD forks were probably a good thing, as it's allowed the BSD systems to thrive and grow in several directions. Generally there's a synergy there in the way the code gets passed around between the different groups that would probably be more destructive if they were one group with all the infighting that would entail.

    5. Re:a bsd question by cant_get_a_good_nick · · Score: 4, Insightful

      There are some ego questions, Theo used to work on NetBSD. As smart as he is, and productive as he is, they found him abrasive and let him go. He hasn't changed much, and isn't likely to, and the world's a better place for having OpenBSD. From what I understand FreeBSD and NetBSD forked around the same time from the original BSD code, and 386/BSD. 386/BSD was kind of showing its rough edges, and people wnated to clean it up. FreeBSD went the x86 route, NetBSD always tried to be multiplatform.

      That said, there is a lot of code sharing. The USB core is exactly the same in both Net and Free, probably OpenBSD as well. systrace was originally slated for NetBSD, ended up in Open. 5.0 is getting a new /etc/rc startup, pioneered in NetBSD. A lot of the userland is the same, and there's some action on getting a standard ports system.

      In some respects, there's more sharing in BSD than in some of the Linux distros. Since all the owners of the BSDs are essentially non-commercial, there's no real incentive to make proprietary stuff. In some situations, the BSD license is easier to share stuff, but it really doesn't in this case - if they were all GPL they could share things.

      I understand what you're saying, that it diverts attention and resources. But you also have to realize they pick up thing as well. There's some cross pollination. I believe the SMP stuff is kind of taken from BSDi, if not the actual code then at least the general idea.

      The other thing is "one-size fits all" gives you a huge XXXXL product. If all the things went into just one or the other, it would be pretty bloated. The focus of FreeBSD (optimized for Intel) is in respects incompatible with NetBSD (ultra-portability). Ask anyone who's worked on gcc about the problems of optimizing portable code.

  55. Re:Why OpenBSD is so slow by Anonymous Coward · · Score: 0

    But.. OpenBSD is more secure! Just try cracking
    my OpenBSD based webserver at 198.247.175.96

  56. Re:Hooray! by gooser23 · · Score: 1

    Very true, I could do this.
    So why not? Because I don't actively run that computer. I used to muck around with it for C++-on-UNIX development, php development, and in general learning UNIX. Now I just use it to encode CDs to ogg (and this one time to build a library for a friend).

    My main desktop computer is a WinXP box. I haven't found a UNIX-based OS that suits my needs as a desktop OS (I'd purchase a PowerBook today if I had an extra $3088).

    Why wasn't Linux From Scratch on my list of things to try out when I was tyring things out? Simply because I didn't know about it. I got turned on to OpenBSD by a friend, tried the others, but stuck with OpenBSD. I ran 2.9 for a long time, upgraded to 3.0 for some feature that 2.9 lacked, and have stuck with it.

    I do everything in monotype. You are not the first to complain. I find it easier to read. My only wish is that it be sans-serif.

    --
    "Dying tickles!" -- Ralph Wiggum
  57. Re:Hooray! by jpmorgan · · Score: 3, Interesting
    Part of the problem with security with respect to SMP isn't just the kernel. Many subtle race conditions that could result in security flaws are more likely to be exploitable in a truely parallel environment than they are in just a concurrent uniprocessing environment.

    In addition to just making sure the kernel has it right, you've got to make sure that it's not going to open up any holes in the userspace too.

  58. Re:'ehh by Gothmolly · · Score: 2

    And 640k ought to be enough for anybody.

    --
    I want to delete my account but Slashdot doesn't allow it.
  59. Note: Announcement Not From OpenBSD.org by Nathan+Ramella · · Score: 3, Insightful

    Please take note that this announcement didn't come from OpenBSD.org. The guys doing it as just doing it as their own project (which is neat). One of the main reasons people enjoy OpenBSD is that it's code has been audited by Theo and his folks and prepared to be the most security oriented distro around.

    --
    http://www.remix.net/
    1. Re:Note: Announcement Not From OpenBSD.org by ISWalker · · Score: 5, Informative

      Finally someone who is correct. I'm one of the students working on this. It is our computer engineering project. The plan is to have it somewhat working by January. We decided to this because we needed an idea for project and we thought it would be fun and allow us to learn a lot in the process. When the project is complete, we plan to release the code we have and if OpenBSD wants to use it he can, however, that wasn't necessarily the original intent.

    2. Re:Note: Announcement Not From OpenBSD.org by Anonymous Coward · · Score: 0

      The plan is to have it somewhat working by January.

      Let me guess; "working" means that you'll have the whole 200 lines of code needed for spinlocks done, and it will init the ASIC, spin up all the CPU's, and then you'll have one big lock in the syscall interface that wraps the entire kernel and makes the second CPU a small space heater. Yes?

      Have fun making all that code re-entrent by the way!

  60. Not quite? by Anonymous Coward · · Score: 0

    Hmmmm....last I heard it was something like "Only multiple remote kernel holes in the default install, in more than 7 years!"

  61. Re:Hooray! by Anonymous Coward · · Score: 0

    You're still posting in monospace.

    It still sucks.

    Since there is no modifier to allow me to have monospaced posts marked -2, fuckwit, I'm asking you nicely, please stop.

  62. Re:'ehh by skelley · · Score: 1
    Hmm. Four OS crashes in 18 months. Not great, but not too bad. They spent more time down due to power and network failures.
    And, as always, the experience of one person is merely anecdotal (definition:Based on casual observations or indications rather than rigorous or scientific analysis).

    • 2000-08-23 ~04:00 GMT: OpenBSD crash. Cause undetermined.
    • 2001-01-05 19:45 GMT through 21:10 GMT: OpenBSD crash. Cause undetermined.
    • 2001-08-26 ~04:00 GMT through ~19:00 GMT: OpenBSD crash. Cause undetermined.
    • 2002.02.26 ~17:30 GMT through ~19:30 GMT: OpenBSD network stack crash. The load was not heavy (about 20 web downloads per second from slashdot, plus a few mail deliveries per second) and presumably would have been handled without trouble by the FreeBSD network stack.
  63. But... by Anonymous Coward · · Score: 0

    I thought BSD was dead? :/

    1. Re:But... by Anonymous Coward · · Score: 0

      Darn you, stop posting as AC so I can mod you down!

  64. SMP, yet won't boot with loader beyond 8G by LM741N · · Score: 2

    I find it funny that all of these wonderful features are being added to a system that won't boot beyond 8G.

    I've been having my own personal hell getting grub or lilo to boot this system on a second HD. My only success so far is to use the entire disk and then chainload it. Suggestions are welcome.

    1. Re:SMP, yet won't boot with loader beyond 8G by Anonymous Coward · · Score: 0

      All you need is the kernel below the 8G limit. The simple fix is to put a slice down towards the beginning of your disk with the OpenBSD / -- 128 MB is lots of room for it, then put whatever else you want, and after that, put the rest of the OpenBSD install.

    2. Re:SMP, yet won't boot with loader beyond 8G by iggymanz · · Score: 2

      8G limitation is due to your bios and use of crummy Wintel architecture. My Sun machines boot from any partition anywhere, as does my SGI.

    3. Re:SMP, yet won't boot with loader beyond 8G by Anonymous Coward · · Score: 0

      Its due to a crummy loader. GRUB can boot from anywhere on a disk; the problem is that OpenBSD does not use GRUB.

    4. Re:SMP, yet won't boot with loader beyond 8G by iggymanz · · Score: 2

      here's a link to using OpenBSD with GRUB, the problem is that the GRUB docs for OpenBSD are so old they're wrong. But, whether or not GRUB can get beyond certain limits of disk size have to do with particular BIOS in question (according to GRUB pages, scroll up from this entry point): http://geodsoft.com/howto/dualboot/grub.htm#openbs d

  65. I know... by drivers · · Score: 2

    This would be an extension of that... one version of unix reimplementing something that is already in linux.

  66. Re:Toasters and Wristwatches by Lord+Bitman · · Score: 2

    But linux has already done both of those! Get a new goal!

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  67. Re:Hooray! by Anonymous Coward · · Score: 0

    And thus you put your foot in your mouth as you explain the exact reasons why IPv6 came first while at the same time question why SMP is late--OBSD has a different focus than your typical lame-brained OS.

  68. Re:'ehh by Anonymous Coward · · Score: 0

    Hmm ... two years up here, never seen a crash, and I run OBSD on 3 different architectures. Only rebooted for things like kernel patches. He probably has some subtly incompatible or buggy hardware -- such is life. OpenBSD is pretty much just as stable as Linux or other BSDs, but hardware support isn't always as expansive or broadly tested as, say, Linux (exactly as you would expect with only a fraction of the users).

  69. Re:Hooray! by DA-MAN · · Score: 1

    I don't see how you came to that conclusion from my post. I was stating that things should be implemented in an order that makes the kernel most useful. I mean shit, even NT4 had SMP, which came out 7 years ago. OpenBSD is a great OS, but there are some seriously weird decisions being made on how things are implemented.

    I mean ipv6 will be in use probably never now that nat has caught on. Now there are ugly hacks in the works for dns and nat to allow for two way communication.

    What's the point of having the most secure OS out there if you can't use it for things that need to be secure because you are limited to one proc. Anyone know of any high traffic dynamic web sites that use OpenBSD? Ever wonder why?

    --
    Can I get an eye poke?
    Dog House Forum
  70. Re:Am I reading this right? by Anonymous Coward · · Score: 0

    >On the comercial side of things, most BSDs *do* have SMP. And very good SMP as well.

    Actually, that's crap. Most commercial Unixes are based on SVR4, not BSD. BSDi is (was?) probably the only close-to-mainstream commercial BSD.

  71. Re:Supporting SMP: How you can help. by Anonymous Coward · · Score: 0

    It starts off sane, then wanders into lunacy. Brilliant joke or just a troll... I can't decide.

  72. Re:Supporting SMP: How you can help. by Anonymous Coward · · Score: 0
    You consider democracy, the cause for which many millions have died, to be "lunacy"?

    Thank you for your valuable opinion Adolf.

  73. Re:Why OpenBSD is so slow by ibennetch · · Score: 1

    But.. OpenBSD is more secure! Just try cracking my OpenBSD based webserver at 198.247.175.96 try cracking mine at 127.0.0.1

  74. Re:'ehh by grub · · Score: 2


    am I the only one that's surprised that it didn't have this before?

    Don't be suprised. OpenBSD's goals and claims to fame are stability, security and correctness. I donated a dual i386 mobo some time ago to them for the SMP project. I knew SMP on OpenBSD would be a long time coming, but also knew that when it came it would be well tested and solid.

    If you want support for the latest whiz-bang crud to work on your desktop (at any cost) then install the Linux kernel du jour and whatever leet distro is hot this month.

    --
    Trolling is a art,
  75. Re:'ehh by defile · · Score: 2

    That's one example, but his are better documented than mine which is why I didn't share mine.

    Informally, I've run OpenBSD, FreeBSD, and Linux on the same exact machine and had OpenBSD crash for no reason whereas FreeBSD and Linux run fine. *shrug*

    I understand OpenBSD may have less eyeballs but that still doesn't make it acceptable to me. Especially not so when I consider all of the other reasons plus the alternative systems which are just as good if not better in terms of stability, support, etc.

  76. Re:Supporting SMP: How you can help. by Anonymous Coward · · Score: 0


    Isnt OpenBSD already sponsored in part by DARPA and AFRL (air force research labratory)?

  77. Re:Openbsd by SN74S181 · · Score: 1

    OpenBSD was designed to be a secure server, even with default install.

    There's no 'even' about it being secure in the default install. There are other OSes that are pretty secure in their default install as well. That state, in most modern freenixes, is that most services aren't running, most ports aren't open by default.

    So it's MORE likely that boxes with the 'default install' are secure. When the person who did the install starts adding services, configuring it, etc. it's likely it will become by definition somewhat less secure.

  78. Wrong priority. by IGnatius+T+Foobar · · Score: 2

    I'm probably going to get modded down for this, but it's got to be said (and this is from experience; it's not mindless cheerleading) --

    This isn't the best use of OpenBSD developer time, if what they want is a better OpenBSD. Despite its good (but not perfect) security track record, this is an operating system that is riddled with mysterious problems when it comes to Unix compatibility.

    I've got a bunch of source code that builds and runs fine on FreeBSD, Solaris, Linux, and a bunch of other Unices, but OpenBSD introduces reliability problems and some serious performance problems. (The same computer processes the same data with the same program at about 20% of the speed of Linux.)

    SMP is a nice thing to have, but before OpenBSD can really be seriously considered for production use on any but the most trivial tasks, the reliability and performance issues need to be ironed out first.

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
    1. Re:Wrong priority. by Anonymous Coward · · Score: 0

      Could you link to these pieces of sourcecode so we can have them examined and try to find out what is wrong?

    2. Re:Wrong priority. by Tony-A · · Score: 2

      Have you taken the effort to find out *why* it's taking 5 times longer to run on OpenBSD? There are a number of speed/safety tradeoffs where OpenBSD should be overly paranoid and everybody else overly trusting.

    3. Re:Wrong priority. by Strog · · Score: 1

      This isn't the best use of OpenBSD developer time

      Good thing this is 4 students project. They aren't developers for OpenBSD.

  79. from the smp@openbsd.org mailing list: by Anonymous Coward · · Score: 1, Informative

    Date: Tue, 10 Dec 2002 00:11:57 -0500 (EST)
    From: Richy Kim
    To: Will Ellis-Adams
    Cc: smp@openbsd.org
    Subject: Re: spinlocks

    ay papi,

    I can speak for most of the group that our intentions were never as lofty as they appear on deadly or slashdot.
    This is a 4th year design project. It was an opportunity to couple our academics requirements and our personal interests. But the goal, first and foremost, is to graduate -- on time.
    Getting our code merged back is a trifling priority, if even.
    And unfortunately, as academic projects go, we're restricted in contributors outside our group.

    But thanks for encouragement, we will keep in touch with the list as we progress.

    -richy kim

  80. Re:Openbsd by Anonymous Coward · · Score: 0

    ha. i don't think you get it. sure one can install an OS with nothing running on it and nothing listening, but that is plain useless. the idea is to make the box useful, which means that services and applications can be enabled or turned on, knowing that that "default" code base has been audited. the services and applications that are included by default have gone through this audit process.

  81. Re:haha I knew that openBSD was dying.... by iggymanz · · Score: 3, Insightful

    I've yet to see a real-world business application with even a 25% speedup with the addition of a second processor. SMP is expensive and overrated for all but certain "embarassingly parallel" computational tasks.

    I worked for an "internet incubator" that had huge farms of 8 and 4 way Compaq servers running MS-SQL Server 7. One CPU would be pegged at near 100%, while the other processors on the machine would be near idle. With Oracle, the situation was some better, but again less than 25% speedup for 2nd processor, and less than 25% of 25% for 3rd, etc.

    Maybe YOU need to grow up, and actually test the benefits of SMP rather than coo and goo-goo over it like some shiny toy.

  82. goals? by fries · · Score: 1

    Someone please tell me where it says on the goals page that SMP is a high priority?
    When you do security as a priority, fancy features that support threaded (read complex and untrustable from a security perspective) applications just don't quite get a front seat.
    I do wish those dudes the best of successes, perhaps it will get merged in after the posix realtime extensions from rtmx, in the best case.
    I sympathize with many who think they want SMP, but when the choice is security, stability, SMP, pick two .. there can be no question as to the obvious reality for the official distribution in the forseeable future;-)

    --
    Todd Fries .. todd@fries.net .. OpenBSD, because security matters!
  83. Re:Hooray! by octogen · · Score: 2

    Fine, but why do you pay for two processors if you only use one? Of course, you can run OpenBSD on an SMP machine, but if I'd like to run a non-SMP-enabled OS, I would certainly not buy an SMP machine.

  84. Re:Hooray! by gooser23 · · Score: 1

    That is a very good and valid point.

    I purchased the machine off of a friend, equiped it with a few spare hard drives, ram, and 2nd processor, and initially instaled linux 2.4 on it. Later, after concluding that there must be something better than linux/XFree86 became an OpenBSD box.

    Of course, it still runs XFree86 (it really is a shame what happened to Be), but it also runs about 90% less stuff than linux.

    I've considered helping out the OpenBSD team by contributing to the SMP code, but I just don't have the background, time, energy or interest right now.

    --
    "Dying tickles!" -- Ralph Wiggum
  85. Scissors, Paper, Stone by Tony-A · · Score: 3, Insightful

    Pick ONE.
    Different approaches, different world views. It's hard to tell which is better (and why) *after* it's been done, much less *before* it's been done.
    I don't think the duplication of effort is all that wasteful. Image the state of Linux and FreeBSD security if OpenBSD did not exist.

  86. Re:Am I reading this right? by OrangeSpyderMan · · Score: 2

    Most commercial unix systems like solaris are based on BSD.

    Wrong. SunOS 4.x (renamed posthumously to Solaris 1.x I believe, by the Sun Marketroids) was a BSD based UNIX. Sun bit the bullet and shifted to SysV for Solaris 2.x, hence the renaming and major version increment (though IIRC SunOS 4.x was never called Solaris 1.x until Solaris 2.x came out - go figure). The Sun marketroids consequently spat on everything BSD based explaining how the way ahead was SysV. Before that, of course, they spat on SysV explaining how superior BSD was. Marketroids, you see. The other big players (AIX, HP-UX, and, I believe, Tru64 or whatever they call it now) are also SysV based. This was no doubt one of the compelling reasons for Sun's switch, at the time. Which brings me to my point - please name come commercial BSD implementations that have "very good" [sic] SMP.

    --
    Try NetBSD... safe,straightforward,useful.
  87. done it by DrSkwid · · Score: 2

    I broke in and deleted /usr

    hahahahahaha

    no wait .....

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  88. Re:Hooray! by Viol8 · · Score: 1

    I agree about the IP6 thing. Its far too complex compared to IP4 which makes programmers and network admins lives a total pain plus as you say NAT solves the main issue that IP6 was created to address (excuse the pun), ie running out of IP addresses. Having had the misfortune to try and set up IP6 I can safely say it should be back in the lab being sorted out , it sure isn't ready for prime time yet unless you have a Phd in network engineering.

  89. Re:YOU FAIL IT! by deathcloset · · Score: 1

    these work good if you imagine rick moranis as Dark helmet reading them.

  90. Re:haha I knew that openBSD was dying.... by Anonymous Coward · · Score: 0

    Rubbish. If your Compaq servers really behaved that way it's because something else was starving performance (RAM? I/O?). Indeed throwing a dozen CPUs at an I/O bound app will show little or no difference, but throwing CPUs at a CPU bound database improves performance dramatically.

  91. OpenBSD by PegQuin · · Score: 0, Flamebait

    OpenBFD.

    --
    PegQuin--I've got a sneakin' suspicion
  92. Re:Am I reading this right? by Fry+a+Lad+Up · · Score: 1

    Compaq Tru64 UNIX was once called Digital UNIX which was once called DEC OSF/1. The Open Software Foundation (OSF) was created, in some significant part, to counter AT&T's control of the UNIX market: the OSF wanted to prevent an AT&T/Sun hegemony. The OSF code base is very much rooted in BSD (and also includes Mach microkernel code [also used in Apple's Mac OS X]).

    So, Compaq Tru64 UNIX is a very good SMP BSD implementation.

    Tru64 does a good pretty good job of being bilingual with basic apps like /bin/ps understanding both BSD and Sys V options.


    Since noone else has mentioned it: BTW, Bill Joy, a founder of Sun Microsystems, is also the founder of BSD. He packaged the first Berkeley Software Distribution.

  93. Re:Am I reading this right? by merdark · · Score: 1

    Hehe, your right about Solaris. I was afriad of that but was too lazy to do research. Shall we start

    BSD/OS has SMP. SunOS *did* have SMP in the later years. But admittedly it seemed to suck as much as Linux 2.0's SMP. SCO had SMP as well, granted it's also now defunkt. Another BSD based system was DEC's Ultrix, which also did SMP. Again, whether it was *good* was questionable. I never used it and don't know enough to comment.

    Anyways, the point is, there were a lot of BSD based systems that did SMP. Also keep in mind SysV didn't do SMP even in 1988. If your talking about modern BSD based systems, and not BSD/Mach systems (where it's reallly Mach doing the SMP work I think) then we must limit ourselves to FreeBSD (SMP, soon to be very good SMP), OpenBSD (no SMP, but it seems will evenutally have SMP), NetBSD (Has SMP as of next major release, in other words it's complete), and BSD/OS (has SMP).

    So currently most BSD actually have SMP I guess. :) Anyways, it's a pointless argument, I'm not an SMP guru and next time I'll research more before posting.

  94. Re:haha I knew that openBSD was dying.... by iggymanz · · Score: 2

    yes! you're exactly right! In most real world *business* applications, there are other bottlenecks that keep SMP from giving near 100% increase in performance for each additional processor (it was I/O and cache thrashing in this case). I *have* seen scientifc and engineering applications where that wasn't the case, but those 4 and 8 ways are usually a waste of money in view of cost/benefit.

  95. Re:Hooray! by Anonymous Coward · · Score: 0

    You could mark him as a foe and add a -5 to all his posts.

  96. Re:Hooray! by wd123 · · Score: 2

    IPv6 support is not really any more complicated, at an application level, than IPv4 support. In fact the two can be unified using a common interface which is even defined in POSIX.1g. NAT does *not* "solve" the problem of diminished IP space, it simply makes it less immediately burdensome. NAT brings with it a set of unique new problems (like accepting inbound connections). Maybe you've had trouble with IPv6, but that does not mean that it is "inherently broken" or anything like that. IPv6 support on some systems no doubt lacks documentation, but the core technologies are for the most part sound, stable, and ready for prime time.

    The key factor, I think, to lack of IPv6 rollout so far is missing support in routers and Windows. That will come, though.

    Of course, IHBT perhaps. :)

    --
    "question = (to) ? be : !be;" --Shakespeare
  97. Re:Openbsd by SN74S181 · · Score: 1

    I don't think *you* get it.

    If it's not enabled in /etc/inetd.conf as installed from the installation media, it's not the 'default configuration.'

    What good is an httpd that points to some 'default' directory? Once you start loading in content, forms, etc. it's not 'audited'.

    This is picking over nits. But I 'get it'.

  98. Re:Hey! by teamhasnoi · · Score: 2
    Jesus, why is this still being modded? Is there such a lack of good posts that this needs to go to -1?

    Like I care about my karma, being maxed out for the last YEAR. Go mod something UP for chrissake. What a waste of mod points.

    For your modding pleasure, this is offtopic, flamebait, trollish, overrated and quite sad that I even feel the need to mention this.

  99. Re:Hooray! by Viol8 · · Score: 1

    I'm not saying its broken , its just far too complex. I'm sure it would work very well if set up probably , but getting it set up probably is a monumental task. Being a network admin is hard enough without having to worry about all the new issues that IP6 brings to the table which for 99% of companies and home users are irrelevant anyway. And yes there is a common posix interface for ip4 and 6 but the standard C API is not everything. I've recently had to write a network protocol and part of this required sending orginating user IP addresses in our packets. This meant reserving 16 bytes of space in packets in case we ever upgrade from just ip4 which only requires 4 bytes. Plus ip6 addresses have to be stored in an array , not a simple unsigned int making life a lot harder on low level coders like myself.

  100. Re:Hooray! by Anonymous Coward · · Score: 0

    A simple unsigned int on a SPARC, or a simple unsigned int on an x86?

  101. SMP != Server by Anonymous Coward · · Score: 0

    SMP is not a server requirement, at least not for file/web/data servers. There the primary requirement is fast I/O (disk, network). Compute servers would be an exception.

    I submit you're more likely to find SMP in the workstation of someone doing heavy duty crunching (image editing, PCB layout, simulations).

  102. Support will far outpace other BSDs by Theo+DeRaadt · · Score: 1, Interesting

    As OpenBSD is already the most secure OS available, it's no wonder that we have some of the top scientists in Canada working on bringing in SMP support. We would have taken a ton of code from FreeBSD, but we believe that their upcoming implementation is inferior to what we could come up with on our own. Besides, there's no telling what kind of glaring security holes there could be in FreeBSD's SMP implementation.

    --

    --
    Theo DeRaadt
    Founder, OpenBSD project.