Slashdot Mirror


The BSDs in the WSJ: "Help Build the Web"

conio writes "The Wall Street Journal published an article on Friday about the open-source BSDs (mainly FreeBSD) and how they're silently serving the Net. " This was submitted yesterday quite a bit, but was in the pay area-thankfully it's free reading now. Good to see BSD get some of the limelight.

290 comments

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

    Feel free to demo your init programme without an operating system.

    Is it so terribly difficult to understand that an operating system is useless without software running on it, and vice-versa? That fact doesn't change the definition of an operating system.

  2. Re:My experience with FreeBSD by reg · · Score: 1

    Try http://www.freebsd.org/~3d/

    It's a few days out of date (No 3.3.5 yet), but I'm sure the avid gamers will figure it out... Or look at http://glx.on.openprojects.net/

    Like most third party software, the source code used for FreeBSD (the other BSD's) and Linux is the same, and so the feature set is pretty much the same.

    Regards,
    -Jeremy

  3. Re:Start Linux vs BSD Flame war here by Anonymous Coward · · Score: 0

    Both Open and FreeBSD have SMP support for x86 boxes. Theres more anti-FreeBSD FUD
    in the linux world then linux FUD in the windows world (no joke)


    Buggs, this is simply bullshit and you know it. Tell me where I can download OpenBSD kernel source which supports SMP x86. C'mon. All I want is a URL. That's not too much to ask for, is it? You claim the software exists, so tell me where I can find it.

    get your facts straight PLEASE! :P and of course the userland is the same!

    Nonsense. They're three different distributions which ship three different collections of software. As such, the userland *has* to be different.

    Add in other assorted differences (differing binary format standards), and you've got fragmentation at two levels instead of one.

    Buggs, *you're* the one who needs to check your facts. Advocacy is always well and good, but blind advocacy that's nothing more than lies (as in your statements above) only hurts your cause. I, for one, will no longer believe anything you say as a result of this little post of yours. Remember, as Nietzsche said, "What upsets me is not that you lied to me, but that from now on I can no longer believe you."

    As for me, I'll happily run my OpenBSD kernel on my uniprocessor 486 routers, and my SMP Linux kernel on my UltraSparc, Alpha, and PII-class machines.

  4. Re:hmm I dont mean to start a flame war but.... by NovaX · · Score: 2

    hmm.. well, I'm not quite sure about that. From my understanding, only the Berkeley code was stripped of the advertisement. On the rest of the BSD code, which is everything else, it either has the clause or doesn't.

    Sure, now the BSD networking code is largly free, due to UCB. But, Berkeley didn't write all the code in NetBSD, OpenBSD, and FreeBSD, did they? Others tacked on their varient of the clause, while others took it off entirely.

    On the GNU website where they recomend the GPL over the BSDL (obviously was slightly updated due to the p.3 removal), they like to give their propiganda speeches, etc. I'm already a bit disgusted of the GNU project from just reading that.. but that's just becuase I don't see them as freedom fighters, more of lobbyists.

    What they say there, if you go read, is that FreeBSD agreed to change once it was asked of them (I find that shows the maturity of the people on BSD side), etc. That doesn't mean everyone uses the new BSDL, many have their varient.

    I also don't want to start a big war (would be fun if others were up to discussing it in a rational, logical way), on whether the clause was better or not. In some ways, I think it was a protection against the GPL'ing of BSD, which snobby zealots like to talk about, saying they'd love to create another fork, etc. GPL'ing for the good of the community I can understand and be behind, but I really can't imagine anyone being that grown up to do it.

    And people already are working on it. Some take BSD code and submit it to the GPL groups (this happened in reverse once. I (believe) it was NetBSD that accidentally had GPL code in it and they immediately removed it. Its nice GNU didn't laugh at them and force the rest of the surrounding code GPL'd). Others claim they are working on removing any code with clause 3 in FreeBSD and GPL'ing it (someone from CMU said they were doing this (on slashdot). True or not, some one s bound to try). It just goes on, and on...

    But your right, it would be the true test. And I really can't see it as helping BSD. I would suspect that once its GPL'd, the popularity of Linux means it will be imbedded in that system. Insead of BSD getting better, it will be leeched for its treasures. Linux will get better, Linux will get the credit, Linux will get the publicity, Linux will get the developers, and BSD will be hurt. Its legal, but its disrespectful to the groups.

    It would be just like going to a user/news group and starting a license flame war. It was done to piss them off, to show that you can, and the thrill (I believe) is your going into their homes and and trying to demean them. Its really quite childish, which I think over the year both sides have basicly admitted to and try to stop it. But GPL'ing BSD code just to do it and put it in Linux is the same. At least that's my opinion, others may disagree.

    --

    "Open Source?" - Press any key to continue
  5. Here is a clue. by mr · · Score: 2

    >didn't the *bsd flavors of unix had what, 20 years to get their act togethe

    Act together? Hrmmm, considering Sun (perhaps you have heard of them) BUILT their company on the back of BSD, it looks like the BSD act has been together for some time.
    OR how every major Unix has BSD compatibility libs?

    Apple is using BSD in their Mac OS X.
    IBM is using BSD in thier thin client, and the InterJet.
    (are you willing to say that neither Apple nor IBM have their act together?)

    And a bonus clue for your flamebait:

    Linus is on record as saying that *IF* AT&T wasn't suing BSD, there would not be Linux...he would have been using BSD.

    Back to the de-bunking:

    >Then came linux and now the *bsd users have had it and are beginning to come around. I applaud
    them for selling and marketing and creating hype about there product which is what they should of
    done 20 years ago.

    Repeat after me.
    BSD before 4.4 had AT&T licened code.

    Do you UNDERSTAND what that means? It means that only ACEDEMICS could afford a AT&T source licence for AT&T.
    Do you grasp that to distribute the BSD code, you as the user would have to pay AT&T? And pay them a figure over $5,000. $5000 is a few dollars more than the cheapbytes price for the BSD release.


    >Linux said that linux is made up of 30 full time and
    over 1,000 part time programmers who work on the kernel while freebsd has only 15 guys.

    Errr and exactly WHERE are these numbers from?

    >I believe the *bsd
    group should go gnu to compete with linux.

    Hrmmmm. If that were to happen then Apple, IBM (Thin client, whitle and whomever else they have), the 3 man shop in Milwaukee imbedding BSD, and a whole host of others who work on the kernel and submit changes would all just go away. (Wow. When you Add in Apple and IBM it seems like a whole lot more than 15 people work on BSD. Are you getting the feeling that your 'reasons' are less and less reasonable?)
    Whatever happened to the idea that differences make the whole stronger?

    But, from your post, the whole OpenSource community doesn't enter into your view of the world.




    --
    If it was said on slashdot, it MUST be true!
  6. no you don't by delmoi · · Score: 1

    you're link dosn't work
    "Subtle mind control? Why do all these HTML buttons say 'Submit' ?"

    --

    ReadThe ReflectionEngine, a cyberpunk style n
  7. Minor factual Error WAS Re:FreeBSD can't keep up by mr · · Score: 1

    Minor points:

    IBM is *ALSO* 'behind' BSD.
    Whistle Communications
    The Thin client IBM Sells.

    Are 2 examples I am aware of. (Oh, and the Whistle division, like Apple have a history of giving BACK code to the BSD releases)


    So is Intel. (they have given boxes to BSD *AND* Linux developers)

    (And if you want some insight into Apple...read the BSD mailing lists and check out the comments from Apple. It looks like the Darwin decision was a hard fought one....(and given that most of what Darwin is is code that was already published...sorta a no-brainer))


    --
    If it was said on slashdot, it MUST be true!
  8. Re:Loving my FreeBSD-3.3 RC #3 Box by dennisp · · Score: 1

    Ok. 1. FreeBSD also has a package system that allows you to install binaries. (try /stand/sysinstall) 2. Many compile time options. IE. I wanted to compile the newest vesion of apache -- but you can't just get binaries with both mod_perl and php compiled in -- so i just cd to /usr/ports/www/apache13-php3 and compiled apache13+php3+modssl+freetype with the 'make' command; then compiled in mod_perl, then did make install. There are also many programs that I run into that I like to modify before installing. 3. You are right though, that compiling wasted precious time and cpu. I, however, prefer being able to modify settings before compile and install. Large programs like X, though, I'll just install from /stand/sysinstall.
    ----------

  9. Re:Ugh! by Guy+Harris · · Score: 1
    I'm sorry, but `my' definition is the standard, accepted definition of an operating system in computer science.

    Funny, when I was in school, I seem to remember people including more than just kernel-mode code - in particular, one operating system partially developed at the school where I went, namely Multics, had very little code running in "kernel mode" (called "master mode" on the GE 6xx machines and their Honeywell successors) - most of it ran in "slave mode", with some running in "ring 0" (no, this was not an x86 processor, so "ring 0" was not equivalent to master mode - even in ring 0 you couldn't execute the instructions to e.g. start an I/O operation), some running in "ring 1", and some running in "ring 4", which was the ring in which user-written code mainly ran.

    Please show some hard evidence that your definition is "the standard, accepted definition of an operating system in computer science".

  10. Re:hmm I dont mean to start a flame war but.... by Guy+Harris · · Score: 3
    ...didn't the *bsd flavors of unix had what, 20 years to get their act together and yet let windows and proprietary unix os's come in without a care in the world

    20 years ago, you had to get a license from AT&T to get BSD, as large parts of the code in BSD were based on AT&T UNIX code that hadn't been replaced. They weren't out for World Domination at that point - but, then, Linus Torvalds wasn't our for World Domination when he started working on his kernel, either, as far as I know....

    and now the *bsd hackers are pissed at linux users and the whole computer world for ignoring them.

    There may well be *BSD hackers who are pissed at Linux users and the whole computer world for appearing to ignore them, but

    1. not all BSD hackers are;
    2. not all Linux users are ignoring BSD and much of the computer world isn't ignoring BSD, either, as the Wall Street Journal article this thread started out with shows.
    They screwed up bad on marketing it, selling it, creating hype about it, and giving it to users.

    To what extent did the Linux community "market it, sell it, and create hype about it"? And where did the "marketing, selling, and hype" about Linux come from? I'm not sure it all came from "the Linux hackers".

    Linus invented linux because he couldn't get a unix os for his 386 pc. freebsd either couldn't run on it or it was accessible at the time.

    FreeBSD (and the other freely-available BSDs) have always run on PCs, as I think FreeBSD and NetBSD both came from 386BSD which was a port of Net-2 to, err, umm, the PC.

    IF I am correct (I could be wrong). The group of *bsd hackers bickered among themselves and fragmented and made a terrible mistake. THe mistake was it wasn't involved with the IBM pc when it first came out.

    The first attempt at a completely-free BSD (with all the AT&T code either replaced or blessed as "OK to give out") was, I think, 386BSD, whence came FreeBSD and NetBSD; the "386" in "386BSD" referred to the 80386, because it was a BSD port to the PC.

    The *bsd group didn't let outsiders contribute code so users who wanted a more powerful OS had to buy a separate OS more proprietary OS like sun os, irix, aix. The fragmentation in unix itself began.

    "The *bsd group" of those days was the Computer Systems Research Group at the University of California, Berkeley, and they certainly did accept contributions from outsiders. However, not all the stuff Sun, SGI, IBM, etc. did with either AT&T UNIX code or BSD code was necessarily sent back to Berkeley by those companies, and not because the Berkeley folk wouldn't accept it. You can't solely blame Berkeley for the existence of N different flavors of UNIX....

    Unix was crazed by the IS departments until the early 1990's when unix completely became fragmented, proprietary, expensive, and unix companies began bickering among themselves

    That all happened well before the early 1990's; UNIX was well-fragmented by the mid 1980's, with several different proprietary variants, from vendors who largely sold it on their own boxes rather than on, say, IBM-compatible PCs - UNIXes for PCs had existed for a long time, but I don't know how well IN/ix ran on 8088-based PC's (yes, 8088, the one with segmentation but no memory protection), but I suspect it may not have run well enough to push DOS out of the way, and I suspect the same may have been true of the UNIXes for 286-based PCs, although I think Xenix (yes, the Borg's own UNIX, later handed to SCO) may have had a decent market share for small business computers and the like.

    The *bsd crowd ignored bill totally instead of pointing out there fallacies and marketing there OS and they still haven't learned from there mistakes and the source code was still closed and the users ignored average users and were real snotty.

    "The *bsd crowd", if by that you mean the folks at Berkeley and their successors on the {Free,Net,Open}BSD projects, weren't spearheading the commercial UNIX movement - as far as I know, they were building free OSes for their own purposes, which I think was largely what the Linux community was also doing when they started.

    Guess what! Windows took over everything and NT 3.51 came out next and began to steal the unix market.

    Said market was the commercial UNIX market, not the free UNIX "market"....

    Linux has buzz

    Linux has software companies distributing it; for whatever reason, there's no equivalent of Red Hat or SuSE or Caldera or Pacific HiTech or... filling that role for {Free,Net,Open}BSD (no, Walnut Creek CD-ROM isn't in that position, as far as I know), although there is BSDI selling BSD/OS.

    "The *bsd community", if, by that, you mean the developers of {Free,Net,Open}BSD is probably more like the Debian community than like Red Hat or SuSE or... in that regard (although the Debian folk aren't necessarily the official "owners" of all the components that go into their distribution - they're the official source of versions of the kernel, libraries, utilities, etc. that go into a Debian release, but they're not the official home of the Linux kernel or GNU "libc" or...).

    Linux said that linux is made up of 30 full time and over 1,000 part time programmers who work on the kernel while freebsd has only 15 guys.

    The FreeBSD Core Team does have 16 members, but the core team, as the list linked to say, "constitutes the project's ``Board of Directors'', responsible for deciding the project's overall goals and direction as well as managing specific areas of the FreeBSD project landscape" - they're not the sole developers of FreeBSD code. The same probably applies to NetBSD and OpenBSD. There are 151 additional "FreeBSD Developers" "who have commit privileges and do the engineering work on the FreeBSD source tree", and, according to the Contributing to FreeBSD page in the FreeBSD Handbook

    Contrary to what some people might also have you believe, you do not need to be a hot-shot programmer or a close personal friend of the FreeBSD core team in order to have your contributions accepted. The FreeBSD Project's development is done by a large and growing number of international contributors whose ages and areas of technical expertise vary greatly, and there is always more work to be done than there are people available to do it.

    Again, the same may be true of NetBSD and OpenBSD; I'm less familiar with those projects.

    I don't know how many of the core team or the development team work full-time on FreeBSD, so I can't say that FreeBSD has 167 full-time and (some unknown number of) part-time developers (the latter being those who don't have commit privileges but who do contribute code) - and note that this does not say that FreeBSD has more people working on it than are working on Linux systems, as I don't know if those "30 full time people" counts only people working on the kernel or also counts people working on GNU "libc", GNU utilities that aren't also used in the BSDs, etc..

    However, it does suggest that "freebsd has only 15 guys" is a big oversimplification.

    There could well be more people working on the stuff that goes into a Linux distribution and that doesn't also go into the BSDs or that isn't also available for BSD (people working on XFree86 aren't "Linux developers", as their stuff goes into the BSDs as well, and the folks working on KDE, at least, aren't "Linux developers", either, as binary packages of KDE 1.1.1 are available for FreeBSD and possibly the other BSDs) than are working on FreeBSD, but this doesn't mean that FreeBSD, or any of the other BSDs, are ipso facto doomed.

    I believe freebsd had the unix code already and was around over 12 years longer then linux

    12 years before today is 1987; FreeBSD didn't exist then, and Linux didn't just show up today, so FreeBSD wasn't around 12 years longer than Linux. Much of the BSD code was around before Linux existed, but much of the GNU and other code that goes into a Linux distribution was around before Linux existed as well, so I'm not sure {Free,Net,Open}BSD had as big a head start as you seem to think (it did have one, as far as I know, but not a 12 year head start).

  11. Re:Ugh! by Guy+Harris · · Score: 1
    Win32 is no more an OS than POSIX.

    That was the point I was making.

  12. Linux crapware by Anonymous Coward · · Score: 0

    Even the best version of Linux still seems thrown together compared with BSD. Try "man diff" or "man getyx" on Linux. No answer. Now try it on BSD. Even when Linux doesn't tell you to go blow, it's still inferior. Compare "man 4 tty" on Linux and BSD, for example.

    1. Re:Linux crapware by MadCat · · Score: 1

      Even the best version of Linux still seems thrown together compared with BSD. Try "man diff" or "man getyx" on Linux. No answer. Now try it on BSD. Even when Linux doesn't tell you to go blow, it's still inferior. Compare "man 4 tty" on Linux and BSD, for example.

      Don't you mean that the documentation is inferior? I agree that Linux' man pages are lacking but that has nothing to do with stability of the OS itself.

      Each OS has it's own good and bad sides. FreeBSD is more suited as heavy traffic server, then again Linux is more suited for small businesses, since it is easier to install and easier to configure (in my own humble opinion.

      Why can't everyone just get along? It's bad enough that there's so much bickering between *BSD and Linux advocates -- after all it's all Unix.

      --
      There is no sig...
    2. Re:Linux crapware by Anonymous Coward · · Score: 0

      The documentation is part of the whole kit and kaboodle. It's pretty rough developing a program is you can't look up the behaviour of the components you want to use, as illustrated above.

  13. Re:Free BSD / Linux by Skapare · · Score: 1

    I see the BSD vs Linux debates as not really much different than the Redhat vs Slackware vs Debian vs Caldera vs Suse ..... (and on and on).

    Different strokes for different folks.

    We should all be working together to promote the similarities as well as the diversities. Ideally I should be able to plug in different versions or totally different code for applications, daemons, libraries, and even the kernel itself. Of course what makes one system unique can impede that to a degree.

    Now if I can only find someone that will really help me try to get my 3.1 CD installed, instead of telling me that my hardware, which runs Linux and Windows just fine, is broken. Maybe I should try a net install instead.

    --
    now we need to go OSS in diesel cars
  14. Re:If only your article were not so full of FUD... by Guy+Harris · · Score: 1
    and apt-get install apache is certainly less typing than feeding the whole (sometimes very long and akward) URL to pkg_add on FreeBSD

    I may well have typed a full URL to pkg_add once, but, most of the time, I just use the -r flag and give pkg_add the package name.

  15. Re:Ugh! by Guy+Harris · · Score: 2
    In short, the operating system is the software that runs in system space (aka kernel space). Anything that runs in user space is, by definition, not a part of the OS.

    That may be your definition of OS.

    It is not my definition of OS.

    Yes, any application running on a system with a UNIX-flavored system call interface and APIs implemented atop that could, in theory, be written solely using system calls by replacing all the non-system-call APIs by reimplementations of those APIs.

    However:

    1. it's not clear whether this would, in general, be a useful undertaking;
    2. the rewritten application (or, for that matter, a statically-linked application not rewritten in that fashion) might not function entirely as desired when run on a later version of that system (consider, for example, a system in which "gethostbyname()" merely read "/etc/hosts" - if somebody wrote their own "gethostbyname()" into their application, and a later release of the OS replaced that "gethostbyname()" with one that determined from a "/etc/nsswitch.conf" file whether to use "/etc/hosts" or NIS or NIS+ or DNS or... to look up host names, an application dynamically linked with "gethostbyname()" would automatically pick up the new behavior, but a statically-linked application, or one that used only system calls and read "/etc/hosts" itself, wouldn't;

    so I don't consider "an OS is the software that runs in kernel mode" a particularly useful definition (especially given that there may well be machines that have a more fine-grained privilege level than just kernel vs. user).

    I'm not sure what the right definition of "OS" is, but I tend to consider anything that, if removed, would keep the system from running usefully to be part of the OS, which means that, at a minimum, that includes, on a modern UNIX-flavored system, init, the shell that runs the "rc" files, the commands run from the "rc" files as distributed and configured by system installation, and the shared libraries with which those programs are linked - and if that brings in "libc", well, the "libc" in most Linux distributions is either derived from a GNU "libc" or is a GNU "libc", so....

    Yes, some of the stuff that falls into that category may also run on other systems, but I don't consider that sufficient reason to consider it "not part of the OS" on a system where it's a standard component of that system - GNU "libc" isn't "part of the OS" if the system has its own "libc", but if the system's "libc" is GNU "libc", I consider that a different matter.

  16. Re:BSD/Linux and BellLabs/Linux -- ??? by Anonymous Coward · · Score: 0

    Do you have brain? How come such names as BSD and BellLabs are relevant here? If you want to make a point, make a valid one. You look pretty much like a child who just want to win without reasoning. BTW, I'm a proud FreeBSD user as well as ex- slackware and ex-RH since 1993.

  17. Re:Ugh! by Guy+Harris · · Score: 1
    If the kernel is the OS, then I'd appreciate it if you start referring to the "Win32 OS" from now on.

    Win32 isn't actually implemented by the NT kernel - the NT kernel implements its own programming interface, which is used by the libraries and Win32 subsystem process that implement Win32.

    This, arguably, even more strongly emphasizes the point that the OS isn't ipso facto the kernel, if the kernel of some system doesn't directly implement any of its API, unlike UNIX-flavored systems where at least some of the API tends to be direct system calls, even though a lot of it isn't.

  18. Re:hmm I dont mean to start a flame war but.... by NovaX · · Score: 1

    wow.. what a load. I think the two earlier replies strongly defeated your claims, and pointed out the weaknesses to your argument. But it was a good argument.

    I just have two points to add:

    I believe the *bsd group should go gnu to compete with linux.

    Please tell me how this makes any sense? I keep hearing this, but I really don't see the point in the argument.

    First, even it might be impossible to track down all of the people who contributed and somehow get them all to agree to a new license. Do you think Linux could do the same? Everyone must agree, and then even after that there's likely some other legal tidbits to work out. Its just crazy.

    I remember when GNU/RMS and others attacked free *BSDs, especially FreeBSD, saying they were unstable as the group could just go closed source, and exploit its user base to buy upgrades. That's just as illogical. Even if FreeBSD, Inc. tried to do that, its code is still BSD'd, and enough programmers would split and take over. That was just creating FUD, and saying BSD needs to GPL itself to compete is just more FUD.

    Oh, and lets not forget another catch. Why would you want all these OSes under a GPL? That competes with Linux, and as Linux is the hype, it makes absolutely no sense for BSDs. If you claim BSD's would thus get more programmers, how? Lots of BSD hackers like the BSDL better, and BSD would lose much of its community, as many companies use BSD code in their products. Microsoft uses BSD networking code, as a small example. Would they if it were GPL, nope. Would small startups based on networking use it? Nope. Would Sun have ever used it, back in the day. I doubt it.

    So, please tell me where any shread of logic is in this statement. I really would like to know, honestly. I can't figure out why so many Linux users say this. Is it just monkey-do, monkey-see, or is there some twisted (or untwisted) logic to it? And please, don't say 'because I like the GPL better.' That doesn't explain why its a good stratigy.

    Secondly,

    Linux is accelerating faster then *bsd while the community scoffed and ignored linux and now like the rabbit in the story it may be too late for freebsd unless it radically changes.

    Again, I beg to differ. The community that scoffed was mostly the Windows/Mac/OS2 and commercial UNIX/non-UNIX (server/workstation) community. Sure, BSD hackers had some ego on their part, they deserved it, they were mostly proffesional programmers verse a mixture of proffesional and non-proffestionals. The community was a bit kinder to BSD because of its license and academic background. That's about it.

    Shall we create some affirmative action plan because Linux at one point was 'scoffed' at? Maybe we need to start trading developers, saying every 10 bad remark ever said.. wait, ever thought against Linux deserves to force 1 BSD developer to convert. Nah, wouldn't work. And this is all beside the point, because calling Linux the underdog isn't all that accurate either.

    I'd actually incline to say that line has no relevant meaning at all. Here's a bit from SVLUG's history, back in the day when it reformed its UNIX SIG into a free UNIX SIG, and tried to pick which brand to support...

    "The fight for which system was best continued through 1993. In December we had a combined meeting with SVNet where we had speakers comparing Linux, NetBSD and Coherent. By then 386BSD itself was drifting away because of the lack of updates, and the 2 groups, NetBSD and FreeBSD, were fighting for control. At the same time there were many happy users of Coherent that were willing to spend $99 for a system that had a number you could call for support. 1993 was also the year Linux on CD-ROM became popular. Linux won over *BSD because of the "fear, uncertainty and doubt" about putting Net/2 on a CD-ROM and getting sued. In 1993 we lost the Cupertino library and moved to the meeting room attached to the Carl's Jr restaurant at First and Trimble in North San Jose.

    "In Februrary 1994 we had a meeting discussing the newly released NetBSD 0.9. In August 1994 SVNet had a meeting where Bill and Lynn Jolitz demostrated their 386BSD Release 1.0. There were a few *BSD holdouts, but by this time the rest of the group had all gone with Linux. In December our listing in the Mercury News (which was the only announcement that month) was changed from "PC Unix SIG" to "PC Unix/Linux SIG", and our attendance jumped from 12 to 20. It became clear that the community interest was in Linux, and we should probably change our name."


    Maybe I should mention SVLUG is the oldest, debated as the largest, and is definately one of the most active LUGs. Just take a glance at it, and you'll see many of the old and new media blitzes that revolved around Linux users came through their handywork. The Burn all Gifs day was the most recent, started by a member. They did a good job on the Refund Day (I believe it was a few LUGs working together), etc. Many splended things, and many great members.

    But please.. can someone explain the GPL thing. It really boggles me.

    --

    "Open Source?" - Press any key to continue
  19. Re:Start Linux vs BSD Flame war here by Anonymous Coward · · Score: 0

    This is not true. OpenBSD hasn't SMP support and never will have unless NetBSD developers will write it. (which is on-going project on sparc, alpha, i386)

  20. Re: Factual issues by Anonymous Coward · · Score: 0

    1.Theo didn't show full e-mail exchange. 2.He publicized _private_ emails. Isn't that a little bit rude ?

  21. Re:hmm I dont mean to start a flame war but.... by Guy+Harris · · Score: 1
    may be you'll know about people like Bill Joy and the great work he did on the original AT&T Unix creating the BSD branch, and Kirk McKusik too, he did the FFS, and all worldwide contributors before the Internet that helped to make BSD the best Unix in 1980

    Bill Joy and Kirk McKusick were at Berkeley when they did their work, so they're not counterexamples to the allegation that the BSD people didn't accept outside contributions.

    Robert Elz of (if I remember correctly) the University of Melbourne may be a better example - he (and perhaps other people there) did the disc quota code that got into 4.2BSD.

    SLIP was another external contribution - Rick Adams at Computer Consoles, Inc. did an implementation of the IP-over-serial-lines encapsulation that 3Com's UNET product (a non-BSD-based TCP/IP stack for UNIX) used, as we needed it for a project we were doing at CCI for the US Naval Surface Weapons Center, and sent it back to Berkeley.

    e2fs is a great fs but was not adopted by any vendor/project, why?

    Vendors didn't want to drop a GPLed file system amidst their non-GPLed software?

    A number of vendors have, in a sense, adopted ext2fs - Red Hat, SuSE, Pacific HiTech, Caldera, etc. provide it as part of their operating system offerings. :-) (I.e., I suspect vendors tend to pick up the Linux kernel, or a Linux distribution, in its entirety, rather than picking up pieces of it.)

  22. My boss only looks at windows NT by Anonymous Coward · · Score: 0

    You think this guy who only looks at linux is pretty bad, my boss refuses to acknowledge that unix even exists. I told my boss about running solaris at the manufacturing plant and he told me "Think NT, unix no longer exists as far as I am concerned". Well I wonder how long my boss will have his job when the manufacturing plant stops during the bsod. I believe he is buying a cluster of 5 NT bozes all switched together so only one of the boxes will crash and I will be the one at 3:00 am driving to work to reboot the machine. Ohhh you got to love IT weekly magazine. :-)

    Oh well!

    I should of got my college degree so I could change jobs.

  23. Re:You've just gotta love diversity.. by PG13 · · Score: 1

    But we aren't lying you are looking at it the wrong way. Imagine you have to sell a beer, will you put ugly people in your beer commercial? NO! Will you be lying because not only attractive people will drink the beer? No! No one actually believes that drinking beer will make them attractive and so forth but people are more likely to use something if it is associated with good looking people.

    Similar issue for Linux. Yes go out and tell everyone that GNU coded most of it just like a little blurb at the bottom of a beer add saying (beer does not make you sexy) this will comunicate the information without hurting the media attention.

    Yes, I grant that RMS has been a driving force behind free software. I am not saying he is bad, merely, this particular insistance is counterproductive. I don't care if Jesus Christ himself had created linux from void if it doesn't make the world a better place to put his name in the title (JesusOS) then he shouldn't demand it be put there.

    --
    Marriage is the "pseudo-ethics" that cloaks the messy truth of sexuality in the raiment of propriety -- it's "Don't Ask,
  24. Re:and the ports by Guy+Harris · · Score: 1
    FreeBSD is more of a standard *NIX, than Linux is.

    In what sense?

    I was recently informed that Hotmail which is owned by M$ runs FreeBSD. I originaly thought that Hotmail ran Solaris and HP, which was why M$ ported its IE to thoses platforms

    I'd not heard that Hotmail ran HP-UX, just a mixture of Solaris and FreeBSD.

    I'd also not heard that this had anything whatsoever to do with Microsoft's choice of platforms to which to port IE; the impression I had was that some customers wanted to standardize on one browser for all platforms in the company, including their UNIX boxes, and that they ported IE to the platforms that would help them the most in getting those customers to choose IE.

    The choice of platforms probably also depended on the platforms for which Mainsoft's MainWin "Win32-atop-UNIX" platform was available, as that's how they did the port; it doesn't appear to be available on any x86 UNIX, just AIX on RS/6000's, HP-UX on PA-RISC machines, IRIX on SGI MIPS machines, Solaris on SPARC machines, and Digital^H^H^H^H^H^H^HTru64 UNIX on Alpha. Whether this is the result of Microsoft not wanting competition on PCs or not is an interesting question, to which I don't know the answer.

  25. Re:My experience with FreeBSD by cobar · · Score: 1

    I've actually been running the linux Xserver that nVidia provides + their GLX driver for playing Q1/2/3test, etc. Works fine under emulation except I can't drop to a console without crashing X. I'd switch up to fBSD XFree 3.3.5 but Q3test went crazy on me when I tried.

    SBLive support is non-existant at this point and probably will continue to be until Creative opens the specs/OSS releases their driver. For the time being I'm using an AWE32 in it's place.

  26. U don't have to deside by Kajakske · · Score: 1

    I'm a win32 user (ok, it sucks), but I will go to linux or unix with my new computer.
    So I doubted between RedHat (they come in a very nice box, unfortunatly it costs a lot so I downloaded it) or freeBSD (I liked the devil).

    But after all the doubts I desided to use RedHat and FreeBSD.
    First I'm going to try RedHat, then FreeBSD. Then I will deside what's the best one and then use that one.
    If u haven't tried a piece of software yet, you can't make up if it is good or not.

    So to all u who are shouting at the other OS (linux, Unix Beos, I don't care) just try the other ones. They are probably all better than Win32 :)


    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Belgium HyperBanner
    http://belgium.hyperbanner.net

    1. Re:U don't have to deside by Anonymous Coward · · Score: 0

      Don't say "go to linux or unix". You just mean Unix.

    2. Re:U don't have to deside by Anonymous Coward · · Score: 0

      No, they might mean Linux, instead of Unix.

    3. Re:U don't have to deside by Anonymous Coward · · Score: 0
      Wrong. Linux is Unix, and BSD is Unix, and all the things that are UNIX are also Unix, albeit at times lamely. Linux is Unix. Windows is not.

      Got it? Good.

    4. Re:U don't have to deside by Anonymous Coward · · Score: 0

      GNU= GNU's not Unix

    5. Re:U don't have to deside by Anonymous Coward · · Score: 0

      GNU is a religion, and the whole "not Unix" gmae is a semantic trick, just like most of their propaganda. Think about it. The whole "free" thing is a self-serving game.

    6. Re:U don't have to deside by Kajakske · · Score: 1

      Ok, so ...
      Linux is Unix ... Fine to me :)



      =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
      Belgium HyperBanner
      http://belgium.hyperbanner.net

  27. Re:Factual issues -WRONG by Tim+Sutherland · · Score: 1

    I'm glad the author didn't say that, because it's not true. Minix is under a more restrictive license than Linux, so Linus could not use any Minix code for Linux. Linus did early development under Minix though.

  28. Doing *bsd a disservice? by rde · · Score: 0

    I'm not sure he's being fair to the popularity of *bsd; pretty much everyone I know is aware of the fact that if you want a more secure server, BSD is the way to go. Regardless of how much we all love Linux, a lot of people feel a lot more secure.

    (I'll reply too, to save some you the hassle).
    U fukin luser if u cant configre linux 2b sekure u shoudnt b fuckin usin it

    1. Re:Doing *bsd a disservice? by Anonymous Coward · · Score: 1
      Someone hasn't been reading Bugtraq lately. *Lots* o' BSD exploits lately. To claim that FreeBSD is *inherently* more secure than Linux is nothing more than silliness. OpenBSD, maybe...but only when appropriate services are running, and the system is regularly updated.

      Linux vs. BSD is mostly a matter of taste. And license advocacy.

    2. Re:Doing *bsd a disservice? by lomion · · Score: 1

      Article seems like mostly a rehash of what every other BSD vs. Linux article is saying. This is mostly a fluff piece.

      They don't get into why it's used by some of the heavily hit sites on the Internet.

      --
      this space for rent
    3. Re:Doing *bsd a disservice? by Anonymous Coward · · Score: 0

      If you do not run Linux because "there are some 42 Linux distributions" then do not install them all; stick with one. If you do not run Linux because the interface does not meet your need for "stability" then you could pick one dist and find the "stability" you require. If you do not run Linux because the "stability" is not available in the "crash sense;" well you are just full of it. Admit it you are talking out of your Back orifice.

    4. Re:Doing *bsd a disservice? by Anonymous Coward · · Score: 0

      Last I heard it was >100 linuxes out there, but I haven't seen a good list.

    5. Re:Doing *bsd a disservice? by sirket · · Score: 2

      What some OpenBSD zealots forget is just how much cross development goes on between OpenBSD and FreeBSD. All of the holes found in FreeBSD in the last two weeks were found by Ra'daat in openbsd first. However the FreeBSD guys quickly fixed them. Besides which it would take 3 years at this exploit pace to come even close to the number of exploits linux has had. And we dont all use FreeBSD just because it is more secure than linux. It is more secure but the reason I use it is stability. Both in the crash sense and in the interface sense. I also use it for the ease of administration. Things stay the same and the update path makes sense. Linux has none of those features. I also use FreeBSD because I dont like the fact that there are some 42 linux distributions out there none of who can agree on how things should work. There is only one FreeBSD and I like that alot.


      -sirket

    6. Re:Doing *bsd a disservice? by Anonymous Coward · · Score: 0

      Yes, I think we recognize that.

      And we also recognize that Linux isn't based on any coherent architecture.

      It's stone soup. Feeds the masses, but certainly not culinary excellence.

    7. Re:Doing *bsd a disservice? by Anonymous Coward · · Score: 0

      What does it matter how many Linux dists there are? First I have come across a dist that was so different that I could not figure out how to configure things. Second from a user prospective there is less then 1% difference between any *nix. All this talk about how many dists there are is just more FUD.

    8. Re:Doing *bsd a disservice? by Progman · · Score: 1

      This is because the only answer to that is that most unix-like OSes are similarly stable. There are lots of high-trafic sites that use *BSD, lots that use Linux, lots that use Solaris.
      Therefore this stupid religious war will never end, because no way can either followers prove anything against each other.

    9. Re:Doing *bsd a disservice? by Anonymous Coward · · Score: 0

      Hmmm, you say "*Lots* o' BSD exploits lately", summing up they're still less in number than a normal RH release two weeks later. And none of them is a remote xploit to date. I think its a bad idea to compare "linux" vs. "bsd" regards security, there is no such a thing "linux", we have distributions. Some of them (eg. Debian) are safe, others (RH) are like SunOS 4, use the insecurity as free marketing. Each time someone finds a new hole on RH it gets lots of midia for free.

    10. Re:Doing *bsd a disservice? by Anonymous Coward · · Score: 0
      others (RH) are like SunOS 4, use the insecurity as free marketing.

      Of course you realize that SunOS 4.x was BSD-based? :-)

      Solaris, OTOH, is SysV, mostly.

    11. Re:Doing *bsd a disservice? by mochaone · · Score: 1

      To the person who moderated the parent post as flamebait:

      Get off you BSD high horse and get a life, you little piece of shit.

      --
      Hates people who have stupid little sigs
    12. Re:Doing *bsd a disservice? by Anonymous Coward · · Score: 0

      "They don't get into why it's used by some of the heavily hit sites on the Internet. That's what I'd like to know, too! Surely, WSJ/DJ must have used Sun servers at one time along with Solaris/SunOs. The article didn't even let us know what type of servers they're running, just about the BSD OS.

    13. Re:Doing *bsd a disservice? by Anonymous Coward · · Score: 0

      Yep I'm not talking about flavours of Unix but intrinsic security, how many years did SunOS 4 fresh install put a /etc/hosts.equiv with a + + on your server? This has nothing to do with it being derived from 4.1BSD but with Sun bad practices. Compare Debian with RH and you'll got the point

    14. Re:Doing *bsd a disservice? by Zurk · · Score: 1

      what im curious about is why poeple use FreeBSD which has a lot more holes than OpenBSD and then claim its "more secure" than linux. thats a bunch of bullshit, IMHO. If you want security - go with OpenBSD..there is *no* other alternative among the BSDs which has the level of auditing openbsd has..or any other os has for that matter.

    15. Re:Doing *bsd a disservice? by Trepidity · · Score: 2

      I haven't seen any important BSD holes reported to Bugtraq lately. Most have been simple local DoS attacks, which are not really a problem unless you're a shell provider or have untrusted local users. None have been remote exploits, the only category of exploits that are really critical. Compare that to the Red Hat exploits over the last few weeks...

  29. Re:Ugh! by Anonymous Coward · · Score: 0

    I'm sorry, but `my' definition is the standard, accepted definition of an operating system in computer science.

    If you care to ignore standard definitions, your comments constitute meaningless absurdities; useless speech. It's like carrying on about round squares, incorporeal substances and such like. In a word, nonsense.

  30. Re:You've just gotta love diversity.. by Anonymous Coward · · Score: 0

    For crying out loud, man, "GNU" didn't code most of the crud. Who is "GNU"? Do you mean the FSF? I think not. And RMS is hardly the "driving force behind free software". That's just anohter propaganda lie. Free software was here before RMS, and continues to exist -- despite him.

  31. take that by Anonymous Coward · · Score: 0

    you linux zealots (-1 that fast, damn)

    1. Re:take that by Anonymous Coward · · Score: 0

      So the answer to his question would be...yes.

    2. Re:take that by Anonymous Coward · · Score: 0

      *** Obscure? A year ago linux was in 2.0.x -- and a piece of shit I might add. Take a look at FreeBSD 2.2. I'm writing this article on FreeBSD 2.2 that I installed in July of 97' on a Pentium 200 with 96 megs of ram. Don't believe the hype kid. FreeBSD has been what linux hopes to be for years.

  32. Re:BSD/Linux and BellLabs/Linux -- ??? by Anonymous Coward · · Score: 0

    UCB and Bell Labs are relevant because they actually invented this. The FSF didn't.

  33. Re:Ugh! by Anonymous Coward · · Score: 1

    What Linux advocates say often has little to do with reality.

    As to the `Win32 OS', there isn't any such thing. In Windows NT 3.51 and earlier versions of the NT OS, Win32 was simply a user-mode subsystem. Essentially, the NT OS provided a Win32 emulation layer, along with a POSIX emulation layer, an OS/2 emulation layer, etc. In Windows NT 4.0, a large portion of the Win32 layer (including the window manager and the graphical device interface) was moved into system space (to improve performance), and this can now reasonably be considered part of the NT OS itself. Nevertheless, there is still a Win32 subsystem which runs in user space, and which completes the implementation of the Win32 layer.

    Once again, there is no `Win32 OS'. Windows NT (soon to be called Windows 2000) is not the same operating system as Windows 98 (or Windows 95). Both implement the Win32 API, but the underlying operating systems are completely different.

    If you find this difference hard to grasp, consider the number of operating systems which implement the POSIX API (including IBM's OS/390, which nobody in his right mind would claim is the same operating system as, say, SunOS).

  34. Re:Ugh! by Anonymous Coward · · Score: 0

    Win32 is no more an OS than POSIX. Both are APIs which are implemented on multiple operating systems.

  35. Re:Free unix-like OS'es already dominate by Anonymous Coward · · Score: 0

    "In my country the .gov sites are the lame..."

    I thought *.gov was USA government only?!

  36. BSD by Anonymous Coward · · Score: 0

    BSD is great. It's about time it got some real recognition. Linux has its strong points, but it just doesn't have the edge. CMB - NBPS

    1. Re:BSD by bsDaemon · · Score: 1

      i'm pretty sure you're right on that...wasn't the first distribution, like SLS or somthing? Anyway, what's with Linux people calling it a FreeBSD distribution and such anyway? there is ONE FreeBSD, which for all intensive purposes is NOT NetBSD, or OpenBSD. they are different operating systems, unlike RedHat, Caldera, and SuSE Linux's, which are all pretty much the same thing. if you compile a copy of something on a RedHat system, it will most likely work on a Caldera system or what ever, assumning you have the same C libs. If i compile something on FreeBSD, NetBSD may not run it, but OpenBSD has an emulator for FreeBSD binaries (which show obviouse lack of binary compatablility in the first place)

      bsDaemon
      dfree@inna.net

    2. Re:BSD by T-Punkt · · Score: 1

      > i don't get why Linux users are agsinst BSD users and vice versa, just because of their OS?

      It's the typical stupid "my d*ck is longer" or "my daddy's car is faster" game kids play in kindergarden.

      I try to care not too much about it but sometimes when I'm in this special mood I join the game.

      *BSD or Linux?
      The answer is: Yes!

    3. Re:BSD by Arandir · · Score: 2

      "Only thing i want to know is, why is BSD a programme, and Linux an operating system, when *BSD is the kernel, and the libraries and the tools, and linux is just a kernel?"

      Simple, Linux is the name of the kernel, operating system, and the name of most distributions. Likewise, FreeBSD is also the name of the kernel, OS and distro.

      Now I'm sure that this will get me flames since I didn't mention GNU/Linux. So I will. GNU/Linux is the name of a distribution, namely that non-existant distribution provided by the FSF. When RMS started the GNU project, he didn't set out to create an OS. Instead he wanted to make an OS plus everything else needed for normal everyday use. To quote, "The GNU system includes programs that are not GNU software, programs that were developed by other people and projects for their own purposes, but which we can use because they are free software." Thus, RMS was creating what we today call "distributions." Create a small core OS (which isn't complete yet) and add to it the best of free software in every category.

      Who ever puts it names it. The first Linux distribution was called "Linux", so that's why people continue to say it, when technically it should be "Redhat Linux", "Debian GNU/Linux", "SuSE Linux", or whatever else the makers named it.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    4. Re:BSD by Anonymous Coward · · Score: 0

      The first distribution I played with was called "LGX". It was back when Yggdrasil was the first CD distribution. I think they wanted to name it something they could claim "ownership" of. Not sure on that part, though.

    5. Re:BSD by Anonymous Coward · · Score: 0

      Aren't we forgeting a *libc issue on Linux while talking about binary compatibility?

    6. Re:BSD by Trepidity · · Score: 2

      How can you claim that the first distribution was named "Linux"? I haven't heard this before. Sure, the kernel is named Linux, but I see no evidence of there being a complete distribution being called simply "Linux." AFAIK, Linus himself has never created a distribution, just a kernel. All the distributions I've seen have been either "Somebody's GNU/Linux" or "Somebody's Linux," or homebrew systems built around the Linux kernel.

    7. Re:BSD by Arandir · · Score: 2

      "How can you claim that the first distribution was named "Linux"?"

      SLS, Yggdrasil, et al., were all called "Linux". The name "GNU/Linux" didn't arrive until the FSF started to put together a distribution (Debian), which later went independent.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  37. Start Linux vs BSD Flame war here by Anonymous Coward · · Score: 0

    I just know this is going to get FreeBSD likened to Al Gore by Linux enthousuiasts, and "While Microsoft almost never talks about it, its own Hotmail free e-mail service runs not on its flagship Windows NT but on FreeBSD." is going to invoke some heavy giggling. Finally a nice mentioning of "Factional battles and online fusillades" will grow a nice thread about BSD being "hopelessly divided" again.

    1. Re:Start Linux vs BSD Flame war here by Anonymous Coward · · Score: 0

      Hope you're not running Red Hat.

    2. Re:Start Linux vs BSD Flame war here by Anonymous Coward · · Score: 0

      I would rather have the same /etc structure.

      And I would rather have one built on a long tradition, than one a bunch of Python junkies thought up.

    3. Re:Start Linux vs BSD Flame war here by Anonymous Coward · · Score: 1

      Regards: --------- Finally a nice mentioning of "Factional battles and online fusillades" will grow a nice thread about BSD being "hopelessly divided" again. --------- There are more diferences between Red Hat and Slackware than any of the *BSD. Please, the kernel is just a piece of the engine, for the average user it is invisible and userland and configuration counts a lot

    4. Re:Start Linux vs BSD Flame war here by T-Punkt · · Score: 1

      > There are more diferences between Red Hat and Slackware than any of the *BSD.
      > Please, the kernel is just a piece of the engine, for the average user it is invisible and userland and configuration counts a lot.

      Yes, the other big point people flaming *BSD miss is that there is a lot of direct and indirect cooperation between the three BSDs, e.g.:

      If OpenBSD finds and fixes a Bug, the other *BSDs will do the same with their code. FreeBSD has invented the package (they call it "ports") system all *BSDs now have and NetBSD brought USB to the *BSD world.

      The *BSDs help each other *MUCH* more than they "fight". *BSDs diversity is on of its strengths and no weakness.

    5. Re:Start Linux vs BSD Flame war here by randolfe · · Score: 1
      The *BSDs help each other *MUCH* more than they "fight". *BSDs diversity is on of its strengths and no weakness.

      A good example of this is the recent beta release of the LAP (Linux Application Platform) for BSD/OS (BSDI). Our early testing has been extremely positive, with LAP running some native Linux bins faster than equivalent Linux installs. And, LAP was largely the efforts of cooperation between FreeBSD and BSDI, as I understand it.

    6. Re:Start Linux vs BSD Flame war here by Anonymous Coward · · Score: 0

      That's true! That's why both Slackware and Red Hat will use multiple CPUs on SMP Intel boxes, whereas FreeBSD can but OpenBSD can't.

      But enough sarcasm. I'd much rather have the same kernel and different userland (Linux) than different kernel and different userland (*BSD).

    7. Re:Start Linux vs BSD Flame war here by bugg · · Score: 1
      Both Open and FreeBSD have SMP support for x86 boxes. Theres more anti-FreeBSD FUD in the linux world then linux FUD in the windows world (no joke)

      get your facts straight PLEASE! :P and of course the userland is the same!

      --
      -bugg
    8. Re:Start Linux vs BSD Flame war here by Anonymous Coward · · Score: 0

      different userland?

    9. Re:Start Linux vs BSD Flame war here by Anonymous Coward · · Score: 0

      I wouldn't trust Python junkies to design anything in Unix. Remember that the more you hate Unix and C, the more you love Python. I don't trust someone who hates me to look out for my best interests.

  38. Re:FreeBSD can't keep up by Anonymous Coward · · Score: 0

    who cares? We don't need crappy commercial sourcecode. If Linux needs the help of IBM and SGI - fine. BSD doesn't. BSD already has a journaling-fs-style filesystem. (softupdates)

  39. Re:As I make world by Anonymous Coward · · Score: 0

    Does it really work well, linux emulation? I've only ever had to use it once, and dumped that program because it wasnt very useful for me (wordperfect).

  40. FreeBSD can't keep up by delmoi · · Score: 0

    Even if FreeBSD is technicaly ahead of linux now, it won't be for long, Company's like SGI, IBM, and others are behind Linux (and providing code). Those same companys arn't going to want to reliese there code under a BSD style licens beacuse it would enable there compeitors to pilfer there work.
    "Subtle mind control? Why do all these HTML buttons say 'Submit' ?"

    --

    ReadThe ReflectionEngine, a cyberpunk style n
    1. Re:FreeBSD can't keep up by Anonymous Coward · · Score: 0

      We will see if that ever happens.

      Thus far, such threats have just proven to be smoke and mirrors.

      There is a day in court ahead for the GPL. That's inevitable due to the growth of such a large body of code infected by it, from so many different people, of widely varying ideologies.

    2. Re:FreeBSD can't keep up by Anonymous Coward · · Score: 1
      Those same companys arn't going to want to reliese there code under a BSD style licens beacuse it would enable there compeitors to pilfer there work.

      This is a very good point, and one that the BSD zealots often miss.

      If companies are going to go open source, they are unlikely to use a BSD-style license, because the *last* thing they want is for some other company to take their code and use it in a proprietary program, as it doesn't generate good PR/goodwill.

      So, in at least one way, the GPL makes more sense from a commercial open source standpoint.

    3. Re:FreeBSD can't keep up by Anonymous Coward · · Score: 0

      GPL on the other hand makes commercial closed source software impossible. Both licenses have their limitations.

    4. Re:FreeBSD can't keep up by Oniros · · Score: 2

      Apple and I am sure some other big names are behind BSD too. I think Apple chose BSD over Linux for MacOS X because:
      a) NexT was already using some flavor of BSD
      b) the BSD license let them make proprietary extensions without having to release the source.

      So with Darwin (the kernel used by MacOS X client & server) you have the BSD & Mach based kernel/core, and at the top of that Apple will put their proprietary technology (Mac GUI, Quicktime, etc etc.)

      I'm not sure if they could do that with a Linux or another GPLed OS.

      Janus

    5. Re:FreeBSD can't keep up by HalJohnson · · Score: 1

      I haven't been able to find any absolute information regarding the FreeBSD license (if anyone has a good link, please share it with me), so excuse me if I'm totally off base here.

      It was my understanding that the FreeBSD license put less restrictions on the use of the core code. So why wouldn't it be possible for these companies to release their contributions under any type of license they liked? If this were the case, I would think that FreeBSD would be a more enticing platform for them if anything.

      Again, good chance I'm totally wrong here, would really love some definite information regarding the FreeBSD license (and it hasn't been for lack of trying).

    6. Re:FreeBSD can't keep up by Anonymous Coward · · Score: 0
      I'm not sure if they could do that with a Linux or another GPLed OS.

      Of course they could; they would only need to make source available for any modifications/distribution of the GPLd software itself. That wouldn't stop them from distributing proprietary userland stuff. And if they needed additional kernel functionality, they could even add binary-only kernel modules.

      I'm sure the decision to use BSD had a lot more to do with the fact that NEXTSTEP, which they were using as a base for MacOS X, was already BSD-based. Why fix it if it ain't broke?

    7. Re:FreeBSD can't keep up by C.Lee · · Score: 0

      >The flaw in this argument is that the legality of the GPL is very >dodgy. It's never been tested.

      Wrong. It's never been tested as you put it because the person who would contest it would lose. The GPL spells out exactly what the terms of useage are of anything placed under it. Given the wide-spread use of GPL'ed software the argument that people don't know what these terms are can't be made either.

    8. Re:FreeBSD can't keep up by cmc · · Score: 1
      Why fix it if it ain't broke?

      So that's why one of the "CVSmeisters" from the Darwin project is a FreeBSD committer:

    9. Re:FreeBSD can't keep up by belswick · · Score: 1

      Supposedly TiVo's product is Linux-based, but I haven't seen any of their extensions released. Maybe I'm not looking in right places?

    10. Re:FreeBSD can't keep up by Anonymous Coward · · Score: 0

      It wouldn't be tested by an opponent of the GPL. The would be tested if a GPL supporter actually tried to actually block distribution of a non-GPL'd product containing GPL'd code.

      Even though such products are known by many people to exist, none of the GPL's supporters have tried to block their distribution. This is quite possibly because they know the GPL probably wouldn't hold up in a court of law, and exposure of this would end the whole GPL charade.

    11. Re:FreeBSD can't keep up by Anonymous Coward · · Score: 0

      naw, cause if the code is useful --even under the GPL -- anyone can and will pilfer code and include it in their own proprietary implementations.

    12. Re:FreeBSD can't keep up by xuvetyn · · Score: 1

      as far as the license, it boils down to: "Give us credit for our work, and don't sue us if something breaks".
      try this

      xuvetn (proud freebsd-er)

      --
      alive to the universe, dead to the world
    13. Re:FreeBSD can't keep up by bmetzler · · Score: 1
      GPL on the other hand makes commercial closed source software impossible. Both licenses have their limitations.

      On the other hand, how many commercial closed source software packages do you see using the BSD license? The BSD License is an open source license, and although BSD licensed code can be used in a closed source project, the closed software isn't released under the BSD. I am making sense?

      I agree with the poster above. If a company wants to develop open source software, they are going to use a self-defending license. However, I see a strong benefit to supporting BSD's in commercial closed source products over Linux. Linux carries the stigma of "requiring" an open source license to all software released for it. Think of the common response to when a company announces a product for Linux. "Where's the source?" The BSD's don't carry this stigma. I feel that no one in the BSD camp would have a problem if a company released a closed source application for a BSD. So I see, in the future, when people finally understand that Linux is a strong stable platform, and that the BSD's are no different, or perhaps even better, we'll see companies released closed products first for the BSD's, and open source products under the GPL for Linux first. But that's just MHO :-)

      -Brent
      --
    14. Re:FreeBSD can't keep up by Zurk · · Score: 1

      but not *legally*. thats the whole point of the GPL. If caught the company has to open *all* its code - and no one wants to do that.

    15. Re:FreeBSD can't keep up by Zurk · · Score: 1

      TiVo's giving the code to its customers on CDROM for $24..see the manual.

    16. Re:FreeBSD can't keep up by bugg · · Score: 1
      Dont be silly. BSD style licensing makes more sense for a company that already has a codebase

      Release a BSD-licensed version, watch the hackers improve it, take their improvments, encorporate it into their own commerical product

      Plus theres the big 'ol advertising clause :D don't forget that.


      I've yet to see someone release a lot of code under GPL or a similar license and have it not flop.

      Look at Mozilla.

      GPL is good for products by individuals with low resources and little code

      BSD is good for established code bases. There. Its settled. End.

      --
      -bugg
    17. Re:FreeBSD can't keep up by Anonymous Coward · · Score: 0

      The flaw in this argument is that the legality of the GPL is very dodgy. It's never been tested.

    18. Re:FreeBSD can't keep up by Arandir · · Score: 1

      Under the GPL, their competitors can still pilfer their work, they just have to keep it open, that's all.

      However, I see companies using other licenses instead: ASPL, Jikes, QPL, NPL, SCPL, etc.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  41. Please NO MORE *BSD items on slashdot. by Anonymous Coward · · Score: 0

    It only leads to tiresome 'My daddy can beat up your daddy' threads. It was a nice try, but obviously Slashdot is a Linux only forum. Not it's makers, but it's readers.

    1. Re:Please NO MORE *BSD items on slashdot. by Anonymous Coward · · Score: 0

      Fear?

    2. Re:Please NO MORE *BSD items on slashdot. by AndyElf · · Score: 1

      > Slashdot is a Linux only forum. Not it's makers, but it's readers.
      Always thought it was a geek forum regardless the color.

      --

      --AP
    3. Re:Please NO MORE *BSD items on slashdot. by Anonymous Coward · · Score: 0

      disgust.

    4. Re:Please NO MORE *BSD items on slashdot. by Anonymous Coward · · Score: 0

      That's probably because you've not noticed how diverse 'geekness' can be, and is.

  42. You've just gotta love diversity.. by Kitsune+Sushi · · Score: 3

    "The free programs are all variants of the venerable Unix system invented by AT&T Corp. And they aren't just running Yahoo. While Microsoft almost never talks about it, its own Hotmail free e-mail service runs not on its flagship Windows NT but on FreeBSD."

    I wouldn't want to talk about either, since when Microsoft first acquired Hotmail, they switched over all the servers to Windows NT. Needless to say, their setup experienced mild "difficulties" as NT tried to handle the all the user load, and failed.. miserably.. After a short period (not short enough for many, I'm sure) they were forced to switch back. And they call their systems "advanced"?

    "The Linux saga is already the stuff of modern legend. In 1991, Linus Torvalds, a 21-year-old student in Helsinki, began writing an operating system essentially from scratch so he could have something to use on his home computer. The programs FreeBSD, NetBSD and OpenBSD, by contrast, are the descendants of code written in the late 1970s and early 1980s at UC Berkeley."

    Oh please. No matter how technically accurate or inaccurate the media is, they always leave out some important aspects. I know I sound like a broken record, but I feel as if this is an important issue which needs to be addressed. Is there any way we can let the media know that we have GNU/Linux today because of both the GNU Project and Linus Torvalds, and not just Linus? Public perception is a big deal.. the only thing people listen to are just PR issues, anyway. Any insights on this? I don't believe I've heard of any before.

    Ugh. Just killed article window. Too lazy to reopen. Hmm.. "no ego about letting people use their software"? I think I got that right, and it sounds egotistical in and of itself. What, GNU/Linux was all written by just one person? Ha!

    --

    ~ Kish

    1. Re:You've just gotta love diversity.. by Anonymous Coward · · Score: 0
      "The free programs are all variants of the venerable Unix system invented by AT&T Corp. And they aren't just running Yahoo. While Microsoft almost never talks about it, its own Hotmail free e-mail service runs not on its flagship Windows NT but on FreeBSD."

      Don't they actually use Solaris for the back end (with FreeBSD for the web servers)?

    2. Re:You've just gotta love diversity.. by goop+crap · · Score: 1

      i thought Hotmail was run on Solaris before Microsoft took them over...

    3. Re:You've just gotta love diversity.. by lomion · · Score: 1

      Yes it's solaris on the back end, i think they were focusin on the web aspects though. Note the title of the article..


      --
      this space for rent
    4. Re:You've just gotta love diversity.. by Anonymous Coward · · Score: 0

      Linux is succeding where BSD did not b/c linux is sexy.

      Gack! Please, oh please, stay on Linux. It wants people like you. It needs people like you to succeed.

    5. Re:You've just gotta love diversity.. by PG13 · · Score: 2

      >Is there any way we can let the media know that >we have GNU/Linux today because of both the GNU >Project and Linus Torvalds, and not just Linus?

      Look this is a silly stupid ego issue for Stallman. Is it true that much of what is considerd linux is actually GNU software? Yes. Is it true that plenty of other people but Linus deserve credit? Yes.

      Does this mean it will benifit linux or the public at large by forcing GNU/Linux down their throughts? No!

      The myth of Linus and his singlehanded development of the operating system plays an important role in the media recognition of linux. People's imaginations are not fired up by commitees, they are fired up by individuals and strong leaders. There is a reason we consider the president of the US to represent the United States when in reality congress hasmore to do with the present state of the US than the president.

      Linux is succeding where BSD did not b/c linux is sexy. Stallman would take this away from us with his self serving whining about getting credit. If he truly cared about free software rather than his own image he would let it go for the greater good.

      --
      Marriage is the "pseudo-ethics" that cloaks the messy truth of sexuality in the raiment of propriety -- it's "Don't Ask,
    6. Re:You've just gotta love diversity.. by Trepidity · · Score: 2

      So what? Sure, the myth about Linus single-handedly developing Linux from nothingness into Linux 2.2.10 is a compelling one, but it's still a lie.

      Lying to get more market share doesn't sound like a very good thing to me. If it takes that to get market share, fuck market share. I'd rather have integrity. That's something Richard M. Stallman has plenty of.

      As for all your whining bullshit about Stallman hurting Free Software, let me remind you that without Stallman, much of this Free Software you want to gain more market share wouldn't exist. Without GCC, there would be no Free Software UNIX-like operating system, since there'd be no way to compile software on it, or even to compile the kernel.

  43. Re:Ugh! by Anonymous Coward · · Score: 0

    Why would anybody want to demo init (it's shocking that you refer to it as "your init program" but I guess you slept through part of your Operating System class or whatnot) without the rest of the operating system?

  44. stability? by Wakko+Warner · · Score: 1
    Er, I have never had either FreeBSD *or* Linux crash on me in as long as I can remember. To claim one is more stable than the other and use it as a selling point strikes me as rather ill-informed.

    I've got a FreeBSD box on one side of this room that's been up for 169 days, and a Linux box on the other side of the room that's been up for 168 days. Which is more stable? Flip a coin.

    - A.P.
    --


    "One World, one Web, one Program" - Microsoft promotional ad

    --
    "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
    1. Re:stability? by Anonymous Coward · · Score: 0
      Really? But you use it as a home system or a small server, right? You can't compare your pornsurfing to running a HUGE web site...

      -T

    2. Re:stability? by Wakko+Warner · · Score: 1
      Any idiot who runs a "HUGE web site" on a single machine and expects stability deserves every single thing they get.

      - A.P.
      --


      "One World, one Web, one Program" - Microsoft promotional ad

      --
      "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
  45. Re:Loving my FreeBSD-3.3 RC #3 Box by Anonymous Coward · · Score: 0

    As a minor note, EGCS is the standard compiler on FreeBSD CURRENT builds, and you can use -mpentiumpro on newer x86 machines. The following is from the CC/GCC (EGCS) man page in FreeBSD 4.0-CURRENT:

    i386 Options
    -m386 -m486 -mpentium -mpentiumpro -mno-486
    -mcpu=cpu type -march=cpu type -msoft-float -mrtd
    -mregparm -msvr3-shlib -mno-ieee-fp
    -mno-fp-ret-in-387 -mfancy-math-387
    -mno-wide-multiply -mdebug-addr -mno-move
    -mprofiler-epilogue -reg-alloc=LIST

    http://www.freebsd.org/cgi/man.cgi?query=cc&apro pos=0&sektion=0&manpath=FreeBSD+4.0-curren t&format=html

    Among other things, I also use size optimisation on systems with limited memory/disc space (-Os rather than -O2 or -O3).

    The only Linux systems I've actually used are SuSE and Red Hat. SuSE is quite nice, but less of a pure `UNIX development workstation' environment than FreeBSD (IMHO). I didn't much care for Red Hat; in part, perhaps, because of file-system corruption, but that is really the fault of EXT2FS, not Red Hat.

    At any rate, I have heard good things about Debian GNU/Linux, and would probably consider using it if FreeBSD wasn't an option. It sounds like it's a similar project to FreeBSD, really (despite the ideological licence differences). In all honesty, the Debian web site can't compete with the FreeBSD one, but then I've never seen any that can (neither NetBSD nor OpenBSD comes close in this respect).

  46. Re:As I make world by Anonymous Coward · · Score: 0

    I've found the current Linux ports to be excellent. The linux_base port installs the core Red Hat components with RPM. There are additional linux_* ports, and other Linux-based ports (such as Netscape for Linux), or you can use the standard Red Hat RPM tools to add additional packages (which aren't managed by the ports scheme, of course).

    A Red Hat 6.0 package is available, but hasn't made it into the distribution yet (it's still being tested, etc.).

    I primarily use Linux mode for Netscape and RealPlayer, but it seems to work brilliantly.

  47. Re:Hey, lets do some math by Anonymous Coward · · Score: 0

    "We" the "OpenSource", may be?

  48. Re:hmm I dont mean to start a flame war but.... by Anonymous Coward · · Score: 0

    Please read Peter Salus book before posting, may be you'll know about people like Bill Joy and the great work he did on the original AT&T Unix creating the BSD branch, and Kirk McKusik too, he did the FFS, and all worldwide contributors before the Internet that helped to make BSD the best Unix in 1980. Not to talk about TCP/IP on Unix, telnet, ftp, r* commands, etc. BSD is the most influential open source project of the Unix history, you can find its ideas, concepts, methods and applications deep inside all other Unices. I'm still waiting the Linux contribution comming back to other systems, e2fs is a great fs but was not adopted by any vendor/project, why?

  49. Re:Free unix-like OS'es already dominate by Anonymous Coward · · Score: 0

    take that as: (1) my country is USA; or (2) by *.gov we understand *.gov.XX or *.go.XX and *.gov. You'll be surprised but it works.

  50. Re:Factual issues by Anonymous Coward · · Score: 0

    This isn't meant to be a flame, but I think part of the problem with GNU is it's got a stupid name (an acronym which is pronounced differently to the identically-spelt English word), and it's founder/leader looks and acts like a complete nutter.

    When faced with this ridiculous name and bizarre, fanatical leader, many people naturally associate GNU with fanaticism.

  51. Ayup.. by Kitsune+Sushi · · Score: 1

    Actually, I was going to mention Java, but even talking about its performance issues these days hurts my head. I mean, for all Sun promised when it originally came out, I think its funny that most people can't think of anything more useful to do with it than slow the loading time of Web pages I visit considerably.

    I realize that the chances of a program running on all systems/processors/whatever else isn't the most likely thing in the world to happen, though it would be nice if people diversified just a little bit instead of writing for one specific platform. Reminds me of the argument of producing games for consoles rather than general OSes I was involved with a little while back on the recent PSX 2 delayed again story..

    --

    ~ Kish

  52. Re:hmm I dont mean to start a flame war but.... by Brian+Knotts · · Score: 2
    First, even it might be impossible to track down all of the people who contributed and somehow get them all to agree to a new license. Do you think Linux could do the same? Everyone must agree, and then even after that there's likely some other legal tidbits to work out. Its just crazy.

    I don't think this is correct. Since you can already take the code and stick it into whatever you want, proprietary or otherwise, there is no reason whatsoever that you could not redistribute it under the GPL. You're not changing the copyright; you're just adding licensing terms, which the BSD license allows you to do.

    The biggest obstacle in the past was the advertising clause, but even that is being removed now.

    As for why some people think this would be a good idea, this is my guess:

    People have many theories as to why Linux has achieved the popularity among users and companies that it has. Usually among these theories is the idea that volunteer programmers are more likely to contribute to a project that forbids the proprietarization of their code than to one that does not. This may or may not be true; it's a tough one to prove.

    So, if you buy that theory, the thought goes...by going to the GPL, BSD would lose some hackers (the hard-core BSDL advocates), but pick up more in return. Of course, it's just that a theory, and an untested one at that. I don't really know that things would work out that way. A reasonable counter argument is that there are only so many hackers of the GPL persuasion, and Linux is already using those resources.

    My guess is that with the removal of the advertising clause, someone is going to try to start a GPL BSD project. That will be the true test; we'll just see how many developers they pick up, and whether developers are lost from Linux, the BSDs, or neither.

    --
    Interested in XFMail? New XFMail home page

  53. I had this really funny thought.. by Kitsune+Sushi · · Score: 1

    Anyone seen the title of the GNU Project's Web page lately? What do those first three words say? Let's not confuse the issue.. And as far as "childish whining" goes, I don't see why so many people are so eager to drag Stallman down and kick him a few dozen times or so. Do you honestly believe he hasn't contributed anything to our community?

    --

    ~ Kish

    1. Re:I had this really funny thought.. by C.Lee · · Score: 0

      >I don't see why so many people are so eager to drag Stallman down and >kick him a few dozen times or so.

      Because just like most of the Trekkies, Stallman brings this kind of abuse on himself with his attuide. There's a reason why SF (notice I said SF, not Sci-fi) fans and writers don't like Trekkies. Just ask someone like say Harlan Ellison for instance what he thinks about Trekkies...

  54. *rofl!!* by Kitsune+Sushi · · Score: 1

    Now that's the first time in a while I've gotten a really good laugh.. All I can say is that I didn't mean -that- kind of sexy..! *grin*

    --

    ~ Kish

  55. This is a joke, right? by Kitsune+Sushi · · Score: 1

    Allow me to clarify.. I don't care if you call it GNU/Linux. I care about the fact that people say Linus wrote the Linux OS. GNU stuff, Linux, and all that other neat nifty software we love so dear was written by many people all over the world. Linus is sexy, but he isn't -that- damn sexy.

    --

    ~ Kish

    1. Re:This is a joke, right? by JordanH · · Score: 1
      Linus is sexy,

      Who says that the new Internet Media isn't changing people's perceptions?

      I understand it now. Linus came to the US to take up a career as a Supermodel. It only makes sense, really. He could have worked for Transmeta from Finland, but you have to go to Paris, London, Japan or the US to be a Supermodel!

  56. Amen. by Kitsune+Sushi · · Score: 1

    "Lying to get more market share doesn't sound like a very good thing to me. If it takes that to get market share, fuck market share. I'd rather have integrity. That's something Richard M. Stallman has plenty of."

    I love everything in that post, but this I feel I must remark upon. Lying to to get market share is the tactic of Microsoft we see quite arguably the most often. Half-truths, outright lies, and other misconceptions aren't what we need. If we want to be different or better, we should follow up on those things with more than just bashing Microsoft. However, if we just want to flex our muscle and crush everything in sight in any way possible, why are we even bothering with what we are doing in the first place? There's more than enough of that to go around..

    --

    ~ Kish

  57. Hmm.. by Kitsune+Sushi · · Score: 1

    "When will you *ALL* come to the conclusion that "A rising tide can float all boats", and instead of running about drilling holes in the other boats, agree on what we all can agree on. That OpenSource is good, and getting vendors who wish to run on "OpenSource" OSes should write there code so it can run on *ALL* the OSes. (Hint: Think Linux compatible Binaries. )"

    Actually I think the idea of programs that run on all the different free operating systems like Linux, the BSD trio, etc. is a rather critical issue. Of course, I see a growing number of programs that run only on Linux for Intel.. We should all have a choice. We should be able to choose our OS, our hardware, and whatever software we damn well please without being restricted by the first two things we would like to have a choice on. A growing number of people seem to be losing sight of this, however..

    --

    ~ Kish

    1. Re:Hmm.. by mr · · Score: 1

      *ALL* OSes and *ALL* Processors won't happen. A combination of technology and politics.

      At least not for a long time from now.
      (yes we have Java...no it is not fast enough. And P-code is a long time ago.)

      The closest was the 86Open project, one binary for all X86 op-code Unixes.
      Technology-wise one binary has happened.
      Politically one-binary has *NOT* happened.
      1) Market-share in-fighting
      2) End users are not asking for 'linux compatible binaries'. The Linux COMMUNITY needs to express to vendors that there is value in running on ALL LINUX AND LINUX EMULATORS.

      A 'linux standard binary' format exists....the emulator for Linux. Go to the BSD sites and look at what they have done. Declare the BSD emulator the standard, and avoid the politics of the LSB.

      --
      If it was said on slashdot, it MUST be true!
  58. and the ports by josepha48 · · Score: 1

    Having used both Linux and FreeBSD, they both have there plusses and minuses.

    I have found that most Linux distributions are easier to install. The install is rather straight forward. Linux distributions do things like letting the user do the partitioning, and they do not recommend any partitioning schemes.

    I have also noticed that Linux and its new spotlight has made the 2.2 kernel series less stable than they should be. There seems to be a public driving force that is causing a need for features and comprimising the stability of the kernel.

    FreeBSD does not seem to be suffering from this thou. There install is not that difficult, but it is not as friendly as most Linux distros. There stability has not been comprimised by the need to support new hardware, and all sorts of features.

    FreeBSD is more of a standard *NIX, than Linux is. The good part of FreeBSD is that most Linux software has been ported over to FreeBSD. So it is possible to have most of the same software that you have on a Linux box running on your FreeBSD box, should you choose to go that route. This includes Gnome, KDE, Windomaker, and afterstep, and many of there associated programs, as well as many of the other commonly found programs.

    FreeBSD does also have a dependancy checking mechanism in there installation, so that dependancy problems can be resolved. This is similar to rpm or deb of Linux.

    On another note, I did notice that the article had mentioned that Microsoft was being threatened by the free software. While this may be true, I was recently informed that Hotmail which is owned by M$ runs FreeBSD. I originaly thought that Hotmail ran Solaris and HP, which was why M$ ported its IE to thoses platforms. If Hotmail does run on FreeBSD, then why did M$ not port there IE to that platform instead?

    --

    Only 'flamers' flame!

    1. Re:and the ports by Anonymous Coward · · Score: 0

      >> FreeBSD is more of a standard *NIX, than Linux is.
      > In what sense?

      This is just me, but FreeBSD feels more like a `real UNIX workstation' to me because I learnt UNIX on Suns running SunOS (pre-5.x). The original poster may have similar experience.

    2. Re:and the ports by Anonymous Coward · · Score: 0

      Ever notice how the Linux tty driver has the wrong rules for your werase char? Compare it with BSD.

  59. *cough* by Kitsune+Sushi · · Score: 1

    Yeah.. Sure. Well, whatever. There has been free software for a while, yes, but up until now, who has paid attention to any of it? The public? Certainly not. Who's paying attention now, and why? Because of who? Most of us with any sense know the answers to those questions, whether we agree with them or not. It's really no surprise this was an AC post. I'm not sure I agree with the "necessary evil" thing anymore.

    --

    ~ Kish

    1. Re:*cough* by C.Lee · · Score: 0

      >Yeah.. Sure. Well, whatever. There has been free software for a >while, yes, but up until now, who has paid attention to any of it? >The public? Certainly not.

      Really? Why don't you ask the people who grew up using the Apple II's,Atari-8 bit and the Vic-20/Comodore 64 computers? There was a great deal of free software for these machines, and a lot of it had nothing to do with the FSF. In fact a lot of it was around before the FSF even existed.

  60. Re:Umm.. by JordanH · · Score: 1
    I don't care whether people call it "Linux" or "GNU/Linux" or "Roland the headless Thomson gunner"

    Hey, I like this. I might start calling it "Roland the headless Thomson gunner". The only problem is that it's kinda long...

    We'd need to get rid of Tux, too. Anybody got a good image of a headless Thomson gunner?

  61. Re:So far most of the comments have been negative by JordanH · · Score: 1
    These articles are *good*. Please accept that.

    It seems to me that people here feel they have ownership over these issues and have trouble with other media covering them.

    In a way, I can understand. These things are covered much better here. Perhaps some of the mass media could have Slashdot readers/contributors do collaborative articles. This could help fund Slashdot.

    I don't have a good idea about such a thing could be organized, but it would be neat.

  62. Re:Ugh! by Anonymous Coward · · Score: 0

    Yes, but I think you're coming at it from the wrong direction. Win32 and POSIX are API layers which are implemented above actual operating systems such as UNIX, Mach, Linux, NT, etc. That's why you have portions of POSIX and Win32 implemented in user-mode libraries, rather than as systems calls in the actual operating systems.

    If I've got it wrong, I apologise.

  63. Re:Ugh! by Anonymous Coward · · Score: 0

    Yes, Interix is a nice example of the flexibility of NT's modified microkernel design.

    On the other hand, I actually prefer U/WIN, which runs on top of the Win32 layer (and can therefore run on any OS for which a Win32 implementation is available).

  64. Re:Ugh! by Anonymous Coward · · Score: 0

    Perhaps it shocks you because you don't understand what `init' is. `init' is just an ordinary user binary, from which the system creates the initial user process. There is nothing magical about it, and the OS can quite easily create the initial process from a different binary to `init'. On FreeBSD, for example, the binary used for the initial process is set in loader.conf (and for installs, in fact, the initial process is created from `sysinstall', not `init').

    In short, the operating system is what controls the hardware and provides a virtual machine to the user processes. `init' does neither of these. It is a user binary like any other, not part of the OS.

  65. More unfortunate FUD. by cmc · · Score: 2
    This is getting old...
    Then came linux and now the *bsd users have had it and are beginning to come around. I applaud them for selling and marketing and creating hype about there product which is what they should of done 20 years ago.

    Ask Linus about this. The reason we couldn't "be" is because BSD was the subject of a lawsuit. I believe Linus can be quoted as saying that if such lawsuit did not exist, neither would Linux.


    Linux said that linux is made up of 30 full time and over 1,000 part time programmers who work on the kernel while freebsd has only 15 guys.

    More FUD. See the core team list and the FreeBSD CVS committers list. Both of these groups of people can commit directly to the CVS repository, effecting what people use in FreeBSD directly. No permission from God (Linus) or Co-God (Alan) is necessary under FreeBSD. Additionally, many people use the send-pr facility to submit patches to repair software in FreeBSD. One of the people listed in the core team or committers will then respond, and if it is "OK", the patch supplied is committed (perhaps with modifications) to the source tree.


    Also, FreeBSD consists of both userland (/bin, /sbin, /usr/bin, /usr/sbin) and kernel. Since they're all kept in one place, both are constantly and consistently updated. I find this to be very beneficial to FreeBSD.



  66. Re:hmm I dont mean to start a flame war but.... by Anonymous Coward · · Score: 0

    You wrote: "This is also why my boss at work refuses to look at freebsd and I agree with him." Sorry but this is really stupid and your boss is, at least, irresponsible. He should look all solutions and choose the ones that brings the best results *today*, if tomorrow we'll move to BeOS or back to VMS is another problem, but your company must be there to make another choice, this is an evolving world my friend, not marriage

  67. Re:Sigh..... by Anonymous Coward · · Score: 0

    Speak for yourself. Microsoft are not my enemy, and I use FreeBSD and NT, each for different purposes. Mac OS X sounds rather nice (Office, IE and BSD UNIX on one OS), so I may want to give it a try at some point (after the non-server version is released).

  68. Re: Factual issues by kevin+lyda · · Score: 1

    sorry to rain on the theo was mean, the other *bsd's were mean, it was a netbsd person who added a patch that would cause openbsd to fail to boot. and that was deliberate.

    yes, it's old news, but the netbsd's core team is amazingly cliqueish. the *bsd method of organising around "core" while seeming like a great idea all too often ends up as an old boy network where newbies dare not tread.

    --
    US Citizen living abroad? Register to vote!
  69. Countering the FUD by Anonymous Coward · · Score: 0
    BSD advocates are FUDing Linux users, saying that we're the ones starting the flame wars vis-a-vis BSD vs. Linux.

    Look at the first few posts under this article. They were by BSD advocates, attacking Linux users.

    I suspect some of the people stirring up shit, on both sides, are paid Microsoft Astroturfers.

    1. Re:Countering the FUD by Anonymous Coward · · Score: 0

      You must stop seeing FUD on all that you dislike, someday you'll have a job, wife, children, house and the FUD argument just will not work with them.

    2. Re:Countering the FUD by Anonymous Coward · · Score: 0

      The use of the word "FUD" is just a cheap ploy to silence dissent and discussion, to toss someone's point of view in the garbage can. It is not honorable.

    3. Re:Countering the FUD by Anonymous Coward · · Score: 0

      I knew eventually Microsoft would be blamed for something in this thread.

      Roll out the sod, boys.

      In case you're wondering what a Linux sodroller is, it's someone who takes sod off a truck and rolls it out onto the bare land, pretending it grew from seed.

      What does the sod symbolize? The sod represents the truth, countering the notion people seem to have that the Linux userbase grew up out of the source code. Here's a clue: Almost all the Linux being run in the world (what I refer to as sod, or binary code) grew on a special farm and was trucked in.

      Roll out the sod, boys. Roll out the sod. Don't try to claim it's grassroots. It ain't.

      (moderate this down so I can post it again, and again.)

  70. Idiot moderation (was Re:Pro-BSD moderation...) by Anonymous Coward · · Score: 0

    IMNSHO, neither of those posts should have been marked down. Some moderators around here need to develop thicker skins, I feel. Both posts were (slightly erroneous, perhaps) personal opinions, but neither came even close to being flamebait. Where are the metas when you need them?

  71. Re:Sigh..... by Anonymous Coward · · Score: 0

    Microsoft *are* not your enemy? How many are they?

  72. Re:Factual issues by gr · · Score: 1

    WNight wrote:
    The code is often the smaller part of making a new util. Design, both in identifying the problem, and in deciding on the implementation, are as much of a problem as the actual coding.

    Ah, yes, but you've glossed over an important point there: one big thing that's different between Gnu utilities/the Linux kernel and 4.4 BSD/System V utilities and kernel is the implementation. This is the bulk of the "actual coding".

    When you write a piece of software to mimic another piece of software, your front end may look very much the same, but your back end could well be going about things differently.

    That said, the Gnu tools weren't built as if in a clean room, so they probably mimic implementation pretty closely. I was referring mostly, however, to the Linux kernel, which we all know does some things in a very (and at times purposely) different way.

    (Why can't we have a thread that mentions GNU without someone using the term fanatic? They have stated a goal and are working towards that goal, not getting distracted in the meme of the moment isn't fanaticism.)

    I don't really want to get in a debate over defintions of fanaticism (and it would just be silly, anyway), but suffice to say that I didn't mean that all (or even most... or, really, even more than a handful) of the members of the Gnu project were fanatics. I was referring to one particular individual, whose initials start with R and end with S. Anyway, who said fanaticism was necessarily a negative concept? It definitely gets things done...

    --
    Do you have a /. uid shorter than five digits? No? Then piss off.
  73. Grand unification theory. WAS Re:Ayup.. by mr · · Score: 1

    Here's the thing:

    Today there are 2 OSes. (Ok, There are more, but that is what the field is down to. If you lump them all together, the rest are a small group called OTHER)

    Windows and Unix.

    Both can do POSIX. Both can do OpenGL. Both have MOTIF/X. And the Unix side is working hard on Win32 compatiblity libs.

    So there is no excuse for non-portable code. Unless you are lazy or pick Micro$oft tools to build with.

    And, if SCO, Solaris, and BSD can figure out how to make 'Linux Compatible Binaries' run on thier platforms, there is no reason why Windows can't do the same, other than a lack of interest.


    It is a converging world. Reconginze this and work to help *EVERYONE* in the convergance.

    --
    If it was said on slashdot, it MUST be true!
    1. Re:Grand unification theory. WAS Re:Ayup.. by Anonymous Coward · · Score: 0

      > And, if SCO, Solaris, and BSD can figure out
      > how to make 'Linux Compatible Binaries' run on
      > thier platforms, there is no reason why Windows
      > can't do the same, other than a lack of
      > interest.

      SCO, Solaris and BSD are ultimately derived from Bell Labs UNIX, and Linux is a clone of it/them. As such, they all operate in a very similar way.

      The NT OS is far less similar, meaning Linux can't be `emulated' by simply remapping system-call numbers (which is essentially what the BSD/UNIX systems do). Creating a Linux subsystem on NT would be rather more like creating a Linux server on Mach (I believe MkLinux is a single server for Mach, which would make it a similar sort of emulator).

  74. Re:Er.. I don't like all of that stuff you mention by conio · · Score: 1

    >> So I wish the *BSD people here could push with more force...

    Well, we try, but we may as well hit our heads against a brick wall -- the Linux users always scream FUD.

    Tell your friends to loosen up.

    -Sam

    --
    Sam
  75. Re:Sigh..... by Anonymous Coward · · Score: 0

    > Microsoft *are* not your enemy? How many are they?

    Sorry? Microsoft are a company comprising thousands of employees; I don't know exactly how many. Does that make any difference?

  76. Absolutely by Anonymous Coward · · Score: 0

    It seems the majority of Slashdot users aren't mature enough to resist flamebait when they see it.

  77. Re:I never said BSD was going to die by Anonymous Coward · · Score: 0

    At some point in the future, Linux will be technicaly (sic.) suprior (sic.) to FreeBSD. The reason for this is beacuse (sic.) Linux is getting more support from the industry, has more code contributers (sic.) , etc, etc.

    I would choose to say, instead, that Linux will arrive in Babylon land sooner. Far, far sooner. (hint- read a biblical account of the tower of Babel)

    If you don't know what I mean, try to hold an intellectual conversation in a crowded bar sometime. A lot like reading a Linux newsgroup, isn't it?

  78. Re:software *use* and software *creation* by Anonymous Coward · · Score: 0
    Hello Mr FUD.

    You don't know what you're talking about. :-( Apple has contributed back a lot of kernel and userland code to the BSD projects.

    -T

  79. Re:Gosh! Where did you learn to write? by Anonymous Coward · · Score: 0

    Sorry, but I am always pissed of by a linux zealot who doesn't know how to spell. Yup, -1 here, thanks : )

  80. GCC? by Anonymous Coward · · Score: 0
    No, there are several more c-compilers than GCC, so the projects would have existed without gcc.

    Examples are TenDRA, Small-C, Bruce's Compiler, lcc.

    -T

  81. Re:Natural Selection.. by Mithy · · Score: 1

    If we're to believe the recent stories about IRIX, there's your 5% right there for the taking... (Albeit slightly out of date.)

    --
    This isn't the post you're looking for. Move along.

    --

    --
    "This isn't the post you're looking for. Move along."
  82. Re:BSD people need to be loyal( like mac cronies) by Progman · · Score: 1

    If you use neither BSD nor Linux, then you don't know what you're talking about. You're just spreading the FUD you've read elsewhere.

  83. in the sense by josepha48 · · Score: 1

    Most standard *NIX es do not include color ls as part of the install. So far all Linux distrinutions that I have tried, Slackware, Redhat, SuSE, TurboLinux include this, and install it by default. This makes dirictory navigating (IMHO) easier. Well you can install color ls in FreeBSD and probably other *NIXes it is not installed by default. There are many other things that make Linux, a friendlier to use system than most other *UNX systems, this is what seperates Linux from other *NIX systems. I am not saying Linus is the best OS I am not a Linux purist. Linux does not feel like *NIX to me. FreBSD feels more like a traditional *NIX. I believe that part of the reason for my feeling this way is that I have used SUN. Although Sun today is much different than FreeBSD, I believe that the Sun OS had its roots in BSD. (correct me if I am wrong). FreeBSD had its root from BSD so SUN and FreeBSD have similar ancesstory. Linux on the other hand only inherited some of the directory structure and that even depends on the distribution you try. THis is just my opinion.

    --

    Only 'flamers' flame!

    1. Re:in the sense by Anonymous Coward · · Score: 0

      What can't you write Unix? What is this damned "*NIX" crap?

    2. Re:in the sense by Guy+Harris · · Score: 1
      Linux does not feel like *NIX to me.

      It does to me; when I log into a Linux box, it feels about the same to me as any other box running a UNIX-flavored OS (not all of which feel exactly the same as one another, so it's not as if there's a "UNIX" that everything but Linux looks exactly like).

      Yeah, maybe the GNU "ls" that Linux distributions use does color (I don't normally have an "xterm" that does color, so it doesn't make any difference to me), but some systems have an "ls" that shows the user and group names with "ls -l", others have one that shows only the user name, etc..

      On many Linux distributions, the twisty little maze of "rc" files, all different, looks more like that of, say, SunOS 5.x/Solaris 2.x/Solaris 7 than like that of BSD systems.

      So, from where I stand, Linux distributions aren't any more noticeably different from other UNIX-flavored OSes, either as a user or as somebody writing code to run atop them, than are any other UNIX-flavored OS (i.e., UNIX-flavored OSes aren't all exactly like each other, and Linux distributions don't seem any more divergent from any "norm" than do any other UNIX-flavored OSes).

      The OS source itself, e.g. the kernel and the C library, might be more different from any such "norm" than is the source to other UNIX-flavored OSes - but, given the number of vendors, etc. who've been hacking on the code they got from AT&T, Berkeley, etc., it might not be that much more different. The kernel source, say, is less familiar to me in organization than is, say, the FreeBSD source - but, not having seen the SunOS 5.x kernel source in several years, I don't know how alien it would seem to me.

  84. its the way by Anonymous Coward · · Score: 0

    sure we all linux freaks love linux. But lets face it, if was to really set up server -meaning as to stay there 24/7 for bandwith usage, i go with a bsd depending on the type either NET, or Free... but surely BSD the way i see it Linux is out there -talking about RedHat kind of line for desktop support mainly. i want a server i go BSD. i want features, i want GIMP right i want games, i goto linux.

    1. Re:its the way by Lazaru5 · · Score: 1

      Since when is GIMP only for Linux?

      --

      --
      My comments and opinions completely reflect those of anyone and anything I am remotely associated with.
    2. Re:its the way by bugg · · Score: 1

      I get all of that with FreeBSD.
      Games run fine with compat. /usr/ports/graphics/gimp, iirc
      Features? How is that different?

      --
      -bugg
  85. Re:Ugh! by Anonymous Coward · · Score: 0

    Furthermore, I have a rather nice POSIX API that runs on my Windows NT 4 box. Interix is fairly tight POSIX API that runs on top of the NT Kernel. It includes GCC, a TCSHell, and most of the common Unix tools. I can build and run X clients on my NT box now, and display them anywhere. Interix is also Posix compliant, not just a mostly-compliant clone like Linux. (GNU people rarely comply with standards, they embrace and extend standards, like Microsoft)

  86. your opinion by josepha48 · · Score: 1
    I am stating my opinion on Linux. I like it but am not a purist. If you do not noone is forcing you to like it. I am not bickering I use both FreeBSD and LInux on my systems. As I said they both have there plusses and minuses.

    You seem to contridict your self in your first and third paragraph. Linux is thrown together .. then you say it is easier to install... As for the stability issue. you aren't running 2.2.12 are you. I am and I have to reboot it cause of a memory leak in the Tcp/Ip stack.

    --

    Only 'flamers' flame!

  87. So far most of the comments have been negative by jfunk · · Score: 3

    Why is that?

    I read the article, and liked it.

    These journalists have come a long way since the "UNIX has no GUI" days. The article was entirely positive, written to give credit where it was due (I'm a Linux guy, btw).

    The article wasn't posted to start a flame war, but that's going to happen anyway. It's already started.

    It's like Ford vs. GM vs. whoever. Strong points, weak points, there are always reasons behind one's choice, and they're always valid.

    The noise has only been getting worse, and it's extremely redundant.

    These articles are *good*. Please accept that.

    1. Re:So far most of the comments have been negative by randolfe · · Score: 2
      I'd just like to echo the comments above. Having attempted to bring sanity to a some of the perplexing "Linux vs. Java" flame wars, I see the same thing occurring with any article about BSD. I like your reference to Ford vs. GM. Where I grew up in Ohio you could get your ass kicked for something as silly as a stray comment about an American auto brand. They didn't even see the Japanese coming on.

      Perhaps that analogy is relevant here. Linux proponents need to realize that there are many trends, currents, variables, forces at work in the market; more now than in the past 10 years. We all have a very small vote in forming the future. I, for one, cast my small vote for the power of diversity and choice. Read: BSD has a valid role to play and articles which help promote that message to the rest of the world are positive.

      It's so much easier to deconstruct than to construct.

    2. Re:So far most of the comments have been negative by holloway · · Score: 1

      It's like Ford vs. GM vs. whoever, hmmm, GM.... vs Michael Moore?

  88. Re:Ugh! by Anonymous Coward · · Score: 0

    Please feel free to delete the userspace program called init and demo your "operating system" to me.

    Wow, I am really impressed!

  89. Re:Got a source for that? by Anonymous Coward · · Score: 0

    Hay now!

    Stop that.

    The truth hurts! (ouch)

  90. Re:Hey, lets do some math by Anonymous Coward · · Score: 0

    One problem: who the heck is this "we" you mention?

  91. Re:Sigh..... by Anonymous Coward · · Score: 0

    In English, "Microsoft" is a singular noun. One says "Microsoft is" just as one says "China is". One does not say "Microsoft are" or "China are". Perhaps the rules are different in Swahili.

  92. Sigh..... by NiggaPet · · Score: 1

    Come on people, every os has its pluses and minuses, They are both free stable operating systems, and both are running the internet as we speak, we shouldnt be bitching amung ourselves, we all have a common enemy, Micro$oft, why not bitch about whether BeOS is better than *NIX for christ sakes.

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

      Firstly, that isn't necessarily true. The treatement of collective nouns in English is entirely a matter of context.

      In formal usage, if you're referring to, for example, a committee, you use the singular if the reference concerns the committee as an entity (e.g. `the committee published its report'). However, if the reference is to the committee as separate individuals (e.g. `the committee took their seats'), the plural is used.

      Secondly, your analogy is nonsensical, in that China is the name of a physical region of the Earth (clearly singular), where as Microsoft refers either to an entity which only exists in law (singular), or to the people who act in the name of that entity (collective).

      The singular is preferred except in cases such as the example above, which may or may not cover the original reference to Microsoft (referring to the individuals who make up the company, though in a rather vague manner). Either way, the broader use of the plural for collective nouns is very widespread in informal use (which certainly applies to a Slashdot post).

  93. Re:Loving my FreeBSD-3.3 RC #3 Box by Anonymous Coward · · Score: 0

    vi /etc/inetd.conf

    Whoops! Which Python script just undid everything I changed!?!

    apt-get install "insert-name-here" is even easier and faster.

    Cool! Where do I find that documented on the Red Hat website?



  94. Censorship ? Was: Re:Please NO MORE *BSD items on by Anonymous Coward · · Score: 0

    hmmm

  95. Small Nitpick by Anonymous Coward · · Score: 1
    The Linux license, by contrast, requires users to make any use of the software -- such as a piece of specialized computer networking gear -- freely available to everyone else. That restriction keeps many companies from using Linux in key products.

    Inaccurate. The GPL does not regulate any kind of "use"; it only regulates distribution. And it seems like they're saying that the use of Linux in a particular piece of hardware would make the hardware itself subject to the GPL. This is too silly to comment on, other than to simply say, "no, it wouldn't." They'd just have to make the source code (along with any modifications thereof) available to customers.

    RESUME FLAMEFEST

  96. Free BSDs and AT&T's source by SimonK · · Score: 1

    While the original BSD was based on the AT&T sources, I believe the AT&T code was "cleaned" out when it was made un-free.

    The free BSDs derrived from this "clean" source tree, so while the AT&T code may have had some impact on the structure and so on, it isn't there now.

  97. Hey, lets do some math by Anonymous Coward · · Score: 0

    15% FreeBSD + 31% Linux = 46% of the web, we need the other 5% to dominate the net, not a flamewar

  98. Re:As I make world by PigleT · · Score: 1

    Well, it's the small part of the user base that constantly has to say "my OS is better than yours."

    Agree entirely. Shoot all fundamentalists, I say, then re-use the bullets :8]

    rpm -ivh ftp://site.org/path/to.rpm works fine.

    Does it do dependencies? That, coupled with (AFAIK!) no equivalent of /etc/apt/sources.list, is RPM's main failing, not the supposed "lack" of remote URLs.
    Contrast 'apt-get install licq' which goes and gets the latest qt libs required *as well*. Never seen no rpm do dat...

    --
    ~Tim
    --
    .|` Clouds cross the black moonlight,
    Rushing on down to the circle of the turn
  99. BSD people need to be loyal( like mac cronies) by Whizziwig · · Score: 1

    Think about it, windows is the most prolific operating system on teh planet, no windows enthusiast sees it goign anywhere soon.

    Linux is now in the mass media is gaining acceptance, and has a wider and wider userbase.

    Mac people must be loyal, thier OS is an endangered species, why else would people put apple tatoos on thier bodies? Appple was *THE* premier computer in school,s then MS took over. They were *GUI*, then MS took over, they were teh renegade OS, then linux took over.

    BSD is similar, they were the free unix, teh open source people, teh unix at home people. They were an elite club. Now linux is taking over, and they need to be defensive. BSD people are even more loyal then MacOS'ers, especially when in the company of linux geeks.

    BSD is having much less of a problem keeping both old and new hardware supported (ie 386 - 8 way SMP Athalon). BSD has a great linux emulator, wwith full compatibility with any linux libs you can throw at it. NetBSD has a much wider range of hardware support. The port system is supposed to be a much better development model.

    According to most BSD-ers, linux geeks are nuts, their fs sucks (ext2 vs. fsf) their competing package systems, their library incompatibilities, their little distro wars, the development model sucks. I don't know, I like debian, I like linux, I like glibc2, I liek our distro wars and library incompats, it makes life fun!

    door bell.

    ---dave
    What's brown and sounds like a bell? DUNG!

    1. Re:BSD people need to be loyal( like mac cronies) by Trepidity · · Score: 2

      You seem to have hit on the head what the BSD fans have been saying for a long time. BSD is for serious work, while Linux is for home users who are adventurous and, like yourself, have fun with library incompatibilities, distro wars, crap filesystems, etc.

      And before somebody accuses me of being a BSD zealot, I use neither BSD nor Linux.

    2. Re:BSD people need to be loyal( like mac cronies) by sterwill · · Score: 1

      So you're just making this up as you go?

      --

  100. GPL is legally untested by Anonymous Coward · · Score: 0

    You assume the person contesting the GPL would lose. Don't be stupid: every court case is a gamble. Ask any lawyer. There are no guarantees. The GPL is weak in two areas. First, there is no way that use of a library API contaminates the program using it. Libraries are meant to be used. Secondly, in similar IP cases, the courts always look at the proportion of "infringement". One 12-line GPL function incorporated as a whole into a much larger work would not give the FSF rights over the whole work. They would be awarded something in proportion to the whole. 12 out of 12,000 line, for example, would almost certainly be judged virtually irrelevant. One tenth of one percent? Don't be silly. The courts aren't that dumb, and there is no case history supporting most of what the FSF alleges. In fact, it's nearly all to the contrary. It serves the FSF's purpose of spreading FUD by making threats and ad-hoc interpretations of intention not written into the licence at all. The world is not the black and white place that fanatics like Stallman make it out to be. The courts would be much more realistic. The reason the GPL hasn't been challenged is hardly because the challenger would lose. You can't know that, and depending on the circumstances, there's a lot of case law that says that Stallman would not be as successful as he pretends he would be.

    1. Re:GPL is legally untested by Anonymous Coward · · Score: 0

      Of course, there is an easy way around that little GPL legality of source distribution...

      The GPL says that I must provide access to the source, but do NOT necessarily have to ship the source with my product. I must only make it available.

      So, I create a large tar file (oh.. sorry, I *forgot* to tgz it, so it'll take a *LONG* time to download), that naturally includes both source and object files, and binary's on top of it. Presume, for the sake of my argument, its a large project so you wind up with say 100Mb of tar file. Then, I put my web server up on the WWW on a dialup 9600 baud modem link (I have a few old 9600's floating around myself, actually), and setup a cron job to reboot the machine every 12 hours, and to do a kill on the ftp daemon every 2 hours...

      The source is "available" (ahem) on the net, but not really. I won't have a phone# available, and if you email me I will be glad to provide you the source on a DEC TK50 tape (although I think my drive may be slightly out of alignment...), or on 400 5-1/4" 360K floppies, at $2/disk to cover my media and labor costs to copy them. Don't like the cost? Well, you can always, ahem, download it for free...

      I personally agree that the GPL may not hold up very well in court. If I took the linux kernel, changed the source around so the messages were different, etc, and then sold it in binary format... could *you* prove it was GPL'd linux code from the binary? I'm sure there's a lot of GPL'd code out there in proprietary products... we've got a Xerox Printer/Copier that the tech said is "just a linux box" inside... the doc's didn't say anything about the source being available... I suppose it could be BSD and the tech doesn't know the difference... or is it?
      Even if it was linux, would the FSF jump on the bandwagon to sue Xerox? Who can afford the better lawyers, FSF who gives their code away for "free", or Xerox who makes millions every year?

      And who wins in the long run? The lawyers. I knew a guy here at work who joined the "14-inch monitor is only 12.9-inches" suit a few years back. After the settlement, the lawyers walked away with millions, and he was told that he could buy a new monitor and they'd give him $15 towards it, or if he waited 2 years they'd mail him a check for $12. Oh boy!!!

  101. Pro-BSD moderation once again by Anonymous Coward · · Score: 0

    The BSD zealot moderators are in action again. Note how the above comment was moderated down as flamebait, when, in fact, it was the parent comment that should have been so moderated.

  102. But do they get along now? by hawk · · Score: 2

    I haven't tried to use an ext2 partition under FreeBSD for over a year (two years?). When I did it wouldfrom time to time include random garbage as part of disk writes. This is a bad thing :)

    Linux is no friendlier to ufs. Compile your system with ufs support, and suddenly the ufs partition 3 slices appear before your ext2 partitions in partition 4, and you attempt to mount the ufs slices as ext2 partitions. KA-BLAM! Trashed partition tables when you go back to BSD. Even if you remember to move them, you'll probably forget about this some time when you pull out an old rescue disk, and BOOM.

    Also, I found that FreeBSD would complain aobut the labels in the linux extended partitions, which caused a panic on boot about 20% of the time. I finally removed the linux extended partition.

    Mmm, and just using UFS for shared partitions doesn't work, either. They don't get fsck'd properly under linux, and I couldn't find a way to manually fsck them.

    The only filesystem that they both seem to get along with is dos. I finally resorted to tarballs on a dos partition to exchange files :(

  103. GNU/Linux is "fighting words" -- ban the name by Anonymous Coward · · Score: 0

    The WSJ is to be commended for avoiding feeding the flames with this inanely unmerited and pretentious "GNU/Linux" moniker. Put simple, irrespective of what side of the matter you should happen to find yourself, it's "fighting words", plain and simple. Even if you are on the side that feels the appelation to be nothing more than awarding advertising/marketing credit where this is due, you're still generating more heat than light. Whining and name-calling is only going to make fewer people pay attention to you -- at least in a favorable light. Not all worship RMS, so cut the crap.

    1. Re:GNU/Linux is "fighting words" -- ban the name by Trepidity · · Score: 2

      Using an accurate name is not "bad" because it upsets other people. It's not name-calling, it's simply an accurate name. I'd be more worried about the Linux kiddies and their "Microsucks winbloze" bullshit - that's immature name-calling.

      If you'd prefer, I can refer to it as the GNU OS, since that's what it mostly is (and will be 100% whenever Hurd finally finishes and the Linux kernel can be replaced). Then, if people inquire, I can point out the detail that I use the Linux kernel along with my GNU OS.

      Anyway, I presume you dislike Debian GNU/Linux for this reason. Red Hat user?

  104. Re: Factual issues by cjs · · Score: 1

    There was a lot of that going around on both sides. For a long time, OpenBSD was fixing security flaws, but putting just `RCS ID Police' in the commit message, to make it hard for NetBSD developers following the commits to see what bugs they'd fixed.

    As for the change in NetBSD that, when imported into OpenBSD sources, made OpenBSD fail to compile on Alphas, it was sort of dumb thing to do, yes, but it was quite obvious and simple to fix. What got the OpenBSD users so angry about it was it sat in their code for almost two months without them noticing it, proving that they didn't do any maintenance on the Alpha port.

    cjs

    --
    The world's most portable OS: http://www.netbsd.org.
  105. Re:Factual issues by Xander+Harris · · Score: 1
    I was referring to one particular individual, whose initials start with R and end with S.

    Richard Simmons?

    --

    Xander
  106. Is this a history class? by Kitsune+Sushi · · Score: 1

    If so, I'm aware of the relavent facts and have no need of an instructor. I, for one, am speaking of current events (or reasonable fascimiles thereof), not history. Free software has been around for a very long time. The entire reason why we have the FSF is because we used to have more of it, and for a while we didn't really have much of any.

    --

    ~ Kish

  107. Keep in mind the audience by warlocke · · Score: 1

    WSJ isn't aimed at geeks -- although I think they'd be surprised how many pay attention, especially after the RedHat IPO!

    For the audience this is aimed at, it's a nice short 'executive summary.' Leaves out a lot of things some of us consider important, but that's the nature of the beast.

    Don't expect a mass newspaper aimed at financial types, managers, etc. to cover (or be interested in) all the fiddlin' details. Instead, rejoice that they're paying any attention at all -- and be joyful and thankful that the errors are of omission. What's there is right, which is better than 90% of today's journalists can say.

    Regards,
    Ric

  108. Umm.. by Kitsune+Sushi · · Score: 1

    "Look this is a silly stupid ego issue for Stallman."

    This really has nothing to do with the point.

    "Does this mean it will benifit linux or the public at large by forcing GNU/Linux down their throughts? No!"

    I thought "people deserve to know the truth". Is this a dead concept?

    "The myth of Linus and his singlehanded development of the operating system plays an important role in the media recognition of linux. People's imaginations are not fired up by commitees, they are fired up by individuals and strong leaders. There is a reason we consider the president of the US to represent the United States when in reality congress hasmore to do with the present state of the US than the president."

    Commitees? Whatever. I don't think we have many things that are quite that formal in our community. Personally, I get fired up over the idea of people from all over the world working together to produce good, quality software without the concept of money driving them. And if you realize that it's silly to focus on the president of the U.S. when the legislature holds more of the real power, why would you try to spread an obviously flawed belief and even focus on it? Ignoring things of this nature only allows the problems we refuse to recognize to remain unattended.. and thus grow worse and spread into other areas.

    --

    ~ Kish

    1. Re:Umm.. by PG13 · · Score: 1

      I am not implying that a flawed belif should be spread merely that people should be allowed to keep their icons. Everyone knows that congress has just as much if not more power than the president yet very few feel an emotional or patriotic attachment to congress.

      This has nothing to do with actual knowledge, hell it would be a good idea to put a little footnote in every article explaining that GNU contributed most of the code etc.., it is about image. Example from science: does anyone think that Einstein spun modern physics out of whole cloth? No, everyone knows he built on work done by others, but *Einsteins* theory of relativity generated far more interest and respect for physics than "A thgeory partially developed by einstein moslty building on the work of others" would ever have.

      And rah for you, you get fired up by the concept of open source. We wish there were many more people out their who shared your belifs, unfortunatly, many people do not, or at least do not yet. Linux grabs their attention in a way FreeBSD never has. If not for this myth of Linus Linux would never have made it into the lime light and free software would have suffered a large setback.

      --
      Marriage is the "pseudo-ethics" that cloaks the messy truth of sexuality in the raiment of propriety -- it's "Don't Ask,
    2. Re:Umm.. by Guy+Harris · · Score: 1
      I am not implying that a flawed belif should be spread merely that people should be allowed to keep their icons.

      ...but that doesn't ipso facto mean others are obliged not to say anything that would make it more difficult for those people to hold onto their beliefs. (You may believe it does, but I and I suspect many others don't, and aren't willing just to accept your belief that it does.)

      If not for this myth of Linus Linux would never have made it into the lime light

      Do you have any solid evidence to support this belief? Did the "myth of Linux" spring up prior to corporate/media/etc. interest in Linux, and help lead to that interest, or did it spring up as, or after, that interest started growing, with the myth being a hook on which journalists could hang their stories about Linux?

      (I don't care whether people call it "Linux" or "GNU/Linux" or "Roland the headless Thomson gunner" - and there's a lot of stuff in a Linux distribution that doesn't come from the GNU project, so, if somebody insists that it be called "GNU/Linux" to give credit where credit is due, they should note that even "GNU/Linux" doesn't fully give credit where credit is due - but I've yet to see any solid evidence that the mere use of "GNU/Linux" somehow shatters a fragile myth upon which much of the popularity of Linux is based.)

    3. Re:Umm.. by Uart · · Score: 1

      Nobody is covering up the GNU participation, we just aren't changing the name of a successfull product. People know it as Linux. Half of the software in any given distribution is called GNU-somethingorother, isn't that enough recognition, that the GNU name is associated with the software written by the GNU??? I think it is. I know that Emacs is GNU, but emacs isn't linux, it isn't the kernel, it isn't the drivers, its a freat piece of software, and RMS deserves all the credit in the world for it, and the GNU derserves every bit of credit for, but Linus, and the community at large wrote Linux, its GPL, but ut isn't GNU.

      --

      Opinionated Law Student Strikes Again!
  109. Re:Loving my FreeBSD-3.3 RC #3 Box by Lazaru5 · · Score: 1

    You do *NOT* have to rebuild all your ports after remaking the world. (Where other people would yell "FUD", I'll just say "misinformed". "FUD" is overused.)

    Fact: There is *NOTHING* like the FreeBSD ports system. There are better /package/ systems than FreeBSD's, but the ports are unique.


    --

    --
    My comments and opinions completely reflect those of anyone and anything I am remotely associated with.
  110. Ugh! by Kitsune+Sushi · · Score: 1

    "The WSJ is to be commended for avoiding feeding the flames with this inanely unmerited and pretentious "GNU/Linux" moniker."

    GNU is the OS, Linux is the kernel. How does that make it unmerited? And knowing that, how can anyone possibly think that GNU/Linux is more pretentious than Linux?

    I don't worship Richard Stallman, either. It's no wonder this was an AC post. However, if not for his philosophy, Linus Torvalds wouldn't have a leg to stand on. Richard Stallman isn't important. What he did, what Linus did.. all of the people who have worked on GNU projects and GPL-covered software (including them) and what they did.. all of these things and people are. I thought I made that clear to begin with.

    --

    ~ Kish

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

      I believe that precise definition (OS equals kernel-mode code) is used in _Operating Systems: Design and Implementation_, by Andrew S. Tanenbaum.

      Of course, it's only one definition, but it is from a very good source.

    2. Re:Ugh! by Guy+Harris · · Score: 1
      I believe that precise definition (OS equals kernel-mode code) is used in _Operating Systems: Design and Implementation_, by Andrew S. Tanenbaum.

      ...although, in Modern Operating Systems, he uses a similar definition and then later discusses Amoeba, which does a lot of what he considers "operating system" stuff in servers, although I didn't see anything in a quick look that indicated whether all those servers ran in kernel mode or not. One might consider a server process with special privileges, with which unprivileged code communicates via messages as "privileged code" even if it doesn't run in kernel mode, though.

      On the other hand, the MIT Exokernel is a small kernel that "concentrates solely on securely multiplexing the raw hardware", with "library operating systems" running in userland (but in the context of the process requesting services from the OS) implementing "traditional operating system abstractions" such as file systems and networking stacks.

      I.e., the APIs of modern systems tend to be implemented with several layers of abstraction; the layer of abstraction that's implemented by code with special privileges often implements only a part of the API, and may not implement any of it directly. Even in a "traditional" UNIX-flavored system such as a Linux distribution, in which a lot of the API is implemented by kernel code (plus a system call stub wrapper), enough of the API isn't that credit is due the implementors of the rest of the API as well.

      (Alas, I don't have my copy of Inside the AS/400 at work, so I can't check how much of OS/400 runs in kernel mode, but the system software on the AS/400 is another interesting piece of software, with an architecture fairly different from the "conventional" architecture one gets exposed to with UNIX-flavored systems, Windows OT, Windows NT, VMS, etc..)

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

      Perhaps it's a matter of distinguishing the operating system from the system as a whole (the latter including daemons, shells, compilers and so on).

      I think A.S. Tanenbaum considers a lot of user-mode code part of the system, but not part of the operating system. It is, IMHO, a useful distinction.

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

      Linux is an operating system. GNU is a set of tools which can be run on a number of operating systems, including BSD/UNIX (the OS GNU was originally developed on), Linux, HURD, even Microsoft Windows.

      In short, the operating system is the software that runs in system space (aka kernel space). Anything that runs in user space is, by definition, not a part of the OS. GNU is not part of the Linux OS. Full stop.

    5. Re:Ugh! by hpa · · Score: 1

      GNU is *not* the OS, except in Stallman's fantasies. If anything, "RedHat" or "Debian" or "SuSE" is the OS. Just as Stallman's team has quite happily integrated other people's works into "the GNU system" (TeX, X11, BSD, you name it), so has the various Linux teams integrated other Open Source software into our respective systems. We just have chosen to use the "Linux" name as a common term for operating systems built around the Linux kernel.

    6. Re:Ugh! by Trepidity · · Score: 2

      So then why do Linux advocates compare the "Linux OS" to the "Windows NT OS"? Either you compare the "GNU/Linux OS" to the "Windows NT OS", or you compare the "Linux OS" to the "Win32 OS."

      If the kernel is the OS, then I'd appreciate it if you start referring to the "Win32 OS" from now on.

    7. Re:Ugh! by Trepidity · · Score: 2

      Well, you say that "Debian" is an OS. However, there is no distribution called "Debian." It is called "Debian GNU/Linux." Therefore, it'd be the "Debian GNU/LInux OS." You seem to have just disproven your point.

  111. Re:Loving my FreeBSD-3.3 RC #3 Box by Lazaru5 · · Score: 1
    --

    --
    My comments and opinions completely reflect those of anyone and anything I am remotely associated with.
  112. Was linux "dying" before SGI/IBM showed interest?? by Anonymous Coward · · Score: 0
    Your argument is very odd - firstly, I don't know why SGI's support would have any real meaning to the growth or erosion of support for any OS.

    Secondly, IBM still pushes AIX as a first order of business wherever it can - its support for linux has so far been fairly shallow - in case you haven't noticed from their tacit support of Java, IBM is more than willing to throw a hundred employees behind any hyped technology to get some good press.

    *BSD unix is not dying. Its growing. More people than ever are using *BSD to get work done. They don't care if Apple is behind it, or that SGI and IBM aren't. Why would this matter?

    If we judged technologies because of their popularity, we'd all be using Win95.

    I'm sorry to sound like a flamer, but I don't understand the value of the oft-used argument here - because BSD isn't currently a bandwagon for every company looking for an anti-MS strategy, it must be dying. How odd.

  113. Loving my FreeBSD-3.3 RC #3 Box by Anonymous Coward · · Score: 4
    There is no doubt that I am fervently in favor of the growing popularity of linux, but I have to say I am an unabashed fan of my ever-so-lovingly tweaked FreeBSD box. Whats to love?

    1. Easy to harden. I have two ports open - X (6000, 6010) and SSH (22). It was very easy to get my box to this stage. Much easier than it was with RH 6.0, which I have also hardened.

    2. Easy to upgrade. I have yet to see any tool surpass /usr/ports for pure ease of use. I cvsup my ports every night, and in the morning I check the logs to see what package have been tweaked and configured and are ready to be loaded up. Then once or twice I week I cvsup the source code for the OS and do a make world. Upgrading FreeBSD is very very easy - cvsup is gorgeous and I've found nothing like it.

    3. Easy to play nice with linux. I can run linux binaries without recompiling. What else is there to say?

    4. One distribution, great docs, great organization. FreeBSD.org maintains everything I need to deal with regarding the OS in a clear and concise manner. The FreeBSD handbook is available online. I get CD subscriptions multiple times a year, at a good price. I find the linux world of distros rather confusing. FreeBSD makes it easier for me to know the "source of truth".

    Bravo to linux folks for making inroads into corporate America, and thanks to FreeBSD for a island of sanity in the OS archipeligo.

    1. Re:Loving my FreeBSD-3.3 RC #3 Box by guacamole · · Score: 2

      1. Easy to harden. I have two ports open - X (6000, 6010) and SSH (22). It was very easy to get my box to this stage. Much easier than it was with RH 6.0, which I have also hardened.

      vi /etc/inetd.conf

      2. Easy to upgrade. I have yet to see any tool surpass /usr/ports for pure ease of use.

      apt-get install "insert-name-here" is even easier and faster.

      I cvsup my ports every night, and in the morning I check the logs to see what package have been tweaked and configured and are ready to be loaded up. Then once or twice I week I cvsup the source code for the OS and do a make world. Upgrading FreeBSD is very very easy - cvsup is gorgeous and I've found nothing like it.

      FreeBSDs package management is great but it is NO match to Debian GNU/Linux. Debian is even easier to upgrade.
      1) You don't have to fix /etc by hand
      2) You don't have to wait for hours for your stuff to compile (apt-get downloads binary packages unless told otherwise)
      3) You have to remake all your ports one by one after upgrading system. On Debian all packages are a part of distribution. If you upgrade system everything is upgraded.

      apt-get update; apt-get upgrade; will sync your system with the ftp mirror, download and install all updated packages.

      On FreeBSD you need to 1)cvsup everything, 2)make buildworld, 3) make installworld, 4)see if /etc, changes, 5) remake new ports one by one ..

      Sounds like it is more difficult to stay up to date on FreeBSD ..

      4. One distribution, great docs, great organization. FreeBSD.org maintains everything I need to deal with regarding the OS in a clear and concise manner. The FreeBSD handbook is available online. I get CD subscriptions multiple times a year, at a good price. I find the linux world of distros rather confusing. FreeBSD makes it easier for me to know the "source of truth".

      FreeBSD handbook is great, but then most of the major linux distributions(Debian and RedHat) have such handbooks too (usually online too) + a huge collection of online docs at LDP

      Don't get me wrong, FreeBSD is a great system, I would choose it over RedHat in most cases. However, I also choose Debian GNU/Linux over FreeBSD because this distribution is so well engineered and it is easier to maintain than any other *nix operating system.

    2. Re:Loving my FreeBSD-3.3 RC #3 Box by Anonymous Coward · · Score: 0

      Anyway I'd love to see a full system CVS tree for Debian plus a cvsupd server.

    3. Re:Loving my FreeBSD-3.3 RC #3 Box by Anonymous Coward · · Score: 0
      Sounds like Debian is really well put together. I should probably take a look at it and install it over my RH 6.0, which I must say is simply a mess.

      Thanks for the info.

    4. Re:Loving my FreeBSD-3.3 RC #3 Box by drachen · · Score: 1

      I've used both Linux (RedHat, Slackware, Debian) and FreeBSD. I started with Linux and eventually found my way on to FreeBSD (version 2.1.5 at the time). Everything about it was great. Stability, upgradability, documentation, hardware support, strong community development, code auditing, etc. FreeBSD pretty much could do everything that Linux could do, but usually better. Linux may be receiving all the glory these days, but the *BSD's are still alive and strong. I've seen just as rapid development of FreeBSD as I have seen with Linux. The ability to upgrade everything in one centralized way to keep everything relating to the operating system up to date is awesome. FreeBSD also supports a wide range of hardware like Linux (tho maybe not as much you will generally get most anything to work).

      It's good to see the word continuing to spread about BSD and I hope this incites some of them "die hard" Linux users to give BSD a try. If you don't like it at first... you probably haven't used it long enough. I definitly love it.

      --
      James Crawford

    5. Re:Loving my FreeBSD-3.3 RC #3 Box by guacamole · · Score: 1

      First, Let me ask you why do you think compiling is better than getting a binary package. Unless you want to change the compile time options or hack the source I don't see why you should wait for sometimes quite long compiles when you could get a binary package?

      Second, debian's apt-get has a source option, which will download unpack and patch the source package. The you can just run debian/rules binary from the source directory which will build the deb package. But then, I rarely use that, since I rarely have to change compile time options or hack the source.

    6. Re:Loving my FreeBSD-3.3 RC #3 Box by Anonymous Coward · · Score: 0

      Two points:

      1. Debian package management is piss-poor in comparison to RH or FreeBSD when it comes to source. You simply can't do something equivalent to

      rpm --rebuild ftp://foo.bar.com/baz.src.rpm

      or

      cd /usr/ports/baz ; make install

      (system now downloads and compiles baz)

      with any of the Debian package tools.

      2. FreeBSD 3.3? Yeah, right. If you're going to be a liar, at least get your version numbers right. The latest is 3.2 or 4.0. There's no 3.3.

    7. Re:Loving my FreeBSD-3.3 RC #3 Box by cmc · · Score: 1
      2. FreeBSD 3.3? Yeah, right. If you're going to be a liar, at least get your version numbers right. The latest is 3.2 or 4.0. There's no 3.3.

      Actually, 3.3-RC is the branch that's going to become 3.3-RELEASE in a few days; if you'll notice, it's what you get when you CVSup your 3.2-STABLE system.
    8. Re:Loving my FreeBSD-3.3 RC #3 Box by Anonymous Coward · · Score: 0

      Binary packages are not optimised for specific systems. I know which compiler flags to use on each of my systems, based on the CPU, RAM, disc space, etc. For top performance, a system with a 486, 16MB of RAM and a 512MB hard disc requires a somewhat different sort of binary to a Pentium III/500 system with 4GB of RAM and 50GB of disc space.

      I use FreeBSD, and always set up the compiler flags and whatnot on each system in /etc/make.conf. On my FreeBSD systems, the entire userland, including ports which have source (i.e. everything but Netscape), is always tailored to the machine, and a simple `make install' (for a port) or `make update && make world && mergemaster' (for the standard userland) is all that's needed to keep everything up to date (`make update' updates the source tree via CVSup, `make world' builds/installs the standard userland and `mergemaster' merges in any changes to /etc).

      Configuring/building the kernel is slightly more complex (since you've got to create/edit a config file), but it's still fairly easy to do (and is much quicker than rebuilding userland).

      Incidentally, the up-to-date GCC man pages on FreeBSD make things easier (I don't like `info'). So does the use of standard tar files for the distribution of the OS, ports/packages, etc.

      PS The Debian web site doesn't look very useful (limited documentation, no searching, etc.). Have I just hit it at a bad time?

    9. Re:Loving my FreeBSD-3.3 RC #3 Box by Anonymous Coward · · Score: 0
      2. FreeBSD 3.3? Yeah, right. If you're going to be a liar, at least get your version numbers right. The latest is 3.2 or 4.0. There's no 3.3.

      Wrong! FreeBSD is at 3.3 Release Candidate 3. Please do a cvsup and check it out.

    10. Re:Loving my FreeBSD-3.3 RC #3 Box by norn · · Score: 1

      pkg_add -r
      -r Use the remote fetching feature. This will determine the appropriate objformat and release and then fetch and install the package.
      (eg: pkg_add -r gimp)
      You forget that ports are just the front
      end to the package system. Packages are built
      nightly.

      'nuff said.

    11. Re:Loving my FreeBSD-3.3 RC #3 Box by guacamole · · Score: 1

      Yes, optimization is a good reason to use FreeBSD (e.g. make egcs default compiler and use -mpentimum flag for example)


      As for Debian website, If you go to www.debian.org and then click on "Documentation", you'll find the FAQ, user's manual, installation manual for each arch and a link to a Debian Documentation proje ct (yes, their search does not wrok for me either)

  114. Factual issues by gr · · Score: 5
    First off, let me say that it's good to see an article even addressing these issues in the Wall Street Journal, and as one poster said, they did a pretty good job for mainstream media. That said, the author tries to go into details and teach a history that he actually doesn't know, and that some /. readers also may not know, because it's pretty convoluted. These are arguably minor points, but I think they're important.
    The BSD programs and Linux actually share a common lineage, a collective development process and a rambunctious cast of characters.

    The free programs are all variants of the venerable Unix system invented by AT&T Corp.
    This is basically untrue. All four BSDs (including BSDi's BSD/OS) stem from the AT&T Unix sources, Linux was written entirely without access to those sources. It behaves similarly in a lot of ways, but vastly differently in others (arp and routing tables, for instance).

    This isn't to say that either Unix/BSD's or Linux's way is better (I personally prefer the methods that have been around and proven for twenty-odd years, but that's me).

    The author may have been trying to straighten out this mis-statement when he wrote:
    The Linux saga is already the stuff of modern legend. In 1991, Linus Torvalds, a 21-year-old student in Helsinki, began writing an operating system essentially from scratch so he could have something to use on his home computer. The programs FreeBSD, NetBSD and OpenBSD, by contrast, are the descendants of code written in the late 1970s and early 1980s at UC Berkeley.
    ... but I'm not sure that really clarifies things for the average reader, and has some factual failings of its own (Linus wrote a kernel, not an operating system, and operating system needs basic software, Gnu had it, we all know the drill and the fanatics involved).
    OpenBSD was started in 1995 by Theo de Raadt, a mountain biking 31-year-old Canadian after being kicked out of the NetBSD movement.
    Okay, so maybe Theo didn't leave NetBSD under the friendliest of circumstances, but to claim he was "kicked out" isn't really fair. He had disagreements about what the focus of the program should be, so he broke off to pursue the focus he felt was more important. This doesn't make either focus invalid, just points up the fact that you can't have one set of people focusing on both spreading platform support and securing all OS processes. The above comments imply that there's some kind of lasting enmity between the Open- and NetBSD projects, which simply isn't true.

    All of this said, the point an earlier poster made about how this is a pretty good article, and that the mainstream media is doing a much better job than they once did is quite valid. I'm also gladdened to see this article wasn't just more slobbering over RedHat... I've seen quite enough of that to last me the rest of my days.
    --
    Do you have a /. uid shorter than five digits? No? Then piss off.
    1. Re:Factual issues by Anonymous Coward · · Score: 0

      OpenBSD was started in 1995 by Theo de Raadt, a mountain biking 31-year-old Canadian after being kicked out of the NetBSD movement.

      Okay, so maybe Theo didn't leave NetBSD under the friendliest of circumstances, but to claim he was "kicked out" isn't really fair.

      Well, he was forcibly ejected from core and his CVS access was revoked. What more do you need? Read the coremail link on his web page on theos.com as soon as he puts it back up..

    2. Re:Factual issues by Anonymous Coward · · Score: 0

      Okay, so maybe Theo didn't leave NetBSD under the friendliest of circumstances, but to claim he was "kicked out" isn't really fair. He had disagreements about what the focus of the program should be, so he broke off to pursue the focus he felt was more important. This doesn't make either focus invalid, just points up the fact that you can't have one set of people focusing on both spreading platform support and securing all OS processes. The above comments imply that there's some kind of lasting enmity between the Open- and NetBSD projects, which simply isn't true. Go to theos.org and read the huge file Theo has there of the email exchange between NetBSD core and himself. "Kicked out" seems like a pretty good summary of the situation to me.

    3. Re: Factual issues by Anonymous Coward · · Score: 0

      Erm, the basic issue was that Theo was damaging the image of the NetBSD project by being extremely rude to people who were potential NetBSD users/contributors. There was no difference of opinion regarding direction. Later infantile gestures included mailbombing the NetBSD and FreeBSD mailing lists.

      Ultimately, though, you're right that this is ancient history, and irrelevant to the purpose OpenBSD eventually found for itself.

    4. Re: Factual issues by gr · · Score: 2

      Anonymous Coward wrote:
      Go to theos.org and read the huge file Theo has there of the email exchange between NetBSD core and himself. "Kicked out" seems like a pretty good summary of the situation to me.

      First off, that's theos.com

      Second, the file you describe isn't up right now, but I imagine it belongs under theos.com/deraadt somewhere.

      Third, I think I've read it before, and it displays some flaring tempers, but the basic issue was that Theo wanted to go a direction the Core didn't. Also, Theo has made it pretty clear that this is ancient history. The Open- and NetBSD projects are on amicable terms now and regularly kick code back and forth between their CVS repositories.

      --
      Do you have a /. uid shorter than five digits? No? Then piss off.
    5. Re:Factual issues by WNight · · Score: 1

      I don't think that saying GNU utillities are based on AT&T Unix utils is incorrect. The code may be completely from scratch, but the names, functions, and usage is similar.

      The code is often the smaller part of making a new util. Design, both in identifying the problem, and in deciding on the implementation, are as much of a problem as the actual coding.

      This isn't to run down the GNU utils, they are intended to be very similar to Unix tools. If they were vastly different, they wouldn't be as useful.

      (Why can't we have a thread that mentions GNU without someone using the term fanatic? They have stated a goal and are working towards that goal, not getting distracted in the meme of the moment isn't fanaticism.)

    6. Re:Factual issues by Trepidity · · Score: 2

      To add to that, the author also missed that Linus didn't write the Linux kernel from scratch. He extended Minix.

  115. Other side of the coin by twit · · Score: 1

    You've illustrated both sides of the coin, really. It makes plenty of sense for any company to use BSD or BSD-like licensed code written elsewhere, since they can modify at will without releasing source of the end product.

    Conversely it makes plenty of sense for any company to release their own code under the GPL, since no one else can modify at will without releasing source of the end product.

    Fair's fair - these two competing urges drive licenses and by extension drive development methadologies and organizations. Personally, I prefer the GPL and use Linux, but that hasn't kept me from dabbling in BSD.

    --

    --

    --
    There is no premature anti-fascism. -Ernest Hemingway
  116. It is not "Emulation" by Lazaru5 · · Score: 1


    The running of Linux binaries on FreeBSD is not accomplished by emulation, but by a process called "thunking" that converts Linux system calls to analogous BSD calls.

    Calling it Linux Emulation is a misnomer, and "emulation" sometimes has negative connotations associated with it, as if it's a poor reproduction of the original. It couldn't be further from the truth as some people have demonstrated that Linux binaries run *better* on FreeBSD than they do natively.

    The Natives are Restless...

    --

    --
    My comments and opinions completely reflect those of anyone and anything I am remotely associated with.
  117. What about "big" Linux apps like Oracle or DB2? by cpeterso · · Score: 1

    Linux gets the attention of the press and Big Companies, so most commercial applications seem to be showing up on Linux before FreeBSD. How risky is running a big app like Oracle 8i or IBM DB2 using FreeBSD's Linux "emulation"? Any problems?

  118. Looks like you forgot to take your prozac, by Anonymous Coward · · Score: 0

    Your paranoid tendencies are getting the best of you again... --Lazlo knows if you've been bad or good.

  119. Free BSD / Linux by Anonymous Coward · · Score: 0

    Should we be argueing amongst ourselves about who provides the supirior product?

    Is it not "horse's for course's" anyway?

    We should stick together and promote the open source community as a whole, and not reserve our compliments for only that which we use.

  120. default shells by josepha48 · · Score: 1

    The default shells are different and that is what makes one easier for ME and less UNIX like.
    Solaris - .ksh
    Linux -> bash
    FreeBSD -> sh
    AIX -> csh

    Yes you can change the shells, but the sites that I have been at do not do so.

    I feel that bash is an easier to use shell than the other shells. Just working with the bash default shell set up under Linux the arrow up and down make navigating thru history easier for me, especially coming from a DOS world to UNIX. Yes you have history in the other shells, but !47 (csh) is less friendly. I do have color xterms to, which makes color ls for me a good thing in X. I guess I like the features that have been added to Linux and would love to see them become defaults in other UNIX es

    --

    Only 'flamers' flame!

  121. Natural Selection.. by prodeje · · Score: 1

    With good press like this.. the other 5% is bound to come.. If it hasn't already since that survey was released.

    ...

    --

    Bitchslapped? Give Rob a bitchslap from bitchslapped.com.

  122. From where did they take these numbers? :) by hzo · · Score: 1

    could it be that..... (see footer)
    --

  123. BSD by bsDaemon · · Score: 1

    i learned UNIX when i was 12 on a FreeBSD system...i decided to use GNU/Linux instead of FreeBSD when i decided i knew enough to run *nix all the time...how ever, about a month ago, i've been moving everything on my home system over to FreeBSD.
    I loved that article. it's great to see BSD getting the propaganda..i mean, recognition it needs. Only thing i want to know is, why is BSD a programme, and Linux an operating system, when *BSD is the kernel, and the libraries and the tools, and linux is just a kernel?
    and also, i don't get why Linux users are agsinst BSD users and vice versa, just because of their OS? i think it comes for insecurites Linux people have about crappy memory managment, and BSD people getting defensive =0)
    just my two cents

    bsDaemon
    dfree@inna.net
    and my ISP runns FreeBSD, too!

  124. Not limelight. by doom · · Score: 1

    Good to see BSD get some of the limelight.

    That's spotlight. Most of us here want to see free unixes in the spotlight. Microsoft, we want to see fading into the limelight.

    Kids these days. No grasp of cliches at all.

    1. Re:Not limelight. by scrytch · · Score: 1

      That's fading from the limelight.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
  125. Er.. I don't like all of that stuff you mentioned by haggar · · Score: 2

    I love Linux, but the library incompatibilities not! That's a catastrophical issue that Debian seem to be taming somehow. Oh, and I don't like our little distro wars either!
    In my company (it's a very huge neterprise) we are trying to estabilish a policy on using Linux in the labs. I have seen a lot of *BSD machines around, too, maybe as much as Linux hosts. However, noone seems to be supporting the *BSD people. They seem to be very quiet and just go along and use *BSD and not giving a dime about policies. Me being primarily a network man, I don't care that much if we use Linux or *BSD, I only care to find all the OSPF and BGP routing features on the platfor. The more TCP/IP management programs, the better. So far, *BSD has proved to be more useful to us. So I wish the *BSD people here could push with more force, even though I use Linux more.

    --
    Sigged!
  126. Difference between *BSD and Linux? by Anonymous Coward · · Score: 0

    So what's the difference between *BSD and Linux (kernels) ? I mean in terms of features, speed,
    and their merits.

    (Everybody here says *BSD is superior to Linux,
    I'm a Debian user, I don't have the time and
    resources to try *BSD, so some explanations
    are appreciated)

    1. Re:Difference between *BSD and Linux? by Anonymous Coward · · Score: 0

      There aren't enough differences to justify this flamewar and most of the flamers have no knowledge to understand most of the differences. Each kernel moves as its community needs changes. Its more a question of functionality/stability for a given set of applications than "speed". And its not just the kernel but userland too.One group of security paranoids created OpenBSD, a group of strict license terms is driving Debian, etc

    2. Re:Difference between *BSD and Linux? by guacamole · · Score: 1

      If you are just a user, you can't notice any difference unless you run uname or something like that.

      However, there are some differences when comparing Debian and FreeBSD (I use both)

      1) Package management is different. FreeBSD has build-in very capable package management system with pkg_add, cvsup, ports. However, I still prefer the Debian way to any other Linux or *BSD. They started working on their pkg mngmt tools since the beginning and IMHO, they got it right.

      2) FreeBSD is not just a kernel, it is a rather complete OS. They work on kernel, libraries, programs, documentation, etc. However, Debian GNU/Linux is just as complete system. If you look, the most important components mostly come from only 2 sources GNU and Linux kernel.

      3) Installation is slightly different (but both, FreeBSD and Debian are arcane to install for a unix newbie)

      Both systems are very solid. I would chose any of the two instead of redhat or slackware. But then, probably these two simply meet my particular needs better than others..

    3. Re:Difference between *BSD and Linux? by guacamole · · Score: 1

      Oh, yes, FreeBSD and Debian init scripts are different

  127. "Supperior Security" by Anonymous Coward · · Score: 1

    RH 6.0 Security Errata XFree86 (RHSA-1999:035-01) inews (RHSA-1999:033-01) amd (RHSA-1999:032-01) vixie-cron (RHSA-1999:030-02) wu-ftpd (RHSA-1999:031-01) in.telnetd (RHSA-1999:029-01) libtermcap (RHSA-1999:028-01) pump (RHSA-1999:027-02) squid (RHSA-1999:025-01) samba (RHSA-1999:022-02) gnumeric (RHSA-1999:023-01) net-tools (RHSA-1999:017-01) KDE (RHSA-1999:015-01) XFree86 (RHSA-1999:013-03) dev, rxvt, screen (RHSA-1999:014-01) kernel update Netscape INN xscreensaver That's definetely a lot of packages. Of course when you look at the package list, you'll notice, only 2 or 3 are Linux specific (e.g. Kernel update). That means, for the most part, the aforementioned programs are exploitable on all platforms they are used. Just because you are using freeBSD doesn't mean you are immune to the latest netscape hole, or the latest samba bug. Face it, most of the security problems in Linux are specific to applications. Most of those applications are shared among the free unices. That means they are also vulnerable on *BSD. Just because somebody doesnt mass distrubte an exploit, for the bsd's, doesn't mean they aren't vulnerable. This myth, of superior security, is just that, a MYTH.

    1. Re:"Supperior Security" by Anonymous Coward · · Score: 0

      Even as a Linux user ... you are in urgent need of some reading. BSD security is slightly different from running X or not running X. I'm using Linux too, mainly because when I started BSD was out of reach as the phone costs in Europe forbode me to download it via my crappy 9600 modem. Your argumentation though ... /dev/null.

    2. Re:"Supperior Security" by Anonymous Coward · · Score: 0

      would you care to provide more detail? I am using both, although I tend to lean more towards Linux. However, everytiem I hear this 'supperior security' bs, there is never any basis for it. Last time I checked, the majority of the code for X under Linux and X under BSD is the same. Of course, several distributions have different ways to make X somewhat more secure (e.g. Xwrapper, or what not), but teh buffer overflows exist in the versions for Linux and *BSD, not just Linux.

    3. Re:"Supperior Security" by Anonymous Coward · · Score: 0

      Have you heard about "insecure install default packages and modes" ? Just look the latest vix cron xploit on RH only, or better, try to follow Venema and Postfix trying to don run the sendmail wrapper suid root on RH, or... That's the point, RH is running for nice features and user friendly setup, not for security. Even with massive distribution of script kiddies xploits the ratio of RH systems compromised far surpass the other Linux dists, even taken into account the relative numbers.RH behaves like a desktop os regards security

    4. Re:"Supperior Security" by Anonymous Coward · · Score: 0
      RedHat is not Linux.

      The guy has a very good point; why can't you acknowledge that he's right?

      Many of the pro-BSD advocates here act like MacZealots.

    5. Re:"Supperior Security" by Anonymous Coward · · Score: 0

      Actually, there were two problems with vixie-cron (check bugtraq). One had been fixed in debain a while ago, while the otehr hadn't (see debain security advisory). I'm not sure if other distributions using vixie-cron are vulnerable, but I would imagine so. The problem with vixie-cron (besides tehf act that it does not have an active maintanier), was not a improperly setup package, it was insecure code. As for "ry to follow Venema and Postfix trying to don run the sendmail wrapper suid root on RH" .. I have no idea what that means. Even if your unscientific assumption that more rh boxes are hacked, the simple justification would be, that most of teh mass distributed exploits come with defaults set to exploits RedHat bins. Thus only a script kiddie with half a brain would be able to use the same exploit on another machine. 99% of the script kiddies dont have half a brain. The rest of your post deals with opinion and not fact.

    6. Re:"Supperior Security" by Anonymous Coward · · Score: 0

      Unscientific? Hu. Good Luck with RH.

    7. Re:"Supperior Security" by Trepidity · · Score: 2

      I haven't been following the vixie-cron thing extremely closely, but it was my understanding that the BSDs were not completely vulnerable. The vixie-cron bug itself still existed, but the method of exploit was through sendmail, and the BSDs have fixed these sendmail problems, while most GNU/Linux distributions have not.

  128. Yes, limelight. by Anonymous Coward · · Score: 1

    Limelight -is- an early form of spotlight, produced by a mixed-gas flame, directed at a cylinder of lime, concentrated by a lens into a strong beam. Look it up.

  129. You, sir, do not understand cliches. by Anonymous Coward · · Score: 0

    It's not "fading into the limelight", it's "wading into the slimefight". My, that's a lovely papaya.

  130. Free unix-like OS'es already dominate by Anonymous Coward · · Score: 1

    If you count by the number of users accessing sites - notice how all the big sites run BSD or Linux - Google, Yahoo, Hotmail... free OS's already dominate the web.

    It's only when you treat lame FrontPage-generated websites that nobody ever visits as being EQUAL to the flagships of the web that NT pulls slightly ahead.

    1. Re:Free unix-like OS'es already dominate by Anonymous Coward · · Score: 0

      In my country the .gov sites are the lame FP ones that make NT seems to be widespread. I believe this MS/gov afair is very common world wide.

  131. Re:You know it by Anonymous Coward · · Score: 0

    This must be faked!

  132. Re:You know it by Anonymous Coward · · Score: 0

    and this isn't flamebait because...?

  133. You are completly wrong by delmoi · · Score: 1

    The person who *writes* the software can still do whatever they want with it, whether or not they use the GPL license. That includes selling it as closed source, or selling another license to someone who wants to use it in a close-source project.

    so, SGI can still make money from XFS in IRIX, or they could sell it to Microsoft for use in windows NT. Right now, MS can't use XFS in windows without GPLing it. They can use anything that the BSD people think up however.
    "Subtle mind control? Why do all these HTML buttons say 'Submit' ?"

    --

    ReadThe ReflectionEngine, a cyberpunk style n
  134. software *use* and software *creation* by delmoi · · Score: 1

    Remember, apple didn't chose a BSD licens, they chose a BSD Kernel. The BSD community got nothing from apples work, and Darwin is licensed under even more restrictive terms then the GPL I believe. The APSL is closer to the GPL then the BSD license as well.

    The thing is companies can Use work that has already be done in BSD code, but they are under no obligation to give back to the community. While Apple Opensourced part of there operating system, they didn't have to.

    If a company want's to Create something they are more likely going to use a GPL style license (like apple's ASPL) because then they are the only ones that can make money off there software (not counting OSS distributors, tech support, etc.). If Apple actually used a BSD license in with there software, anyone could use it.
    "Subtle mind control? Why do all these HTML buttons say 'Submit' ?"

    --

    ReadThe ReflectionEngine, a cyberpunk style n
  135. Re:If only your article were not so full of FUD... by guacamole · · Score: 1

    Allright, great. The bottom line is that you can upgrade a whole Debian system with just two commands from a shell (and this works very solidly I must say, but I prefer dselect to apt-get when updating the system.).

    and apt-get install apache is certainly less typing than feeding the whole (sometimes very long and akward) URL to pkg_add on FreeBSD.

    Of course this is a minor detail and both systems are very maintainable. Probably you can do this stuff with less worries and faster on Debian. I use both systems, FreeBSD usually needs more tinkering, but I still love it.

  136. I never said BSD was going to die by delmoi · · Score: 1

    All I said was that it would loose it's edge. If you re-read what I said, you will see that I implied that BSD actualy had a technical advantage with comperison to linux. I don't belive that this is going to be the case for much longer, however beacuse Linux is moving faster then *BSD. At some point in the future, Linux will be technicaly suprior to FreeBSD. The reason for this is beacuse Linux is getting more support from the industry, has more code contributers, etc, etc.
    "Subtle mind control? Why do all these HTML buttons say 'Submit' ?"

    --

    ReadThe ReflectionEngine, a cyberpunk style n
    1. Re:I never said BSD was going to die by Anonymous Coward · · Score: 0

      1. IBM's core UNIX product today is AIX, which contains a lot of BSD code (some from NetBSD, in fact).

      2. IBM's core UNIX product for the future is Monterey: a merger of AIX and SCO UnixWare 7 (UNIX System V R5) being developed by IBM and SCO.

      Linux is good for IBM from a PR perspective, and possibly as a tool for potentially hurting Microsoft's Windows platform. I personally doubt Linux will ever put a real dent in Microsoft's dominance of the desktop, but there's little risk to Microsoft's enemies in throwing a few scraps to every hyped `alternative' to the Windows desktop.

      As to SGI, it's been slowly dying for some time now. This Linux effort looks like a last grasp at straws, or perhaps an attempt to devote its final days to helping the latest `anti-Microsoft'.

  137. No Reason To Quarrel by redmist · · Score: 1


    I think that an important thing to remember at this juncture in our *BSD/Linux discourse is that *BSD has strengths specific to itself, and so does Linux. *BSD may be more secure, and Linux may be more friendly to newbies and have more applications, but this is really besides the point.

    The point is that they both have strengths and weakness's, but, after all, it's only an OS.

    --

    .{redmist}.
    -------------------------------------------------

    1. Re:No Reason To Quarrel by Anonymous Coward · · Score: 0

      These kiddies were created on a monopolistic OS world, they never worked on a mixed environment with VMS, VM, SunOS, DOS/packet drivers, OS/2, etc For them the world can have only one OS at a given instant of time, now it's Win* (were they type their homework) and tomorrow will be Linux. No space left for competition. This is just another evil consequence of Mr Gates culture on schools.

  138. Re:You know it by Anonymous Coward · · Score: 0

    NO ! Its OPENBSD you heretic !

  139. My experience with FreeBSD by scrytch · · Score: 2

    Uses disklabel instead of partitions. Basically all of freebsd's partitions are extended partitions. Pain in the ass reading them in linux (I just gave up trying to mount one), but overall a rather nice feature.

    Had to hand-edit a config file of nasty little abbreviated names to configure the kernel for reinstall. That just wasn't terribly fun.

    No configurator/wizard for ppp, had to pretty much set that up by hand. Didn't take me long, but it sure was a speedbump.

    Had some funny ideas about its root device when booted, had to fiddle with the boot loader to get it working. Comes up so often it's a FAQ, but maybe it should install the boot loader with the right parameters to begin with. Just a minor problem tho, and probably what i get for installing it on a secondary slave IDE drive in the first place.

    Ports are great, but it also has a package manager that looked adequate at any rate. KDE installed as a package, worked nicely out of the box.

    Now I'm wondering, will I be able to use the GLX 3d driver for my TNT card, and can I get sblive support for freebsd? I don't play many games on linux, but I like the possibility, and I do play the occasional mods or mp3's through it. Oh I wasn't too thrilled how aha152x support is specifically left out of the later kernels BTW. I know it's a crappy card, but I don't see it interfering with anything.

    --
    I've finally had it: until slashdot gets article moderation, I am not coming back.
    1. Re:My experience with FreeBSD by guacamole · · Score: 1

      Uses disklabel instead of partitions. Basically all of freebsd's partitions are extended partitions. Pain in the ass reading them in linux (I just gave up trying to mount one), but overall a rather nice feature.

      Check out the Linux+FreeBSD minihowto. It's not really difficult

    2. Re:My experience with FreeBSD by T-Punkt · · Score: 1

      > Now I'm wondering, will I be able to use the GLX 3d driver for my TNT card

      I can give you a definite "YES" to this question though I haven't tried it myself (don't have a TNT and don't run FreeBSD).

      Here's a step-by-step instruction:
      http://mail-index.netbsd.org/port-i386/1999/07/0 4/0008.html

      It's for NetBSD but better than nothing in case you don't find any HowTo for FreeBSD.

  140. I'm not a linux zelot, but, no I can't spell by delmoi · · Score: 1

    I don't think Linux is better or worse then FreeBSD, or any other *BSD. I was simply stating somthing that I thout was true. If you had enough intelegence to read what I wrote you would see that I implied that BSD had some technical superiority.

    As for my spelling, all I can say is, if you don't like it. Don't read my posts
    "Subtle mind control? Why do all these HTML buttons say 'Submit' ?"

    --

    ReadThe ReflectionEngine, a cyberpunk style n
  141. not quite.... by delmoi · · Score: 1

    While what you've said about the BSD licens might be true, anyone else could 'roll' the improvements that hackers make into *there* closed software. you would have no competitive advantage.

    Any opesource licens is going to be bad for a company that derives all its money from selling software licenses. But for a company like SGI, where they make most of there money from hardware the GPL makes more sense.
    "Subtle mind control? Why do all these HTML buttons say 'Submit' ?"

    --

    ReadThe ReflectionEngine, a cyberpunk style n
  142. If only your article were not so full of FUD... by cmc · · Score: 3

    FUD, you ask? Yes!

    2. Easy to upgrade. I have yet to see any tool surpass /usr/ports for pure ease of use. apt-get install "insert-name-here" is even easier and faster.

    FreeBSD also allows binary package installation.
    $ pkg_add ftp//:url_to_package

    FreeBSDs package management is great but it is NO match to Debian GNU/Linux. Debian is even easier to upgrade.
    1) You don't have to fix /etc by hand

    This is nonsense. Package management has nothing to do with the /etc directory. FreeBSD uses CVSup for that, and there is an excellent port which can update /etc for you automagically called mergemaster.

    2) You don't have to wait for hours for your stuff to compile (apt-get downloads binary packages unless told otherwise)

    FreeBSD also has gradual binary upgrades for both the -STABLE and -CURRENT systems known as "snapshots". See ftp://current.freebsd.org.

    3) You have to remake all your ports one by one after upgrading system. On Debian all packages are a part of distribution. If you upgrade system everything is upgraded.

    What gives you this idea? I've got a whole lot of ports I've preserved across many dozens of FreeBSD 4.0-CURRENT recompiles over several months:

    • GIMP
    • Many KDE apps (though I use GNOME mainly now)
    • nmap
    • The XFree86 stuff
    • Window Maker
    • Eterm
    • pdksh
    • vMac
    • jade
    • XAnim
    etc...
    FreeBSD handbook is great, but then most of the major linux distributions(Debian and RedHat) have such handbooks too (usually online too) + a huge collection of online docs at LDP
  143. As I make world by BadlandZ · · Score: 3
    Hmm. I have am currently running Debian, Red Hat, and FreeBSD. I have ran Slackware, SuSE, Open Linux, and a few others, plus some commercial UNIX systems (DEC, SGI, etc). And, the one conclusion I have come to is that the worst feature I have seen in any OS is clearly something I see from Linux (and to a lesser extent in FreeBSD).

    What's that feature you ask? Well, it's the small part of the user base that constantly has to say "my OS is better than yours."

    Each has it's benifits, and among the ones I like best are Red Hat and FreeBSD. Advocating the benifits of one over another is pointless when it will only start a flame war. There is no match for ports in the Linux world, dselect and dpkg are not as tight or relyable or intuitive, and it's not compileing from source allowing complete optimization based on your /etc/make.conf file, so it's not comparing apples to apples, it's comparing apples to oranges. And, rpm also has a remote package get, btw, rpm -ivh ftp://site.org/path/to.rpm works fine.

    The "tightness" and "tweakability" of FreeBSD is very good, and trying to say that Linux is better is shortsighted. Linux has a huge (yet unorginized, and frequently poorly documented) breath of applications that run native, and FreeBSD is still working to cetch up.

    Can't we just agree to disagree, and admit there is a great deal of good in both OS's. Start drawing on eachothers strengths, and admit that the interoperability of UNIX in it's many varients is still less fragemented that the Microsoft and Mac world would like us to believe? Or must we continue to drive wedges between diffrent UNIX factions, and fragement ourselfs into oblivion like was done in the past?

    1. Re:As I make world by Trepidity · · Score: 2

      Mostly agree with you, except for the native binaries issue. FreeBSD runs Linux binaries natively, not through emulation, so FreeBSD's native binaries are a superset of Linux's native binaries.

  144. Got a source for that? by Anonymous Coward · · Score: 1

    How false rumors grow...

    I wouldn't want to talk about either, since when Microsoft first acquired Hotmail, they switched over all the servers to Windows NT. Needless to say, their setup experienced mild "difficulties" as NT tried to handle the all the user load, and failed.. miserably.. After a short period (not short enough for many, I'm sure) they were forced to switch back.

    This piece of anti-Microsoft FUD is rapidly approaching classic status. AFAIK, this started as a rumor on PC Week's unattributed sources rumor column and has never been confirmed. The original rumor was that MS only tried out some NT test servers, now this guy's got them switching the whole site over! Surely if that actually happened, someone would be able to come up with documented dates. The truth seems to be that Microsoft has always taken a "don't fix what isn't broken" approach to hotmail. There's no evidence that they ever tried to switch it to NT.

  145. The average slashdotter..pathetic by Anonymous Coward · · Score: 0

    Regarding your first comment: apt-get source downloads the source to a package. Fix it up how you like it and run "debian/rules binary" to build a .deb. apt-get -b source downloads and rebuilds a package. Regarding your second comment: FreeBSD is developed using CVS using two source branches at once. One group focuses on the next major release, 4.0, in FreeBSD-CURRENT while another focuses on the next minor release, 3.3, in FreeBSD-STABLE. The guy said he is running 3.3 RC #3, so he must be running code he got out of FreeBSD-STABLE. Regarding the general tone of your post: Don't accuse people of being liars or it will come back and bite you in the ass

  146. I've used it by Anonymous Coward · · Score: 0
    I use FreeBSD every day, but I prefer Linux overall. It's just a matter of personal preference.

    I like the fact that Linux leans more toward SysV, like the Solaris systems I also use. FreeBSD reminds me too much of SunOS 4 (at least the *BSDs have fixed the mbuf thing...hello, Sun!?!), which I never really cared for.

    Runlevels are a Good Thing(tm). ps -ef...you'll feel better in the morning.

    In the big picture, the differences between Linux, FreeBSD, other BSDs, Solaris, etc., are not all that great. Pick one, pick two, pick 'em all, and have fun.

    I will use whichever of these gets the job done in the most efficient way possible, while still not being a major pain the ass.

    The only OS I really *hate* dealing with is NT. It has earned my hatred over three years of flakiness.

  147. GLX and the TNT2 on FreeBSD by Anonymous Coward · · Score: 0

    There's an article up on FreeBSDRocks (http://www.freebsdrocks.com) telling how to compile the nVidia stuff to work on FreeBSD. It worked fine for me.

  148. I have a link for you: by Anonymous Coward · · Score: 0
  149. Re:You know it by Anonymous Coward · · Score: 0

    But of course you know FreeBSD is much better than that crap that comes out of torvalds basement! Not to mention the developers of that fine Linux OS got screwed out of IPO money. All together now, repeat after me... FreeBSD is now your os of choice...

  150. Re:hmm I dont mean to start a flame war but.... by Anonymous Coward · · Score: 0

    My guess is that with the removal of the advertising clause, someone is going to try to start a GPL BSD project.

    Yes, and isn't the irony beautiful.

    Some idiot, or group of idiots, is going to use the GPL to force the forking of an Open Source project.

    I'm not really sure it will impress a lot of people, though. It seems spiteful more than anything else.

  151. BSD/Linux and BellLabs/Linux by Anonymous Coward · · Score: 0

    If you think "GNU/Linux" is an accurate name, then you're lying to yourself. It would be a lot more honest to call it "BSD/Linux" or "BellLabs/Linux", since the operating system originated there. It's remarkable how egotistical Stallman is, and how quick he is to try to steal unmerited publicity for himself. How does this help anything? I'm asking an honest question. I can't see how his childish whining does anything but bring grief.

  152. GNU/Linux or just Linux. by mr · · Score: 1

    So long as there are people who claim

    "Linux is the kernel"

    And

    "Linus wrote the kernel" (or is the hi potentate of the lernel)

    Then you will have 'factual errors' like the original article.


    Now, Linus is on RECORD saying that the offical name is "GNU/Linux" and that "Linux is more than the kernel".
    Both are ignored in the partisan in-fighing of the various distrobutions and the siupporters thereof.

    The 'unification of Unix' battles of the past are nothing like the moden "My Distro is better than your distro" battles of today. In the bad old days, there were not 107 versions of product.

    *sigh*

    When will you *ALL* come to the conclusion that "A rising tide can float all boats", and instead of running about drilling holes in the other boats, agree on what we all can agree on. That OpenSource is good, and getting vendors who wish to run on "OpenSource" OSes should write there code so it can run on *ALL* the OSes. (Hint: Think Linux compatible Binaries. )


    --
    If it was said on slashdot, it MUST be true!
  153. hmm I dont mean to start a flame war but.... by winnt386 · · Score: 0

    ...didn't the *bsd flavors of unix had what, 20 years to get their act together and yet let windows
    and proprietary unix os's come in without a care in the world and now the *bsd hackers are
    pissed at linux users and the whole computer world for ignoring them. They screwed up bad on
    marketing it, selling it, creating hype about it, and giving it to users.

    Again I don't want to start a flame war but people don't necessary buy OS's for technical reasons.
    I would like to compliment freebsd's technologies. Freebsd is technical superior to linux in many
    area's like tcp/ip stacks. TO help prevent a flame war between linux users and bsd users I give the
    credit of superior technology to freebsd and its cousins. I freely admit its superior. But politically
    its a disaster.

    Linus invented linux because he couldn't get a unix os for his 386 pc. freebsd either couldn't run
    on it or it was accessible at the time. He had to use minux. IF I am correct (I could be wrong).
    The group of *bsd hackers bickered among themselves and fragmented and made a terrible
    mistake. THe mistake was it wasn't involved with the IBM pc when it first came out. The *bsd
    group didn't let outsiders contribute code so users who wanted a more powerful OS had to buy a
    separate OS more proprietary OS like sun os, irix, aix. The fragmentation in unix itself began.
    Businesses who standardized on DOS discovered it was crap but put up with it because it was a
    temporary solution until unix or OS/2 would fill the gap. Unix was crazed by the IS departments
    until the early 1990's when unix completely became fragmented, proprietary, expensive, and unix
    companies began bickering among themselves and our good old pal Bill Gates came in and
    introduced win32 and promised windows95 which was going to be unix like and NT which was
    going to be even more unix like and may or may not replace it (remember people like Jesse Berst
    actually believed Microsoft at the time and Bill's words were "...unix like" when referring to the
    upcoming 32 bit windows OS's). I believe pcmagzine called windows95 the true unix like OS (I
    am not joking). The *bsd crowd ignored bill totally instead of pointing out there fallacies and
    marketing there OS and they still haven't learned from there mistakes and the source code was
    still closed and the users ignored average users and were real snotty. Guess what! Windows took
    over everything and NT 3.51 came out next and began to steal the unix market.

    Admit it how many unix workstations (not servers) are bought today? Not many. IF your an
    engineer which platform is your high end cad software written in? Which one would it have been
    10 years ago? Unix is really a server platform now thanks to microsoft and the EA market is really
    the only market that still runs unix workstations. I am fully aware that unix workstations are still
    bought for tasks other then EA but compare today's sales of unix workstations (not servers) to the
    sale of unix workstations 5 years ago.

    Then came linux and now the *bsd users have had it and are beginning to come around. I applaud
    them for selling and marketing and creating hype about there product which is what they should of
    done 20 years ago.

    I believe the only way *bsd can survive the next 5 years is to become very active and political like
    linux users. I met a guy who worked at microsoft and sold windows3.1 to businesses. When they
    asked him why should they select his OS over others and his response was "ITs better marketed.
    Everyone will be switching to it and using it". I know technogeeks like us hate this but an OS's are
    sold more for political reasons then technical. We have NT as an example of this. Linux has buzz
    and its a very good OS technically. Linux has the bst of both worlds.

    This is also why my boss at work refuses to look at freebsd and I agree with him. ALso linux has
    more programers and I believe it will catch up very soon. Linus tried to fix disk caching and tcp/ip
    performance in kernel 2.3 so perhaps 2.4 might begin to catch up to *bsd. I believe the *bsd
    group should go gnu to compete with linux. Linux said that linux is made up of 30 full time and
    over 1,000 part time programmers who work on the kernel while freebsd has only 15 guys. Do
    any of you remember the old nursery story with the rabbit and the turtle who raced together? The
    rabbit took a nap and the turtle was way ahead and even though he quickly ran fast, the turtle still
    won. I believe freebsd had the unix code already and was around over 12 years longer then linux
    so it had an advantage. Linux is accelerating faster then *bsd while the community scoffed and
    ignored linux and now like the rabbit in the story it may be too late for freebsd unless it radically
    changes.

    These are my 2 points about freebsd coming from a linux user. Feel free to comment.

    --
    "Never stick an electrical appliance down your pants." -Tim Allen
  154. Linux vs BSD vs Mac vs nt vs honda civic vs volvo by Orbit! · · Score: 2

    How many slashdoters does it take to change a lightbulb? A: Exactly Five Hundred: 1 to change the light bulb and to post to slashdot that the light bulb has been changed 7 to share similar experiences of changing light bulbs and how the light bulb could have been changed differently. 4 to caution about the dangers of changing light bulbs. 17 to point out spelling/grammar errors in posts about changing light bulbs. 21 to flame the spell checkers 49 to write to the modorator complaining aboutthe light bulb discussion and its inappropriateness 20 to correct spelling in the spelling/grammar flames. 32 to post that this topic is not about light bulbs and to please take this email exchange to alt.lite.bulb 69 to demand that cross posting to alt.grammar, alt.spelling and alt.punctuation about changing light bulbs be stopped. 41 to defend the posting to this topic saying that we all use light bulbs and therefore the posts **are** relevant to this topic. 106 to debate which method of changing light bulbs is superior, where to buy the best light bulbs, what brand of light bulbs work best for this technique, and what brands are faulty. 12 to post URLs where one can see examples of different light bulbs 8 to post that the URLs were posted incorrectly, and to post corrected URLs. 2 to post about links they found from the URLs that are relevant to this topic which makes light bulbs relevant to this topic. 15 to concatenate all posts to date, then quote them including all headers and footers, and then add pointedly, "Me Too." 6 to post to the list that they are not visiting slashdot because they cannot handle the light bulb controversy. 9 to quote the "Me Too's" and happily add, "Me Three"3 to suggest that posters request the light bulb FAQ. 1 to propose new slashdot topic. 24 to say this is just what www.bugtraq.org was meant for, leave it here. 53 votes for slashdot.org