Slashdot Mirror


Why is BSD Not As Popular As Linux?

hill writes "An article over on Economic Times explains why BSD is as not as popular as Linux. Both use an open-source model, but Linux demands the user community to disclose modifications on its source code, while BSD allows its users to make proprietary changes. The current size of the BSD community is estimated at 2 million, with Linux being around 10 million. This is definately worth the read for anyone interested in comparing the two operating systems. " I'm sure we have a few opinions on the subject.

690 comments

  1. maybe... by abram_fettig · · Score: 1

    ...because penguins are cuter that daemons?

    1. Re:maybe... by Bruce+Perens · · Score: 1

      You weren't at Comdex.

    2. Re:maybe... by martin-k · · Score: 0

      >> Have you checked out TECHNOCRAT.NET? Yeah, great site! I especially love the graphics and the animation.

    3. Re:maybe... by martin-k · · Score: 1
      >> Have you checked out TECHNOCRAT.NET?

      Yeah, great site! I especially love the graphics and the animation.

    4. Re:maybe... by bmetzler · · Score: 2
      Yeah, great site! I especially love the graphics and the animation.

      Waah!!! The links to the graphics are broken. I can't see it.... :)

      -Brent
    5. Re:maybe... by Anonymous Coward · · Score: 0

      This is true. I've tried BSD and use it through my web host. I like it because it's UNIX and LINUX is not. But I can't get myself to run it on my own boxes because that of daemon-like embled. I've seen the CDrom box for OpenBSD. None of those demon things, so maybe I'll try it in the future.

      Sorry, guys, but you've got to have good marketing and those daemons just keep you in hell.

    6. Re:maybe... by Anonymous Coward · · Score: 0

      The daemon mascot is what caught my attention in the first place.

      Then again, one of my former roommates did happen to be Satan, so maybe I'm biased.

      (Actually, what really caught my attention was the fact that all the sysadmins at work used it - bing, instant tech support) (luckily for both me and them, I never ran into problems I couldn't figure out)

    7. Re:maybe... by Anonymous Coward · · Score: 0

      No, because FreeBSD is a server OS and Linux is leaping more towards a desktop os.

    8. Re:maybe... by Anonymous Coward · · Score: 0

      What a stupid lie. There is no difference.

    9. Re:maybe... by Anonymous Coward · · Score: 0

      Yeah, there is. Look at things like scheduler latency, rather than just raw throughput. In later 2.3.x kernels, Linux will reschedule SCHED_FIFOed tasks within ~1ms of becoming ready to run (usually as a result of an interrupt from the soundcard or IDE/SCSI controller). This means I can reliably process audio with a max latency of ~2ms. BeOS (the "media OS" or so says their marketing dept) quotes 3ms latency on audio. (Too be fair, BeOS's video manipulation framework is quite impressive, while all linux has is xanim. And some promises from xmms).

      The same app on FreeBSD would get drop outs with buffers sized for 10ms. I didn't go higher, because it simply got too high. FreeBSD might make a great webserver, but as far as workstation class tasks like advanced multimedia, Linux is the way to go.

      Humorous aside: Trying to do the same thing on windows95 would drop out even with buffers for 30ms of end to end latency. UGH.

  2. Linux Logo is cuter by kermyt · · Score: 1

    I think the reason for the awe inspiring sucess of Linux should be obvious. that darn penguin is much cuter than the little devil. that is the same reason imacs ar available in so many cute colors.

  3. The more the better by core · · Score: 5

    First, we should look at it this way: there are 12 million people that use a free unix-like operating system. Most if not all opensource applications run equally well on both. One (Linux) is an implementation from scratch, the other (Free/Net/OpenBSD) has royal blood as it is the direct descendant of 4.4BSD which itself descends from Unix. This should keep happy both the new army of coders that like to toy with new concepts, and the traditionalists for whom 30 year old code doesn't mean outdated, but proven and stable. Both points of view can be defended I think. We therefore have 12 million users and users-developers of free unixish applications, that's great and was absolutely unthinkable 10 years ago!

    As for the technical side, I keep having to look at both the linux and freebsd kernels as part of my work; they are good references. Both have very good parts. I have to say that usually, the solution adopted by FreeBSD is simpler and a lot more commented/documented (take the bogomips case for example; people are starting to wonder what will happen if the cpu speed changes at runtime, how to detect and recalculate it, etc; freebsd spins simply by looking at changes in the hardware clock counter. simpler :). Same for NIC drivers usually (hello, donald becker, do comment weird things :-). But the linux kernel is full of good and new ideas.

    So we need both if we want to keep the high standards we are used to have in the free unices now. That was my original point :) Long and happy life to all the linux and free/open/netbsd hackers, be it kernel or office applications writers :)

    1. Re:The more the better by Foogle · · Score: 1
      I could be mistaken, but I think you'll find a very serious absence of 30-year-old code in any of the three major BSDs.

      -----------

      "You can't shake the Devil's hand and say you're only kidding."

    2. Re:The more the better by Anonymous Coward · · Score: 0

      If Linux is a from-scratch thing, why do I find so much BSD code in any given Linux distro?

    3. Re:The more the better by Spamizbad · · Score: 1

      State Examples. Besides BSD init scripts.

    4. Re:The more the better by core · · Score: 1

      I could be mistaken, but I think you'll find a very serious absence of 30-year-old code in any of the three major BSDs.

      It's not meant to be taken literally. It can be 5 or 10 year old code. Some of the source files like C headers for network protocols (tcp/ip et al) were certainly created more than 20 years ago, IIRC for 4.2BSD.

      As I said old doesn't mean bad, just that there was no point in changing what wasn't broken. It doesn't mean any of the BSD code is out of date.

    5. Re:The more the better by Anonymous Coward · · Score: 0

      Oh wow the whole kernel is from "scratch" The rest is stolen BSD code anyway. BSD is not for the masses.. Unless you count all the people using BSD with some guys hacked up kernel (LINUX). The linux kernel code quality is junk compared to the REAL UNIX kernels in the BSDs...

    6. Re:The more the better by Zurk · · Score: 1

      yep. the whole kernel is from scratch. be enlightened : http://khg.redhat.com - everything you need to know about linux kernels.

    7. Re:The more the better by Anonymous Coward · · Score: 0
      State Examples. Besides BSD init scripts.
      Very well.
      redhat% cd /usr/man/man1/
      redhat% grep -il 'copyright.*regents' */*.*
      man1/ash.1
      man1/bsh.1
      man1/col.1
      man1/colrm.1
      man1/finger.1
      man1/ftp.1
      man1/gprof.1
      man1/lpq.1
      man1/lpr.1
      man1/lprm.1
      man1/lptest.1
      man1/more.1
      man1/pftp.1
      man1/pmake.1
      man1/rcp.1
      man1/rdist.1
      man1/rev.1
      man1/rlogin.1
      man1/rsh.1
      man1/rup.1
      man1/ruptime.1
      man1/rusers.1
      man1/rwho.1
      man1/script.1
      man1/snmpnetstat.1
      man1/talk.1
      man1/tclsh.1
      man1/tftp.1
      man1/tixwish.1
      man1/tsort.1
      man1/uuencode.1
      man1/whereis.1
      man1/wish.1
      man2/accept.2
      man2/bind.2
      man2/connect.2
      man2/getpeername.2
      man2/getpriority.2
      man2/getsockname.2
      man2/getsockopt.2
      man2/ioctl.2
      man2/killpg.2
      man2/listen.2
      man2/lseek.2
      man2/readlink.2
      man2/recv.2
      man2/setpgid.2
      man2/setregid.2
      man2/setreuid.2
      man2/shutdown.2
      man2/sigblock.2
      man2/sigpause.2
      man2/socket.2
      man2/socketpair.2
      man2/statfs.2
      man2/truncate.2
      man3/3DBorder.3
      man3/AddErrInfo.3
      man3/AllowExc.3
      man3/AppInit.3
      man3/Async.3
      man3/BackgdErr.3
      man3/Backslash.3
      man3/BindTable.3
      man3/CallDel.3
      man3/Clipboard.3
      man3/ClrSelect.3
      man3/CmdCmplt.3
      man3/Concat.3
      man3/ConfigWidg.3
      man3/ConfigWind.3
      man3/CoordToWin.3
      man3/CrtCommand.3
      man3/CrtErrHdlr.3
      man3/CrtFileHdlr.3
      man3/CrtGenHdlr.3
      man3/CrtImgType.3
      man3/CrtInterp.3
      man3/CrtMathFnc.3
      man3/CrtSelHdlr.3
      man3/CrtTimerHdlr.3
      man3/CrtTrace.3
      man3/CrtWindow.3
      man3/DString.3
      man3/DetachPids.3
      man3/DoOneEvent.3
      man3/DoWhenIdle.3
      man3/Eval.3
      man3/EventHndlr.3
      man3/ExprLong.3
      man3/FreeXId.3
      man3/GeomReq.3
      man3/GetAnchor.3
      man3/GetBitmap.3
      man3/GetCapStyl.3
      man3/GetClrmap.3
      man3/GetColor.3
      man3/GetCursor.3
      man3/GetFont.3
      man3/GetGC.3
      man3/GetImage.3
      man3/GetInt.3
      man3/GetJoinStl.3
      man3/GetJustify.3
      man3/GetOption.3
      man3/GetPixels.3
      man3/GetPixmap.3
      man3/GetRelief.3
      man3/GetRootCrd.3
      man3/GetScroll.3
      man3/GetSelect.3
      man3/GetUid.3
      man3/GetVRoot.3
      man3/GetVisual.3
      man3/HandleEvent.3
      man3/Hash.3
      man3/ImgChanged.3
      man3/InternAtom.3
      man3/Interp.3
      man3/LinkVar.3
      man3/MainLoop.3
      man3/MainWin.3
      man3/MaintGeom.3
      man3/ManageGeom.3
      man3/MapWindow.3
      man3/MoveToplev.3
      man3/Name.3
      man3/OwnSelect.3
      man3/ParseArgv.3
      man3/Preserve.3
      man3/PrintDbl.3
      man3/RecordEval.3
      man3/RegExp.3
      man3/Restack.3
      man3/RestrictEv.3
      man3/SetAppName.3
      man3/SetClass.3
      man3/SetGrid.3
      man3/SetRecLmt.3
      man3/SetResult.3
      man3/SetVar.3
      man3/SetVisual.3
      man3/Sleep.3
      man3/SplitList.3
      man3/StrMatch.3
      man3/Tcl_AddErrorInfo.3
      man3/Tcl_AddObjErrorInfo.3
      man3/Tcl_AllowExceptions.3
      man3/Tcl_AppInit.3
      man3/Tcl_AppendElement.3
      man3/Tcl_AppendResult.3
      man3/Tcl_AsyncCreate.3
      man3/Tcl_AsyncDelete.3
      man3/Tcl_AsyncInvoke.3
      man3/Tcl_AsyncMark.3
      man3/Tcl_BackgroundError.3
      man3/Tcl_Backslash.3
      man3/Tcl_CallWhenDeleted.3
      man3/Tcl_CancelIdleCall.3
      man3/Tcl_CommandComplete.3
      man3/Tcl_Concat.3
      man3/Tcl_ConvertElement.3
      man3/Tcl_CreateCommand.3
      man3/Tcl_CreateFileHandler.3
      man3/Tcl_CreateHashEntry.3
      man3/Tcl_CreateInterp.3
      man3/Tcl_CreateMathFunc.3
      man3/Tcl_CreateTimerHandler.3
      man3/Tcl_CreateTrace.3
      man3/Tcl_DStringAppend.3
      man3/Tcl_DStringAppendElement.3
      man3/Tcl_DStringEndSublist.3
      man3/Tcl_DStringFree.3
      man3/Tcl_DStringGetResult.3
      man3/Tcl_DStringInit.3
      man3/Tcl_DStringLength.3
      man3/Tcl_DStringResult.3
      man3/Tcl_DStringSetLength.3
      man3/Tcl_DStringStartSublist.3
      man3/Tcl_DStringValue.3
      man3/Tcl_DeleteFileHandler.3
      man3/Tcl_DeleteHashEntry.3
      man3/Tcl_DeleteHashTable.3
      man3/Tcl_DeleteInterp.3
      man3/Tcl_DeleteTimerHandler.3
      man3/Tcl_DeleteTrace.3
      man3/Tcl_DetachPids.3
      man3/Tcl_DoOneEvent.3
      man3/Tcl_DoWhenIdle.3
      man3/Tcl_DontCallWhenDeleted.3
      man3/Tcl_Eval.3
      man3/Tcl_EvalFile.3
      man3/Tcl_EventuallyFree.3
      man3/Tcl_ExprBoolean.3
      man3/Tcl_ExprDouble.3
      man3/Tcl_ExprLong.3
      man3/Tcl_ExprString.3
      man3/Tcl_FindHashEntry.3
      man3/Tcl_FirstHashEntry.3
      man3/Tcl_GetBoolean.3
      man3/Tcl_GetDouble.3
      man3/Tcl_GetHashKey.3
      man3/Tcl_GetHashValue.3
      man3/Tcl_GetInt.3
      man3/Tcl_GetObjResult.3
      man3/Tcl_GetStringResult.3
      man3/Tcl_GetVar.3
      man3/Tcl_GetVar2.3
      man3/Tcl_GlobalEval.3
      man3/Tcl_HashStats.3
      man3/Tcl_InitHashTable.3
      man3/Tcl_Interp.3
      man3/Tcl_InterpDeleted.3
      man3/Tcl_LinkVar.3
      man3/Tcl_Main.3
      man3/Tcl_Merge.3
      man3/Tcl_NextHashEntry.3
      man3/Tcl_PosixError.3
      man3/Tcl_Preserve.3
      man3/Tcl_PrintDouble.3
      man3/Tcl_ReapDetachedProcs.3
      man3/Tcl_RecordAndEval.3
      man3/Tcl_RegExpCompile.3
      man3/Tcl_RegExpExec.3
      man3/Tcl_RegExpMatch.3
      man3/Tcl_RegExpRange.3
      man3/Tcl_Release.3
      man3/Tcl_ResetResult.3
      man3/Tcl_ScanElement.3
      man3/Tcl_SetErrorCode.3
      man3/Tcl_SetHashValue.3
      man3/Tcl_SetObjResult.3
      man3/Tcl_SetRecursionLimit.3
      man3/Tcl_SetResult.3
      man3/Tcl_SetVar.3
      man3/Tcl_SetVar2.3
      man3/Tcl_Sleep.3
      man3/Tcl_SplitList.3
      man3/Tcl_StringMatch.3
      man3/Tcl_TraceVar.3
      man3/Tcl_TraceVar2.3
      man3/Tcl_TranslateFileName.3
      man3/Tcl_UnlinkVar.3
      man3/Tcl_UnsetVar.3
      man3/Tcl_UnsetVar2.3
      man3/Tcl_UntraceVar.3
      man3/Tcl_UntraceVar2.3
      man3/Tcl_UpVar.3
      man3/Tcl_UpVar2.3
      man3/Tcl_UpdateLinkedVar.3
      man3/Tcl_VarEval.3
      man3/Tcl_VarTraceInfo.3
      man3/Tcl_VarTraceInfo2.3
      man3/Tk_3DBorderColor.3
      man3/Tk_3DBorderGC.3
      man3/Tk_3DHorizontalBevel.3
      man3/Tk_3DVerticalBevel.3
      man3/Tk_Attributes.3
      man3/Tk_BindEvent.3
      man3/Tk_ChangeWindowAttributes.3
      man3/Tk_Changes.3
      man3/Tk_Class.3
      man3/Tk_ClearSelection.3
      man3/Tk_ClipboardAppend.3
      man3/Tk_ClipboardClear.3
      man3/Tk_Colormap.3
      man3/Tk_ConfigureInfo.3
      man3/Tk_ConfigureValue.3
      man3/Tk_ConfigureWidget.3
      man3/Tk_ConfigureWindow.3
      man3/Tk_CoordsToWindow.3
      man3/Tk_CreateBinding.3
      man3/Tk_CreateBindingTable.3
      man3/Tk_CreateErrorHandler.3
      man3/Tk_CreateEventHandler.3
      man3/Tk_CreateGenericHandler.3
      man3/Tk_CreateImageType.3
      man3/Tk_CreateSelHandler.3
      man3/Tk_CreateWindow.3
      man3/Tk_CreateWindowFromPath.3
      man3/Tk_DefineBitmap.3
      man3/Tk_DefineCursor.3
      man3/Tk_DeleteAllBindings.3
      man3/Tk_DeleteBinding.3
      man3/Tk_DeleteBindingTable.3
      man3/Tk_DeleteErrorHandler.3
      man3/Tk_DeleteEventHandler.3
      man3/Tk_DeleteGenericHandler.3
      man3/Tk_DeleteSelHandler.3
      man3/Tk_Depth.3
      man3/Tk_DestroyWindow.3
      man3/Tk_Display.3
      man3/Tk_DisplayName.3
      man3/Tk_Draw3DPolygon.3
      man3/Tk_Draw3DRectangle.3
      man3/Tk_Fill3DPolygon.3
      man3/Tk_Fill3DRectangle.3
      man3/Tk_Free3DBorder.3
      man3/Tk_FreeBitmap.3
      man3/Tk_FreeColor.3
      man3/Tk_FreeColormap.3
      man3/Tk_FreeCursor.3
      man3/Tk_FreeFont.3
      man3/Tk_FreeGC.3
      man3/Tk_FreeImage.3
      man3/Tk_FreeOptions.3
      man3/Tk_FreePixmap.3
      man3/Tk_FreeXId.3
      man3/Tk_GeometryRequest.3
      man3/Tk_Get3DBorder.3
      man3/Tk_GetAllBindings.3
      man3/Tk_GetAnchor.3
      man3/Tk_GetAtomName.3
      man3/Tk_GetBinding.3
      man3/Tk_GetBitmap.3
      man3/Tk_GetBitmapFromData.3
      man3/Tk_GetCapStyle.3
      man3/Tk_GetColor.3
      man3/Tk_GetColorByValue.3
      man3/Tk_GetColormap.3
      man3/Tk_GetCursor.3
      man3/Tk_GetCursorFromData.3
      man3/Tk_GetFont.3
      man3/Tk_GetGC.3
      man3/Tk_GetImage.3
      man3/Tk_GetImageMasterData.3
      man3/Tk_GetJoinStyle.3
      man3/Tk_GetJustify.3
      man3/Tk_GetOption.3
      man3/Tk_GetPixels.3
      man3/Tk_GetPixmap.3
      man3/Tk_GetRelief.3
      man3/Tk_GetRootCoords.3
      man3/Tk_GetScreenMM.3
      man3/Tk_GetScrollInfo.3
      man3/Tk_GetSelection.3
      man3/Tk_GetUid.3
      man3/Tk_GetVRootGeometry.3
      man3/Tk_GetVisual.3
      man3/Tk_HandleEvent.3
      man3/Tk_Height.3
      man3/Tk_ImageChanged.3
      man3/Tk_InternAtom.3
      man3/Tk_InternalBorderWidth.3
      man3/Tk_IsMapped.3
      man3/Tk_IsTopLevel.3
      man3/Tk_Main.3
      man3/Tk_MainLoop.3
      man3/Tk_MainWindow.3
      man3/Tk_MaintainGeometry.3
      man3/Tk_MakeWindowExist.3
      man3/Tk_ManageGeometry.3
      man3/Tk_MapWindow.3
      man3/Tk_MoveResizeWindow.3
      man3/Tk_MoveToplevelWindow.3
      man3/Tk_MoveWindow.3
      man3/Tk_Name.3
      man3/Tk_NameOf3DBorder.3
      man3/Tk_NameOfAnchor.3
      man3/Tk_NameOfBitmap.3
      man3/Tk_NameOfCapStyle.3
      man3/Tk_NameOfColor.3
      man3/Tk_NameOfCursor.3
      man3/Tk_NameOfFont.3
      man3/Tk_NameOfJoinStyle.3
      man3/Tk_NameOfJustify.3
      man3/Tk_NameOfRelief.3
      man3/Tk_NameToWindow.3
      man3/Tk_Offset.3
      man3/Tk_OwnSelection.3
      man3/Tk_Parent.3
      man3/Tk_ParseArgv.3
      man3/Tk_PathName.3
      man3/Tk_RedrawImage.3
      man3/Tk_ReqHeight.3
      man3/Tk_ReqWidth.3
      man3/Tk_ResizeWindow.3
      man3/Tk_RestackWindow.3
      man3/Tk_RestrictEvents.3
      man3/Tk_Screen.3
      man3/Tk_ScreenNumber.3
      man3/Tk_SetAppName.3
      man3/Tk_SetBackgroundFromBorder.3
      man3/Tk_SetClass.3
      man3/Tk_SetGrid.3
      man3/Tk_SetInternalBorder.3
      man3/Tk_SetWindowBackground.3
      man3/Tk_SetWindowBackgroundPixmap.3
      man3/Tk_SetWindowBorder.3
      man3/Tk_SetWindowBorderPixmap.3
      man3/Tk_SetWindowBorderWidth.3
      man3/Tk_SetWindowColormap.3
      man3/Tk_SetWindowVisual.3
      man3/Tk_SizeOfBitmap.3
      man3/Tk_SizeOfImage.3
      man3/Tk_Uid.3
      man3/Tk_UndefineCursor.3
      man3/Tk_UnmaintainGeometry.3
      man3/Tk_UnmapWindow.3
      man3/Tk_UnsetGrid.3
      man3/Tk_Visual.3
      man3/Tk_Width.3
      man3/Tk_WindowId.3
      man3/Tk_X.3
      man3/Tk_Y.3
      man3/TraceVar.3
      man3/Translate.3
      man3/UpVar.3
      man3/WindowId.3
      man3/alloca.3
      man3/exec.3
      man3/fclose.3
      man3/ferror.3
      man3/fflush.3
      man3/fopen.3
      man3/fread.3
      man3/fseek.3
      man3/getpass.3
      man3/popen.3
      man3/printf.3
      man3/scanf.3
      man3/setbuf.3
      man3/stdarg.3
      man3/stdio.3
      man3/strtod.3
      man5/fstab.5
      man5/inetd.conf.5
      man5/printcap.5
      man5/resolver.5
      man5/uuencode.5
      man7/hostname.7
      man7/mailaddr.7
      man7/me.7
      man8/fingerd.8
      man8/ftpd.8
      man8/gated.8
      man8/gdc.8
      man8/in.fingerd.8
      man8/in.ntalkd.8
      man8/in.rexecd.8
      man8/in.rlogind.8
      man8/in.rshd.8
      man8/in.talkd.8
      man8/in.telnetd.8
      man8/in.tftpd.8
      man8/inetd.8
      man8/lpc.8
      man8/lpd.8
      man8/ntalkd.8
      man8/ospf_monitor.8
      man8/pac.8
      man8/ping.8
      man8/portmap.8
      man8/rdist.8
      man8/rexecd.8
      man8/ripquery.8
      man8/rlogind.8
      man8/rpc.rstatd.8
      man8/rpc.rusersd.8
      man8/rshd.8
      man8/rusersd.8
      man8/rwhod.8
      man8/swapon.8
      man8/talkd.8
      man8/telnetd.8
      man8/tftpd.8
      man8/timed.8
      man8/timedc.8
      man8/vipw.8
      mann/Balloon.n
      mann/BtnBox.n
      mann/ChkList.n
      mann/ComboBox.n
      mann/Control.n
      mann/DItem.n
      mann/Destroy.n
      mann/DirDlg.n
      mann/DirList.n
      mann/DirTree.n
      mann/EFileBox.n
      mann/EFileDlg.n
      mann/FileBox.n
      mann/Fmann/FileEnt.n
      mann/Form.n
      mann/GetBool.n
      mann/GetInt.n
      mann/Grid.n
      mann/HList.n
      mann/InpOnly.n
      mann/LabEntry.n
      mann/LabFrame.n
      mann/ListNBK.n
      mann/Meter.n
      mann/Mwm.n
      mann/NBFrame.n
      mann/NoteBook.n
      mann/OptMenu.n
      mann/PanedWin.n
      mann/PopMenu.n
      mann/SHList.n
      mann/SListBox.n
      mann/SText.n
      mann/SWindow.n
      mann/Select.n
      mann/StdBBox.n
      ileDlg.n
      mann/TList.n
      mann/Tcl.n
      mann/TixIntro.n
      mann/Tree.n
      mann/Utils.n
      mann/Wm.n
      mann/after.n
      mann/append.n
      mann/array.n
      mann/bell.n
      mann/bgerror.n
      mann/bind.n
      mann/bindtags.n
      mann/bitmap.n
      mann/break.n
      mann/button.n
      mann/canvas.n
      mann/case.n
      mann/catch.n
      mann/cd.n
      mann/checkbutton.n
      mann/clipboard.n
      mann/close.n
      mann/compound.n
      mann/concat.n
      mann/continue.n
      mann/destroy.n
      mann/entry.n
      mann/eof.n
      mann/error.n
      mann/eval.n
      mann/exec.n
      mann/exit.n
      mann/expr.n
      mann/fcopy.n
      mann/file.n
      mann/fileevent.n
      mann/flush.n
      mann/focus.n
      mann/focusNext.n
      mann/for.n
      mann/foreach.n
      mann/format.n
      mann/frame.n
      mann/gets.n
      mann/glob.n
      mann/global.n
      mann/grab.n
      mann/history.n
      mann/if.n
      mann/image.n
      mann/incr.n
      mann/info.n
      mann/join.n
      mann/label.n
      mann/lappend.n
      mann/library.n
      mann/lindex.n
      mann/linsert.n
      mann/list.n
      mann/listbox.n
      mann/llength.n
      mann/lower.n
      mann/lrange.n
      mann/lreplace.n
      mann/lsearch.n
      mann/lsort.n
      mann/menu.n
      mann/menubutton.n
      mann/message.n
      mann/open.n
      mann/option.n
      mann/optionMenu.n
      mann/options.n
      mann/pack-old.n
      mann/pack.n
      mann/pid.n
      mann/pixmap.n
      mann/place.n
      mann/proc.n
      mann/puts.n
      mann/pwd.n
      mann/radiobutton.n
      mann/raise.n
      mann/read.n
      mann/regexp.n
      mann/regsub.n
      mann/rename.n
      mann/return.n
      mann/scale.n
      mann/scan.n
      mann/scrollbar.n
      mann/seek.n
      mann/selection.n
      mann/send.n
      mann/set.n
      mann/source.n
      mann/split.n
      mann/string.n
      mann/subst.n
      mann/switch.n
      mann/tclvars.n
      mann/tell.n
      mann/text.n
      mann/time.n
      mann/tix.n
      mann/tk.n
      mann/tk_bindForTraversal.n
      mann/tk_dialog.n
      mann/tk_focusFollowsMouse.n
      mann/tk_focusNext.n
      mann/tk_focusPrev.n
      mann/tk_menuBar.n
      mann/tk_optionMenu.n
      mann/tkerror.n
      mann/tkvars.n
      mann/tkwait.n
      mann/toplevel.n
      mann/trace.n
      mann/unknown.n
      mann/unset.n
      mann/update.n
      mann/uplevel.n
      mann/upvar.n
      mann/while.n
      mann/winfo.n
      mann/wm.n
      Even discounting the strange tcl and tk stuff, there's a great deal there.
    8. Re:The more the better by Anonymous Coward · · Score: 0

      Who cares about documentation? Try grepping for the regents in the redhat source code.

    9. Re:The more the better by Anonymous Coward · · Score: 0

      You can't grep in the Redhat source code. It's not like running xargs on /usr/src the way you should be able to. In fact, most of these cruddy Linux OSes don't even ship with complete source. Only one of them seems to have a reasonable source-based system. The rest don't.

    10. Re:The more the better by Anonymous Coward · · Score: 0

      scared to try are we ? afraid you may find nothing ? redhat's source cd is available online from metalab if youre interested.

    11. Re:The more the better by Anonymous Coward · · Score: 0

      ahaha....that guy is a fucking fraud. for all we know, he didn't even get those results. he's probably typing them up manually. Besides, which regent is he talking about?

      It's probably Tom Christiansen's faggot ass anyway,

    12. Re:The more the better by Anonymous Coward · · Score: 0

      Don't be a stupid dick. All those programs given are BSD programs. Stop lying. Damned Winix zealots.

    13. Re:The more the better by Anonymous Coward · · Score: 0

      With linux-2.2.12

      $ find . -name '*.[ch]'|xargs grep -il 'copyright.*regents'
      ./include/linux/quota.h
      ./include/net/slhc_vj.h
      ./drivers/net/slhc.c
      ./drivers/net/slip.c
      ./drivers/net/ppp.c
      ./drivers/net/bsd_comp.c
      ./drivers/char/tpqic02.c
      $


      Some other things are BSD derived. Read the sources and stop bitchin'.

    14. Re:The more the better by Anonymous Coward · · Score: 0
      What a facile and deceitful response. Now grep the whole O/S, kernel babe. Not just /sys. For example:
      % cd /usr/src
      % ls -1F
      Makefile
      bin/
      distrib/
      etc/
      games/
      gnu/
      include/
      kerberosIV/
      lib/
      libexec/
      lkm/
      regress/
      sbin/
      share/
      sys/
      usr.bin/
      usr.sbin/
      Try looking there and get back to us.
    15. Re:The more the better by Anonymous Coward · · Score: 0

      Yeah what's not to love about the BSD games package it's probably all the multimedia games on this poor slob running BSD's system. Bwahahaha! Hunt the wumpus anyone?
      Oh here's all the kernel code Linux has from BSD all of it too ho hum for anyone to be even remotely interested in rewriting I suppose:

      /usr/src/linux-2.2.13/drivers/net/slip.c: printk("CSLIP: code copyright 1989 Regents of the University of California.\n");

      /usr/src/linux-2.2.13/drivers/net/slhc.c: printk(KERN_INFO "CSLIP: code copyright 1989 Regents of the University of California\n");
      Hmm SLIP I've read about SLIP never actually used it...

      /usr/src/linux-2.2.13/drivers/net/ppp.c: "TCP compression code copyright 1989 Regents of the "
      Yeah I used to use PPP used to...

      Face facts BSD gets more from Linux than we've gotten off of you in a long time. 1989 cutting edge baby! Hell half the BSD userbase has got to be elite clowns that started out running Linux and it quickly became not elite enough for them. You know the type.... Wanna start a shit throwing match better make sure ya got the ammo.

    16. Re:The more the better by Trailer+Trash · · Score: 1

      Linux is an OS kernel, and it is from scratch. Here's a hint, folks. man pages aren't part of the kernel, neither is anything is /usr/bin, or /bin/, or /sbin (see a pattern yet?).

      This is why Stallman notes that what we call "Linux" should be called "GNU/Linux", since an OS kernel is pretty much useless without the programs required to do something, minimally the C compiler.

    17. Re:The more the better by Anonymous Coward · · Score: 0

      Sophistry. Can't you lie more artfully? You just refuse to face the truth: that Linux is filled with BSD.

    18. Re:The more the better by Anonymous Coward · · Score: 0

      Stallman is on crack and you know it. We don't need glory hounds and prime donne like that. Makes you want to wash out your mouth just to have mentioned His Holy Name.

    19. Re:The more the better by kijiki · · Score: 1

      look, I'll try to make this simple for you. Linux is a kernel. The SLIP, PPP, and qic02 (yay) code is BSD derived.

      Lines of code in 2.2.13 (wc -l `find . -iname "*.[chS]"`):
      ...
      1927155 total

      Lines of code in files containing ANY BSD code (wc -l `find . -name "*.[chS]" | xargs grep -il 'copyright.*regents'`):
      ...
      11011 total

      Sooo.... ~ 0.5% of Linux is BSD derived. Did you have any other stupid claims you wanted shot down?

      (Note: This is ignoring the fact that non-BSD code was undoubtedly added to the 6 .c and 2 .h files that contain BSD code to integrate them into linux.)

    20. Re:The more the better by kijiki · · Score: 1

      oops, got a bit more I forgot to attach to that post:

      number of lines in the openbsd kernel (wc -l `find /usr/src/sys -name "*.[chsS]"`):
      ...
      1874216 total (and this includes non-working ports)

      number of GNU lines (wc -l `find /usr/src/sys/gnu -name "*.[chsS]"`):
      ...
      12004 total

      So OpenBSD (the only BSD I have locally, sorry Free and NetBSDers) contains ~ 0.6% of that EVIL, tainted GNU code. Which, in case you're up too late, is 0.1% more lines than BSDed lines in Linux.

      In other words, not only are the "Linux is full of BSD code" people idiots, at least OpenBSD contains some of that evil FSF/GNU code.

      Note: I run OpenBSD and Linux. I love OpenBSD and think Theo et al are doing a great job. I will not, however, let such foolish statements as "Linux is full of BSD code" pass uncommented. These idiots reflect poorly on the entire free software community, GPLed or BSDed. Please refrain from resorting to lies when advocating your platform of choice, if you insist on advocacy. It undermines your credibility.

    21. Re:The more the better by Anonymous Coward · · Score: 0

      You're not making much sense here. If Linux is stolen BSD code, and Linux's "kernel code quality is junk" then doesn't that mean BSD code is junk?

      Also, see the post in this thread with the proof that Linux is .5% BSD code (that'd be 1/200th of the code). There is more GNU code (by percent and by count) in OpenBSD than BSD code in Linux.

  4. Moderation this ARTICLE redundant by FascDot+Killed+My+Pr · · Score: 1

    This discussion is already being held right here
    ---

    --
    Linux MAPI Server!
    http://www.openone.com/software/MailOne/
    (Exchange Migration HOWTO coming soon)
    1. Re:Moderation this ARTICLE redundant by paul.dunne · · Score: 2

      Hah! Proof that complaining about Slashdot doesn't work: JonKatz will be right back after this short break...

  5. Oops. by abram_fettig · · Score: 0
    I meant "than" of course.

    Ok, I admit it, I was trying for a first post. So moderate me down to the very depths of the karma underground. I deserve it.

  6. popularity is a matter of opinion by Anonymous Coward · · Score: 0

    BSD rocks

    1. Re:popularity is a matter of opinion by Anonymous Coward · · Score: 0

      I think it is safe to say right now that Linux is more popular than all the BSDs put together. Preference is a matter of personal opinion general popularity isn't. Now this doen't make Linux more technically superior than any of the BSDs but it has it's advantages. User base is important to community. It was one of the driving reasons behind my initial choice between BSD and Linux when I had to make the choice myself. Today I'd still make the same choice. Penguin Powered!

    2. Re:popularity is a matter of opinion by Anonymous Coward · · Score: 0

      If Popularity is so important to you, why don't you use Windows?

    3. Re:popularity is a matter of opinion by Anonymous Coward · · Score: 0

      see "community". BSD lusers are elitest idiots.

    4. Re:popularity is a matter of opinion by Anonymous Coward · · Score: 0

      http://slashdot.org/comments.pl?sid=99/12/27/10620 7&cid=161
      Supports your point of view eh?

    5. Re:popularity is a matter of opinion by Anonymous Coward · · Score: 0

      BSD doesn't have lusers. It has programmers. Winix has lusers.

    6. Re:popularity is a matter of opinion by Anonymous Coward · · Score: 0

      Whereas you, I suppose, are truly 1337?

    7. Re:popularity is a matter of opinion by Anonymous Coward · · Score: 0

      Some logic for the "programmer"
      BSD Linux
      so if you use BSD you are Linux user.
      Linux users win BSD users lose!

    8. Re:popularity is a matter of opinion by Anonymous Coward · · Score: 0

      "If Popularity is so important to you, why don't you use Windows?"
      Hmmm well in making important decisions of a complex nature a number of factors usually must be considered and weighted. Both BSD and Linux can accomplish the same things. That is if I can configure it, or get the software. With Linux it's simply easier for me it's more visible. I'm not stupid after all. Or I wouldn't have properly weighted all of the factors and I would use Windows. The other AC nailed it "community" There is no Windows community that I am aware of. And the BSD community is just a bit too closely knit for my tastes. Still Penguin Powered!

  7. It seems fair enough by stimuli · · Score: 2
    Frankly I haven't crawled around in either Kernel to know which is superior, but I'm not about to accept any simplistic analysis that BSD is better than Linux, of visa-versa.

    What I am convinced of, however, is that the BSD's are each a solid piece of work, and each deserves as much attention as Linux has gained lately. It isn't that much work to write software that will run on the BSD's as well a Linux, and I think vendors should be encouraged to support them.

    In the end I'll probably keep using Linux, I'm comfortable with it, but I don't want that choice to be based on a lack vendor support for BSD -- we've all had enough of the "one supported OS" syndrome, let's not continue it.

  8. Interest and Effort by Foogle · · Score: 2
    Well other than the legal-issues that BSD had when they should have been becoming the prominent free OSes, there's the matter of interest, which is directly tied to effort.

    More people are interested in Linux simply because more people are interested in Linux. It's sort of like a rolling ball of snow; Linux is collecting more people as it goes. So are the BSDs but they are a little behind right now.

    -----------

    "You can't shake the Devil's hand and say you're only kidding."

    1. Re:Interest and Effort by Cramer · · Score: 1

      That's not really true. People like the openness of Linux... any idiot can mess about with the kernel, discuss messing about with the kernel, and submit patches and/or new stuff for the main kernel. FreeBSD is a rather closed environment. Of course, these are both good and bad things.

      Compared to Linux, BSD is alot harder to install and always has been. Can you install FreeBSD with only a floppy and a net connection?

    2. Re:Interest and Effort by Anonymous Coward · · Score: 0
      Compared to Linux, BSD is alot harder to install and always has been.
      Says you. I find Open/BSD quite easy to install, and Redhat hard/annoying.

      Can you install FreeBSD with only a floppy and a net connection?
      I don't know about Free/BSD, but I put Open/BSD on both a Sparc and an Intel laptop that way.
    3. Re:Interest and Effort by Anonymous Coward · · Score: 0

      This is FUD. BSD is just as open as Linux. More so, usually, since a lot of Linuxes don't have source with them.

    4. Re:Interest and Effort by davet · · Score: 1

      "Can you install FreeBSD with only a floppy and a net connection?"

      Yes, you can. As a matter of fact, I've installed FreeBSD this way on my laptop, which only supports USB peripherials and has a single PCMCIA slot, occupied by the network card. So FreeBSD booted off a USB floppy drive, something I haven't been able to do with any Linux distribution I've encountered.

    5. Re:Interest and Effort by Cramer · · Score: 1

      The boot loader uses the BIOS interface to the floppy. As long as you only need the boot floppy for the initial kernel and ramdisk (assuming the ramdisk is loaded by the boot loader), everything should work ok. Two of my machines have LS-120's so I've got the same problem -- once the kernel takes over, the "floppy" is gone (win98's the only thing that hasn't cared so far.)

      Not that I like Redhat, but have you tried this with RH6.1? (boot from floppy and install from a CD? I think that's the only one that won't ask for the other floppy.)

    6. Re:Interest and Effort by Anonymous Coward · · Score: 0

      >Can you install FreeBSD with only a floppy and a net connection?

      I'm assuming you didn't know that FreeBSD coudl do this long before any linux distro did.

    7. Re:Interest and Effort by Anonymous Coward · · Score: 0
      >Can you install FreeBSD with only a floppy and a net connection?

      I'm assuming you didn't know that FreeBSD coudl do this long before any linux distro did.

      Thanks for the demythification.
    8. Re:Interest and Effort by Lazaru5 · · Score: 1

      These are VERY irresponsible comments.

      If you don't know that you CAN do a net install with *BSD, then I would say you're not terribly experienced with their installation process at all and you're not really in a possition to say whether or not they're harder to install.

      As for FreeBSD being closed, that is also not from first hand experience, but from misinformation propogated on this and other forums.

      Want to mess with the kernel? It's in /usr/src/sys. Want to discuss it? `echo "subscribe freebsd-hackers" | mail majordomo@freebsd.org` or check out comp.unix.bsd.freebsd.misc. Want to submit patches/additions? `/usr/bin/send-pr` or use the web interface at http://www.FreeBSD.org/send-pr.html


      People will read your lies and believe them. Please be more cautious.

      --

      --
      My comments and opinions completely reflect those of anyone and anything I am remotely associated with.
    9. Re:Interest and Effort by Anonymous Coward · · Score: 0

      FreeBSD is not a rather closed environment. It may be more organized but it is still open to even the newest people.

    10. Re:Interest and Effort by Anonymous Coward · · Score: 0

      It's considerably easier to perform an NFS install of NetBSD on a laptop with a single floppy than with any version of Linux.

      The PCMCIA ethernet drivers are built into the kernel. Not a bolted-on kludge as they are with Linux.

    11. Re:Interest and Effort by Anonymous Coward · · Score: 0

      What you talking about?

      Name one Linux Distribution that doesn't provide the source code? You can't because they all do. All Linux Distributions abide by the conditions of the GPL. Most distributions don't provide the source because they only give a single CDROM and all the applications completely fill up the CDROM. But even these all give the source code for the Linux Kernel itself.

      And BSD is not as open. Anyone can fork off a secret branch of BSD code at anytime and modify it without releasing their code changes back. I would rather not work for a company for free without being compensated with bug fixes for my code. This also fragments BSD into hundreds of existing OSes, none exactly compatible with the others. This is a support nightmare.

      Give me the GPL anyday. I do work on Linux and a company then improves my work, they have to give the changes back to me. Hey, I provided the base for free, it is only fair that they give back the tiny changes that they made for free as well. This is the reason that their is only one Linux source tree.

      Even if someone did branch off a new Linux source tree their good ideas would merely be absorbed back into the main tree within just a few months. This guarantees that a company like Microsoft can't take Linux, make a bunch of proprietary changes and not release the source for those changes to the rest of us.

      Can BSD say the same? Isn't this the reason that BSD has 5 or 6 main free versions right now? And by the way, MS is very interested in BSD right now. Get ready to be embrased and extended.

    12. Re:Interest and Effort by Anonymous Coward · · Score: 0
      Man, you are so confused. Show me a single Linux system that you can say "make world" or its equivalent on.

      And BSD is far more open and free than Linux, for reasons you don't seem to understand.

      Finally, BSD is much less fragmented than Linux. Linux has a 100 incarnations. By contrast, there are only a few BSD OSes.

    13. Re:Interest and Effort by Anonymous Coward · · Score: 0

      No Linux operating system comes with source installed. And even if you get it, it's that insane fucking RPM crap. Give me /usr/src and makefiles any day.

    14. Re:Interest and Effort by Anonymous Coward · · Score: 0

      Hey kid, you're repeating all the standard anti-BSD FUD that the screaming fanatics always rant about. This has all been soundly and thoroughly disputed. Do your own research about why you're massively fucked in the head. Don't waste our time with duplicate nutsinesses. We've heard it all before. It was wrong ten years ago, and it's wrong today.

    15. Re:Interest and Effort by Cramer · · Score: 1

      Redhat (assuming you have a few spare gigs of HD for all the source)...

      rpm --rebuild


      REBUILD AND RECOMPILE OPTIONS
      There are two other ways to invoke rpm:

      rpm --recompile +

      rpm --rebuild +

      When invoked this way, rpm installs the named source pack-
      age, and does a prep, compile and install. In addition,
      --rebuild builds a new binary package. When the build has
      completed, the build directory is removed (as in --clean)
      and the the sources and spec file for the package are
      removed.

    16. Re:Interest and Effort by Cramer · · Score: 1

      Actually, that "fucking RPM crap" just wraps up the original source tarball and all the bugs^Wchanges done by Redhat (etc.)

      The RPM crap is mostly a Redhat-ism. Other dists have started using it, but some don't. As I recall, slackware is all tarballs and yes, you can do a "make world"-ish rebuild everything.

      This begs the question, "why would you want to?" How often do you have the need to rebuild everything on your hard drive?

    17. Re:Interest and Effort by Cramer · · Score: 1

      All I can say is the first linux system I installed back in '91 was from a single floppy download. It ftp'ed everything it needed to install and went on it's merry way.

      If this is true, why isn't it documented somewhere obvious?

    18. Re:Interest and Effort by Anonymous Coward · · Score: 0
      Redhat (assuming you have a few spare gigs of HD for all the source)...
      Isn't "HD" some peecee term for space on a filesystem? Couldn't be please dispense with babytalk?

      Anyway, I can't imagine needing a few gigs to have the source loaded. That's insane. Open/BSD is only 300 megs, including the kernel? Is Redhat/Linux really that bloated?

      As for your rpm stuff, is that really the whole system, or do you have to specify packages? And why isn't this in the makefile where it belongs? You shouldn't ever have to do anything besides just typing make.

    19. Re:Interest and Effort by Anonymous Coward · · Score: 0

      `hard drive'? Icky poo-poo!

    20. Re:Interest and Effort by Anonymous Coward · · Score: 0

      Because I expect to cd to /usr/src/DIR/proggie and fine the source. I expect to type make to get it built, and make install to put it in its place.

    21. Re:Interest and Effort by Cramer · · Score: 1

      Couldn't be please dispense with babytalk?
      no.

      Yes, it's insane. However, seeing as the netscape source code is 127M!... If one installs everything on the Redhat 6.1 x86 CD, you'd lose about 1.3GB. I've never installed the entire source code, but I'm venturing a guess that it'd be around 4x that size. The Linux kernel is an enormous snowball of code -- there's what, nine arch's in the tarball? Glibc... I'm not gonna go there. [I'll give it a go tonight if the AccelRAID 150 doesn't lock up again #$%@$]

      As for "just type make"... nothing is ever that simple. Someone/thing has to install the source code first. "rpm --rebuild" isn't that much different, but it is a redhat-ism. As it was explained to me a year ago, the FreeBSD "make world" will download the missing source code (via cvs.)

      But this still doesn't answer my previous question: Why would you want to rebuild your entire distribution?

    22. Re:Interest and Effort by Anonymous Coward · · Score: 0

      That's insane. RedHat needs to go on a diet. Are there any other Linuces that aren't such behemoths? No wonder Redhat's O/S is clumsy and non-integrated. I'll never say anything nasty about the immensity of Microsoft again.

    23. Re:Interest and Effort by Anonymous Coward · · Score: 0

      Slackware and Debian can both be as small or as comprehensive (read HUGE) as you want them to be. RedHat can too, to a lesser extent, if you choose "choose packages to install."

    24. Re:Interest and Effort by Anonymous Coward · · Score: 0

      I know that its hard for you, since you can't code ,to contribute to the community, but inane and content free posts like this one contribute nothing.

      Please shut up unless you (unlikely) actually have something to add.

    25. Re:Interest and Effort by Anonymous Coward · · Score: 0

      The Linux kernel is an enormous snowball of code -- there's what, nine arch's in the tarball?

      Curious that Red Hat Linux apparently provides kernel sources for nine architectures when it only runs on three (x86, Alpha, SPARC). Quite stupid, if you ask me. Is it really all in a single tarball, forcing code for six unsupported architectures onto the poor sods running it?

    26. Re:Interest and Effort by Anonymous Coward · · Score: 0

      just use the PCMCIA bootdisk for your distro.

      Uninformed, counterfactual arguements like that one don't do anything to advance your point.

    27. Re:Interest and Effort by Anonymous Coward · · Score: 0

      I like to keep my source tree up to date. I also like binaries which match my source tree, and which have been optimised for the system they're running on.

      It's actually easier, in my view, to type `make world' than it is to dig through the logs and rebuild everything that's changed (especially if one of the development tools, e.g. the compiler, has changed, which could necessitate rebuilding everything anyway).

  9. Only 10 million Linux users by Anonymous Coward · · Score: 0

    that seems a bit on the low side now. Maybe 18-24 months ago that was about right, but now ? Where are the most accurate+up to dates figures.

    1. Re:Only 10 million Linux users by Anonymous Coward · · Score: 0

      For one of the fastest growing platforms on the surface of the Earth Linux has had about 10 million users for about 2 years now. Then again it's impossible to track Linux users really. When a magazine comes out in India with Linux bundled with the publication who knows how many people install and run the OS? Or when one guy in Brazil downloads an ISO and burns a CD. Didn't Mexico's school system switch to Linux? They probably did it with one CD heh. On the flipside I download new releases fairly often, but I'm only one user. I think I have bought Linux on CD maybe 4 times and downloaded it 3 times. Doesn't make me 7 users though. Although I do have 3 systems that run Linux. Hmmm.... As you can see we'll simply never know how many people or how many systems Linux is on. Remember it takes about 5 minutes to change the OS on a system (evil grin) World domination started out as a joke, at some point everyone will stop laughing.

    2. Re:Only 10 million Linux users by Anonymous Coward · · Score: 0

      If you're lucky. That number is so grossly over inflated it's makes me sick. 5-6 million tops. And that is HUGE difference. I think they count every end table coaster (linux CD) they give away at COMDEX and with gamer magazines. Sorry, just because you gave a CD away, doesn't mean that anyone installed anything.

      Linux ranks so far behind MacOS and Windows in installed base it's laughable. They are about even with OS/2...maybe...

    3. Re:Only 10 million Linux users by MinusOne · · Score: 1

      > Linux ranks so far behind MacOS and Windows in installed base it's laughable. They are about even with OS/2...maybe...

      Perhaps you could bother to provide some evidence for this opinion? I have no clue how many Linux users there actually are, but I could pick numbers out of the air just as easily as you or anyone else. Until I find some solid number backed by reasonable research, I'll keep my mouth shut. I *believe* the number must be more than 10 million, but I can't back it up any more than any else can their guess.

    4. Re:Only 10 million Linux users by Anonymous Coward · · Score: 0

      One way to see how much each OS is really being used is to look at the OS stats on distributed.net.

  10. Follow the Money by mr · · Score: 4

    There is no billion dollar IPO backing the hype about BSD.

    The hype will come when:
    1) There is a billion dollar BSD IPO.
    2) When the BSD community starts explaining the biggest advantage of the BSD licence to Multinational corporations. That advantage is, you can choose to HIDE your own source code if you wish. (Get them to at least start supporting OpenSource. Once they find its not as bad as Microsoft says, they will keep coming back for more. Like drugs...the first hit, we'll give ya free.)
    3) Some cleaver BSDers (Hi Pat!) start whispering in Wall Streets ears "Feel that you mised out on the Linux IPO frenzy? Take heart, here is BSD...the next big IPO launchpad. It runs Linux binaries, its OpenSourced, AND the licencing difference over Linux doesn't cause the heads of the lawyers in your IP departments to spin about."

    When the first IPO of BSD is successful, then you will see the people who use Linux instead of the word OpenSource, refer to BSD as OpenSource...and Linux also. And, the more OpenSource is out there, the better for BSD, Linux, Apache, Sendmail, vi,
    NO CARRIER

    --
    If it was said on slashdot, it MUST be true!
    1. Re:Follow the Money by Anonymous Coward · · Score: 1
      That advantage is, you can choose to HIDE your own source code if you wish. (Get them to at least start supporting OpenSource. Once they find its not as bad as Microsoft says, they will keep coming back for more. Like drugs...the first hit, we'll give ya free.)

      This is a definition of "supporting" with which I was previously unfamiliar. After you've been subsidizing their proprietary products, how do you get them to free their software. You can't just stop; there will always be more unpaid employees out there eager to "help"...

    2. Re:Follow the Money by mr · · Score: 1

      Take some time to examine the history of Apple and Rhapsody.

      Note how Apple (one of the most closed companines in existance due to thier past with Apple ][ cloning) has submitted bug fixes to BSD. Note also how Apple had no intention of OpenSourcing the code now called Darwin, and yet here we are today....with even Apple SUPPORTING OpenSource.

      Also note, how the BSD code writer considers SUPPORT of the code as USE of the code.

      If you can't grok the above views of support, perhaps you need to think different?!?

      --
      If it was said on slashdot, it MUST be true!
    3. Re:Follow the Money by Thomas+Charron · · Score: 2

      Linux was successfull *LONG* before the market hype. I hope that's not what you're basing your argument on as to why Linux is more popular then BSD.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    4. Re:Follow the Money by JordanH · · Score: 2
      • The hype will come when:

        1) There is a billion dollar BSD IPO.

      Uhhmmmm... billion dollar IPOs are a result of hype, not the cause of it...

      Seems like you're getting the cart before the horse.


      -Jordan Henderson

    5. Re:Follow the Money by JordanH · · Score: 2
      • 3) Some cleaver BSDers (Hi Pat!)

      That Pat must be a pretty sharp fellow!


      -Jordan Henderson

    6. Re:Follow the Money by sklein · · Score: 1

      There is no billion dollar IPO backing the hype about BSD.

      Uhh, looks like the hype backs the IPO. I know the hype certainly came first. It was there when I started using Linux well before the first IPO. You may not have known about it, but it was there.

      cheers,
      sklein

    7. Re:Follow the Money by Anonymous Coward · · Score: 0

      Based on the metric you seem to be using:

      BSD code is what Sun used to build its business.
      BSD code is used in Linux, from the kernel to the application space.
      BSD code has driven the Internet. (Sendmail as an example)

      As BSD is core to Linux, Sun, and the InterNet, it looks like BSD was a win LONG before Minix was a twinkle in Linus's eyes.

    8. Re:Follow the Money by Anonymous Coward · · Score: 0

      OK, I'll follow your logic. Why don't we go further back then? Just because something is a founding stone, that doesn't mean it will be popular or stay popular. Yes, in the grand scope of things, BSD has meant more to computing then Linux. Heck, BSD is easily as important, if not moreso then RMS and the GNU (remember, without free compilers and what not, modern BSD's wouldn't be much, and Linux wouldn't exist).

      So what's my point? BSD is important. No denying or disputing that. And who really CARES if it's Linux that holds the limelight right now. Linux got there on its technical merits, and if there's ever a need for something else, BSD will be it. The fact that BSD isn't superpopular doesn't mean squat, and certainly doesn't mean it 'sucks' or anything. It's different, and good.

      And on the argument of BSD users vs. Linux users, I'm just going to say that most people who use either are in no position to have a qualified opinion. Hence, both BSD and Linux lusers sucks. No worries.

    9. Re:Follow the Money by MasterMnd · · Score: 1

      I think you've got that kind of backwards.. There will be a billion dollar BSD IPO AFTER the hype takes off.. the only reason linux companies are doing so well is because linux is getting popular, not the other way around...

    10. Re:Follow the Money by mr · · Score: 1

      Popular is when my parents and grandparents ask "What is Linux?"

      That happened AFTER the billion dollar IPO. Not before. I don't have it backwards.

      Things like a billion+ help your popularity. Being popular because you have a billion+ isn't the best reason to be popular, but its still a reason for popularity.

      --
      If it was said on slashdot, it MUST be true!
    11. Re:Follow the Money by JordanH · · Score: 1
      • Popular is when my parents and grandparents ask "What is Linux?"

      Well, this says a lot about your parents and grandparents, but not much about the populace at large. I guess all those investors that made the billion+ $ IPOs were completely in the dark about Linux.

      What a crazy stock market. People are pushing prices up to 10 and 20 times initial offer and they've never heard of what it is the company is doing.

      A certain level of "popularity" is necessary before investors are attracted to something. Sure, there's a feeding frenzy effect caused by this, which makes it even more popular, but you have to have a certain mindshare to make it possible.


      -Jordan Henderson

    12. Re:Follow the Money by mr · · Score: 1

      The investment style is called momentum investing. This style has NOTHING to do with what the company actually does. What you try to do is jump on the same bandwagon as everyone else.

      It comes from the concept of technical analysis. You don't care what the company does, only how it has performed.

      As for the parents/grandparents crack, the majority of the population doesn't have computers. (Unlike the readers of /.) So the majority don't GIVE A DAMN about this site, Linux or OpenSource.
      And for most brokers, OpenSource is as remote to them as biotechnology, sub-micron lithography, or FPGA's. The people who are analysts care, but your average broker doesn't. The people who read the analyst don't grok the technology, just what the analyst says.

      Again, the MAJORITY of investors read what some analyst says. Look at what you have read about OpenSource or Linux or BSD in the 'mainstream' and ask yourself: Do these 'experts' understand?

      From the Fool
      message board: VA Linux
      date: 12/09/1999 author: gliptak
      I heard this IPO was cancelled, as the underwriters did not anticipate enough interest
      [VA Linux IPO wasn't canceled]

      message board: VA Linux
      date: 12/10/1999 author: JeanDavid
      In the Linux market, the biggest two databases are probably MySQL and Oracle.
      [And PostgreSQL was voted #1 database, with MySQL as #2. Lack of facts (again)]

      That is 2 pages in.

      I'd post some of the tech analysts from the broker, but:

      1) I don't have them at hand
      2) Posting facts on /. Is rather useless....especially if it conflicts with Linux-based religious zelotry.


      --
      If it was said on slashdot, it MUST be true!
    13. Re:Follow the Money by Anonymous Coward · · Score: 0
      Look at what you have read about OpenSource or Linux or BSD in the ?mainstream? and ask yourself: Do these ?experts? understand?
      I hope you don't expect us to take seriously a troll who makes illegal posts using MS-HTML.
    14. Re:Follow the Money by Anonymous Coward · · Score: 0

      Oh, you can't refute the posts with FACTS so lets use an ad-homnem attack.

      (and people wonder why GNU/Linux and /. have a rep as a bunch of childern.)

    15. Re:Follow the Money by Anonymous Coward · · Score: 0

      It's only the GNU/Linux freaks from the Richard M. (M's for Mafia!) Stallman hit squad are children. Regular Linux people are ok.

    16. Re:Follow the Money by JordanH · · Score: 1
      • Oh, you can't refute the posts with FACTS so lets use an ad-homnem attack.

      It's not exactly a post that can be refuted by facts. The poster has one definition of "popular" that doesn't yield to argument.

      I think something is popular when it attracts a lot of investor interest and thus the Billion $ IPOs.

      The poster feels it's not popular until somebody's relatives are asking about it.

      It's a semantic argument with no authority to decide it.

      As for Ad Hominems it was the poster - mr - who bitterly complained about the Slashdot posters as being religious zealots who don't listen to facts.


      -Jordan Henderson

    17. Re:Follow the Money by Thomas+Charron · · Score: 2

      And, by the same token, CP/M was a win long before BSD was ever dreamt of.. ;-P

      I was merely stating that Linux is currently more popular then BSD, and this popularity is NOT based on marketing hype..

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    18. Re:Follow the Money by Anonymous Coward · · Score: 0

      No, it's not based on hype. It's based on ignorance.

    19. Re:Follow the Money by Thomas+Charron · · Score: 1

      Please expand on this. How is the popularity of Linux based on ignorance??

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    20. Re:Follow the Money by Anonymous Coward · · Score: 0

      > When the BSD community starts explaining the biggest advantage of the BSD licence to
      > Multinational corporations. That advantage is, you can choose to HIDE your own source code if you
      > wish.

      Only one problem: just because the people who contribute code to today's BSDs _allow_ closed-source derivatives does not necessarily mean that they _support_ them.

      Corporations that come to BSD expecting a free handout and nothing else will be disappointed. They aren't going to get free help unless they give something back in return.

    21. Re:Follow the Money by Anonymous Coward · · Score: 0

      Its nice to see Amiga Persecution Complex is alive and well in the BSD camp.

      Hopefully that doesn't mean that BSDs fate will be the same as the amiga's. I don't know what I would do without OpenBSD.

  11. Mostly cause BSD is harder to say than Linux by WillAffleck · · Score: 1

    I think it also has something to with the name. Maybe not for the serious amongst us, but I remember some of the reactions against unpopular languages were driven by how hard it was to say the name, in the past. Even if we can't agree on how to pronounce Linux, it still is easy to say. BSD, on the other hand, is very staccatto and doesn't roll trippingly off the tongue on the way to Piccadilly.

    --
    Will in Seattle
    1. Re:Mostly cause BSD is harder to say than Linux by heh2k · · Score: 1

      say "beast-dy", not "bee-es-dee"

    2. Re:Mostly cause BSD is harder to say than Linux by WillAffleck · · Score: 2

      A nice theory, but people don't. Linux is normally pronounced by the great unwashed with two syllables, although Europeans tend to pronounce it differently than Americans. BSD, three syllables. Just like the Net is one syllable (three in French, but at least it's shorter than most words).

      Spiff it up, give it a new name, a plush toy that won't poke kid's eyes out, and you've got marketing acceptance. Stick to the computerese and it loses points.

      Sigh.

      People frequently mistake my descriptions of reality for my personal opinion as to How Things Should Be - this is what I'm saying, not What Should Be.

      --
      Will in Seattle
  12. Big fallacy alert by Anonymous Coward · · Score: 0

    BSD not as popular as Linux? The script kiddies might prefer Linux, but for most mission critical systems BSD is the better choice.

    1. Re:Big fallacy alert by Anonymous Coward · · Score: 0

      mission critical this : http://kt.linuxcare.com/kt19991220_47.html#1 up your arse. see why BSD isnt as stable as its hyped to be.

    2. Re:Big fallacy alert by shlong · · Score: 1

      If you would have read the entire article, you would have seen that Linus eventually reversed his position and agreed that the optimization (used in FreeBSD) was safe and correct. Man, I really want to turn on the flame switch when I read uneducated posts like yours. You make a perfect example of the reason that Linux is slowly gaining a black eye in the enterprise world.

      --
      Cat, the other, tastier white meat.
    3. Re:Big fallacy alert by Infidel+IV · · Score: 1
      So because it was suggested on the FreeBSD list (as it apparently was on the Linux lists) FreeBSD is more unstable?

      Did this optimization even go into the FreeBSD source tree? (It's not in my system anyway, just checked)

    4. Re:Big fallacy alert by shlong · · Score: 1

      Yeah, it went in around early December. Only on -current though (which is where experimental stuff is supposed to go).

      --
      Cat, the other, tastier white meat.
    5. Re:Big fallacy alert by Anonymous Coward · · Score: 0

      you idiot. he didnt. read the *whole* thing specially the last part.

  13. better luck w/ bsd, for now. by pope+nihil · · Score: 1

    my brother couldn't get a shiny clean install of redhat 6.1 to work properly, so i suggested he load the latest from OpenBSD (2.6). it properly detected and configured all of the devices. now he's happy about it 'cuz he gets to finally ditch M$.

    unfortunately, there's nothing to prevent an Evil Empire (TM) from making proprietary changes to *BSD and selling, for instance, M$ BSD. the ability of proprietary companies to embrace and extinguish is what really scares me.

    1. Re:better luck w/ bsd, for now. by Anonymous Coward · · Score: 0

      Let them!!!!! I for one would be over joyed if
      M$ decided to really do unix.

      But ummmm .... Im not holding my breath

    2. Re:better luck w/ bsd, for now. by Anonymous Coward · · Score: 0
      unfortunately, there's nothing to prevent an Evil Empire (TM) from making proprietary changes to *BSD and selling, for instance, M$ BSD. the ability of proprietary companies to embrace and extinguish is what really scares me.

      I think that their contract with SCO would prevent them from doing that

    3. Re:better luck w/ bsd, for now. by Anonymous Coward · · Score: 0
      I think that their contract with SCO would prevent them from doing that
      Wrong. BSD doesn't carry the "UNIX(tm)" imprimature; it's just got the Unix API. Anyway, the Bill doesn't care about contracts. He'd make it work if he cared.
    4. Re:better luck w/ bsd, for now. by Anonymous Coward · · Score: 0
      there's nothing to prevent an Evil Empire (TM) from making proprietary changes to *BSD and selling, for instance, M$ BSD. I
      So what? There's nothing wrong with that.

      I hope you realize there's nothing stopping the evil one from creating their own MS-Linux distro, too.

    5. Re:better luck w/ bsd, for now. by Anonymous Coward · · Score: 0

      They already have , doesent anyone remember ?

    6. Re:better luck w/ bsd, for now. by Anonymous Coward · · Score: 0

      The microsoft/SCO contract has nothing to do with the Unix trademark, please restrain yourselfs to comment only on issues you have some knowledge about

  14. Two factors by Bruce+Perens · · Score: 5
    I like the BSD system and might even do some commercial things with it. So please don't take this as anti-BSD propoganda.

    1. Time. BSD was held back by the ATT lawsuit and Linux already had so much mindshare when that was over.

    2. The BSD license doesn't enforce the quid-pro-quo. This is a real sticking point for me personally. When I put a lot of work into something, I like to be a partner in a free software development, not someone's unpaid employee dupe. But I feel like a dupe when somebody takes that work private, makes proprietary modifications to my work and doesn't return their modifications to me or the other free software authors who gave him our work.

    Unfortunately, history shows that without a license requirement the return of code doesn't happen. Most of the workstation Unix systems are BSD-derived (although these days there is more System V in there) and all of their X servers are derived from software under a very similar license to the BSD. Try to get the source code for those systems. Sun only released its modifications to the BSD system recently, 10 years late, and then under a license that would not allow their reincorporation into the BSD system as free software! Most other workstation manufacturers didn't bother to release source at all.

    So, I am more likely to put work into a GPL project. It is possible to take the BSD system and GPL it. The new BSD license and the GPL are compatible, and you can GPL all new work that you do, and in general establish a GPL source thread. But that would annoy a lot of the long-time BSD folks.

    Thanks

    Bruce

    1. Re:Two factors by nickm · · Score: 2

      The real reason is that BSD is an acronym, while Linux is a bit of a play-on-words.
      People find acronyms inscrutible. Imagine if RMS had not named it POSIX, and the original "IEEEIX" name was chosen.
      --
      I noticed

      --

      --
      I noticed

      It's getting about time to leave everywhere

    2. Re:Two factors by Anonymous Coward · · Score: 0

      "Annoy" is putting it mildly. Expect to get roundly flamed. The unwritten rule of the BSDL seems to be "you can make a proprietary version, but not a GPL'd version", which doesn't even make sense if they think GPL'd code isn't Free. They seem to resent the fairness we insist on. Perhaps they're trolling for work from naive coders they can take proprietary (since the profession is currently so broken as to reward that behavior).

    3. Re:Two factors by bvmcg · · Score: 2
      Sun only released its modifications to the BSD system recently, 10 years late, and then under a license that would not allow their reincorporation into the BSD system as free software! Most other workstation manufacturers didn't bother to release source at all.

      This is disgusting to read. It was nearly ten years ago that Scott McNealy, president/CEO of Sun Microsystems, spent a full half hour radio broadcast of the Commonwealth Club meeting beating on the government. The reason? He was insisting that it was ludicrous and short-sighted to spend money on closed systems. He further insisted that it shouldn't even be allowed, pushing a move such as the one the government of Brazil may enact.

    4. Re:Two factors by Bruce+Perens · · Score: 1
      I just don't buy that. I think the users are following developer mind-share, and Linux still has more of that, and the developers simply don't care if it has a marketable name or not.

      By the way, I started running 4BSD in the early 80's, so I'm no stranger to it. I got to NYIT computer graphics lab in 1981, we had one of the first VAXes to get out of DEC (it's the one in Soul of a New Machine) and ran Unix 32V (ATT VAX Unix, I think with no virtual memory) until we got 4BSD. We also had Version 6 Unix on PDP-11 systems. The lab had a V6 paint system application called Images that they never ported to V7. I finally ported 2.8 BSD to the V6 binary API to support that application.

      Bruce

    5. Re:Two factors by cjs · · Score: 2

      You can expect to get flamed if you ask one of the current BSDs to switch to the GPL; you won't get flamed if you simply fork off your own and GPL it (or, rather, GPL the bits that don't have a clause 3 in the licence; UCB is only one of hundreds of contributors to the kernel code).

      As for `resent[ing] the fairness [you] insist on,' well, yes, because a) it's certainly not fair to anyone who wants to incorporate ten lines of GPL'd code into ten thousand of his own, b) I don't believe it's fair to anyone to tell him what he can do with the code he writes, which is what the GPL does, and c) the FUD that Linux folks love to spread about how all non-GPL'd software is being taken proprietary and disappearing forever from public view is getting a bit old.

      cjs

      --
      The world's most portable OS: http://www.netbsd.org.
    6. Re:Two factors by Anonymous Coward · · Score: 0

      Did he mean closed source (AFAIK Solaris still hasn't been freed) or just non-interoperable?

    7. Re:Two factors by evilpenguin · · Score: 3

      Open systems and Open source are not the same thing. McNealy has always advocated Open systems (meaning systems based on open standards), but he never went so far as to say that companies should give away their source code or the right to modify it and give it away modified.

      McNealy was ahead of the curve on networking and open standards, but he is very much behind the curve on Open source. He was truly commited to "open" he would not have withdrawn Java from the standards process. He still wants control. He hasn't picked up that last piece of the puzzle...

      Don't be disgusted. McNealy does not embrace Open source.

      To me, there's a heirarchy of technology worlds I want to work in:

      1) Open source -- the software is free, programmers are not.

      2) Open systems -- the standards are free, the software is not, and programmers are the drudges of the business world.

      3) Proprietary systems -- there are only de facto standards, software is expensive, and programmers are serfs of the dominant technology company. This was IBM in the past. This is Microsoft today.

      McNealy had the vision to aim at level 2. In the early 80's, this was radical indeed. He has not figured out the advantages of level 1. He's partway there, but he has missed the last step -- that the code belongs to the world, not to the originator. That assurance, that the code is yours, that the benefit you get for giving away your mods is the absolute assurance that anyone else who improves it must share his/her mods with you is the payment you receive for giving away your mods. It works. McNealy doesn't see this yet. He thinks programmers will give their mods to him, with no assurance that Sun's further improvements will go back to those programmers. The Sun version is a one way street.

      No, I do not weep for Scott McNealy.

    8. Re:Two factors by Anonymous Coward · · Score: 0
      Unfortunately, history shows that without a license requirement the return of code doesn't happen.
      Patently false and demonstrably so via a trivial existence proof: The BSD distros are full of code.
    9. Re:Two factors by Bruce+Perens · · Score: 2
      Right. Remember that Open Systems != Open Source. People still get them confused. Open Systems means the API is documented and someone else can program to the system or application side of that API. It says nothing about the actual software being free or open, generally it's proprietary.

      One influential person I know still thinks that Open Source is a subset of the field of Open Systems, and we are constantly in argument about this because I think that Open Source means so much more, and he thinks I am not seeing the forest for the trees.

      Thanks

      Bruce

    10. Re:Two factors by Anonymous Coward · · Score: 0

      [a] then he should write his own
      [b] the authors decision was to release under the GPL not your concept of fairness
      [c] its true - quit whining.

    11. Re:Two factors by Anonymous Coward · · Score: 0

      Yoour misrepresenting this matter. It's not that BSD doesn't expect the same fairness. That's an artful deception. BSD doesn't expect anyone to be forced into their own mold. Their is no coercion. It is a far fairer, more moral approach than what YOU think is fair. There's a hell of a difference between "do unto others as you would have them do unto you" and "make others do unto you what you want them to".

    12. Re:Two factors by Anonymous Coward · · Score: 1
      you won't get flamed if you simply fork off your own and GPL it

      Check an archive of gnu.misc.discuss; I'll dig up a reference if I have time. Some BSD authors go ballistic if you do this. I guess if you're publishing but not under the BSDL they'd just rather not know about it.

      a) it's certainly not fair to anyone who wants to incorporate ten lines of GPL'd code into ten thousand of his own,

      Sure it is. The only reason he has my code is that I get his in return, otherwise why would I publish it?

      c) the FUD that Linux folks love to spread about how all non-GPL'd software is being taken proprietary and disappearing forever from public view is getting a bit old.

      Are you arguing this doesn't really happen, or just that we shouldn't object to good work being abused to subsidize more proprietary crap we have to cope with?

    13. Re:Two factors by Bruce+Perens · · Score: 2
      Well, I'm assuming they will eventually release it under the SCSL. Fold that back into your BSD work. Ugh.

      Thanks

      Bruce

    14. Re:Two factors by Andy · · Score: 1

      Both true. BSD is great software but it failed to attract a fanatical developer base like lignux because of the aristocratic development model they employ. Lignux inspires orders of magnitude more contributers. This certainly has its negative side -- lignux does not have a reputation for being a scupulously clean design.

    15. Re:Two factors by Anonymous Coward · · Score: 0

      oops, meant viral. The GPL is indeed virile, unlike Tom's faggot ass. Fuck you Tom.

    16. Re:Two factors by Anonymous Coward · · Score: 0

      IMHO anything you have the source for (not even having Open-Source-like rights to modify, just being able to read it is sufficient) is inherently an Open System. Though Open Source certainly has loftier goals, if that's what he's disregarding.

    17. Re:Two factors by Anonymous Coward · · Score: 0

      "lignux" is a great way to start a flamewar. Please stop trolling. Without BSD, you wouldn't even have a Linux. Call it Linux, or call it BSD/Linux, but keep the flaming religious zealots and their communist antibusiness unrelenting "our way or nothing" attitude out of here.

    18. Re:Two factors by _Sprocket_ · · Score: 1

      Heh. No flame bait to be found here either. :P

    19. Re:Two factors by Anonymous Coward · · Score: 0

      IMHO there's nothing moral about aiding and abetting organizations who have ripped off their customers and all but eliminated progress in my profession. Where does "refuse to help others do what you don't want them to" fit into your worldview? I give them source, they give me nothing- how can that ever be fair?

    20. Re:Two factors by Guy+Harris · · Score: 2
      [c] its true - quit whining

      What is "true"? The claim that "all non-GPL'd software is being taken proprietary and disappearing forever from public view", as per the statement of the person to whom you're responding:

      the FUD that Linux folks love to spread about how all non-GPL'd software is being taken proprietary and disappearing forever from public view is getting a bit old.

      or the claim that said noise is, in fact, getting a bit old?

      If you're asserting that the first claim is "true", then this is a use of "true" to which I was previously unacquainted; the use of "true" with which I'm familiar has connotations such as "in accordance with reality". It is NOT true that "all non-GPL'd software is being taken proprietary and disappearing forever from public view" (unless this is a use of "all" with which I was previously unacquainted, e.g. "all" meaning "some"); the code to FreeBSD, OpenBSD, NetBSD, and X11 are not "proprietary", and are still in public view. Proprietary derivatives of said code have been made, but that doesn't mean the code from which they're derived has been taken public; the attempt of The Open Group to impose restrictions on the redistribution of X11R6.4 source was, fortunately, beaten back - yes, there is the risk that this might happen with other software, and, yes, the GPL would make that more difficult, although note that XFree86's response was to say "we're not upgrading to X11R6.4", as the existing X source releases were still free. Even were one of the BSD groups to decide to impose those sorts of restrictions on the distribution of their OSes - something I consider unlikely, given that, unlike The Open Group, which was composed largely of commercial organizations, they're just collections of developers working on free OSes - earlier releases would continue to be available.

    21. Re:Two factors by Syberghost · · Score: 2

      Right. Remember that Open Systems != Open Source. People still get them confused.

      No shit; I've spent half the day responding to those people over in another story.

      Dare to say that the PC architecture is prevalent because of it's "Openness", and you'll get flamed for not knowing your history.

      Dare to suggest, in fact, that IBM makes money off the PC world, and you'll get flamed.

      Careful, Bruce, there are piranhas in the pool. :-)

      (Thankfully, with a little moderation they'll go from piranha to pariah. Just set your threshold to 2 and you can swim freely.)

      So, I have a question; why has no one released a "mainstream" GPL'ed BSD? Is it just because everybody inclined to do so is working on Linux instead?

    22. Re:Two factors by Guy+Harris · · Score: 2
      Are you arguing this doesn't really happen

      No, he's arguing that it is not the case that it always happens and that all non-GPL'd software "is being taken proprietary and disappearing forever from public view". It is, in fact, not the case - {Free,Net,Open}BSD are still in public view, and there is no sign that they are being taken proprietary, and there's plenty of other non-GPLed software that's non-proprietary and publicly available (heck, even if The Open Group hadn't abandoned their restrictions on the distribution of X11R6.4 source, previous releases wouldn't have "disappeared forever from public view").

      Yes, there is perhaps a greater risk of non-GPLed software "being taken proprietary and disappearing from public view" - although it may just be future versions that disappear from public view, allowing a fork to preserve the public version - but the mere existence of a risk doesn't amount to a certainty that the risked outcome will happen.

    23. Re:Two factors by Anonymous Coward · · Score: 0

      You can't for off you own and GPL it as you don't own the copyright. This appears to be a common mis-conception that you can whack the GPL on something. You can't unless you have the copyright.

    24. Re:Two factors by Anonymous Coward · · Score: 1

      The BSDL allows derived works and does not require them to be distributed under the same license. Work under recent versions of BSDL (without the advertising clause) can and has been derived from and distributed under the GPL. Many BSD proponents get very upset about it, though IMHO they were fools not to realize their license allowed this.

    25. Re:Two factors by Daniel · · Score: 2

      I think it was a joke, Bruce :-)

      Daniel

      --
      Hurry up and jump on the individualist bandwagon!
    26. Re:Two factors by mr · · Score: 1

      As opposed to taking GPLed code and folding it back into your BSD work.

      Ugh.

      Thanks

      M.R.

      --
      If it was said on slashdot, it MUST be true!
    27. Re:Two factors by Bruce+Perens · · Score: 2

      Oops. Open mouth, insert foot :-)

    28. Re:Two factors by Bruce+Perens · · Score: 2

      No.

    29. Re:Two factors by Bruce+Perens · · Score: 1
      What good is a disclosed-source system that you can't modify? It's good for one thing: you can audit it. However, I'm not sure this works because I don't see why anyone would be interested in auditing such a system. You could pay someone to do it, I guess. I like it more when my heart's in it.

      If the API is encumbered, it's not an Open System even if it is published. You still can't program to it.

      I reject the notion that View Source in a web browser is Open anything. Sure, you can see it and learn the general principles, but you can't reuse the software at all.

      Thanks

      Bruce

    30. Re:Two factors by Anonymous Coward · · Score: 0
      I reject the notion that View Source in a web browser is Open anything.
      Bruce, I normally think you're full of it, but this is the best thing I've seen you post in a long, long time. Thanks for making me laugh.
    31. Re:Two factors by Eivind+Eklund · · Score: 1
      Unfortunately, history shows that without a license requirement the return of code doesn't happen.

      This is not true. The return of code does happen - just not always. However, we do get a lot of returned code, and we get a lot of returned code from places that wouldn't have used our codebase if it had been under the GPL.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    32. Re:Two factors by Cramer · · Score: 1

      Ain't that the damned truth... the Linux solution to just about everything is "stick it in /proc." procfs has become nothing more than a run-down gheto full of pimps and drug dealers.

      Seeing the ass-backwards shit being done via procfs makes me want to wipe the hard drive and install Win2000. (RC2 even)

    33. Re:Two factors by Anonymous Coward · · Score: 0

      Do you see why this guy is loved? He has humility and can laugh at himself. Paying attention, Tom Christiansen?

    34. Re:Two factors by Anonymous Coward · · Score: 0

      What the fuck is wrong with you, sick puppy?

    35. Re:Two factors by Anonymous Coward · · Score: 1

      Why not? It gets us a few steps closer to Plan 9 and Hurd. Since a file is Unix' quantum of both namespace and I/O, we should be asking why anything in the system can't be manipulated using our thorough collection of file-oriented tools.

    36. Re:Two factors by Anonymous Coward · · Score: 0

      I think the BSD folks feel that free code should be "free" The GPL puts restrictions on what others may do with your code, hence it is less free because it is restricted. Obviously some feel these restrictions are necessary. But to have a pro-GPL coder take your code and re-release it as GPL is annoying because they then have the nerve to say they are protecting it for you. Not freedom...

    37. Re:Two factors by Gleef · · Score: 2

      Syberghost asks:

      So, I have a question; why has no one released a "mainstream" GPL'ed BSD? Is it just because everybody inclined to do so is working on Linux instead?

      Two reasons, first, until very very recently, the BSD license was not compatible with the GPL. The advertising clause of the BSD license prevented such a thing from happening. Secondly, some of the people most loyal to the BSD way of doing things have very anti-GPL feelings. Typically, such people are more concerned with their code being widely used (in Free or non-Free systems) than encouraging Free software, and the GPL gets in the way of that.

      We probably will see a GPLed BSD at some point, but there's no pressing need I see for someone to jump on the opportunity. The flaming that such a project would likely receive makes it even less worth it. In general, a developer picks a license because it matches how they want the software to be used; changing the license, even while legal, would be bad form without a very good reason.

      ----

      --

      ----
      Open mind, insert foot.
    38. Re:Two factors by _peter · · Score: 1


      > why has no one released a "mainstream" GPL'ed BSD


      Because the people who appreciate *BSD and know it well enough to maintain it tend to be the developers -- and they have bad associations with GPL'd code. Associations like the spaghetti mess that is gnu-tar, the overladen info/emacs help system, or not being able to exchange freely with the Linux kernel like they can amongst themselves.

    39. Re:Two factors by Gleef · · Score: 2

      Bruce Perens wrote:

      I reject the notion that View Source in a web browser is Open anything.

      Well, on most systems it's an open window :-)

      ----

      --

      ----
      Open mind, insert foot.
    40. Re:Two factors by Bruce+Perens · · Score: 1
      Well, if you folded GPL work back in it would still be free software. What's more, it would stay free software thereafter. I don't find that so bad.

      Bruce

    41. Re:Two factors by Lx · · Score: 1

      a) it's certainly not fair to anyone who wants to incorporate ten lines of GPL'd code into ten thousand of his own,

      Sure it is. The only reason he has my code is that I get his in return, otherwise why would I publish it?


      Because you are writing FREE software. The idea is not to have other people improve your code, although that is a side effect, but to give software into the public domain that you feel should belong there. To do it for other reasons is, IMO, selfish.

      -lx


    42. Re:Two factors by notsosilentbob · · Score: 1

      Actually, I think there is some merit to this. I just called out to my wife (who is NOT a geek in any way) and asked:

      Have you heard of Linux? Answer: "of course!"
      Have you heard of BSD? Answer: "Huh?"
      Have you heard of Posix? Answer: "Hmm.. that sounds familiar"
      Have you heard of RMS? Answer: "no"
      Have you heard of Richard Stallman? Answer: "I think so"

      Never underestimate the power of a catchy word: Apple, Yahoo, Linux, Emacs, iMac, Redhat.

    43. Re:Two factors by mr · · Score: 1

      As you said Ugh.

      People who've chosen a new-style BSD licence (happy RMS?) over all the other licence models have no desire to take GPLed code and infect the BSD code.

      So GPLed code is as useless as SCSL code. For neither option allow the FREEDOM TO DO WHAT YOU WANT WITH THE CODE. For the BSD camp, its about the rights of humans to make code use choices, and not about the rights of code to 'be free'.

      Again, as you said Ugh.

      --
      If it was said on slashdot, it MUST be true!
    44. Re:Two factors by dublin · · Score: 2

      Bruce,

      Two things:

      First, it's more than a little unfair to lump the present FreeBSD license in with the historic commercial BSD license. Due to the AT&T concerns and other issues, they are really completely different animals.

      As you no doubt know, Sun and the other workstation OEMs were under the old commercial BSD license, which does not require or even encourage reincorporation of code from the licensees. It's my understanding that even so, many (but not all) Sun improvements made it back into BSD up through the SunOS 3 & 4 days - which ended a geological epoch ago in Internet time.

      (You're right about there being more Sys V code than BSD in most modern commercial Unixes - although I'm personally more comfortable with Berkeley Unix practices, when the father of BSD (Bill Joy, for the newbies) decided that the SVR3-based Solaris was the only way to provide for future needs, that sent a message!)

      Sun went further than they had to in giving back any changes at all - as you corectly point out, almost no one else has given anything! I'm not sure what you're beef with either Sun or BSD is here other than, "the world isn't like it'd be if *I* were king!"

      Second, although I have not taken the time to seriously try FreeBSD (I should, I know), it's probably quite premature to either declare Linux' victory or the failure of the BSD license model. In fact, it's quite possible that BSD could have the last laugh - Both Linux and FreeBSD user bases are comparatively small, and big numbers will likly come from big promoters. (Of your two factors, I think time is the big one.)

      It's no secret that many commercial developers are more comfortable with the BSD license - if that ultimately translates into more commercial support for the BSDs rather than the Linuxes, then we could see a real shift in "popularity". Remember the communities are sparse enough that there's only about a 4 or 5:1 edge for Linux now, and most of the big guys are still straddling the fence. (e.g.: IBM both supporting Red Hat and buying BSD-based Whistle.)

      Some people will always abuse the system, and there's no good way to stop it. (I think most of us suspect GPL'ed code has been "privatized" a time or two!) License purity is not a cure for human greed.

      And no, I don't think "poisoning" the BSD waterhole with GPL would do either camp (or open/free software in general) any good at all. In reality, I think the town is more than big enough for both Linux and FreeBSD, and it appears there are things both camps could learn from one another.

      --
      "The future's good and the present is nothing to sneeze at." - Roblimo's last ./ post
    45. Re:Two factors by Anonymous Coward · · Score: 0

      On the other hand, ask your typical mid-30s MIS guy:

      Have you heard of Linux? Answer: "Yeah, I should have bought that stock! I'm trying to run 6.0 at home but my sound is broken."

      Have you heard of BSD? Answer: "Uhh, yeah in college, it's a kind of Unix. I thought everyone was running System Vee by now."


    46. Re:Two factors by Anonymous Coward · · Score: 0
      The GPL's only restrictions boil down to "don't add other restrictions", which is harmless and leaves the software far more usable than the restrictions proprietary vendors would add.

      Anarchy starts out looking more free than civilization, but it quickly degenerates to tyranny by the most threatening without strong self-defense.

    47. Re:Two factors by Eivind+Eklund · · Score: 1
      IMHO there's nothing moral about aiding and abetting organizations who have ripped off their customers and all but eliminated progress in my profession. Where does "refuse to help others do what you don't want them to" fit into your worldview? I give them source, they give me nothing - how can that ever be fair?

      You are assuming that they don't give back any changes. From my experience, this is generally false. Companies have employees that are human, and many of the companies that base things on open source software employ open source advocates.

      Changes will, in most cases, come back. Just not all of them, and perhaps not at all if what is being done is creating a new Unix clone. But this isn't common; what is common is to use the code for various types of embedded systems.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    48. Re:Two factors by Anonymous Coward · · Score: 0
      You are assuming that they don't give back any changes. From my experience, this is generally false.
      Could you give some precise references so we can add this to the demythification list, please?
    49. Re:Two factors by Anonymous Coward · · Score: 0

      Correct me if I'm wrong, but doens't GPL let you make proprietary modifications to anything you want as long as you don't distribute it [publicly]? It seems to me as though this should annoy you too. I'm guessing that any entity who's about to "proprietarize" a piece of software they've just discovered isn't going to have qualms over BSD vs GPL. I don't see how this affects "code return" in the least, if I don't want to return BSD-licensed code, I don't have to return GPL-licensed code either.

      Obviously this doesn't apply to software that's developed for the puposes of general sale but I'd imagine that constitutes a pretty small portion of _modified_ source. Further, in that case, GPL is the license preventing development!

    50. Re:Two factors by Guy+Harris · · Score: 2
      and they have bad associations with GPL'd code. Associations like the spaghetti mess that is gnu-tar, the overladen info/emacs help system

      Are either of those due to the GPL? It seems silly to reject a license merely because some code released under that license doesn't meet your standards, unless you have solid evidence that the license somehow caused the code not to meet your standards and will cause a lot of other code not to meet your standards....

    51. Re:Two factors by Anonymous Coward · · Score: 0

      Thanks for the insightful post. Too bad it will be lost.

    52. Re:Two factors by Anonymous Coward · · Score: 0

      If you infect BSD with an insidious and proprietary licence like the GPV, you will ruin it. It is our freedom that makes us strong.

    53. Re:Two factors by Anonymous Coward · · Score: 0

      Good catch. That's like saying, "I know that stupid people eat corn flakes, so I won't have any." Stupid people are associated with everything. And there's bad code everywhere. It's not reasonable to assume that the licensing affects code quality without proof to that effect.

    54. Re:Two factors by Anonymous Coward · · Score: 0

      Of course you don't have to return GPL code. You can always make it a CGI script, or put it in a library, or just use it for your own company.

    55. Re:Two factors by cnflctd · · Score: 1

      selfish

      RMS calls it "pragmatic idealism", noting that "The GNU GPL is not Mr. Nice Guy."

      Would you admit at least that this selfishness isn't inspired by greed? Idealism is not a vice, so leveraging the copyright laws for idealistic reasons shouldn't be either.

      --
      I'm cool like a fool in a swimming p-p-pfft-pool
    56. Re:Two factors by Bruce+Perens · · Score: 2
      Yes, I remember the commercial BSD license, but it's been gone for quite a while now, and it doesn't seem to have changed much. Of the two companies that did at least make an attempt to give back, both wrote their own licenses rather than use the BSD license for their modifications.

      And of course the argument is different for X, that's been under a BSD-like license for much longer.

      I wouldn't suggest the GPL as a means of "poisoning the BSD water-hole" - that's pejorative. I would suggest the GPL as a means of providing a path for people who prefer to have a license protecting the free-ness of their efforts.

      Thanks

      Bruce

    57. Re:Two factors by Anonymous Coward · · Score: 0

      Bruce, as usual, you've warped the issue. The GPL isn't for people who wish to preserve the freeness of their own efforts. The BSDL will do that just fine, thank you very much. The GPL is about not letting your work be used in larger products by businesses who pursue a traditional licence-fee system. It's a way to make sure that other people's work is also unusable for such evil money-sucking businesses. You see, the BSDL is about your own work. The GPL is about others' work. Completely different.

    58. Re:Two factors by Anonymous Coward · · Score: 0

      You don't think that Stallman is motivated by nastiness? He was burnt once. It pissed him off. He now takes it out on the whole world, trying to cloak it all within a faux moral argument to hide what's really going on.

    59. Re:Two factors by cnflctd · · Score: 1

      My God, you're right! He's Dr. Evil with hair! The fiend!

      But what about all the thousands of GPL developers? Don't they realize they do the bidding of Dr. Evil-With-Hair? The fools! Look! RMS is nibbling his pinky!

      (whew, I'm all out of sacrasm. can't...even...hold...down...the...shift key. oh, well, better eat some more doritos.)

      --
      I'm cool like a fool in a swimming p-p-pfft-pool
    60. Re:Two factors by Lx · · Score: 1

      I suppose that I would admit that the selfishness is not motivated by greed in the traditional sense. Its hard to say which license is the more idealistic, though.

      -lx

    61. Re:Two factors by Anonymous Coward · · Score: 0

      It is not a question of who gives what -- it is a question of if the community is an order of magnitude large enough to support itself. FreeBSD, has hundreds of developers working directly on the system. This is large enough to be successful. There are also commercial entities who do choose to give their code back.

    62. Re:Two factors by dennisp · · Score: 2

      The fact still remains that the BSD community has reached an order of magnitude that brings sufficient returns.

      The fact that it is not imperative to return code is irrelevant. There are many corporate users who have returned portions of their code who would not have used the GPL in the first place because they can not pick and choose.

    63. Re:Two factors by Eivind+Eklund · · Score: 1
      I said: You are assuming that they don't give back any changes. From my experience, this is generally false.

      Anonymous coward said:Could you give some precise references so we can add this to the demythification list, please?

      To give just a few examples:

      This is just a short list off the top of my head. There are a lot of other cases.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    64. Re:Two factors by Anonymous Coward · · Score: 0

      Are you arguing this doesn't really happen, or just that we shouldn't object to good work being abused to subsidize more proprietary crap we have to cope with?

      It sounds to me like you're part of the "it must all be GNU" steamroller. The borg-like mentality that anything for the computer that doesn't come with source code you can climb around in must be obliterated.

      It seems frighteningly like the ideologies of the 1930s (Stalinism, Naziism) that many of us had hoped we could overcome.

    65. Re:Two factors by _peter · · Score: 1

      What I was trying to get across without becoming flamebait was: the GPL is strongly connected to the FSF and their gnu utilities. The BSD people tend to dislike the creeping featurism and code bloat in GNU utils.

      Second, people who write code under BSD licenses do so because they believe that writing useful code is a higher goal than worrying about tit-for-tat. Yes, companies can rip their code off. But this happens much more often in the small case than the large.

      For example, I have a friend whose job for several months was adapting OpenBSD's ftp server for his company's specific requirements. In the process he found several obscure bugs in the ftp code. Those bugs have been submitted to Open's developers. Things like that happen often enough that sticking to the GPL looks unwise and petty.

    66. Re:Two factors by Guy+Harris · · Score: 2
      the GPL is strongly connected to the FSF and their gnu utilities.

      Yes, the GPL is strongly connected to the FSF, given that it was originally, I think, the idea of the FSF's founder.

      And, yes, the GNU utilities are, not surprisingly, licenced under the GPL.

      However, what I was trying to get across is that this does not, in and of itself, demonstrate that the GPL is connected to "the creeping featurism and code bloat in GNU utils"; somebody could write, say, a GPLed cat that lacked such creeping featurism and code bloat as the -v flag (-v being, by the way, Berkeley creeping featurism, not GNU creeping featurism...)

    67. Re:Two factors by Anonymous Coward · · Score: 0

      > Correct me if I'm wrong, but doens't GPL let you make proprietary modifications to anything you
      > want as long as you don't distribute it [publicly]?

      Yes, it doesn't _compel_ you to distribute anything at all. The conditions kick in once you have distributed either source or binary.

      This is one of the major criticism's of Apple's license for the open source parts of Mac OS X-- you are required to send them your changes as a condition of using the code.

      Also, it doesn't compel you to distribute except to those people you've already given code to. So you and your friends can use a custom "proprietary" code with GPL stuff in it, but (a) you can't have your friends sign a contract disallowing them from distributing source or binary, because that would break the terms of the GPL, and (b) you have to give source to at least your friends if you give them binaries.

    68. Re:Two factors by Anonymous Coward · · Score: 0

      we have always been at war with eurasia.

    69. Re:Two factors by Anonymous Coward · · Score: 0

      By implicit comparison with Naziism, and transatively with Hitler himself, I hereby declare this thread dead, by godwin's law.

    70. Re:Two factors by cjs · · Score: 2

      `Fools' is perhaps a bit strong a word here, but I'm not surprised that some BSD advocates didn't realise some of the implications of the licence. Certainly some GPL advocates have shown from time to time that they don't realise the implications of the GPL, as well.

      But a lot of us have chosen the BSD licence (or something even more free--personally, I put my code into the public domain) specifically because we want you to be able to take it and GPL it if you like.

      BSD folks say to GPL folks, `Take our code and do what you like with it. If it helps you, great!' GPL folks say to BSD folks, `you can't use our code unless you GPL all of your code.' Now what does this say about the spirit of sharing on each side?

      cjs

      --
      The world's most portable OS: http://www.netbsd.org.
    71. Re:Two factors by Arandir · · Score: 2

      "Idealism is not a vice"

      But idealism put in practice often is. Because all idealism is, is wondering what the world would be like if you/I were king.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    72. Re:Two factors by Arandir · · Score: 2

      "IMHO there's nothing moral about aiding and abetting organizations who have ripped off their customers and all but eliminated progress in my profession."

      You are correct. The only progress in software has come solely from the GNU camp.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  15. V/S by razvedchik · · Score: 2

    Yes, but we all have to agree that both camps are adequately staffed with a bunch of radicals who will give you one hundred reasons why their brand is superior.

    When, for instance, they both run EMACS, VI, Apache, and loads of other GNU software.

    I think that if you don't like the look of the "alternative alternative operating system", A)Your information is out of date B)Wait 6 months and see if it has what you want C)What, you're using a MAC!!!

    --
    I do what the voices on my console tell me to do.
    1. Re:V/S by paul.dunne · · Score: 2

      Much as I hate to nick-pick... vi isn't GNU, nor is Apache.

    2. Re:V/S by razvedchik · · Score: 1

      Contex-derived error. You can take the phrase two ways. One is that the before mentioned software is GNU, and so are the tons of other software. The other is that they run these programs, and also the tons of GNU software.

      My bad.

      how about "...and tons of GNU software too."

      I used to be able to write in English fairly well. Then I learned Russian.

      --
      I do what the voices on my console tell me to do.
    3. Re:V/S by Anonymous Coward · · Score: 0

      > When, for instance, they both run EMACS, VI, Apache, and loads of other GNU software

      Interesting ... Windows does this right now.

    4. Re:V/S by Anonymous Coward · · Score: 0

      Microsoft now owns Interix.

      Interix is a Posix subsystem that runs on top of the NT kernel.

      Interix includes the GNU C Compiler.

      Microsoft is now in the business of selling a port of GCC that runs on NT.

      Just thought it interesting enough to mention here.

  16. Lets not start a flame war over this by rbunner · · Score: 1

    FreeBSD and the other BSD's are not as popular as Linux because they don't have as many users. They also have fewer distributions. The BSD's have also been more server sided then desktop untill recently. Certainly the BSD's have become more popular due to the succes of Linux as Linux has brought a great many people to look at Unix-like OS's. Which is better. I don't think there is an answer to that. Both work well. I use FreeBSD. It fits me well so I have no reason to look at Linux. I'm sure the same is true for many Linux user's.

    1. Re:Lets not start a flame war over this by Anonymous Coward · · Score: 0

      Well, I prefer NetBSD because it runs on my HP9000/345, my Mac, my SPARC and my PC. So I have to port a program only once to get it working on all my systems. And as if this isn`t enough, the binaries are the same for the HP and the Mac (both 68030).

    2. Re:Lets not start a flame war over this by Anonymous Coward · · Score: 0

      Does Open/BSD run on as much as Net/BSD? Isn't Free/BSD just Intel, kinda like Redhat/Linux?

    3. Re:Lets not start a flame war over this by Anonymous Coward · · Score: 0

      openbsd runs on fewer.

      freebsd is intel and alpha only.

  17. bsd didn't capture new users' interest by poopie · · Score: 5
    Life's not fair. I personally believe that linux has been so successful because:

    it invited in more new users than BSD
    it has a smart, savvy figurehead/spokesperson in the form of Linus, where BSD doesn't really have a single spokesperson for the media to contact, quote or interview.
    it has been marketed as something new, as opposed to yet another fragmented version of unix. (how many forms have a unix checkbox and a linux checkbox?)
    the linux community is more helpful to newbies, where the BSD community is more guru focused - RTFM!
    timing - linux timing was right for a unix renaissance
    random chance
    number of developers involved in linux kernel development and testing created a snowball effect with number of end users.
    confusion over the difference between FreeBSD, NetBSD, and OpenBSD. Maybe it would server BSD better (marketing-wise) to have a single name for their OS, and varying distributions
    the mass quantity of resources that are mostly unix-generic that have linux in their name -- like the LDP and many unix apps that have linux in their name
    1. Re:bsd didn't capture new users' interest by Gurlia · · Score: 1
      number of developers involved in linux kernel development and testing created a snowball effect with number of end users.

      But this begs the question. Why didn't the BSD developers snowball the same way?

      the mass quantity of resources that are mostly unix-generic that have linux in their name -- like the LDP and many unix apps that have linux in their name

      Objection, Your Honour. If this is the case, the question would be, why didn't the coders adopt BSD as part of the name, instead of Linux? Perhaps there is something deeper here.

      Just my $0.02 worth...

      --
      mikre he sophia he tou Mikrosophou.
    2. Re:bsd didn't capture new users' interest by homebru · · Score: 1

      Simple enough.

      BSD wouldn't run on my 486; Linux would. And that 486 still runs 1.2.8. (Slackware.)

    3. Re:bsd didn't capture new users' interest by Anonymous Coward · · Score: 0

      Stop calling it {Open,Net,Free}BSD, or *BSD, or MacOSX/BSD or BSDOS or whatever. Just call it BSD, and you won't confuse people with stupid distro issues.

    4. Re:bsd didn't capture new users' interest by Anonymous Coward · · Score: 0

      *yawn*
      And **I** have a 486 that Linux (5.2 redhat) won't install on yet FreeBSD (2.1.5 and better) will.

    5. Re:bsd didn't capture new users' interest by Rilke · · Score: 5
      To add to this:
      • Linux has a cool name and a cool story. Folks (especially in the US) just eat up the whole Linus story.
      • a major goal in the early days of Linux was "let's write a driver for everything". BSD never really pushed that goal, and today Linux runs on a whole lot more popular hardware than BSD does.
      • Open development: Linus accepted patches from just about anyone. Kernel improvements on BSD always went "let's discuss it, and then one of the core developers will implement it". Linux discussions were always "send a patch in, and then we'll talk about it".
      • The lawsuit, of course. Linux owes much of its early success to the CD-ROM, which was just getting popular. At the time of yggdrasil and early slackware, I don't remember seeing any complete easy-to-install BSD CD-ROMs (did walnut creek have one maybe?)
      • Linus himself. He's directed the whole movement incredibly well, staying out of arguments when needed, and stepping in when necessary.
    6. Re:bsd didn't capture new users' interest by jedinite · · Score: 3

      the linux community is more helpful to newbies, where the BSD community is more guru focused - RTFM!

      This is a common concern I hear from the pro-Linux community. Admitably, the BSD guru's willing to help are lesser in number than those on the Linux side (and thus perhaps the underlying message of the article), but they're still out there, and are still willing to help the newbies.

      For example, check the following mailing lists for great support for those new to BSD:

      Free-BSD-newbies@FreeBSD.org*

      FreeBSD-questions@FreeBSD.org*

      -newbies is a discussion group for people new to FreeBSD, it's not intended for technical questions. Likewise, -questions is for technical questions, and not for discussions by new people. You WILL see a lot of "RTFM" on that list, and deservedly so...

      Also, of course, check out the support page at FreeBSD.org for more help.

      *=note: SlashDot is inapropriately parsing the extended info in the mailto's. You should be able to get the gist of it if you click on the mailto links. It should be addressed to majordomo@FreeBSD.org, and have the text subscribe FreeBSD-newbies or subscribe FreeBSD-questions

      ---------
      Question: How do I leverage the power of the internet?

      --

      ---------
      There is no try at jedinite.com
    7. Re:bsd didn't capture new users' interest by ChristTrekker · · Score: 1
      • confusion over the difference between FreeBSD, NetBSD, and OpenBSD. Maybe it would server BSD better (marketing-wise) to have a single name for their OS, and varying distribution

      OK, maybe I'm off my rocker here, but aren't Free/Net/Open basically equivalent to a distribution? How is it different to say "I run NetBSD" than "I run Red Hat Linux"? If anything, I think Free/Net/Open is alot less confusing than SuSE/Red Hat/Yellow Dog/Caldera/Slackware/Debian/etc. The BSDs are borrowing from each other all the time, so it remains relatively unified. One tweaks this and another tweaks that, no different than the Linux distros.

    8. Re:bsd didn't capture new users' interest by technos · · Score: 1

      Microchannel PS/2? That's the only non-flawed 486 that RH 5.x (and the rest of the 2.0.xx ilk) wouldn't run on. The 2.1.1xx and newer kernels run nicely. Both the current SuSe and RH distros install easily and even like the brain-damaged MCA SCSI adapters they usually shipped with.

      Just remember, there is a special MCA boot image for installation, and SuSe doesn't lock during the SCSI probe, it just takes seemingly forever to reset the SCSI bus.

      --
      .sig: Now legally binding!
    9. Re:bsd didn't capture new users' interest by Jerome+Jahnke · · Score: 2

      I think there are two reasons it didn't snowball. The first was, BSD was aleady well done, a lot of really good work had already gone into by the time it developers got to it. Linux was still a bit raw, which led to people poking around in it.

      Linux played catchup with BSD for quite a while. They clearly run neck and neck now. But lots of people like one camp over the other. I think both the BSD and Linux camps have lots of good developers working them both, and it will be intersting to see hat will happen in the next two or three years, neither is going away, but will industry embrace the GPL? It does seem unlikely to me.

      Personally since I learned about BSD OS's when I was in school I like them better than Linux ones. But I guess if I had to choose today which one I was going to install on a machine I could pretty much pick and choose. Lots of schools now teach Linux instead of BSD, in the OS classes. Some of them still teach Minix (if you want to read something entertaining you should try to find the thread of Torvalds and Tannenbaum discussing the merits of a monolithic vs a micro kernel.)

      I think overall the major difference in BSD vs Linux is Torvalds. One intelligent, well spoken, until recently, accessable individual has made all the difference in the world. Even now he remains a powerful voice in support of it, and he plays well in the papers. He is less important now than he was earlier, but don't discount his influence, there were a LOT of good alternative OS's out at about the same time.

      Jer,

    10. Re:bsd didn't capture new users' interest by _peter · · Score: 1
      • confusion over the difference between FreeBSD, NetBSD, and OpenBSD. Maybe it would server BSD better (marketing-wise) to have a single name for their OS, and varying distributions?

      Two problems:
      1. BSD types don't have take-over-the-world aspirations, they just want to write useful code. Thus, anything justified as better for marketing tends to be scorned.
      2. The three *BSDs are not just different distributions, there are fundamental technical differences among them. To the extent that they're interoperable at all, it's from emulation & conforming to a standard API.
    11. Re:bsd didn't capture new users' interest by homebru · · Score: 1

      Nope. Not microchannel, ISA. Good, clean, standard hardware.

      The problem wasn't with the bus, but with the drives I was using. I had one Seagate and one Maxtor. And the BSD "known problems" file (I forget the exact filename) said that that was the one configuration that had been found to not work. It didn't for me either, so I moved over to Linux.

      The 486 box remains at 1.2.8 (Slackware) because:

      1) it works (modem, print, file server)
      2) it only has 8mb of ram
      3) I'm lazy
      4) I have a p-II (300) that runs Linux 2.0.36 (RedHat).

    12. Re:bsd didn't capture new users' interest by The+Welcome+Rain · · Score: 1
      -newbies is a discussion group for people new to FreeBSD, it's not intended for technical questions. Likewise, -questions is for technical questions, and not for discussions by new people. You WILL see a lot of "RTFM" on that list, and deservedly so...

      So where do newbies go when they have technical questions?

      It does happen, you know.

      --

      --
      Some keywords for the NSA in the Lord of the Rings universe: One Ring bind find Sauron quest Nazgul freedom
    13. Re:bsd didn't capture new users' interest by Punto · · Score: 1
      I think there is another important thing: most new users don't know the difference between linux and bsd.

      When I first wanted to install linux, I went to some unix irc channel, and then to a linux irc channel, and I asked "where can I download a small linux to install on a 100MB hd, or run from a floppy disk?" (I didn't want to go and buy the CDs). And someone said: "you can go to freebsd.org and install freebsd through FTP".

      So, at first I though that FreeBSD was another linux distribution, like "red hat". At that time, all I knew was "linux is a free version of unix; unix is a OS that doesn't crash ever 5 minutes". Then I found out that there is actually a guy named "Linus", and that he wrote the kernel, and that there is a GNU part, etc.

      So, I think that a lot of people that are new to this think that bsd and linux are the same thing, and not the opposite, because they hear about "linux" and then run into bsd (because linux has more attention from the media and all).

      --

      --

      --
      Stay tuned for some shock and awe coming right up after this messages!

    14. Re:bsd didn't capture new users' interest by Anonymous Coward · · Score: 0

      New users have no business adminning a professional computer system. They are a danger to themselves and others.

    15. Re:bsd didn't capture new users' interest by Anonymous Coward · · Score: 0

      Walnut Creek was the early adopter of FreeBSD. I'm frankly surprised that they dont do more to promote both Slackware and FreeBSD. Both excellent products. If the word doesnt get out to the public, there is no mass acceptance. Look at the success Red Hat has now. This is mostly do to marketing.

    16. Re:bsd didn't capture new users' interest by Anonymous Coward · · Score: 0

      And I'm sure you just rolled out of bed one morning and knew everything there was to know about unix, BSD, linux, NT, network, how to be a better lover, etc.

    17. Re:bsd didn't capture new users' interest by jojo80 · · Score: 1

      I wonder, if you wanted to start a flame war... ;) the linux community is more helpful to newbies, where the BSD community is more guru focused - RTFM!
      I really don't think so. At least in German Linux-Newsgroups there are lots of people who only answer 'RTFM man foobar(1)'. I rarely got good and helpful answers when I needed them.
      When I had a problem with FreeBSD and ISDN I did get very helpful answers, no one referred to man pages or told me to RTFM. To me, it appears as if the *BSD community is more helpful. timing - linux timing was right for a unix renaissance
      hmm....but the BSDs were already there. Why didn't people use *BSD? That would make more sense to me - don't take the trailing edge stuff, but the proven technology if you need a flavour of unix. just my 0.02 Euro...

    18. Re:bsd didn't capture new users' interest by Raven667 · · Score: 1

      The BSDs are no more compatable with one annother than any other Unix OS, or Linux. They are as fundementally different as Linux is to Solaris or HP-UX or SCO.

      While it is true that changes can get distributed between the different OSs it is not too much different than the code exchange between Linux and *BSD. Certainly not the same as the difference between RedHat and Caldera or Debian or SuSE, they can easily run each others binaries, use the same libraries, etc. The only main difference between distros is the default configuration and file locations.

      --
      -- Remember: Wherever you go, there you are!
    19. Re:bsd didn't capture new users' interest by Anonymous Coward · · Score: 0

      That's not true. The same programs run fine on all my BSD systems, but not on the Linuxes. The admin is way weird.

    20. Re:bsd didn't capture new users' interest by Anonymous Coward · · Score: 0

      a major goal in the early days of Linux was "let's write a driver for everything". BSD never really pushed that goal, and today Linux runs on a whole lot more popular hardware than BSD does.

      No kidding. NetBSD (at least, when I last played with it, about 1.5 years ago) doesn't support any ISA card that needs DMA. Since ISA DMA only works for the first 16megs of physical memory, it is "broken" and not worth supporting.

      More rational OSes (including freebsd and linux) use bounce buffers to work around this flaw. While they have a point that the hardware is brain damaged, it is not a user friendly attitude, and is part of the reason NetBSD is less popular than Free or Linux.

      Tangent: Despite the fact that OpenBSD split off from NetBSD, I suspect in the next couple of years, OpenBSD installations and development will surpass NetBSD's. Security is becoming more and more important, and I know of no other OS that has undergone a rigorous security audit. Its not perfect, but it beats the hell outta anything else out there.

    21. Re:bsd didn't capture new users' interest by Anonymous Coward · · Score: 0

      I'm gonna have to call your lie on this one. Your statement is only true assuming those "same programs" are all FreeBSD, Linux or another universally supported binary.

      Lets see you run some of my OpenBSD binaries on your Freebsd or Netbsd box. Lets see you run a NetBSD binary on your Freebsd box.

      Meanwhile, any binary with the proper libc version will run on any linux box with that version or better. Since almost all linux boxes running today (ignoring the small number of libc5 holdouts who compile everything themselves anyway) run at least glibc2.0, you can simply link against glibc2.0, and your binary will run on 2.0 and 2.1 systems. These days that is pretty much everything, excluding the old slackwarers mentioned above.

      In other words, you are quite wrong, and your vague "admin is way weird" comment adds nothing to your argument.

    22. Re:bsd didn't capture new users' interest by E-Dragon · · Score: 1
      To rebuke some of these comments:

      1. FreeBSD developers develop drivers for the things they use. The OS itself supports a very large number of devices. If you want a specific device added, all you have to do is find a developer willing to add it, send them your hardware, and get them technical docs from the manufacturer. Of course, if they have the device themselves, maybe that's all the encouragement they need.
      2. FreeBSD will take patches from anyone. The problem is, most people don't know how to send them in - you can use the send-pr(1) interface at http://www.FreeBSD.org/send-pr.html. Of course, whether or not it gets accepted into the main source tree is what the discussion is for. The big misconception that I highly disagree with here is the fact that anyone can help out patching the system source. It's up to them to take the initiative to send mail the the appropriate mailing list, or to use send-pr(1).
      3. Walnut Creek has had FreeBSD CD's sent out since 1993 or 1994, ever since FreeBSD 1.0. Whether it was as "easy to install" back then as it is now (and has been for several years), I don't know.
      4. We have our own "representative" - Jordan K. Hubbard. He's just as energetic, helpful, and as much of a driving force for FreeBSD as Linus has been for Linux. And the FreeBSD community has obviously appreciated his efforts - there were a large number asking for his autograph at the closing ceremonies for the FreeBSDCon '99. And the other BSD's have their own representatives, most notably Theo de Raadt for OpenBSD and Alistair Crooks for NetBSD.

      Please don't try to spread untrue rumors for things you don't know anything about. If you had actually tried to give patches to the FreeBSD project and were rejected in the appropriate form, I'd be interested. But this is just a rumor spread around by people who don't know what they're talking about.

      In particular, I am irritated about the "closed discussion" and "elitist bastard" theory regarding BSD developers. I used to be a nobody in the FreeBSD scene, but after I started porting a large number of programs/libraries, I discovered how simple it is to contribute to this great OS, as well as how friendly MANY of the FreeBSD developers can be should you take it upon yourself to contribute.

      What I think is the best part is that with the send-pr(1) interface, you really don't need to have a fix already for a bug you've found. Somebody will eventually take up bugs/ideas that have been recorded in the GNATS database. They will not be thrown away without a valid response.

      As you can see, all it takes to contribute is an understanding of the differences between the organization for Linux and the organization for FreeBSD (and the other *BSDs as well).

      --Will
      --
      GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X+
  18. The Oreilly Connection by Erore · · Score: 2

    The answer is so obvious is isn't a wonder that we are missing it: Linux is more popular than BSD because Oreilly has published more books that pertain to Linux.

    I mean, we all know that the only way we ever learn anything is by reading an Oreilly book.

    1. Re:The Oreilly Connection by Anonymous Coward · · Score: 0

      This is precisely what led me to Linux 4 years ago. I had both Slackware and FreeBSD disks. But when I went to the bookstore I only found 2 books, and they were too technical for me. So, I picked up Redhat Linux Unleashed and the rest is history. I did like FreeBSD, though. I just wish it had more books at a beginner's level. Now that I've become a Linux user, for what reasons should I add a FreeBSD partition? Convince me, and I'll do it.

  19. Source model? License model? User model! by Anonymous Coward · · Score: 5
    Perhaps one of the biggest reasons is that the Linux community is very inclusive, while the BSD community is highly insular. Visiting the FreeBSD web site and reviewing their mailing list archives, or visiting #freebsd and spending ten minutes watching the conversations is enough to prove the point.

    This applies somewhat to users and to an extreme with developers. As a user, a question revealing that you don't know UNIX, not just *BSD, is enough to have you shouted out the door. As a developer, unless you're a 20 year BSD veteran, suggest an idea or ask where you can begin to help and you should be prepared to be stomped on. Hard and repeatedly. Largely by many of the project principals.

    Review some of Matt Dillon's contributions to FreeBSD in the mailing lists. He's repeatedly helped to pull large portions of FreeBSD up to and even past their Linux equivalents. Then consider the rationale behind the community's treatment of him.

    A similar type of treatment resulted in the split of NetBSD and OpenBSD. Again, reviewing their mailing list archives shows that this kind of childish animosity and cliquish cult behavior abounds.

    To the contrary, it takes all of five minutes to find something to do for Linux and to find a mentor who will help you find your way to the in crowd the first few times you've got a core-level contribution to make. They give you the benefit of the doubt as a new contributor, reviewing and considering your contribution, not your credentials or your ability/willingness to pose as a BSD veteran long enough to be heard.

    Frankly, it's surprising that this group exists outside of acedemia at all.

    1. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0

      [a] BSD users are elite.
      [b] BSD developers are rude to newbies.
      [c] BSD licensing sucks.
      and :
      [d] Therefore BSD sucks.

    2. Re:Source model? License model? User model! by bvmcg · · Score: 1
      Assuming that the goal is to further the OS, the BSD crowd doesn't get it. Social Engineering is a foreign language to them. "Just do it. Someone might thank you later, now piss the fsck off and don't bother us until you've rewritten the SCSI subsystem."

      Sorry guys. That doesn't usually work.

      Your average developer wants to feel included and appreciated from the start. Some program for the sheer thrill. But the ones who don't at least secretly want a pat on the back are rare.

      Most want to be part of a club of peers with a common goal at the onset. It's not hard to send them packing early on. BSD isn't going to grow to Linux proportions without change.

      I suggest "How to Win Friends and Influence People" by Dale Carnegie and "Cultivating Successful Software Systems Development Projects: A Practitioners View" from Scott Donaldson.

    3. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0

      Wrong. IRC is no measure of anything.

    4. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0

      It's nearly impossible to get anything into Linux. The kernel is locked up tight. You have to be just as much a genius to get your code into Linux as into BSD. And if you mean the userland distros, there are millions of Linux distros. How are you going to get your stuff into all of them?

    5. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0
      The point isn't that FreeBSD doesn't let bad code in. Yes, you have to be a genius to produce something worthy of the kernel for BSD or Linux. The point is that FreeBSD often doesn't let good code or good developers in.

      For apps: Writing something good and posting it to FreshMeat gets it into just about every Linux and BSD distribution.

    6. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0
      Stop your name calling. Unless you mean elite==competent, you might as well say something else that's bigotted and full of emotional bombshells. Shall we call Windows people Bubbas? Fatsos and oafs? How's that different.

      I hate bigotted trolls.

    7. Re:Source model? License model? User model! by sterwill · · Score: 2

      I think you've touched on a very important point. BSD is a cult; the development is done by a closed group of people who keep running inside-jokes, reject anyone who knows less than they do, and envy those who know more. The code isn't closed, the group is. It's a popularity contest at its absolute worst. The attitude is "do something for us or go away." The BSD license is perfect for these people. No social conscience--"just give us the code, and leave quickly so we can do very important things with it."

      Fortunately, the people who get the most work done are least interested in raising a blue ribbon ego, or "op" status on the IRC channel, or guru of the mailing list. Unfortunately, these people rarely get the recognition they deserve, but are still recipients of any derision towards the group.

      If the high school mentality ended at the so-called "development" level, problems would be confined to the results of that group, but it doesn't. Users do occasionally come into contact with "developers," and when they're told to bugger off unless they've got a patch, that's when the BSD bit in the user's brain flips to 0.

      --

    8. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0
      Yes, you have to be a genius to produce something worthy of the kernel for BSD or Linux. The point is that FreeBSD often doesn't let good code or good developers in.
      Either back that slander up with exact dates, names, and background explanations, or cease and desist. You're lying.
    9. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0
      I'm the original poster. I'm currently running OpenBSD and FreeBSD on two of my three systems, and have used half a dozen BSDs on about as many different platforms.

      I install OpenBSD on clients' internet servers, FreeBSD on some file and intranet servers, and Linux where Linux is explicitly asked for and a BSD sale seems improbable. The benefit with OpenBSD is virtually bulletproof security. FreeBSD gives the speed and stability that keeps clients coming back to me. Both do a wonderful job of limiting clients' choices in system maintainers as well; there aren't half enough consultants supporting BSD.

      This "linux weenie" doesn't deal in workstations, but I'd place FreeBSD there as well if all desired apps were in the ports and Linux weren't explicitly requested.

    10. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0

      You can always make your own distro like SGI or this hehe.

      CY

    11. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0

      FBI == FreeBSD Investigation you sound like an average BSD guy, rude and full of it.

    12. Re:Source model? License model? User model! by Eivind+Eklund · · Score: 5
      This applies somewhat to users and to an extreme with developers. As a user, a question revealing that you don't know UNIX, not just *BSD, is enough to have you shouted out the door.

      Can you back this up with references to actual incidents, as opposed to rumours? It do not match my impression at all, with the exception of #freebsd on efnet, which is an has always been a cesspool (from what I hear, #unix and #linux are very similar.)

      As a developer, unless you're a 20 year BSD veteran, suggest an idea or ask where you can begin to help and you should be prepared to be stomped on. Hard and repeatedly. Largely by many of the project principals.

      This is not true. It match the rumours I hear from the the Linux community, but they do not match the reality I've experienced.

      I entered the FreeBSD community without having much Unix experience; I'd run Linux for a few months (on a machine somebody else set up for me), and had had a login on a couple of other machines (SGIs and Suns). I was welcomed as a mailing list participant without having done any hacking on Unix itself, and as a short time Unix user. I got commit privileges after having been active on the lists for a couple of months, continously feeling them as friendly and welcoming of suggestions.

      I am now regarded as one of the 'project principals' (to use your term); I have never seen anybody being flamed for asking where to help. If I ever see a developer flame somebody for that, that developer will need to defend his commit privileges. I do not consider that kind of behaviour acceptable, and neither does (as far as I can tell) the community as a whole.

      When it comes to ideas, I agree that there can sometimes come a backlash. This is usually in the form of 'Show me the patches' when somebody is suggesting someting that is a lot of work, but we do have people in the community that will pounce rather hard on proposals that are bad, and where the person proposing it could have found that out by spending a small amount of time.

      Review some of Matt Dillon's contributions to FreeBSD in the mailing lists. He's repeatedly helped to pull large portions of FreeBSD up to and even past their Linux equivalents.

      LOL! Matt has contributed a lot, sure, but he's not "pulled things beyond their Linux equivalents" - the things he has been working on has always been further ahead in FreeBSD than in Linux. They are some of our strongest pieces.

      Then consider the rationale behind the community's treatment of him.

      The treatment has mainly been to not accept that he should, on his own authority, refuse to accept advice from the rest of the community, and that he would not keep direct write access to the source tree (commit privileges) unless he learned to work with the community.

      Would you want to have somebody that was contiually at war with Linus write to the Linux source tree, in opposition to what Linus said was OK? One that also fought with the rest of the Linux users? I suspect not - and the FreeBSD core team felt they could not accept that situation, either.

      Note: I cooperate with Matt on FreeBSD development, and consider him a brilliant programmer. I also think that he should have commit privileges (which he has now). However, I don't think he has been mistreated - he has been behaving in a way that brought him repeatedly into conflicts with people, and that had to be handled.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    13. Re:Source model? License model? User model! by dcs · · Score: 1
      There I go... no moderation on this story just to answer to this.


      In two words: not true.


      A "closed group" of people? Of two hundred people with DIRECT access to the repository? Hell, that's so not true that you can see the very proof in the message to which this one is a reply. It mentions the treatment that Matthew Dillon received. Yes, and, guess what, he is a committer too.


      There is nothing "closed" about FreeBSD. It gets new committers all the time, often people whose involvement with FreeBSD is quite recent.


      Do you think all these people from all these different countries have always known each other? That they all even get along with each other all the time? The very existence of some incompatibilities between some of these developers is a proof that the group is by no means closed.


      But, ok, let me back this with facts. Me. I once submitted a keyboard layout and a patch to the ide driver long, but never did anything to actually catch any attention. Then, around mid december 1998, I got interested in the on-going work with the boot loader. I submitted some patches and within two months I was a committer.


      I certainly never got rejected by anyone who knew more than me, and I never saw any signs of envy from anyone knowing less than me.


      Sure, I had to submit patches. You can't become a developer if you don't develop, though. But FreeBSD WILL welcome anyone who is actually willing to do something. This might range from doing userland programming to kernel programming to third-party applications porting to documentation writing to bug fixing. And even if your contribution is not in enough volume to turn you into a committer, your contributions are still accepted (like my keyboard map once was).


      Don't trust me. Check for yourself. The list of committers, minus the core team, who are also committers, and the additional contributors. Feel free to count them. Pretty closed group, eh? :-)


      And that's not even the complete list...


      Now, let me ask you a question... did you intentionally misrepresented the facts, or you just failed to do any research and mindless repeated FUD you read elsewhere?

      --
      (8-DCS)
    14. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0
      A "closed group" of people? Of two hundred people with DIRECT access to the repository? Hell, that's so not true that you can see the very proof in the message to which this one is a reply.
      Very good anti-FUDding. Thank you.
    15. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0
      his is not true. It match the rumours I hear from the the Linux community, but they do not match the reality I've experienced. I entered the FreeBSD community without having much Unix experience; I'd run Linux for a few months (on a machine somebody else set up for me), and had had a login on a couple of other machines (SGIs and Suns). I was welcomed as a mailing list participant without having done any hacking on Unix itself, and as a short time Unix user. I got commit privileges after having been active on the lists for a couple of months, continously feeling them as friendly and welcoming of suggestions. I am now regarded as one of the 'project principals' (to use your term); I have never seen anybody being flamed for asking where to help.
      Thanks for the antiFUD duty. It's appreciated.
    16. Re:Source model? License model? User model! by Eidolon · · Score: 1

      I'm not sure what to make of it all. I am a very seasoned BSD user (since 4.2 running on a VAX) who dabbled in Linux for a while before realizing that beloved BSD runs on microcomputers these days.

      I'm still far from knowing all the answers... BSD has changed a lot since 4.2 and running it on microcomputers is in many ways more challenging than running it on a VAX. ;-) I've probably been around BSD longer than a good many of the #freebsd or #netbsd regulars.

      I've found that asking for help in #linux or #freebsd is rarely helpful. The reasons for this seem to be:

      1. Everyone assumes you're a newbie if they've never seen you before. Instant prejudice.

      2. Most participants don't know any useful answers to (what should be) simple questions.

      3. Some things don't work well on Linux because they came from BSD. Some things don't work well on BSD because they came from Linux. This is a much bigger problem than people customarily admit. The two operating systems are different enough to create real problems, despite binary compatibility. KDE, for example, is extremely Linux-centric and some of its features simply will not work on BSD even if you use the Linux compatibility API.

      The parent post reads as if someone has had a very brief and bitter experience with BSD. That's sad. If that's how things are, at least know that it's not how they used to be. I think it is more than possible to have the same sort of experiences in the Linux world, and I think that there is some truth to the notion that most of the people active on Linux and BSD newsgroups and IRC channels simply don't have a clue to answer technical questions. It takes a great deal of perserverance to find useful information in these forums.

    17. Re:Source model? License model? User model! by Alex+Zepeda · · Score: 1

      Bah. I happen to think that KDE is rather Linux-centric, however, I've tried to work around quite a bit of this. In a way I resent that, because in actuality, all of the base parts of KDE 1.x work quite nicely with FreeBSD. The things that break tend to be apps that other people write (and I don't care about, and apparently none of the other FreeBSDers out there do either). However with KDE 2.x, I'm running into quite a bit of trouble with some oddly undefined symbols. However, all in all, KDE isn't by nature as Linux centric as a lot of people think it is. Damnit Jim, help make it non linux centric.

      --
      The revolution will be mocked
    18. Re:Source model? License model? User model! by dennisp · · Score: 2

      I think it was friday that I and a couple of others (including JKH) helped you with your IPFilter problem.

      If I remember correctly, you said you had very little experience with FreeBSD. In other words, you have no idea what you are talking about and are using blind and misappropriated speculation.

      BSD is not a cult. You are just full of shit.

    19. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0

      Tell pachell (seems to be the de-evolutionary equivalent of obi-wan) to stop acting like a crack addled 5 year old half the time or to just leave and maybe half the people who were previously acting like idiots will stop. I used to sit in #freebsd and help many people -- I do not now because of this person.

    20. Re:Source model? License model? User model! by dennisp · · Score: 2

      Please name some features that KDE has that do not work on BSD. I use KDE on my primary desktop and have not run into any problems whatsoever. I had to change maybe 4 lines in a Makefile to get Kdevelop working and all of base kde works perfectly.

      The one and only thing I did notice that was not working was the computer info page which is based on the linux proc setup which is not similar at all to the BSD equivalent.

    21. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0

      Why? Backing up your comments should not be done if it doesn't match your personal opinions?

    22. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0
      Well I certainly felt included and appreciated... I wrote the MACE Ethernet driver for NetBSD/mac68k, and the mac68k portmaster (the guy who's in charge of the mac68k stuff) pulled some strings to get my driver included in NetBSD 1.3 (it was close to the cutoff date for new features).

      I've had good luck with other changes I've submitted too... I've even been offered commit privileges twice, so I can make my own changes without going through someone else, but I haven't taken 'em up on it, since I've been way too busy with work lately...

      I've seen other people, even some who are fairly new to NetBSD, get commit privileges. At least with NetBSD, if you know your stuff, it's not hard to become a full-fledged developer.

    23. Re:Source model? License model? User model! by Eidolon · · Score: 1

      These are the difficulties I've run up against in using KDE 1.1.1 with FreeBSD 3.3-RELEASE:

      kdm has some subtle configuration issues, and its error reporting is cryptic beyond the call of duty. I still don't have kdm working, and I've put a lot of time into it. The BSD FAQ makes it sound trivial to do (which it isn't) and the KDE FAQ glosses over it totally. It appears that no one on the KDE mailing lists or in #freebsd or #kde over multiple IRC networks has noticed that this problem exists.

      Floppy device support for users other than root. BSD mount and /etc/fstab are different from Linux mount and /etc/fstab; the BSD fstab can't accept the "user" mount option, which KDE depends on to provide mount privileges to regular users. I tried to get around this with a sysctl -w vfs.usermount = 1 and chmod 777 /dev/fd0, but still can't mount floppies from KDE. Naturally, if I go to the shell and run mount by hand, BSD mounts the floppy. This is fine for me, but I've been configuring a FreeBSD system from a non-technical friend. I'd have just gone with Linux, but FreeBSD feels a bit more responsive on her old 486 box; even this slight advantage is important enough for running Communicator that I'm reluctant to switch to another OS.

      Yes, I too had noticed the info module not working, and it was clearly a /proc matter. Not a big deal, mostly.

      Thanks for reading.

    24. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0
      kdm has some subtle configuration issues, and its error reporting is cryptic beyond the call of duty.
      Welcome to Winix! They're just trying to give you the comforting annoyances that Prisoners of Bill have come to expect. This way it remains bug-compatible with that O/S that they are trying to copy.
    25. Re:Source model? License model? User model! by dennisp · · Score: 2

      Interesting,

      If i have time tommorow or thursday, I may look into this problem and submit a patch for the port or just give a heads up to the maintainer..

    26. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0

      What have you added to this discussion with your repeated content-free posts?

      Add something to the discussion, or shut the fuck up.

    27. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0

      KDE != Linux (or winix, if your sense of humor is that underdeveloped). Please make a note of this fact and consider it next time you are about to post a flame that is patently false.

    28. Re:Source model? License model? User model! by Anonymous Coward · · Score: 0

      Interesting. I posted a patch to the l-k list with my simple fix to the epic100 driver to add support for byte statistics. Alan Cox included it into his next -ac kernel, and from there it went into linus's tree. I haven't made any patches to FreeBSD, but I hardly see how it could be any easier than linux.

  20. A peek at history by Anonymous Coward · · Score: 2

    I suspect the real reasons for GNU/Linux's popularity over the BSDs are historical rather than technical. The BSDs were bogged down in legal battles at a critical time, a time when GNU/Linux systems were less mature but starting to take off. If not for that, 90% of the GNU/Linux geeks would probably be BSD geeks today.

  21. Sorry... by Anonynous+Coward · · Score: 1
    But, "Openness" only becomes a factor with a vast miniority of total Linux or BSD users.

    Linux is more popular than *BSD for the same reason Windows is more popular than Linux...Marketing. There's no Linux, Inc. but the grassroots marketing for Linux, and the fact that so many companies are offering easyish to use installation CDs you can buy at CompUSA is far superior to the marketing and end-user distribution available for any of the BSD variants.

    1. Re:Sorry... by Lazaru5 · · Score: 1

      The FreeBSD PowerPak is now also available at CompUSA.

      --

      --
      My comments and opinions completely reflect those of anyone and anything I am remotely associated with.
    2. Re:Sorry... by Anonymous Coward · · Score: 0

      Are BSD service packs like Microsoft service packs? :-(

    3. Re:Sorry... by Anonymous Coward · · Score: 0

      I know it was a joke, but:

      it's freebsd with a bunch of applications and various stuff on 4 cd's.

  22. It's yet another example of pump-priming by NateTG · · Score: 2

    BSD has been around for a long time in the academic world, but it hasn't had the massive user-coder base that Linux developed fairily quickly (This is the true genious of Linus). So it has been maintained AFAIK by a small group of people. BSD isn't as userfriendly as Linux, because that small group of pelple is more interested in the development of BSD than in helping newbies.
    Some BSD distros are really tough to install -- things like making your own boot disks from scratch for certain systems etc specifically because they want to discourage lusers from bugging them about it.
    So in general BSD is smaller because it is smaller -- there is not as big a user/developer community as there is for Linux, hence less development and exposure...
    As the OSS model starts to take more and more market share, BSD will develop a a strong competitor for Linux, especially in professionally administrated systems. This is a good thing -- competition provides for improvement. For example if this occurs we may see companies providing BSD service contracts, and improved security for linux.

  23. Another big reason: college undergrads? by belgin · · Score: 5
    Well, I really had never heard of BSD to any great degree until after I had finished my undergrad degree in computer science. Linux was a topic of discussion amongst undergrads in the first and second years of college.

    As self-fufilling prophecies go, this is another one. BSD continues to be less known, because it is less known. Over half of those same college undergrads I knew in computer science and engineering got hands on experience with Linux before they graduated, myself included.

    BSD continued to languish in the realms of unknown software.

    Many of the undergrads went out into the work force and are now doing jobs where they can at least provide knowledgable input about Linux. Many of them went to find jobs specifically where they could work on Linux systems. There was no similarly large pool of individuals who knew BSD amongst the dozens of fellow students I knew, including the systems operators (I was one) for our UNIX systems, or much in the faculty. Perhaps a few people seemed knowledgable about BSD, but they didn't talk about it much, because people knew more about and were already interested in Linux.

    For the most part, colleges provide the ground where our next generations of individuals in the computer industry learn UNIX-based OS's and determine what technologies they will bring to their initial workplaces. If BSD is as absent from most colleges as it was from mine, BSD won't catch on, because many of the people who would use it will not know about it.

    B. Elgin

    --

    B. Elgin
    "Read at your own risk; feel free to ignore."
  24. Quick factual correction by sethg · · Score: 3
    A lesser known operating system developed in 1970 at the University of California, Berkeley, called the BSD (Berkeley Software Design) is, in fact, the oldest free operating system.
    According to "Twenty Years of Berkeley Unix", Berkeley didn't even have a copy of Unix until 1973.

    The first free version of BSD (Networking Release 2) was distributed in June 1991, but got tied up in lawsuits from 1992 to 1994. By the time that was cleared up, early versions of Linux were already available.
    --
    "But, Mulder, the new millennium doesn't begin until January 2001."

    --
    send all spam to theotherwhitemeat@ropine.com
  25. "Berkeley Software Design" by kevin805 · · Score: 1

    It is "Berkeley Software Distribution", right? I've also heard "Berkeley Standard Distribution", but that makes less sense than "Berkeley Software Design". Maybe "Berkeley Standard Design"?

    1. Re:"Berkeley Software Design" by Anonymous Coward · · Score: 0

      The "D" in BSD is DISTRIBUTION. At least that is what their paperwork said when I got SPICE and NUTMEG from them. Their *nix was "Bsd UNIX ver y.y"

    2. Re:"Berkeley Software Design" by Guy+Harris · · Score: 2

      The distributions of software from the University of California at Berkeley were called "Berkeley Software Distribution"(s).

      A company named Berkeley Software Design, Inc. sells a commercial OS - called "BSD/OS", not "BSDI" - based on the BSD 4.4-Lite source.

    3. Re:"Berkeley Software Design" by Anonymous Coward · · Score: 0

      It is a play on LSD, known for it's popularity at Berkeley during the 60's.

  26. BSD = BERKLEY?! by Ion+Berkley · · Score: 1

    Whilst there are many historical reasons that
    undoubtedly contribute to this including the
    fragmentation of effort of open/free BSD etc....
    and the original BSD licensing issues, I can't
    help wondering if there is a key role played by
    the association of BSD with a physical entity
    namely Berkley rather with a global comunity of
    "no fixed abode". Maybe people psychologicaly
    don't feel an equal part of this thing, but more
    like they are helping with someone elses project.

  27. Stupidity? by Anonymous Coward · · Score: 0

    BSD rocks. Check out netcraft and any HIGH volume site. None of them run Linux. They all run BSD. Those in the know, know BSD. Also, Daemons are cooler than penguins.

    Linux is living high right now, but reality will come crashing down. Currently Linux demands the user community to disclose modifications. That won't last. It can't. RedHat, SUSE, Caldera and others will break that mold and when they do, Linux will come crashing down like the house of cards that it is. After that BSD will be the OpenSource OS, with SCO providing commercial Unix and Novell providing Directory Services. This is the reality, get used to it people.

    Some idiot will now point out that Caldera, RedHat or SUSE CAN'T DO THAT. They can and they will. They can take their installed base in any direction that they so choose (look at Microsoft). It WILL HAPPEN. SOON. They don't have to continue calling it Linux, after all Linus didn't call in Minux when he ripped them off did he?

    The writing is on the wall, and the end is near. Death to the penguin.

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

      the BSD evolutionary model is retarded. It cant protect itself. Youre wrong. BSD is going to die and you know it.

    2. Re:Stupidity? by pigeon · · Score: 1

      Linux is not a house of cards. The hype surrounding linux and it's related companies are. I do noet expect that Linux will come down as a dekc of cards, but the hype might, since Linux itself is not a bad product. But... why a shitty unix like SCO for commercial unix? You're pro BSD... choose BSDi! And your expectations about the companies taking another direction are very unprobable. I think these companies like Linux, and they're less or more stuck to some GPL matters.

    3. Re:Stupidity? by moogla · · Score: 1

      You are neglecting that fact that you don't _need_ RedHat, SUSE or Debian to provide you linux... users have the most control. If the companies were to go astray, the someone would do The Right Thing and resume distributing their untainted versions. Tbis is an important to watch out for,, Linux could become too commercialized at some point, and young computer nerds all over the world will retch simultaneously. But I think that some new group will step up to revive it to it's prior, geeky glory with some new logo and clever name.

      --
      Black holes are where the Matrix raised SIGFPE
    4. Re:Stupidity? by the+eric+conspiracy · · Score: 1

      Check out netcraft and any HIGH volume site. None of them run Linux.

      There are many large, high volume sites that run Linux. Google, for example is a 2000 CPU based Linux site. Other examples include eToys, dejanews and RealNetworks.

      The idea that Linux cannot support a large website is misinformation, easily disproven by the facts of what is happening on the net today.

      Linux demands the user community to disclose modifications. That won't last. It can't.

      Have you no clue as to the provisions of the GPL? The day RedHat tries to hide moddifications is the day the Free Software Foundation sues them.

      This is in fact one of the STRENGTHS of Linux vs. BSD - the BSD license makes it easy for companies to take modifications private, while the GPL makes it impossible.

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

      fastest os around baby. linux talks the talk, but sco is walking the walk, not only as one of the highest rated internet stocks for 2000, but the performance is there... http://www.zdii.com/industry_list.asp?mode=news&do c_id=PR19991213SFM126&ticker=scoc When you get linux numbers that can compete with this let me know, 'cause they just don't exist at this point. Tell me the someday Linux will be there story, and that point SCO will just be that much further ahead...

  28. BSD = Berkely Software Design? by slickwillie · · Score: 1

    When will these people ever get it right?

  29. sloppy reporting by Anonymous Coward · · Score: 1
    Not only is the author thoroughly ignorant of history (BSD started in 1977 and not from scratch, and so until recently it was only "free" if you already had a very expensive AT&T source license- netbs d.org has some good history), he doesn't even get name "Berekeley Software Distribution" right.

    I'll leave the comments about which kernel is better to the more knowledgable, but I have to wonder why you'd question some random suit about it just because his managers holds the Unix trademark this year.

  30. Article is Flame-Bait by Blue+Lang · · Score: 1

    I'm a little tired of the 'we'll start it out sounding neutral and informative and then switch to some unsubstantiated claims about BSD's superiority' articles posted here. This person claims that BSD's kernel is much more 'sophisticated' than linux's, in ways preferred by grad students and professors.. Sigh, and yerg.

    So, responders, do us all a favor, if you wanna prove how, why, and where BSD is better than linux, post code and illustrate the difference - then explain why each OS does it a certain way.

    My opinion: shut up and use whatever you feel like using. If popularity is important, go use windows.

    --
    Blue

    --
    i browse at -1 because they're funnier than you are.
    1. Re:Article is Flame-Bait by mr · · Score: 1

      Hrmmm.

      At The Bazaar, Mr. Raymond said over dinner that the BSD kernel was cleaner.

      And Mr. Perens expressed a similar view. If I'm lucky, that I have on tape, and need to get it off the camcorder.

      Want "proof" of a BSD kernel being better than Linux at task X, or Linux being better than BSD at task Y? Then help create a Debian GNU/BSD. Because that is the only way anyone will be happy with the benchmark.

      (And I'm itred of the 1st posts, the fornicate-esque, and the BSD is dead posts. But because its cold out I wear a hat and so no one sees my point)

      --
      If it was said on slashdot, it MUST be true!
  31. Tehcnical Superiority != hype != popularity by Anonymous Coward · · Score: 0

    Linux was "new and different" and "trendy" so people flocked to that after the AT&T/BSD Lawsuit was decided. It has nothing to do with the GPL's Communist licensing policy or Linux "being better."

    Linux is flakey and not meant for real world use. We all know this. That's why people choose the stability of BSD for their embedded projects (see the Whistle InterJet, NFR's Sniffer, Secure Computing's products, etc.) as well as high end ones (Network Appliance, et al.)

    I love Linux only because of the financial windfalls that have been bestowed upon me by LNUX and RHAT. I have my car paid off now, which is a good thing.

    I'm back to work, using real tools-- BSD-based systems, IRIX boxes, Solaris Boxes and HP/UX machines.

    1. Re:Tehcnical Superiority != hype != popularity by Anonymous Coward · · Score: 0

      My dad can beat up your dad....

    2. Re:Tehcnical Superiority != hype != popularity by Guy+Harris · · Score: 2
      That's why people choose the stability of BSD for their embedded projects (see the Whistle InterJet, NFR's Sniffer, Secure Computing's products, etc.) as well as high end ones (Network Appliance, et al.)

      Well, first of all, Network Appliance doesn't run BSD on their boxes (I joined the software engineering group at NetApp when there were about 7 or 8 people in the group, and I'm still there, so I know what I'm talking about here) - we use the BSD networking stack, and various BSD commands, but it took a fair bit of work with a chainsaw to fit them into our environment (which is a kernel-mode-only, single-address-space OS that would probably not be completely unfamiliar in its innards to a BSD developer, but which is very much not a BSD kernel).

      Second of all, there are also embedded boxes that use Linux, e.g. Cobalt's boxes, and, I'm sure, plenty of others.

      As for whether Linux is "flakey and not meant for real world use", there are Web sites using it, there are places (including, err, umm, Network Appliance, Inc.) where people use it on their desktops and on their compute servers (most of our compute servers are running Solaris or Digital UNIX, but there is one Linux PC, and there will probably be more over time), and so on. People seem to manage to use it in "the real world" even if it's "not meant for real world use".

  32. Three reasons and bonus ranting by bjb · · Score: 3
    I think Linux and *BSD are fairly equal on the features and abilities front (yes, you can nitpick this if you want), but there are a few things:
    1. Linux is under the GPL, and wasn't held back by any ATT garbage
    2. The 'Image' of Linux; created by a single man (media view for the most part) and the logo is cute (the Daemon is cool, but probably scares someone, even WITH the halo)
    3. Microsoft is scared of Linux, not BSD.

    Yes, I fully agree that *BSD has numerous merits and that this is something that could easially be flamebait. However, Linux is just a bit ahead of the game (most likely due to the ATT crap), and it has caught the media attention. Its one thing when something comes out of a university, but when "the young finnish student created his own operating system because he didn't like what was out there" grabs peoples' attention, it seems to be a more heartwarming story.

    Ok, now let's look at this part about the "heartwarming". Yes, we as techies like to look at things for their technical merit, not their popularity. As I said above, they are both quite good and nitpicking is justified, but almost pointless. Wall Street knows about BSD, but they just don't really care. There are no Red Hats or VA Linux companies for *BSD, and Microsoft doesn't acknowledge *BSD (from what I've seen; tell me otherwise, please). I remember a few months back reading in the Wall Street Journal an article on how "If you thought Linux was the underdog, BSD is underground". People have read about it. They don't care.

    I guess I could rant about this for a while, and I'm sure people will flame and argue with this. The point I'm getting to is that Linux just has the head start on the public eye, and it is simply the center of a lot of attention. *BSD may be better than Linux. Linux may be better than *BSD. However, they're both quite good and certainly much better than that software from Redmond. RedHat and VA have both brought Linux to the public attention. I fear, however, that if there is a 'Red Hat BSD', it will just confuse people; it could turn out to be a good thing, but it could also just bring us back to the 80s when there were 20 different platforms and little in the way of 'cross platform' standards.

    Rant, rant, rant. I better stop before I talk in circles

    --

    --
    Never hit your grandmother with a shovel, for it leaves a bad impression on her mind...
  33. Re:Oh really by slickwillie · · Score: 1

    In the not-so-distant past, O'Reilly published more generic Un*x books (e.g. Unix in a Nutshell), but as the popularity of Linux rose so did the number of Linux-specific books from O'Reilly.

  34. Linux=Easy; BSD=Difficult by NatePuri · · Score: 3

    Initially Linux is decipherable with IRC help, mailing lists and on-line docs. Whereas, BSD takes some previous understanding and the man pages on BSD assume Unix know-how. The LDP HOWTOs are written for the uninitiated and that is a major reason why Linux appeals to people more.

    This whole Unix rebirth is very new. So people new to Unix will choose Linux first. Once they realize there is something objectively more mature for advanced purposes, they may consider a switch.

    I started out learning Unix by trying out the various Linuxes. Now I've settled on OpenBSD b/c security a huge issue for my business. And my level of security must be high. That is not so for other people. While I'm a huge proponent of security and privacy I feel most people can be by with their Windows computers if they have a good firewall/ip-masquerading gateway installed that runs either Debian (most secure Linux), FreeBSD or OpenBSD. With the growth of the home LAN, such a configuration is a no-brainer and you can install it on some relic of a PC that you thought could only have been used as a door stop.

    If people want to try a more stable desktop system; I usually will configure a system with KDE and FreeBSD or Debian for them. In terms of application capability they are about the same so it boils down to the person's taste in licencing features.

    But for someone who wants to go it alone and install and learn as one goes, I recommend something easy to install like Corel Linux or Caldera Linux (no not Red Hat which I recommend for the corporate environment).

    If a company came along that made a BSD easy to install and use it would be a truly awesome product; that is what Darwin and MacOS X is all about and they are awesome but expensive. If you have the money for Apple's new OS, the advantages for using a BSD based system speak for themselves after you've used them for a while. Unix gurus don't need convincing. They either only run BSD because it's 'real' Unix or they only run Linux because the GPL is preferrable. The arguments about Linux having more applications and better hardware support are, of course, silly because if that is the basis for an argument then we'd all be using Windows instead.

    The bottom line for new users is documentation that's easy to access and meant for them and an install process that people perceive as easy (i.e., it has a GUI). Linux has it and BSD doesn't.

    1. Re:Linux=Easy; BSD=Difficult by InfiniteReality · · Score: 2

      I'm a FreeBSD user, so I can't comment on other BSDs. However, FreeBSD has an excellent documentation system in their Handbook. It is a great resource for new users and experts alike. Also, FreeBSD 4.0 is scheduled to include hooks in their installation program which allows for a GUI installation.

    2. Re:Linux=Easy; BSD=Difficult by peterarm · · Score: 0

      While I agree with most of what you say, I disagree about one point: hardware support is a (necessary but not sufficient) factor. Yes, windoze has better hardware support, but once you rule out windoze and you start choosing between the BSDs and Linux, then (for desktop systems) hardware support is certainly a factor.

  35. Popularity be damned by Zigg · · Score: 2

    Shrug. I could really care less if it's more popular or not. It works wonderfully for me, and at the time that I switched from Linux, it worked much better. Popularity be damned.

    I've contributed a few ports to FreeBSD. I contribute in the little ways that I can because I believe in BSD and know that if no-one contributed at all, BSD would indeed die. (In the BSD-kernelled Debian threads, someone seemed to think that BSD was dying ``because of its license''. I would challenge that by asking them if ``not dying'' means ``growing to an unmanageable size''.) By the same token, if contributions to Linux stopped, Linux would die.

    I believe in BSD because it works, and because the source code is open (though some seem to think that anything non-GPL'd is not ``open'' -- we need not rehash those arguments here.) I can do with it what I want.

    The community spirit of BSD ensures -- without encumbrance of license -- that BSD will be around as long as there are still people working on it.

    1. Re:Popularity be damned by Anonymous Coward · · Score: 0
      I could really care less if it's more popular or not.
      It's comforting to know that you care so much. Most of us, however, couldn't care less.

      I bet the compiler hates you.

    2. Re:Popularity be damned by treat · · Score: 1
      I could really care less if it's more popular or not.

      It's comforting to know that you care so much. Most of us, however, couldn't care less.

      The idiom is "I could care less". Like many others, it does not mean the same thing when taken literally. It's one of a few that actually means the opposite when taken literally. But this doesn't make your criticism valid.

    3. Re:Popularity be damned by Anonymous Coward · · Score: 0
      The idiom is "I could care less".
      Nope. That's erroneous. The correct phrase is the negation of that one. People who can't say what they mean shouldn't be near a computer.
    4. Re:Popularity be damned by treat · · Score: 1
      The idiom is "I could care less".
      Nope. That's erroneous. The correct phrase is the negation of that one. People who can't say what they mean shouldn't be near a computer.

      Well I don't see how I could possibly disagree with your stunningly brilliant position. You told me I'm wrong, without any explanation or evidence.

      Face it, there are many sequences of words in English that mean something different than what you would expect from the definitions of each component word. It's messy and imprecise, but a great deal of effort is put into learning it, and that's how it works.

      If you don't like it, you should start making suggestions for how the language should be changed. Don't tell people that a phrase that has been in use for half a century is "wrong".

    5. Re:Popularity be damned by Anonymous Coward · · Score: 0

      "I couldn't care less" isn't an idiom; the statement means just what you'd expect from its construction. "I could care less" clearly derives from it through sloppy speech, and is only an idiom to the extent that we expect people not to think about what they're saying.

    6. Re:Popularity be damned by Anonymous Coward · · Score: 0

      I believe `I could care less' is an Americanism which originated as an ironic version of the phrase `I couldn't care less'. It may even be common in American usage, but it annoys me to no end, and I'd be quite happy to never read/hear it again.

  36. Thanks by Anonymous Coward · · Score: 1

    You saved me a lot of typing. :)
    In other words I agree with this poster. Linux is designed to bring in people. BSD doesn't seem to me to be similary designed. It's all about the initial planning stages and mission goals. BSD's goals seemed to be just for a free distribution of UNIX for poor academic geeks or something. Linux was a free reimplementation of UNIX for everyone.

  37. fsckin lame by CrudPuppy · · Score: 1

    pointing to a default apache page... are you just plain stupid?

    --
    A year spent in artificial intelligence is enough to make one believe in God.
  38. TUX by Anonymous Coward · · Score: 0

    everybody loves tux.

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

      I'm sombody. And AC, but somebody.
      And I don't like penguins. They smell bad.

      So not everyone likes tux.

    2. Re:TUX by Anonymous Coward · · Score: 0
      And I don't like penguins. They smell bad.

      You must have been smelling your own breath again.

    3. Re:TUX by Anonymous Coward · · Score: 0

      No, thats what happens when you take animals that have evolved to live in the cold and move them to 70 degree weather.

      Just because you have bad linux-breath problems doesn't mean the rest of the world suffers the same problem.

    4. Re:TUX by Anonymous Coward · · Score: 0

      i'm a linux person, and i hate tux. so there.

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

      Oooohhh... paraphrase: "I know you are but what am I"

      I must say, I'm quite impressed by your witty argument.

    6. Re:TUX by Anonymous Coward · · Score: 0

      TUX SUX?

  39. Sophistication? by ajs · · Score: 3

    The article contends that Linux is not as sophisticated as BSD. While I agree that certain features of BSD might be more advanced (e.g. from a brief chat with one of the NetBSD folks, the UVM sounds cool), Linux is braving uncharted water in a number of previously shunned areas (I was stunned to find, for example, that I can choose to enable a kernel-based static http server in my Linux kernel as of 2.3.x). This willingness to break with UNIX tradition is what sets Linux apart, and frankly is the reason that many of us like it.

    I also like BSD (I was a huge fan of 4.2, back when Ultrix was 4.2 with the serial numbers filed off). BSD has a tradition of stability and innovation that is hard to match, and look forward to a world where BSD and Linux are equal participants in the operating system development community. But can we stop pretending that one OS is "better" than another, and focus on which OS is right for a given task/environment?

    1. Re:Sophistication? by Charlatan · · Score: 1

      ...Linux is braving uncharted water in a number of previously shunned areas (I was stunned to find, for example, that I can choose to enable a kernel-based static http server in my Linux kernel as of 2.3.x). This willingness to break with UNIX tradition is what sets Linux apart, and frankly is the reason that many of us like it. ...

      I think that this is really one of the reasons that people choose BSD over Linux. While Linux is busy developing a 'kernel-based static http server' the BSD developers are ensuring a perfect blend between new features (as demanded by the market) and stability.

      I think it all boils down to the user. BSD users have come to expect a ROCK SOLID operating system. A system that does exactly what's expected of it, exactly as advertised. Linux users seem more willing to accept half operational features because they're 'new and cool'.

    2. Re:Sophistication? by Anonymous Coward · · Score: 0
      ...Linux is braving uncharted water in a number of previously shunned areas (I was stunned to find, for example, that I can choose to enable a kernel-based static http server in my Linux kernel as of 2.3.x).

      Usually people shun things for a reason. Just because no one else does it doesn't mean it's a good thing. In fact I'd be willing to say most of the time it's a bad thing.

    3. Re:Sophistication? by Anonymous Coward · · Score: 0
      >..Linux is braving uncharted water in a number of previously shunned areas (I was stunned to find,
      > static http server in my Linux kernel as of 2.3.x).

      Usually people shun things for a reason. Just because no one else does it doesn't mean it's a good thing. In fact I'd be willing to say most of the time it's a bad thing.

      Thanks for the demything duty.
    4. Re:Sophistication? by ajs · · Score: 2

      While Linux is busy developing a 'kernel-based static http server' the BSD developers are ensuring a perfect blend between new features (as demanded by the market) and stability.

      As I've said, I don't think there's much value in this sort of "my OS is better than your OS" discussion. Anything that I point out that Linux has been audacious enough to do alone is an easy target, but the bottom line is that BSD and Linux are both more stable, feature-rich and supported than any commercial OS that I've ever seen.

      Linux is taking a bold step with khttpd, and perhaps it will turn out to be a mistake, or perhaps it will be succesful, and the BSDs will adopt it in order to maintain a competitive Web server position. Either way, we're watching the power of open source, and when journalists cite bogus comparisons like "In terms of sophistication, the BSD operating system is better than Linux", I just have to hang my head and sigh.

  40. After Mac OS X is released... by musique · · Score: 1

    ...there may be more copies of BSD flavored Darwin/OS X out there than Linux.

    You can still make proprietary changes to Linux, you just can't distribute or sell the binary result, which is counter to what the article states. Apple open sourced OS X (though not GPLed) except it will keep its GUI to itself--since that's what makes the Mac the Mac. If the GUI were opened up, Apple would rot. Apple could not make money without complete control over at least some of its system.

    I think that Linux and BSD are suited for different tasks. It's good that we have them both.

    1. Re:After Mac OS X is released... by Anonymous Coward · · Score: 0

      If Apple can only sell hardware(!) by preventing anyone else from improving or learning from MacOSX, maybe they should rot.

    2. Re:After Mac OS X is released... by Anonymous Coward · · Score: 0
      Apple does not enjoy the luxury of being able to lose millions of dollars a quarter while coasting on IPO capital.

      I do not begrudge Apple the slight price premium I pay for their superior system integration, and am very much looking forward to OS X, due sometime next year.

      =td=

  41. Inspite of Bechmarking Linux & FreeBSD..... ? by siva06 · · Score: 1

    This is one of the many discussions Comparing FreeBSD and Linux ...

    Well there have been many a comparison between these 2 and many good point coming out of them. In turn these two have been raised to such atechnical levels, to countermand their negatives in each reviews. This is possibly the only real success that Open Source or FSF have really met.

    The real success would be in terms of the commecrial value of these system to support further enhancements. But the real situation is that commercial UNIX's like SUN / HP have still not implemented many of the good features that either FreeBSD or Linux have yet they are still outstanding in sales. To top the list the NET has whole list of pathetic performance of Windows NT and talk to any Sys ADMIN for the rest, still It tops the DeskTop...

    Could the real reason be that the word FREE is being misrespresented as POOR QUALITY ....

    I cannot think of a better reason for wither Free BSD or Linux not achieving the Compatitive levels. Where do we start the real education ... ?

    I would like to help on this ..

    Any suggestions

  42. FreeBSD vs. Linux by Kwikymart · · Score: 2
    My trusty FreeBSD book has a section on this. Some of the points are that

    1)FreeBSD aims to be a stable production exnviroment while Linux is more "Bleeding Edge" development enviroment.



    2)FreeBSD is still relatively unknown , since its distrobution was restricted for a long time due to the AT&T lawsuits. Linux did not have any lawsuits to contend with. So for a long time it was only free UNIX-type system available



    3)As a result of lack of knowledge about FreeBSD not much commercial software is available for it. Linux has a growing amount of commercial software for it.



    4)As a result of a smaller user base, FreeBSD is less likely to have drivers for brand-new boards than linux.



    some of these points may not help this discussion at all but I sure hope some do



    --

    Buying a Dell computer is equivalent to dropping the soap in a prison shower.
    1. Re:FreeBSD vs. Linux by TMB · · Score: 1
      3)As a result of lack of knowledge about FreeBSD not much commercial software is available for it. Linux has a growing amount of commercial software for it.

      Since FreeBSD and Linux both use ELF binaries, any well-written application written for one should work on the other, shouldn't it? Mind you, I've seen some commercial software that isn't entirely happy outside the distribution it was written on, never mind on a different OS. :-b

      4)As a result of a smaller user base, FreeBSD is less likely to have drivers for brand-new boards than linux.

      Often true (and self feeding), but it's a two-way street. For example, USB support is much better on FreeBSD than on Linux at this point.

      [TMB]

    2. Re:FreeBSD vs. Linux by Guy+Harris · · Score: 2
      Since FreeBSD and Linux both use ELF binaries, any well-written application written for one should work on the other, shouldn't it?

      No, not necessarily. {FreeBSD,Linux,Solaris x86,Unixware,...} ELF binaries for the platform in question expect the shared library routines they call to have particular calling sequences, with data structures having the layout of the OS on that platform, with various #defines, etc. having particular values, and so on. The mere fact that those OSes all use ELF is insufficient to arrange that binaries for a given CPU will run on all of them.

      Now, there are Linux-ABI implementations for all of those OSes (Linux implements it by definition; FreeBSD has support for Linux binaries; lxrun runs on Solaris and, I think, Unixware - it may originally have been an SCO program), so some commercial Linux binaries may be able to run on all of them.

      Often true (and self feeding), but it's a two-way street. For example, USB support is much better on FreeBSD than on Linux at this point.

      I've heard that to be the case for USB, and plug-and-play ISA seems to work better on FreeBSD than on Linux right now as well.

      Both of those will, I think, change with the 2.4 Linux kernel - but there may, in the future, be other places where FreeBSD does better than Linux, just as there are places where Linux does better than FreeBSD, when it comes to supporting hardware.

      The relative state of OSes X and Y at time T doesn't necessarily indicate that the relative state will be the same at time T plus delta T; some of the Microsoft anti-Linux marketing literature may well make correct points now about stuff that NT does better than Linux, but that doesn't mean it'll always do better - and the same applies to stuff Linux does better. Of course, marketing literature is generally intended to persuade, rather than inform, so if somebody says "XXX does better than YYY at ZZZ", be careful that you don't necessarily implicitly infer from that statement that XXX will always be better than YYY at ZZZ....

  43. im glad... by Anonymous Coward · · Score: 0

    im glad you feel okay calling 10 million linux
    users "script kiddies". maybe you can start
    giving us lessons on how to be real unix gurus??

    i dont know if you would be able to tolerate
    someone like me, with such a lack of knowledge...

    i only admin a dozen or so Enterprise 10k's and
    a couple SP2's...so im prolly still too much
    of a script kiddie for you to teach me :( :(

    1. Re:im glad... by Anonymous Coward · · Score: 0
      "i only admin a dozen or so Enterprise 10k's and a couple SP2's...so im prolly still too much of a script kiddie for you to teach me "

      Only a dozen? Chicken feed. Report back to us when you have a hundred, and then we'll show you what you must learn...

      dawgzsz
    2. Re:im glad... by bugg · · Score: 1

      "with such a lack of knoweldge"

      Apparently, judging by the lack of capitalization. Real gurus follow the syntax of the English language.

      --
      -bugg
    3. Re:im glad... by Anonymous Coward · · Score: 0

      Maybe that's why Linux programmers don't write papers. They can't spell as well as BSD programmers. :-)

    4. Re:im glad... by Anonymous Coward · · Score: 0

      a script kiddie if I ever saw one....

  44. Some thoughts of my own by jd · · Score: 3
    1. The Jolitz' kept their mods secret between releases, and development went at snails pace. At the same time, Linux entered the arena with an open, rapid development model and a lot of people (myself included) defected to the Linux camp, after it became obvious Linux would overtake 386BSD and keep going.
    2. BSD's installation method has not changed since the days of 386BSD. It still autodetects, in much the same way, and has everything in TAR files. No great problem - I prefer tarballs to RPMs, as they're more generic, but they aren't as friendly on novices.
    3. BSD's hardware support, frankly, sucks. It's awful. It's improving, but it's a long way from being as hardware-friendly as Linux.
    4. BSD is harder to obtain. Linux can be found in bookshops, in the computer stores, and probably in your cornflakes, before long. FreeBSD, OpenBSD and NetBSD are lucky to get a mention in some of the online stores on the Internet.
    5. Linux has =LOTS= of distributions, which means there's =LOTS= of choice and LOTS of growth. It also means that any 6th-former can cobble together a distribution for some specialised purpose, put it on the net, and get a name for themselves, and possibly an IPO a few weeks later. For a system that prides itself on being commercial-friendly, BSD hasn't done that. There are only three surviving distributions (386BSD is dead) and no new distributions look like appearing out of the fog. No experimentation = stagnation.
    6. The volume of supplied software, with many distributions of Linux, barely crams onto 4 CD's. You could fit all the BSD distributions on one CD and still have room to spare.
      1. This is nothing "bad" about BSD, but rather why I think there's a huge gap between them. It's a gap that's easily filled, if I'm right, but it's still there, at the present.
    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:Some thoughts of my own by erik+umenhofer · · Score: 1

      >BSD's installation method has not changed since the days of 386BSD....as they're more generic, but they aren't as friendly on novices.

      When I used the install it was pretty wasy and it had a nice gui type sysinstall type setup.

      >BSD is harder to obtain

      Huh? Give me an internet connection and a floppy disk and you shall have BSD.

      >Linux has =LOTS= of distributions, which means there's =LOTS= of choice and LOTS of growth

      I see this as bad! I like to know all the work is in one place. I don't want to buy 10 different version of the same OS to find what i need. (speaking of buying...forget that..ftp install!)

      >The volume of supplied software

      Your gain is our gain, It's called linux_compat! BSD can run linux binaries (among other os's) sometimes better then linux can run them! So if you complain about BSD's software base...then really linux has the problem too!

    2. Re:Some thoughts of my own by jd · · Score: 2
      *G* Never let anyone say that Open Source doesn't encourage quick bug-fixing. A whole host of problems, and all of them get fixed within the span of a few minutes! This must be an all-time record! :)

      Seriously, the *BSD distro I'm most familiar with is OpenBSD, which might as well use the original Jolitz' installation method. If FreeBSD is better, I'll give that a go and try it out. Though maybe the BSD folk should get it more widely known that some dialects of BSD have good installers.

      As for FTP install, you can do that with Linux, and grab stuff from other distros (via Alien) at the same time. What does it matter where it came from? The real advantage of multiple distros, though, is that you can focus on certain stuff. If speed is the name of the game, Stampede is going to save you a -lot- of time! If you want a low-cost embedded router, go for The Router Project's distro. And so on. With Special Interest Groups, there's not such a big demand for "other" software, it's more a case of getting the SIG software running optimally for that group.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    3. Re:Some thoughts of my own by Anonymous Coward · · Score: 0

      Wrong. I can go into CompUSA and get a BSD distro there. And I don't have any hardware that BSD doesn't like, including stuff I've bought over the last year. And BSD has six distros: Free, Net, Open, BSDI, MacOS X, plus one other I forget now.

    4. Re:Some thoughts of my own by _Sprocket_ · · Score: 2
      >BSD is harder to obtain

      Huh? Give me an internet connection and a floppy disk and you shall have BSD.

      As it was pointed out, the same can be said for Linux. But that misses the point.

      Joe newbie isn't going to set up their machine to download an OS for hours on end via their questionable MODEM connection. They want it quick and easy. A CD from a local store provides that. It also provides mindshare as they see "Linux" plastered on different shrinkwrap boxes sitting on the shelf.

      Having said that, it could be argued that this kind of user isn't BSD's target. That's probably a subject for another thread.

      The point is... you like FTP installs. I like FTP installs. But the person who's curiosity is piqued by alternative OS' is more likely to want the quick fix a credit card and a CD they pick up at the store can give them.

    5. Re:Some thoughts of my own by Anonymous Coward · · Score: 0
      Why does anyone want non-tech types using a tech system? This is Linux's mistake, and BSD's success.

      The plural of "OS" is not "OS'" you know. Sigh.

    6. Re:Some thoughts of my own by jd · · Score: 2
      Because the moment you exclude a mind, whether it be the mind of a techie or the mind of Joe Average, you lose:

      1. A potential source of inspiration. Even the most mindless of morons CAN come up with delightful and original ideas.
      2. A potential source of bug-reports. Nobody finds bugs faster than a clueless newbie, except maybe a clueless newbie fool.
      3. A potential source of bug-fixes. Every pair of eyes looking at the code is another chance at finding where the semi-colon should be. They don't need to be technicians, any more than you need to be a professional director, in order to spot where a continuity error is, in a film. It's not much different.
      4. A potential source of suggestions. Is the OS missing some feature that the techs have grown used to coding round? Is coding round the lack a good thing, or is it a waste? If nobody asks, then nobody answers.
      5. A potential source of demand. Development takes money and resources. But if all your users are also developers, you're not going to get any of that green paper circulating, to fuel the fire.
      Discrimination is an Unnecessary Evil, and should be the only thing ever burned at the stake. Nobody should be compelled to use a tech system, but if someone wants to, they should have the means to do so. If BSD is a "free" system, then it's free for all. NOWHERE in the licence does it say that BSD folk should believe in freedom for some.

      BSD, like Linux, can only survive when people truly know that it's Freedom For ALL, Regardless.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    7. Re:Some thoughts of my own by Anonymous Coward · · Score: 0

      BSD is more free for all than free for some. GPL is free only for those who follow the communists. BSD is free for everybody.

    8. Re:Some thoughts of my own by RAruler · · Score: 1

      386BSD perhaps?

      --

      --
      Insert Witty Sig Here
    9. Re:Some thoughts of my own by _peter · · Score: 1


      >no new distributions look like appearing out of the fog. No experimentation = stagnation
      The second part doesn't follow from the first; No new distributions does not indicates no experimentation.


      >You could fit all the BSD distributions on one CD and still have room to spare.
      This is patently untrue; OpenBSD alone takes up 2 CDs and has for several releases.

    10. Re:Some thoughts of my own by Anonymous Coward · · Score: 0
      >You could fit all the BSD distributions on one CD and still have room to spare.
      This is patently untrue; OpenBSD alone takes up 2 CDs and has for several releases.
      Thank you for dispelling the myth. Of course, they'll forget again in a few hours. Ever feel as though you're living Gene Wolfe's Soldier of the Mist?
    11. Re:Some thoughts of my own by Anonymous Coward · · Score: 0

      I saw freebsd at compusa the other day...

      It was 3.1 though, and 3.4 just came out.

    12. Re:Some thoughts of my own by Anonymous Coward · · Score: 0

      Don't forget that when you limit your user base, you are also automatically limiting your hardware support. If only "techies" use an OS, it will be very difficult to try and get support for all the new hardware that comes out every year...

    13. Re:Some thoughts of my own by _Sprocket_ · · Score: 2
      Damn. My Communist Party registration card must have fallen out of my Linux box. Must remember to find it and fill it in so I can continue to use Linux.

      If I were into the flame fest thing (as opposed to lame attempts at humor), I'd point out all this "red scare" stuff that comes from BSD fanatics (note the play on mascot color). Ahh well. Maybe we can herd all the Linux zealots and aim them at the BSD zealots and cancel them all out - or point the whole lot at Microsoft. :)

    14. Re:Some thoughts of my own by _Sprocket_ · · Score: 2
      Why does anyone want non-tech types using a tech system? This is Linux's mistake, and BSD's success.
      The ease of a CDRom install has nothing to do with technical merrit. One day in the near future (hopefully) we'll all have broadband connections to our homes. Then a network install will be somewhat trivial. Until then, we're stuck with a majority of people using MODEMs (lets not even get into the economic issues involved here).

      Doing a network install over a slow connection requires a good deal of dedication (both to investment of time and tying up other resources). Someone who is curious about your favorite alternative OS may not be inclined to make that investment just out of curiosity. Again, going down to the store and transfering the entire OS via a payment, sneakers, and a CD is much quicker and gets them to trying out the new environment quicker. That's good.

      It's great to see Linux enjoying this advantage. It'd be great to see BSD too.

    15. Re:Some thoughts of my own by Anonymous Coward · · Score: 0

      If you'd like to see an example of the same thing in the ranting BSD advocates, look how many times the false statement "Linux is full of BSD code" shows up in the threads. Also see the verifiable proof of its falsity, also attached to this story.

      I really wish these so called advocates (of either camp) would produce more code, and less talk.

  45. The thing to understand. by Amphigory · · Score: 5
    One thing RMS is right about is that the Linux environment is about a lot more than a kernel. It is about userspace utilities. It is about X. It is about GNOME and KDE. It's about Mozilla and Opera. It's about apache, zeus, and sendmail.

    And all of these things will run, mostly without modification, on BSD.

    Who cares which kernel is used! That's a small (but very important) part of the whole picture. The important thing is that we are rapidly developing more and more user-space stuff that will run on any modern UNIXy platform -- whether its Linux, FreeBSD, or the Hurd.

    Linux's success helps to insure BSD's long term viability. Don't forget it. From some stuff I've seen, I gather that the core *BSD teams are well aware of it.

    --
    -- Slashdot sucks.
    1. Re:The thing to understand. by bolthole · · Score: 1

      What this means, is that there is a large vacancy for a "New distribution of Linux", which would consist of X, GNOME, KDE, Mozilla, Opera, apache, zeus, sendmail, .....

      But running on FreeBSD :-)

      Anyone with too much time on their hands, a CD burner, and good BSD setup skills?

  46. expand your horizons by pope+nihil · · Score: 1

    i always figured that it would be better to be well versed in as many different operating systems as possible. that way, not only do you start to figure out which OS is best for the job, you can feel comfortable if your own company pulls a switcheroo on you.

  47. FreeBSD isn't as hyped as Linux by Anonymous Coward · · Score: 0

    The most important reason why there are many more Linux users than FreeBSD is because Linux is very much hyped. When I started with Linux in 1996, I knew only two people who used Linux and nobody else at my college ever heard of Linux back then, so there wasn't really a hype at the time. I liked Solaris very much and I wanted a UNIX machine at home, so I gave Linux a try. But these days a lot of people think it is "cool" to be a Linux user, and don't really use the basic principles of UNIX. The shell, the script-based configurations and programmability of UNIX. Corel Linux is good evidence of people wanting to be a Linux user, but don't want to learn the basic UNIX theory. FreeBSD has never been so hyped as Linux and people think it's not "fashionable" to use FreeBSD. I tried FreeBSD for some time and it's a great platform with great flexibility. But the reason I use Linux in stead of FreeBSD, is because the modularity and configurability of the kernel, the hardware-support and the maintenance. Since the beginning I use Slackware and I'm very happy with it. It was nonetheless worth trying FreeBSD, it is very stable and all programs can be compiled for it. I've tried Red Hat 4.0 to 6.1 and it's very disappointing, I like FreeBSD more than Red Hat, but I like Slackware more than FreeBSD. It's not a matter of Linux compared to FreeBSD, but more a distro-comparison.

    ps. Why are all links here red??? It's not a bug, the HTML-source says link=#990000

    1. Re:FreeBSD isn't as hyped as Linux by tweek · · Score: 1

      Well since I asked this about YRO about a month ago and got an answer, I'll give you the answer I got. Someone mark this up so maybe someone will read it and not ask the question again? ;)

      The colors are indicators of a special section of slashdot. Notice the Sections menu along the left hand side of the screen?
      Try selecting a specific section and check the colors. My favorite is the Apache section. YRO is just plain fugly though.

      The red used here is a tie-in to the bsd colors

      --
      "Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
    2. Re:FreeBSD isn't as hyped as Linux by Anonymous Coward · · Score: 0

      good call you just pretty much described all the reason im using linux. i didn't hear about linux untill about 2 years ago from a friend who was somewhat of a script kiddy. i was told that there was this cool operating system called linux and that all the 'real' programmers used. i ignored him. Then it happened, the name linux was poping up all over the place. magazines whose main focus was always 'what's cool in windows' started running articles comparing windows and linux (and they ofcourse favored windows). so after finding out more about linux a few months ago i went and ordered a copy of 'running linux' and a debian cd. i took me a few days to get used to it but im getting the hang of it and it is pretty cool. Your right that these distros that concentrate on userfriendlyness won't help people learn the workings of UNIX but most of these users probrably don't want to learn UNIX.

  48. BSD appears to load applications faster by Anonymous Coward · · Score: 0

    I am using a P200 with 64Mb of RAM. I was a Linux user and recently decided to try FreeBSD. One of the things that suprised me was it's speed. Netscape 4.7 now takes half as long to load as it did in Linux. I've also noticed that the computer swaps much faster when I load several applications at once. The only problem is with Quake.x11. It compiles (using cd_null.c and snd_null.c) but it crashes during play (with texture corruption). Apart from that, I am having no problems with FreeBSD and wish it had more support since it appears to be a lot faster than Linux (RedHat 6).

  49. Re:Linux=Incoherent; BSD=Integrated by Anonymous Coward · · Score: 1
    convincing. They either only run BSD because it's 'real' Unix
    No, we run it because the BSD distros are significantly more robust than any Linux distro. This means a lot to us. We are accustomed to a different level of testing and integration perhaps that non-Unix people. We know what a solid, connected, intuitive system, not a disconnected, hodgepodge one that feels like a patchwork quilt.
  50. The Linux Community is(was) Nicer by Anonymous Coward · · Score: 0


    The *BSD community routinely treats people who go on their channels looking for help, like they're a piece of crap

    Not unlike that jeff guy on #slashdot on irc.slashnet.org

    BSD people are beyond a doubt the rudest animals on the planet, and Linux people are rapidly sinking to their level.

    1. Re:The Linux Community is(was) Nicer by tsikora · · Score: 1

      Aw come'on there's jerks everywhere it just so happens there are more in comp.os.linux.*.
      (See... it's easy to start a war). Seriously I heard many complaints from people about this. On the other hand many FreeBSD'ers are the archtypical Unix user with zero tolerance for newbies. Myself included on occasion. Most of this attitude stems from users who refuse to read the faqs, readmes, and docs. We learned it that way why can't you. Of course I'm not like any of them.(Ha!)

      --
      -- Ted tsikora@powerusersbbs.com
    2. Re:The Linux Community is(was) Nicer by Anonymous Coward · · Score: 0

      Check out a NT newsgroup, you will find very little (if any) flaming.

    3. Re:The Linux Community is(was) Nicer by drwiii · · Score: 1
      The *BSD community routinely treats people who go on their channels looking for help, like they're a piece of crap
      Not unlike that jeff guy on #slashdot on irc.slashnet.org

      jeff may yawn alot, but I haven't seen him treat anyone like crap. Most people use IRC as a leisure tool, and if their daily job involves heavy computer use or even providing support, I doubt they'd want to do that on their off-hours as well.

    4. Re:The Linux Community is(was) Nicer by treat · · Score: 1
      The *BSD community routinely treats people who go on their channels looking for help, like they're a piece of crap

      I frequent an IRC channel that used to get a lot of people joining and asking questions (we had to set a channel key because of this). They would not usually be treated with kindness, though there were plenty of exceptions to that. They'd frequently get at least a pointer to the answer to their question, even if it was in the kick message. I've seen identical behavior on other channels, e.g. #linux.

      Here's why. First, they're not help channels. The people that are there are not trying to volunteer their time to answer anyone's questions. That's not usually fun.

      The clueless newbies answering questions is constant. Multiple times per hour, perhaps. How do constant stupid questions make you react?

      Nobody in the channel knows these people, they come out of nowhere asking for help. They ask questions that are answered in the documentation, or that a search engine could have easily found the answer to. They ask confusing or vague questions. They ask questions that show they don't have basic fundamental knowledge that nobody wants to explain to them. And these people treat the people they're asking like total crap. They want us to believe that our time is worth so little that it's better that we answer their question out of kindness, rather than them going out on their own and learning it.

      When not treated with perfect kindness, people who ask questions sometimes become incredibly angry. They make threats, try DoS attacks, etc. It gets very annoying.

      And to top it all off, not only do the clueless help-me-please babies *act* like the people in every channel they come to have a responsibility to help them, but there's people like you who almost come out and say it.

      If the people in the channel had to deal with stupid questions all day, the people begging for help on IRC make a fabulous target for the response that we've been longing to give to someone all day. This should be obvious pretty quickly, therefore if you continue to run around on IRC thinking that every channel #x is "help for newbies on x", you're hassling people that you know are in a bad mood, and that you know don't have to take any crap from you at all.

    5. Re:The Linux Community is(was) Nicer by Anonymous Coward · · Score: 0

      This sounds like the typical whining of someone who refuses to read the ample documentation provided both in the manual pages and online at www.freebsd.org.

      Always demanding free support, always refusing to read the documentation... even rejecting the help that's offered. Can it be any surprise that people aren't willing to bend over backward for someone with this attitude? (Never mind the fact that IRC channels like #freebsd aren't considered help resources in the first place.)

      Clearly the clue bird has not pooped in your hangar.

    6. Re:The Linux Community is(was) Nicer by Anonymous Coward · · Score: 0

      And in their zeal they attack even people who come in and who have read all the manuals and who have detailed descriptions of the errors they're encountering. I wouldn't have a problem with this except 1) The linux community has fraudulently swindled its way into an award for technical support. 2) They won't even tell you what IRC channel to go to for technical support. I could live with that. As I said before ... if their mothers came asking for tech support you better believe they'll give it in a heart beat and make darned sure her Linux works right.

    7. Re:The Linux Community is(was) Nicer by treat · · Score: 1
      And in their zeal they attack even people who come in and who have read all the manuals and who have detailed descriptions of the errors they're encountering.

      Yes, because it's still not a help channel, and because these people still have no obligation to help you, no matter how good your question is. Those people don't want to help you, and you should let them be.

      1) The linux community has fraudulently swindled its way into an award for technical support.

      I can see your point, I suppose. Absolutely every single time I have asked a question in the comp.os.linux.* newsgroups, I have received no help. It's probably because I only ask for help there as a last resort, so they're always fairly difficult problems. A few people will try to help, but they'll suggest things that are completely wrong, or I've already said did not work. I always go through great effort to make sure my questions are clear, concise, and include all pertinent information.

      But I have just read those groups also, and helped people in them, and people asking simple questions, or difficult questions that other people have already had to solve, do get very good help. If you ask something that's a little unusual, all the people that are intelligent enough to answer quickly aren't wasting their time with you. And all the people that could solve it with some effort aren't going to bother unless it's an interesting problem.

      The support you can get for Linux on comp.os.linux.* and mailing lists blows away any commercial Unix support I've dealt with. Consider that a scathing indictment of commercial OS support.

    8. Re:The Linux Community is(was) Nicer by Anonymous Coward · · Score: 0

      There are nice BSDers out there... you just have to ask them correctly. THey look down upon people just installing it for fun, but if you show them if you intend to really learn the soul of the OS then they will help

    9. Re:The Linux Community is(was) Nicer by Anonymous Coward · · Score: 0

      You forget. The Winix whingers can't read.

  51. BSD snobishness by mondamay · · Score: 1

    Linux included things like the DOS filesystem that the BSD kernel hackers looked on as a wart on their beautiful OS. Linux and BSD had different philosophies at the beginning, where Linux aimed to make a *NIX for the users, and BSD was shooting for the best--from the purists view--kernel. Since then, I think that you could argue that BSD has moved towards the Linux camp, with a little movement by Linux towards the BSDers (like Linux not allowing GGI).

    --
    --Last Exit To Babylon
  52. BSD rhymes with LSD by UnknownSoldier · · Score: 1

    You say jib, I say gib.

    As long as both parties know what the other person means, then pronounciation isn't [too] important.

    Cheers

    1. Re:BSD rhymes with LSD by norkakn · · Score: 1

      hmm.... i'm just a fool and have been unable to make my quad box work (free, openBSD, Redhat6.1, winblows 95[i ike games ok?]) and i think you may have hit on the solution... hmm....... well a little acid never hurt anyone

    2. Re:BSD rhymes with LSD by Anonymous Coward · · Score: 0

      Peace, Love & Compile The Kernel...

    3. Re:BSD rhymes with LSD by Anonymous Coward · · Score: 0

      3 of those CPUs will be wasted in win95 and openbsd.

      freebsd (the unstable branch, that is) will make limited use of them (similar to linux 2.0.x).

      linux (the stable branch) will make decent use of them

      linux (the unstable branch) will make good use of them.

      NT will do pretty well too.

      It might be interesting to try Solaris/x86, because the SPARC version scales very well to SMP. But all my Solaris experience has been SPARC based.

  53. Re:FreeBSD vs. Linux stability. by Zurk · · Score: 1

    Im not going to bother answering all your points but as for 1)FreeBSD aims to be a stable production exnviroment - youre wrong. Several bad implementations can be found in the FreeBSD x86 assembly code that render it unstable under certain rare conditions. In fact, Linus *rejected* these changes for Linux outright (even though they would have meant speed improvements).
    See this URL : [ http://kt.linuxcare.com/kt19991220_47.html#1 ]for one such example..others can be found elsewhere.

  54. Slashdot red instead of green? by Anonymous Coward · · Score: 0

    What is the significant of slashdot pages whose elements are red instead of the normal green? Does it indicate "hot" news or something?

    1. Re:Slashdot red instead of green? by Anonymous Coward · · Score: 0

      red is the color used on all the bsd topic articles. i think the feature and the ask slashdot articles also have there own color.

  55. Interesting: its in an Indian newspaper by gupg · · Score: 1

    I find it interesting that main stream Indian newspapers are giving thought to such geek dilemas such as why BSD is less widely used than Linux. It seems that the true test and fight of linux/unix variants versus Windows/Microsoft is going to be in Asia; China and India mainly. These are the huge markets of tomorrow with some of the highest growth rate in computer usage. Now is the time to capture market share; since it is always easier to capture market share as the market is created rather than have to take it from someone else. Also, these countries want and need inexpensive solutions; perfect for Linux marketing.

  56. Except.... by Anonymous Coward · · Score: 0

    there is no such thing as GNU/Linux. You mean Linux.

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

      And what planet orbiting a black hole are YOU from?

      King Linus gave Sir nite RMS the blessing to call GNU/Linux GNU/Linux.

      (and if you can be an AC...so can I)

    2. Re:Except.... by Anonymous Coward · · Score: 0

      Very few distributions include Linus' kernel yet are not GNU systems. Project GNU set out to create a copylefted Unix-like system, and we are using their purpose-built tools to... create copylefted Unix-like systems. Like it or not, we're finishing the very same job rms started.

  57. FreeBSD by tsikora · · Score: 1

    Damn straight! That penguin is stealing all our glory. (Just kiddin') Probably for the best. The slower(development) pace makes a far superior and stable platform. Everything about FreeBSD in my opinion is better from CVSup to sysinstall. The very concept of make buildworld/make installworld is lightyears ahead of the rest. Most importantly it demands knowledge of Unix. That alone may very well spell Linux's downfall. Linux is slowly changing but not necessarily for the better.

    --
    -- Ted tsikora@powerusersbbs.com
    1. Re:FreeBSD by Anonymous Coward · · Score: 0

      you will be assimilated. resistance is futile. your codebase will be GPLed. you will be destroyed.

  58. Its the license,s****d! by Kenneth+Stephen · · Score: 2

    No offense, but didnt you read the article? The point was not that BSD is superior or inferior to Linux. It was that fewer people are contributing to it.

    Yes, applications written for Linux may run on BSD and vice-versa. But the catch really is the license. If NT were as stable as *BSD or Linux, do you think that the development community would switch over to NT? No way - and this is because of the license.

    Note that the user community might switch over - but that isnt the point. When we talk of contributions, its the development community that we are talking about.Now, if the BSD license was changed to make a closed source distribution impossible, then you would see contributions increasing tremendously.

    PS : The story to which we are commenting is a bit confused in that the writer is unable to distinguish between the development community and the user community. Linux achieved a bigger user community because of features provided by a bigger development community.

    --

    There is no such thing as luck. Luck is nothing but an absence of bad luck.

    1. Re:Its the license,s****d! by stimuli · · Score: 2
      I agree with you to some extent, but when I talked of support for Linux and BSD, I'm thinking more along the line of applications, which will be covered by what ever licence the vendor sees fit. There is no reason there should be a Word Perfect (not open source, as it is) for Linux, but not for BSD.

      While the issue of the licence is important for kernel development, I don't see how that matters for those who will write applications that, by my estimation, should run happily on both systems.

      For open source applications it often isn't a problem -- in most cases I should be able to compile on either system with minor modification. However, for applications that are either closed-source (and thus binary only), or those which are open source, but have complex library and other environmental issues (such as something like KDE or Gnat -- the GNU Ada compiler), I hope that the makers of such software will take the time to put out a BSD version. I just don't see any reason that they shouldn't.

    2. Re:Its the license,s****d! by Pierre · · Score: 1

      Most apps are on both platforms.

      After running Linux for a couple years I installed FreeBSD and it's ports collection. I'm running KDE and Blackbox right now. I haven't found anything yet that I run on Linux that I don't have on FreeBSD. In fact it's hard to tell the difference. My debian box never crashes and neither does my freebsd box. I think this is what will hurt the BSD in the number of users department. The bulk of the users are likely using the OS as a desktop/workstation. If there isn't much of a difference and there are 5 times the number of people using Linux which do you choose?

      I don't know why more people chose Linux. Maybe the license is why more people use it. I think GPL sounds more glamorous but has it ever been an issue? Even if somebody takes code and folds it in to their program, it doesn't take the code away. It's just more people using the code.

    3. Re:Its the license,s****d! by Anonymous Coward · · Score: 0
      I read the article; I don't think the license has much to do with the difference. Linux just happened to be sexy, probably by novelty value. BSD had toddled along for years, promotion and interest had leveled off... Linus came along, had a big Usenet argument with Tannenbaum, "everyone" noticed Linux, "everyone" went off to play with it. Nobody had to sit and grok existing code; everything had to be written, it was all up for grabs, anyone could come along and contribute.

      Hope you see what I'm getting at...

      I use NetBSD myself, BTW. Largely because when I yearned for a Unix at home, it ran on the Amy and Linux didn't. Since, I've found NetBSD to be much better organised than Linux; when you say you have NetBSD-1.4.1/i386 people have half a chance of knowing what you've got.

    4. Re:Its the license,s****d! by Guy+Harris · · Score: 2
      However, for applications that are either closed-source (and thus binary only), or those which are open source, but have complex library and other environmental issues (such as something like KDE or Gnat -- the GNU Ada compiler), I hope that the makers of such software will take the time to put out a BSD version. I just don't see any reason that they shouldn't.

      Because, for the commercial software, it's Another Platform To Support, and they have to build it for the platform, test it on the platform, take support calls for the platform, etc.?

      Some vendors do have FreeBSD ports - Applix and Perforce, for example. Linux binaries of commercial products may run on FreeBSD, as well - I seem to remember Jordan Hubbard suggesting to vendors that they port to Linux first.

      As for the open-source applications, well, check out the BSD ports collection - my desktop is KDE 1.1.2, from the FreeBSD ports collection....

    5. Re:Its the license,s****d! by Anonymous Coward · · Score: 0
      Some vendors do have FreeBSD ports - Applix and Perforce, for example. Linux binaries of commercial products may run on FreeBSD, as well - I seem to remember Jordan Hubbard suggesting to vendors that they port to Linux first.

      As for the open-source applications, well, check out the BSD ports collection - my desktop is KDE 1.1.2, from the FreeBSD ports collection....

      Guy, thank you for not just this deFUDdification, but also for your years and years and years of service to our community.
    6. Re:Its the license,s****d! by Anonymous Coward · · Score: 0

      > I seem to remember Jordan Hubbard suggesting to vendors that they port to Linux first.

      Yup, makes a nice test for /usr/bin/linux that way. Kind of sucks having to use two different sets of core libraries though.

  59. Third Factor, and Addendum by MattMann · · Score: 3
    Somebody who to me sounded knowledgeable wrote a month ago, somewhere on slashdot, a third reason:

    3. Linux supported IDE long before *BSD did, and these were the inexpensive drives that the masses had.

    To that, I would add, now that Linux is way ahead,

    4. Linux is way ahead in market share, and just like the internal combustion engine, the incandescent bulb, Microsoft OSes, and other less than optimal technologies, once a product is entrenched with sales networks, R&D networks, customer support networks, etc., it takes a vast improvement in the underlying technology to overturn the economic advantage of sticking with the status quo.

    Any open sourced kernel offered just that sort of advantage over windows (to developers) and with the internet paradigm shift to vastly increase the numbers of servers, open source (especially of unix) on the commodity platform offered a compelling enough functionality jump to create the new market/new standard. But since Linux won the initial sprint, expect it to continue its hegemony. The BSDs have a chance of gaining share by being very compatible and utilizing highly transferable skills, so all is not lost for them, but things are often the way they are for many small good reasons, not by random chance, nor for one reason.

    1. Re:Third Factor, and Addendum by Bruce+Perens · · Score: 2
      But BSD had networking then. Linux didn't. So you had a choice of IDE disks or networking. I guess most people had IDE disks and no network to connect to.

      Thanks

      Bruce

    2. Re:Third Factor, and Addendum by MattMann · · Score: 2
      most people had IDE disks and no network

      I suspect you called it exactly there, but it should be pointed out that even with the availability of IDE disk and a network, the answer would still be "disk".

    3. Re:Third Factor, and Addendum by StenD · · Score: 2

      But BSD had networking then. Linux didn't. So you had a choice of IDE disks or networking. I guess most people had IDE disks and no network to connect to.

      I'm not sure when "then" was, but Linux had TCP/IP by early 1993. Trying to remember why we chose to go with Linux over 386BSD, it's a bit hazy. It wouldn't have been the IDE issue, as the systems we were looking to use with an affordable alternative to SCO initially all had SCSI drives. It wasn't failure to know about 386BSD, as Dave Burgess was right down the hall, gently evangelizing. The only thing that I can think of was the uncertainty of the USL vs BSDI lawsuit. I suppose that by the time that was settled, we had already invested enough into Linux, and showed enough progress with it, that there wasn't any reason at that point to switch horses to one of the BSD branches.

    4. Re:Third Factor, and Addendum by Skapare · · Score: 1

      FreeBSD (as of 3.1 which was released march 1999 ... I have not tested 3.4 the most recent version) appears to have limitations in the area of IDE support. Certain ATAPI devices and/or configurations do nor work and/or are not recognized to exist. Earlier discussions from advocates and at least one developer suggested lack of support was intentional because the configuration was not standard (though from reading the standards this appears not to be the case). Recent thread on comp.unix.bsd.freebsd.misc now suggests that support for all IDE is intended and succeeds for others. Perhaps device specific details are problematic.

      In a sense, you could say that BSD has not, or had not in the past, stooped down to the level of the masses. OTOH, I did notice in trying to install FreeBSD 3.1, there was some GUI orientation to the install tools. I much preferred the way SLS (how many Linux old timers go back as far as the SLS distribution) installed.

      --
      now we need to go OSS in diesel cars
    5. Re:Third Factor, and Addendum by dennisp · · Score: 2

      5) they don't have the momemtum gained from the endless hype in positioning it as an 'MS killer'

      6) a less divergent path where supporting anything and everything isn't a top priority

      7) lower key users who are less likely to advocate their OS choice

    6. Re:Third Factor, and Addendum by Anonymous Coward · · Score: 0

      too bad 7 has changed. The FreeBSD advocates have clearly transcended the Linux bigots, and are now in direct competition with the last 3 or 4 Amigans. Not since the Amiga have I seen such breathless advocacy, flaming, and absolute blindness to flaws.

      How many times have you seen the claim "But FreeBSD is more scalabale than Linux!" on slashdot? Compare Linux's SMP support to FreeBSD (use the unstable branch of FreeBSD, to make it even close to a competition). And even ignoring the massive lead Linux has on SMP, Linux will run SMP on PPC and UltraSparc too. Linux also has much better scheduling latency for SCHED_FIFO processes, making it more useful as an interactive workstation and for multimedia.

      Of course, if I'm installing a firewall, there is no question that it'll be OpenBSD (for security reasons, and bpf, which linux lacks). A small to medium sized webserver will be FreeBSD (A large one would be either a farm of FreeBSD, Linux or Solaris machines. With the redundancy of a cluster of servers, the OS choice is much less important).

      Breathless and unwavering *BSD advocacy is just as stupid as breathless and unwavering advocacy of anything. And unfortunately, such extreme stupidity reflects poorly on Free OSes as a whole.

  60. and BSDers are nastier thane Linuxers by Anonymous Coward · · Score: 1

    Really. When I started casting about for a substitute to Win31 or DOS/Minuet, I tried to download a floppy image of BSD.

    The response when I tried to ftp it? "Go away, stupid WinBlows lamer." "Fuck off, gates." I finally got an image on floppy, it wouldn't boot. Last experience with it.

    By then, Barkakati's flame book arrived, everything worked first off. Been using Linux ever since. Even wrote some stuff under the GPL, but mostly using it as an NT replacement for printer and modem serving.

    Might look at BSD again, if php4/apache works under it, but most probably, I'll just get a modern video card and give BeOS a spin.

    1. Re:and BSDers are nastier thane Linuxers by Anonymous Coward · · Score: 0

      I've always found the Linux-advocates much nastier than the BSD ones.

      Not that they would sway my choice in OS. Its just an oberservation.

    2. Re:and BSDers are nastier thane Linuxers by Anonymous Coward · · Score: 0

      Take a look in this thread for repeated counter-examples.

  61. *BSD, various distributions of Linux(TM), etc. by crimsun · · Score: 2

    I will attempt not to fall into the dreaded "*BSD vs. various distributions of Linux" flamebait here. Here's my story:

    I'm still primarily a NT user. Why? Better IDE, more game support and more robust (not to mention widespread) hardware support. However, many, many moons ago I began the Slackware trek. Its simplicity and stability (courtesy of Linus's kernel, of course) really impressed me. I installed a few servers out of curiosity and promptly forgot about them. Four or five months later I realized that they were still running strong (given the requisite `kill ` that one must force on some runaway thread). This was utterly positive; I was used to checking my computers daily to ensure they were still running. Additionally, I noticed that performance wasn't hampered as much as under NT when more users connected or accessed the mounts. Thus, Linux became the fileserver OS.

    A few short months later I installed my first copy of FreeBSD (2.7?), again, just out of curiosity. I setup ircd, nfsd, a few other daemons and went on vacation. When I returned, needless to say, ircd (known for its uncanny ability to split) was still running. Of course the other parts of the installation were doing just fine. So when I was called to do a security-apparent job, I tried OpenBSD. Perhaps I was entrigued by the entire "secure by default" mentality (or was it the line-by-line auditing? ;-). Needless to say, that box is still running Open (uptime is nearly 500 days!), and I'm rather impressed by its ability to simply reject repeated exploits and intrusions.

    Linux has never failed me, nor has *BSD. My limited experience does not qualify me to say that *BSD is any more able to handle mission-critical jobs than Linux, but I will say this: the degree of success that surrounds Walnut Creek is simply amazing. If a site that handles unimaginable daily traffic can withstand attacks and impatient ftp'ers, then I can trust its mission-critical status.

    I now use two primary machines: a FreeBSD 3.4 (just made world a few nights ago! ;-) machine for the "good stuff" and a NT4 machine for gaming.

  62. Some thoughts on Some thoughts of my own by raytracer · · Score: 1

    1. It is true that the original 386BSD was hampered somewhat by the Jolitz' attempt to control development. That was pretty much over by the time FreeBSD entered the scene though.

    2. Installation of FreeBSD is quite a bit slicker than all but the most recent versions of Linux. Various Linux distributors have obviously made this a high priority, so it is improving for them.

    3. Over the years, I've found FreeBSD's hardware support to lag Linux a bit, but I've had some problems with supposedly debugged support under Linux as well. I've found that FreeBSD supports virtually all the hardware I have, but your mileage may vary as your equipment does.

    4. Linux certainly is easier to obtain. I used burn CDs for anyone I knew who wanted to try FreeBSD. Some FreeBSD people I know thought this was a bad idea, that if you wanted FreeBSD you should order the CDs from Walnut Creek to support the project. While I certainly urge people to do that if they find FreeBSD useful, I think it was shortsighted to insist on that. If someone doesn't try FreeBSD, they aren't going to contribute monetarilly or with their programming effort to make it better. Therefore our goal should be to get as many people to try FreeBSD as possible.

    Recently ISOs of the FreeBSD distribution have begun to show up more widely, which makes it easier for people to try it. I think this is a good thing. OpenBSD has not yet adopted this mentality, which is in my opinion at least partially responsible for its rather limited popularity (it also has a relatively unkind installation process, which is another).



    5. Linux does have lots of distributions. I'm not sure that this is a good thing. Most are either of poor quality or simple rehashes of other distributions. The plethora of distributions means plethoras of problems for the most part, as different kernel, config and packaging options make knowledge of one distribution less useful.

    To be fair, BSD suffers from similar divergence amongst its three major distributions as well.

    6. FreeBSD ships on 4 CDs. They are pretty full. Very little software available for Linux is not available on FreeBSD.

    I don't think there is a huge gap. I think the various Linux vendors are a bit further down the road in creating distributions that even novice users can install and use. Given the vast amount of money raised in various Linux IPOs, I don't expect that FreeBSD will close the gap quickly.

    1. Re:Some thoughts on Some thoughts of my own by Trashman · · Score: 1

      Recently ISOs of the FreeBSD distribution have begun to show up more widely, which makes it easier for people to try it.

      And where exactly may I find these iso's? I poked around freebsd.org and couldn't find anything.

      --
      Do not read this .sig
  63. Common misconception by Bruce+Perens · · Score: 2
    You are making a common misconception. The GPL does not tell a copyright holder what to do with his own code. The copyright holder can always issue his own code under any license, place his own code into the public domain, etc. It is only other people than the copyright holder to whom the GPL applies. It only tells people what they may do with other people's code.

    Thanks

    Bruce

    1. Re:Common misconception by Anonymous Coward · · Score: 0

      If person x spends 40 hours writing program X.

      If person y spends 1000 hours writing program XY using X as a base.

      If direct extension of person x's effort, person y must keep his code GPL'd. Person y's code is his own code. He is not free to do what he wants with his own code.

    2. Re:Common misconception by Anonymous Coward · · Score: 0

      If person y hates the GPL, then person y is a fucking idiot for using person x's code. Even assuming this idiotic situation happens, person y can rip out person x's code, and spend the 40 hours rewriting it.

      Your last sentance is a simple lie. person y is free to do whatever he or she wants with their own code, including releasing it under PYSL(person y's super license). Person y is not, of course, free to do whatever he or she wants with person x's code, but person y's 1000 hours of code are person y's to do with as he or she pleases.

      Your attempts to emotionally obfuscate the argument to advance your own irrational anti-GPL agenda are disgusting. No one forces anyone to use GPLed code in their projects. And the duplication of effort to rewrite GPLed code for a BSD project is no more than the duplicated effort to rewrite additions to BSD code that have been taken propreitary.

    3. Re:Common misconception by cjs · · Score: 2

      he GPL does not tell a copyright holder what to do with his own code.
      Well, obviously what I'm saying is that the GPL tells you what to do with your code should you try to combine it with any GPL'd code.

      This makes the GPL different from other free software licenses in that the GPL is a weapon: its purpose is to help Stallman in his fight to purge the world of all non-GNU software. (Yes, all, including other free software. Read his disucssion of the readline library and the LGPL if you don't believe me.)

      I don't mind the GNU license otherwise, but the stance against pluralism really disturbs me. And even if I accepted the argument some people make that Stallman's really only out to get proprietary software, his willingness for free software to be collateral damage in that war is just as bad.

      cjs

      --
      The world's most portable OS: http://www.netbsd.org.
    4. Re:Common misconception by Arandir · · Score: 2

      You misunderstood the comment. If I write an extension to gcc, and that extension is 100% my own code, I am still required to use the GPL. BSDL folks have little problem with those who wish to keep their own personal source code GPLd forever. But it's a very different thing to require distinct code be under the same license.

      Think of how pissed the GNU community would be if BSD had similar clauses. There would probably be an article at GNU describing such a thing as obnoxious.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  64. Why I use Linux instead of *BSD by SoftwareJanitor · · Score: 2

    Let me start off by saying that my first exposure to *nix was 4.2BSD on a VAX-11/780 back in 1985. I spent the remainder of the 1980's using 4.2, 4.3 and 4.3-Tahoe on various VAXen as well as SunOS on Sun 3's. While I also played with other UNIXes such as Ultrix, HP/UX, A/UX, Xenix, Venix and AT&T SVR2 and SVR3 in those days, BSD was my primary platform.
    In the early 1990's I spent a lot of time with various SVR3 derived commercial UNIXes including Motorola's SVR3 on 88000 machines and AIX on RT's and RS/6000's. While still *nix, I pined for a lot of things that were missing compared to BSD. By late 1992 I was back to SunOS 4.1.x on Sparc which was more to my liking.
    The main reason I chose Linux over *BSD is back in 1993 when *BSD and Linux were first coming to my attention and I was able to scrape together enough cast-off parts and $$$ to hack together a decent enough box (a 386DX-20) to run them, I couldn't get *BSD to run on the junk hardware I had. Linux, on the other hand worked. With the olvwm window manager I was astounded how well it made a clunky PC look and act like a SparcStation running SunOS.
    Nowdays I use Solaris on Sparc at work (and some at home, although my primary home platform is Linux and my home SparcStations are all old and slow models) and I could afford to run *BSD as well as Linux at home (I've got dozens of machines), and I do occasionally load one of the *BSDs onto a box to see how things are coming along. I really have nothing against *BSD. If Linux didn't exist, or if it ever somehow falls apart, I will certainly look at switching to one of the *BSDs.
    But I have to say that Linux for me has the comfort level now, after six years, I've spent more time with it than any other *nix family. Every time I have tried the *BSDs lately, I just haven't been able to find a compelling reason that would lead me to pick one of them over Linux. Linux still seems to have a better combination of hardware support, easier installation and wider software availability. Mind that the *BSDs aren't really that far behind, but without any real compelling advantage, it is just enough of a subtle turnoff to keep me complacent.

    Well, there it is, just one person's opinion. Take it for what it's worth and with a grain or three of salt.

  65. BSD vs. Linux by jormurgandr · · Score: 1

    Personally, I use Linux. That is mainly because I am interested in kernel programming, and I like the idea of getting the source code to every app on my system. However, I think BSD has a few good ideas. It's great that a company can come along and take an operating system, pay nothing for it, change it to make it (hopefully) work better and provide some new feature or service that was previously unavailable (Example (kinda), the OpenGL X-server that was recently released). This is great not only for the *nix world, but also for developers. I think I might be installing BSD soon just to give it a try.
    =======
    There was never a genius without a tincture of madness.

    1. Re:BSD vs. Linux by Guy+Harris · · Score: 2
      Personally, I use Linux. That is mainly because I am interested in kernel programming, and I like the idea of getting the source code to every app on my system.

      I also am a kernel programmer, and like getting the source code to all components of my system.

      The OS most often running on my home machine is FreeBSD. I have full source code to the kernel and to all components of my system.

      Liking the idea of getting the source code to every app on your system is not a reason to prefer a Linux distribution to {Free,Net,Open}BSD; it's a reason to prefer an open-source OS - such as a Linux distribution or {Free,Net,Open}BSD - to a closed-source OS.

      (Note also that having Linux is not only not necessary if you want source to every app on your system, it's not sufficient, either - you have to avoid installing third-party apps that aren't open-source, which are available for Linux and {Free,Net,Open}BSD as well as for closed-source OSes.)

  66. *BSD File System by Anonymous Coward · · Score: 0

    What type of file systems does *BSD use? The last time I used it (FreeBSD 3.0) it still used a plain old UFS with no logging or journaling. While FreeBSD is very fast (faster than Linux and perhaps also Solaris on a single processor) the reliability of an enhanced file system is very important on servers. I don't have a half hour to wait for fsck to complete. So for now, I still use Solaris on all of our servers.

    1. Re:*BSD File System by NovaX · · Score: 2

      Generally BSD used UFS, but free varients are now incorperating SoftUpdates into the filesystem. I've been told that for the most part, UFS is slightly slower than ext2, but safer. The main reason is because ext2 doesn't sync as often, though both can be tweaked either for the speed or for the safety. Softupdates will do the same as a JFS for Linux, so both systems can have safe and speedy filesystems.

      I haven't seen to much of an explanation of softupdates, only on McKusick's page.

      --

      "Open Source?" - Press any key to continue
    2. Re:*BSD File System by Anonymous Coward · · Score: 0

      um, what file system does Solaris use? what does your vfstab say?

      if you're so concerned about journalling why aren't you using jfs on AIX or xfs on SGI?

      if you want to reduce fsck times, decrease the number of inodes.

      although it hasn't happened to me, I've seen more data loss off a crashed ext2 filesystem than ufs.

      --clark

    3. Re:*BSD File System by Anonymous Coward · · Score: 0

      ext2 is much slower than ffs for certain kinds of operations: searching large directories.

    4. Re:*BSD File System by Guy+Harris · · Score: 2
      um, what file system does Solaris use? what does your vfstab say?

      ...ufs...logging, perhaps? (I.e., UFS with journaling enabled?) To quote the Solaris 7 "mount_ufs" man page (fetched from Sun's online documentation collection; unfortunately, the URLs look suspiciously like per-session URLs, so I'm loath to put them in the article, but go to "Solaris 7", then go to "Solaris 7 Reference Manual Collection", then go to "man Pages(1M): System Administration Commands", and it's under there):

      logging | nologging

      If logging is specified, then logging is enabled for the duration of the mounted file system. Logging is the process of storing transactions (changes that make up a complete UFS operation) in a log before the transactions are applied to the file system. Once a transaction is stored, the transaction can be applied to the file system later. This prevents file systems from becoming inconsistent, therefore eliminating the need to run fsck. And, because fsck can be bypassed, logging reduces the time required to reboot a system if it crashes, or after an unclean halt. The default behavior is nologging.

      I.e., perhaps he's using a journaling UFS.

  67. Not fighting Microsoft by Anonymous Coward · · Score: 0

    BSD doesn't purport to try to fight with Bill Gates. They just peacefully go on doing their own thing. You don't see Rolex trying to compete with Casio, either. Linux, on the other hand, has attracted so many Windows users that you see them trying to turn Linux into Windows. This just provokes the experienced users. It's not called Winix for nothing, you know. BSD doesn't bother with such fluffenstuff. They have no interest in fighting Microsoft, or getting your grandma to use BSD. They're much more realistic.

  68. it's not the license by arielb · · Score: 1

    if it was simply because of the license then how come more people use apache (bsd license) than any other GPL server?

    --
    ---
  69. 1 million vs. 10 million by SRT · · Score: 1

    In my experience people tend to graduate from Linux to *BSD once they've gotten their feet wet. Has anyone else experienced this?

    I base this not only on my own past, but many others I've spoken with.

    "Waiting for that OpenBSD IPO!!"
    Scott

    1. Re:1 million vs. 10 million by Guy+Harris · · Score: 2
      In my experience people tend to graduate from Linux to *BSD once they've gotten their feet wet. Has anyone else experienced this?

      No, not particularly. I know a number of people who've been using various Linux distributions for quite a while - i.e., they haven't "graduated from Linux to *BSD" - and people who've been using BSD for a while, but haven't personally seen a significant amount of movement in either direction.

      I'd like to see a very broad survey before I drew any conclusions about people moving from Linux to *BSD. The evidence people have presented seems largely anecdotal....

    2. Re:1 million vs. 10 million by rapett0 · · Score: 1

      I have seen that happen more then once. Many of the UK sysadm have gone from other unisys to FreeBSD when the dust settled.

    3. Re:1 million vs. 10 million by Anonymous Coward · · Score: 0

      I've seen that happen a lot, but I wouldn't call it "graduate." The motivations tend to be that Linux has gotten too mainstream and popular, so the uber-geeks all go to freebsd. I suppose NetBSD is next when FreeBSD gets too popular. And from there, to the best (IMHO) BSD, OpenBSD.

      Oh well, there are the sheep, and then those who are sheeplike by being the anti-sheep. Who cares. just use what works.

  70. Timeline by core · · Score: 2

    For the various posts that seem to be interested in the BSD release timeline, here is how it went:

    1977: 1BSD (based on UNIX time-sharing system sixth edition from Bell)
    1978: 2BSD (based on 1BSD)
    1979: 3BSD (based on 2BSD and 32V which itself was derived from unix seventh edition)
    mid-79: 4.0BSD (derived from 3BSD)
    1981: 4.1BSD (derived from 4.0BSD)
    1982: 4.1aBSD
    1983: 4.1cBSD (not based on System V)
    1984: 4.2BSD (not based on System V release 2); SunOS is based on it.
    1986: 4.3BSD
    1988: 4.3BSD-Tahoe
    1990: 4.3BSD-Reno
    1991: NET/2 (386BSD spun from it)
    mid-1992: NetBSD 0.8 spawns from NET/2
    1993: FreeBSD 1.0 spins from 386BSD as well
    mid-1993: 4.4BSD
    1994: 4.4BSD lite 1
    1995: FreeBSD 2.0, 4.4BSD Lite-2, BSDI 2.0 spin from 4.4BSD lite 1

    Note that I'm a linux person, so don't hold me accountable for those dates :) Rather trust the book "the design and implementation of the 4.4BSD operating system" by marshall kirk mckusick et al.

    Linux of course appeared in 1991.

  71. Don't forget that Brent Glass fuckhead by Anonymous Coward · · Score: 0

    'nuff said.

    1. Re:Don't forget that Brent Glass fuckhead by Anonymous Coward · · Score: 0

      good point. Fuck you Brent.

    2. Re:Don't forget that Brent Glass fuckhead by Anonymous Coward · · Score: 0

      Ah, I get the theme here. Anyone who doesn't kiss Stallman's ass can die, eh?

    3. Re:Don't forget that Brent Glass fuckhead by Anonymous Coward · · Score: 0

      you got it cock goblin. RMS is my Lord.

    4. Re:Don't forget that Brent Glass fuckhead by Anonymous Coward · · Score: 0

      oh, you guys are really smart. Doubt you even know who they are... as its Brett, dumbass.

      And of I've met Linux gurus just as obsessed as Tom and Brett, and don't tell me that Bruce Peren's can't be annoying either or ESR for that matter, especially since their opinions with licenses effect OSI, and are not just personal belief.. and OSI's claims are taken to always be pure fact by the GPL community. Both act like philosophers, yet neither have the background knowledge.

      So you know.. don't flame, just try to mold them politly to be better and more efficent (and more factual).

    5. Re:Don't forget that Brent Glass fuckhead by Anonymous Coward · · Score: 0
      It's so sad that you so despise your own member. Your consistent remarks betray your negative obsession with your own organ (and the whole world). Shall we hand you the knive, or did you already vivisect it?

      You sure bitch a lot about people who've contributed their own time and energy. What the fuck did you ever do, and why are you so homophobic?

  72. Re:Linux=Incoherent; BSD=Integrated by law · · Score: 1

    What the flying fuck does this have to do about Linux?
    If you think somthing is a "hodgepodge" it the distro's not "Linux"

    EG
    Debian is not a "hodgepodge" it is not "insecure"
    My two favorite BSDisms. Robust can be argued, maybe.

    If I install or configure any Unix based system poorly. It will be insecure. Linux, BSD, even NT.

    I don't critize BSD, but then again I don't use BSD ethier. If you use these kind of arguments, your doing BSD a DISERVICE!

    Badly reasoned argments make me disbelieve that person's cause.

    --
    "Think of it as evolution in action."
  73. Life _is_ fair by Kenneth+Stephen · · Score: 2

    You missed out the most important reason : the BSD licence.

    Think about it : the Linux developers are just as smart as the BSD developers. The BSD movement also had the advantage that they were a mature operating system at the time Linux was a blip on the horizon. So why didnt the BSD movement gain as many developers as Linux did? Simply because the license was unattractive to them.

    Some people also say that the centralized committee nature of BSD is a detractment. Bosh! Linux also has the same committee nature where a patch doesnt appear in a distribution unless it has been blessed by the core developers and / or Linus. The only difference is that this committee is not as formalized as the *BSD committees.

    --

    There is no such thing as luck. Luck is nothing but an absence of bad luck.

    1. Re:Life _is_ fair by Spamizbad · · Score: 1

      Well... here's how I look at it.

      GPL = Good for the developer
      BSD = Good for the 3rd party source

      Who writes MOST of the software? The developer.
      Who is going to fix the most bugs? The developer.
      Who will in the end, probably write most of the drivers? The developer.

      With linux expanding, and more commericial organizations being involved in it, some say the BSD license would be better then the GPL.... This may be true but Linux NEEDED the GPL to get where it was.

      The GPL wasn't the only element, the posts above states what else it has.

      Everybody knows the major linux people, what about BSD.... it's just "oh-whats-his-name".

      Yes, FreeBSD is more stable, but Linux is something new, something fresh, something with new ideas and innovations. People like new. It comes down to that. Linux offered a new stable alternative to windows, it was easy to rally around, and you felt proud as a user and and/or as a developer of it.

      Linux filled the gap between BSD and Microsoft. Not a traditional Unix (Linux isn't very unixy). This is exactly what needed to be done.

    2. Re:Life _is_ fair by Anonymous Coward · · Score: 0

      This licence thing is overstated. No BSD project wants proprietary software included. They only give in when they've no other choice, such as with gcc.

    3. Re:Life _is_ fair by Anonymous Coward · · Score: 0
      Linux filled the gap between BSD and Microsoft.
      Welcome to the brave new world of Winix. Don't forget to flush.
    4. Re:Life _is_ fair by Kenneth+Stephen · · Score: 1

      First of all, get your facts straight : gcc is not proprietary.

      Secondly, the *BSD's do have a choice. Nobody forced them to use GCC. They always have the option of writing a compiler with the BSD license. The fact that none of the compiler writers have done so speaks for the popularity of the BSD license.

      --

      There is no such thing as luck. Luck is nothing but an absence of bad luck.

    5. Re:Life _is_ fair by Anonymous Coward · · Score: 0
      Sigh. You can reuse the source, learn from it, and fix it. Are you seriously claiming you think of it as proprietary because proprietary derived works aren't permitted? Must I die before I can be said to have lived?

      BSDL'd software hasn't been freed, it's just free for the moment.

      As for embrace and extend, that's what -ansi -pedantic -Wall is for. You have RTFM, right?

    6. Re:Life _is_ fair by Anonymous Coward · · Score: 0
      SDL'd software hasn't been freed, it's just free for the moment.
      Here come the FSF lies again. Don't you guys ever get enough?

      BSDL'd code is free now and it's free forever. It's permanently free. It's merely not viral. Get a clue.

    7. Re:Life _is_ fair by Anonymous Coward · · Score: 0

      The VSF doesn't believe in FMs.

    8. Re:Life _is_ fair by Guy+Harris · · Score: 2
      Yes, FreeBSD is more stable, but Linux is something new, something fresh, something with new ideas and innovations.

      Does anybody have any data from a careful study of both the open-source BSD kernels and of the Linux kernel, or of both the open-source BSD OSes and the open-source components of Linux distributions, to indicate that "new ideas and innovations" are present in Linux to an extent significantly greater than the extent to which they're present in the open-source BSDs?

      (Linux isn't very unixy)

      Could you please justify that assertion with facts? When I log onto a Linux system, it sure as hell looks as much like a "Unix system" to me as do FreeBSD or Solaris or HP-UX or Digital UNIX or....

    9. Re:Life _is_ fair by pwileyii · · Score: 1

      I think 'unixy' is meant to say that linux has all these spiffy graphical utilities to configure things where UNIX has configuration files that you edit and that's it. Yes, Linux also has these, but look at linuxconf, it is not what I would call very 'unixy.'

    10. Re:Life _is_ fair by Anonymous Coward · · Score: 0
      Does anybody have any data from a careful study of both the open-source BSD kernels and of the Linux kernel, or of both the open-source BSD OSes and the open-source components of Linux distributions, to indicate that "new ideas and innovations" are present in Linux to an extent significantly greater than the extent to which they're present in the open-source BSDs?
      More deFUDding. Hurray!

      This man is a true gem, the likes of which are excruciatingly seldom seen anymore. His postings are worth 100 from most anyone else. Listen to what he has to say. He was helping people when most of you were in diapers.

      And he's right.

    11. Re:Life _is_ fair by Anonymous Coward · · Score: 0

      > It's merely not viral. Get a clue. Neither is the GPL. I really wish you BSD bigots would stop playing this silly game. If you want to use someone else's code, you respect their wishes. If you don't want to, don't use it. There's nothing viral about it ... Is that so fucking hard to understand? And don't bother whining about how unfair it is that BSD code can be GPLed, but it cannot flow back the other way. That was your choice of license - you brag about how commercial organisations take your code slap their own license on it, but GPL it and ... jihad! Bloody hypocrites.

    12. Re:Life _is_ fair by Anonymous Coward · · Score: 0

      And you Viral Software Freaks can take your infectiously propietary libraries and stop trying to tell people how to live their lives. I'd rather have Pat Robertson at my door than you.

    13. Re:Life _is_ fair by Anonymous Coward · · Score: 0

      I looked at Linuxconf awhile ago. It made me ill.

      Then I decided "the hell with it" and went to edit config files the way I used to.

      I discovered how badly Linuxconf had kludged up the /etc directory struture.

      So I blew it all away and went back to Slackware.

      Lately I've discovered that NetBSD is Slackware-like, but even better at what's good in Slackware.

      Keeping a few Linux boxes around is okay, but it's certainly not the path forward. Unless your main aim is 'defeating Microsoft' whatever the hell that means in the end.

    14. Re:Life _is_ fair by Anonymous Coward · · Score: 0

      As long as we're deFUDing, I'm amazed that the "freebsd is more stable than linux" comment passed by. Repeated statements don't constitute a proof, regardless of the desires of the sayers.

  74. Article Title is a Fallacy by Overt+Coward · · Score: 1
    The article pre-supposes that Linux is more "popular" than BSD. The real question should be for what group is it more popular -- the majority of both the Linux and BSD user communities are still programmers. For many reasons (as specified in other responses) Linux seems to be more popular among them.

    However, because of the ability for a company to make a proprietary fork of BSD code, I would wager that there are more copies of software out there that owes their origins to BSD than there are for the GPL.

    So, really, "popular" to whom? Developers or end users?

    --

  75. I use Linux because... by Anonymous Coward · · Score: 0

    ... I heard about it first. I like to write programs for my own amusement and education, and I find the Unix environment far more friendly (with its powerful tools such as awk and find) than DOS/Windows/NT with it's lame attempts at sort, fgrep, etc. In NT (at my local astronomy club) I can't even get the command line window to occupy the full screen! I'm not a kernel hacker or anything, and I don't see much difference between Linux and BSD. As far as I'm concerned, they're all Unix and I wish them both well. If BSD uses the C shell as its standard shell then that would be a serious drawback, but you could probably run bash if you wanted to.

    If the Linux and BSD developers were smart, they'd steal each other's best ideas, to the benefit of both systems, rather than worrying about which was the better Unix system.

    --- Brian

  76. because linux rules and bsd cant match it by Anonymous Coward · · Score: 0

    its simple, get it through your thick heads.

    linux kicks the crap out of bsd and thats just a fact.

    who wants to use a secondrate, pathetic hack like freebsd when they can use redhat linux?

    linux has superior security, network code, stability and SMP. in fact bsd idiots steal our code alot because they cant code for shit.

    fuck you bsd, linux 0wnz your ass

    1. Re:because linux rules and bsd cant match it by Anonymous Coward · · Score: 0

      And its comments like that which have people shake thier heads and click their tounges.

    2. Re:because linux rules and bsd cant match it by Anonymous Coward · · Score: 0

      Yes ladies and gentlemen! Your average Linux users! Lets give him a round of applause!

  77. Hippies by Ross+C.+Brackett · · Score: 1

    If people were OSs, BSD would be an accountant. Efficient, not too fancy, to the point, and not opposed to a little blatant capitalism from time to time as long as it got things done. Linux (and a lot of other GNU stuff), on the other hand is a genius hippie. Long haired, occasionally bong-hitting, Lennon-listening cool guy who happens to be a math whiz and plays concert piano. He may not get the job done as well as the first guy, but he's a lot more fun to hang out with!

    Okay bad metaphor. My point is that I think the success of Linux is possibly due to the fact that the Linux community is a little bit funky. And I like that. And I think a lot of people like that. For instance, user support is like being lost and asking a hippie for directions. He won't try to sell you a map, or instead give you directions to a store where he's trying to sell you something. True, the directions might be a little odd, and he might smell a little funny, but it's okay, because as they said at Woodstock, we're all feeding each other.

    What mystifies me is how big business is suddenly interested in Linux. I feel as if they've been bamboozled, but in a good way, like actually getting a pig elected to President. If big business actually knew what was good for them, they would adopt BSD like gangbusters. Big companies like things like restrictive licensing, being mean, and other things the BSD license permits them. But amazingly they've adopted Linux, and now Linux is beginning, in a good way, to corrupt those companies from the inside.

    Well I say nee-haw. Advocacy has paid off, and I say we take the money and run. If Redhat and other companies want to spend millions on producing high-quality GPLed software, I say right on. Free software will never collapse. It will never be un-useful. As long as we're true in our hearts and we code like madmen, the GPL will protect us, and that's exciting. That's why people fall in Linux, and that's why I fell in love with Linux.

    [This groggy Monday morning rant was brought to you by Coffee, or rather the lack thereof.]

  78. Distributions... by Lazy+Jones · · Score: 1

    One of the reasons why *BSD is lagging behind in popularity is certainly the lack of a well-known commercial distribution with the advertising, support and non-proficient-user-friendliness. Red Hat FreeBSD or SuSE FreeBSD would make a difference...

    --
    "I love my job, but I hate talking to people like you" (Freddie Mercury)
  79. Early on... by Rob+Riggs · · Score: 1

    It seems that many of the posters here are relatively new to Linux. But, as someone who was in the market for a Unix-like OS in 1994, I can tell you that "the communities" were the most important factors in the decision of which OS to use. The Linux community was so utterly helpful that it was hard not to use it. A visit to #linux on EFNET would answer just about any question that anyone would have. And just watching the enthusiasm of the group was awe-inspiring.

    On the other hand, the BSD users were the entrenched, holier-than-thou, get-outta-my-face-you-stinkin-newbie "gurus" who needed to deride the less knowledgeable in order to feel adequate. It was not a fun experience to be on the receiving end of the *BSD crowd in those days. The BSD crowd today is far different -- a really bright and helpful bunch. But the early days of the movement really hurt. It will haunt the BSD community for a long time to come.

    The fact that Linux now has the largest market share and the strongest momentum is due to the outrageously helpful member of the community early on. This sense of community and willingness to help was inspired by the kernel developers themselves. Back when the daily volume on the linux-kernel list was under 30 messages a day (imagine!) it was quite common for the developers to very gently point the newbies in the right direction when they asked for help. ("This list is for kernel development... I'm sure if you ask on 'linux-foo' you're question will be answered.")

    I just want to thank the Linux community for being such a helpful bunch. The early developers and users have inspired a large number of people (myself included) to continue the tradition of evangelizing the OS and helping the newbies get on their feet.

    --
    the growth in cynicism and rebellion has not been without cause
    1. Re:Early on... by Anonymous Coward · · Score: 0

      I am sorry.... I was a fanatic linux user till 3 months ago. I didn't switch to FreeBSD because linux was not good enough or because it was not cutting it..... Frankly i was super satisfied with Linux except with the god damned ext2 FS which tended to destroy any HD it used to touch....(just personal experience. I never heard anyone else with the same problems but it literally ate up 3 HDD's 1Fujitsu and two quantum's). I decided to try FreeBSD just out of curiosity and to learn something new. I often heard that the BSD-ers were usually not helpfull. The first thing i had problems with was with my soundblaster. I jumped in #freebsd on efnet and i was very suprised. The guys there guided me STEP by STEP to make my sound card working. They never let go till i had it all working. On the other hand the "gurus" in #linux: 1: half the times they know jackshit of what goes on. Besides some trivial questions of "how do i install lilo" and "how to i configure X" advanced questions go unanswered. 2: They are becoming more and more like what they call BSD-ers (i.e snobby ass*s) While for a total newbie the channel might be helpfull for a bit more advanced users they are useless.... Mind you that i am speaking ONLY from the 4-5 times i tried to get help from #linux so i might be totally biased. But i got much more helpfull answers from the BSD folks than the linux folks. And this is STRICTLY on irc mind you. The linux HOWTO databse is simply...well.... UNBEATABLE and i comment the Linux community for them... Extremely impressive indeed. But before shouting that the BSD folks are snobish jump on #freebsd on efnet first and talk to them. I found them MUCH MUCH more helpfull than the kiddies in #linux......

    2. Re:Early on... by Anonymous Coward · · Score: 0

      #linux is one of those terrible buttholes in the universe. this alone turned me away from linux forever.

  80. who cares about popularity by Anonymous Coward · · Score: 0
    bsd users are not sitting on the edge of our seats biting our fingernails worrying about the results of some popularity contest. who gives a shit if linux has 10 million wankers using it? look at how many morons use microsoft windows! is windows any better as a result of how many people use it?

    linux users often mirror the mentality of windows users. "windows(or linux) has more drivers, more games..." fine, use it then. the bsd community doesn't give a shit. people who think like that are not likely to make a valuable contribution to the community anyhow.

    i hope you linux weenies end up with the most popular operating system ever. it shouldn't be hard to usurp windows once linux gets all the popular commercial apps ported over. then windows users own mentailty will ensure that they choose linux because it will be the "most popular".

    bedwetters...

  81. You smoking crack??? by fr0g · · Score: 1

    Commercial? Have you never see www.bsd.org?

    1. Re:You smoking crack??? by Lazy+Jones · · Score: 1

      Commercial as in "free software backed by a company such as Red Hat".

      --
      "I love my job, but I hate talking to people like you" (Freddie Mercury)
  82. Linux has one major advantage. by kavi_3 · · Score: 1

    Linux has one major advantage over BSD in that Linux modifications happen faster then BSD modifications. The reasons I see for this is a different mindset between people who work on Linux and people who work on BSD and the difference between the GPL and BSD licenses.

    In the Linux world, if a feature is needed, it is added pretty quickly and any problems that arise are fixed when they are found. People don't try to make the software perfect, they just try to make it do what they need it to do. Other people likely to take the isk of using the new feature, because with the source code, they can fix anything that causes a problem, then these fixes are given back to due to the GPL and all will benefit from them. Therefore .many features are more readlily adopted.

    In BSD, things happen slowley because the people working on it are more concerned with sercurity and stability. While this allows them to create some very reliable systems, it slows the development of the OS so that it is always lagginf behind in features. Also, if someone does make a good change or add an important feature, they could always keep it and not share it, so these features will be adopted slowly.

    The end result is that Linux, while more prone to problem when using the latest and greatest kernal/library/etc, it more quickely adopts features that user want and need.

    For the desktop, I think that the Linux model is better, and for servers the BSD model is better. But that can be overcome by using an older and more stable versioin of Linux (most people with production Linux servers so this.)

    --
    "Attention Citizens, 2+2 now equals 3.947547175. Please recalibrate your equipment now" --The Computer
    1. Re:Linux has one major advantage. by Guy+Harris · · Score: 2
      Other people likely to take the isk of using the new feature, because with the source code, they can fix anything that causes a problem

      ...which would also be true of {Free,Open,Net}BSD, as you have the source code.

      then these fixes are given back to due to the GPL and all will benefit from them

      ...which is also often true of {Free,Net,Open}BSD as well.

      In BSD, things happen slowley because the people working on it are more concerned with sercurity and stability.

      Umm, how quickly do things happen in, say, the 2.2[.x] Linux kernel tree, as opposed to the 2.3[.x] tree? You appear to get at least some choice of "bleeding-edge" vs. "stable" there...

      ...and you also do with FreeBSD (and possibly the other BSDs), by going with the "-current" tree if you want to be on the bleeding edge or going with a "-stable" release if you don't.

      Also, if someone does make a good change or add an important feature, they could always keep it and not share it, so these features will be adopted slowly.

      That has nothing to do with adopting features, it has to do with whether they're available for the open-source BSDs to adopt - and there appear to be people contributing stuff back to the BSDs, e.g. Whistle have contributed a number of things to FreeBSD.

      The end result is that Linux, while more prone to problem when using the latest and greatest kernal/library/etc, it more quickely adopts features that user want and need.

      Well, maybe. Perhaps the ISA PnP tools, or the ISA PnP kernel patch, for Linux can be made tow work as well as the ISA PnP support has worked for me on my box (it handles my PnP ISA sound card just fine - no, I do not want a PCI sound card, I'd rather leave my PCI slots available for cards such as networking and SCSI cards), but the PnP ISA patch didn't work very well on the 2.0[.x] kernel on my Debian partition (I could've debugged it, but didn't particularly have any interest in doing so, as it Just Worked on FreeBSD), and it wasn't clear whether I'd have to update some config file to use the ISA PnP tools (I could've dug into that, but didn't particularly have any interest in doing so, as it Just Worked on FreeBSD).

      I.e., I don't think it's as clear-cut as you describe - you can do bleeding-edge stuff with FreeBSD (and perhaps the other ones) if you want, and you can do trailing-edge stable stuff with Linux if you want. (Note: "trailing-edge" is not being used as a pejorative here; heck, I don't run "-current" on my home machine, as I'm primarily using it for development of stuff for the Ethereal network analyzer, and for surfing/reading mail/etc., so I'm reasonably happy to be somewhat on the trailing edge.)

  83. Not... by Anonymous Coward · · Score: 0

    I am not finishing anything that glory hounding egomaniac started.

    My systems run Linux. period.

    There is no GNU/Linux. It is all just RMS and his ego.

    1. Re:Not... by Anonymous Coward · · Score: 0
      I am not finishing anything that glory hounding egomaniac started.

      If that's what you want, you'll need to step away from his groundwork and find some other project to contribute to. A viable GNU System is practically his life's work, and Linux kernel hackers and distro builders are filling in big pieces of it.

      Where's the egomania, anyway? He wants people to talk about Free Software and its premier project, not himself. It's not as if he woke up one day and decided "I know, I'll ask everyone to call it RMS/BSD!"

    2. Re:Not... by Anonymous Coward · · Score: 0

      The only thing you use from the FSF these days in making a BSD system is the compiler. The rest is free.

    3. Re:Not... by Anonymous Coward · · Score: 0

      On OpenBSD:

      /usr/share/man$ grep -il gnu */*.* | wc -l
      98
      /usr/share/man$

      A few of those are libc functions that first appeared in gnu libc, but most of them are GPLed programs.

      This search would have been a lot easier with a /usr/doc that contained the COPYING file for each installed package. Man pages don't usually include licenses (even ones from the FSF, which surprised me).

  84. Can you judge an OS by it's cover? by PC_Circus · · Score: 1

    I have tried both FreeBSD and Linux in my quest for the operating system that fits me. I like both operating systems, though with Linux I am a bit pickier about the distro. (FreeBSD has 1). FreeBSD seems a bit harder to do a post install setup (I.E. kernel config) the Linux "make xconfig" puts me at ease a bit more than scrolling through "LINT" on FBSD.

    I think the part that hurts the BSD community the most is the amount of stores that sell the operating system. You can go online and download or purchase FBSD, but it does not seem to get the shelf space everywhere like Linux.

    You can walk into Wal-Mart now and purchase a jewel case distro of Red Hat, or go to the bookstore and pick up pretty much any "Unix" (*) book or search through the shelves full of Linux books. (Though I think most of the books are outdated, books selling with say Rhat5.2) FBSD just is not out there.

    The people who choose FBSD are those who want it, alot of people find themselves buying and installing Linux because they find a copy of Linux for $19.95 at the local store or are sick of M$.

    Linux just seems to be the buzzword nowadays and the attention it has recieved has been turned into more users. I hope that both BSD and Linux continue to grow in power and availability.

    Nothing can last forever, we will continue to evolve and create more, better, faster as time goes on.

    I will continue to advocate both FBSD and Linux and let the user decide which is better based upon their wants and needs. If approximately 10 million people use Linux and 2 million use BSD, that is still 12 million that don't use Micro$loth!

    *I often wonder who is masquerading Unix with a fresh copy of linux? apples and oranges.. apples and oranges.

    --
    'Speaking in terms of reliability, isn't it time for your Windows to crash?'
  85. Where does... by Anonymous Coward · · Score: 0

    he say that?

    He probably just said it to shut RMS up. Unfortunately, RMS has a bigger mouth than a contribution to software.

    1. Re:Where does... by Anonymous Coward · · Score: 0

      Yes, he's just tired of RMS's yapping. He's just trying to shut the fucking moron up. Put two pints of ale into Linus, and he'll tell you this himself. I've heard it at least twice.

  86. No fricking group hugs by Anonymous Coward · · Score: 0

    BSD isn't into the touchy-feely group hug thing that Linux babes are.

    1. Re:No fricking group hugs by Anonymous Coward · · Score: 0

      If BSD doesn't care about being a community, why do they go ballistic about things like the above? Make up your mind. You care or you don't. It's hard to believe you don't care when you scream it at 110db every time something like this comes up. BSD cares, but it won't change because it's too proud of itself to make an effort in anything it didn't think of first.

    2. Re:No fricking group hugs by Anonymous Coward · · Score: 0

      BSD should be "into" whatever gets it good people making a good OS. Again, assuming making the best OS is the goal.

    3. Re:No fricking group hugs by bvmcg · · Score: 1
      BSD isn't into the touchy-feely group hug thing that Linux babes are
      Precisely that attitude is why it misses out on a lot of good things. You make it sound as though wanting to work as part of an inclusive group is a bad thing.

      For my part, I work for a game company which has created products for Microsoft, Lego, Williams, Interplay and a few other notable players. Earlier this year I was soliciting people to create text content on updating FreeBSD's packaging to give it more shelf appeal and soliciting information and space to create a well-structured PR team.

      My staff created a tasty looking box on their own time without asking for a dime (save the artist making a 3D daemon who was putting in a LOT of hours) as I was cheerleading, working with them and "giving group hugs" as the poster put it. They were working to be part of something and enjoying the appreciation from the onset.

      While this was going on, I was met with a lot of fighting and resistance to most any kind of input, so I just told my team to "drop it. I don't want to work with these people." I care more and work better with positive group attitude. My people too. And it's hard for me to keep it exciting for my people here when people there are busy posturing and pissing on me.

      I still think FreeBSD is one of the best things that's happened to the PC, and it's my undisputed OS of choice - I'm even using it for Linux targetted programming at work. But working on it simply hasn't got the social returns that make it worth my free time, so I'll stick to being a non-contributing user.

    4. Re:No fricking group hugs by Anonymous Coward · · Score: 0

      As Neal Stephenson wrote: "Get away from me, you freak!" :-)

  87. Why Is Disclosing Improvements Bad? It isn't. by EXTomar · · Score: 1

    You make it sound like writing code for any GPL project is bad. Why shouldn't a writer give back any improvements made to a GPL project? After all, the others who have contributed the GPL code did a lot of work for you.

    Sitting on code that isn't submitted back only makes it useful to you. If you don't give back and share, the mainline code is going to advance and you're going to end up constantly patching or even better, some one else who isn't so selfish submits the same code fixes.

    There are plenty of situations where the GPL is not feasible. I just happen to believe that OS-level and mid-level utilities are perfectly suited for GPLing.

    1. Re:Why Is Disclosing Improvements Bad? It isn't. by Anonymous Coward · · Score: 0

      If that is the way it came across, sorry. That wasn't the intent. The bottom line is that with all the money floating around linux, someone is going to attempt to corner it. It's inevitable. The FSF maybe able to do something about it, considering the GPL, but by then the damage will be done.

      Contrary to belief the linux community CAN be fragmented.

  88. We don't need another flamewar! by Daniel · · Score: 4

    If moderation extended to articles I'd mark this one down Score -1: Flamebait. Not necessarily because it's inflammatory in and of itself (although the last comment was practically asking the soapboxers to come out of the woodwork), but because we've all seen this ground hashed over again, again, and again: "BSD license sucks! Disinfect the GPV! BSD==Proprietary! GPL==Commie Facists! BSD users are elitist jerks! Linux users are clueless idiots! BSD is k00l! Linux is k00l!"
    I've browsed the first few comments and found that, unsurprisingly, they say nothing that hasn't already been repeated ad nauseum. I'd like to ask /. to try for a little more discretion in posting articles and to try to cut a little of the hype and bullbaiting. Not that the odds are in favor of this occuring..
    Luck,
    Daniel

    --
    Hurry up and jump on the individualist bandwagon!
    1. Re:We don't need another flamewar! by Geordon · · Score: 1

      I've browsed the first few comments and found that, unsurprisingly, they say nothing that hasn't already been repeated ad nauseum. I'd like to ask /. to try for a little more discretion in posting articles and to try to cut a little of the hype and bullbaiting. Not that the odds are in favor of this occuring..

      That's exactly why I read more than I post. One of these days, I'd like to be able to actually have some valid input, but until then, I just read and learn. (Two eyes, one keyboard...)

      --
      It is by caffiene alone I set my mind in motion. It is by the beans of java that thoughts acquire speed, hands acquire
  89. BSD should be right where it is. by Loualbano2 · · Score: 1

    I think one of the reasons is the "ease of use" factor. This is more of an concern for Linux distos than for xBSD distros. This is probably one of the reasons for the undergroundness of BSD. And frankly I hope it stays that way.

    I would really like things to stay the same as they are now, BSD positioning itself as a rock-stable, bad ass mother and let Linux go off and try to make everyone happy with the pretty install progs and such.

    2 cents from and ex managers of wrestlers

    1. Re:BSD should be right where it is. by Anonymous Coward · · Score: 0

      BSD is much easier to use than Linux is for a professional Unix programmer.

  90. Perhaps the "friendlyness" of the groups long ago. by jopasm · · Score: 1

    Long ago I was searching for a "free" Unix for
    my PC. At that time I was on Delphi (anybody
    remember them? :>) and had access to Usenet as
    well as ftp, etc. I'd heard about 2 different
    "projects" (well, one project and one family
    of project to be precise) - Linux and *BSD.
    I checked out the newsgroup(s) for each project.
    The *BSD seemed to be full of endless flame wars
    about which "version" was better, and any "newbie"
    questions were instantly pounced upon as an
    opportunity to berate the person in public about
    their ignorance. Not a very friendly situation.
    Then I checked out the linux groups - lots
    of people helping others, with an attitude of
    "hey, look at this cool new thing we've got,
    what can you do with it?". Guess which one I
    went with? Personally, I think that the openness
    of the linux guys & gals (and not just the license and/or legal troubles)
    is what really helped push linux in the early days
    over *BSD. No, it may not result in the cleanest
    tightest code ever, but it is a friendly
    attractive environment where would could/is
    progress at a rapid pace and most people involved
    could have fun.

    I'm currently running Linux (various distro's),
    FreeBSD, OpenBSD soon (gotta order that CD),
    and a couple of other things. FreeBSD seems to be
    a nice, tightly written OS. I am in the process of building a file/print server using
    FreeBSD. The documentation structure is not
    as "newbie friendly" as linux, but is fairly complete (hint: "Just get a good book on Unix"
    does not for newbie-friendly documentation make)
    No doubt there'll be some nice "flaming" replies
    to that comment. :>

    The *BSD groups have become *much* friendlier to
    newbies, and *BSD is starting to grow in popularity. Coincidence?

    As somebody else pointed out, both groups are
    (to some degree) working towards the same ends -
    free, powerful, useful software. This is not a
    cut-throat financial competition, there's room
    enough for several OS's/distributions. More and
    more software is being developed "across platform"
    (Linux/BSD/etc), and that's a step in the right
    direction. Cooperation not competition and all
    that. :>

    --

    ObTagLine: The more you run over the 'possum, the flatter it gets.

  91. Loud advocates make the difference. by Proteus · · Score: 1
    Why is Linux more "successful" than BSD?

    First of all, I don't know how true that is unless you define "successful" to be "widely used." Let's just assume that definition for the duration of this post...

    It's simple really: BSD users use(d) BSD because it serve{s|d} thier purpose. BSD is, like Linux, a free implementation of UNIX. The difference is, the BSD community never wanted to be any more than that -- so they succeeded extremely well at what they set out to do: reimplement UNIX under a (arguably) free license.

    On the other hand, the Linux community decided that "a better UNIX than UNIX" and "world domination" were the goals for Linux. This lead to the main advocates (ESR, Linus, AC and others) being much more vocal than BSD advocates. The Linux community _wanted_ universal acceptance, whereas the BSD community was simply concerned with making the best OS possible for their own ends.

    Not that either approach is worse (I use NetBSD for several web and intranet servers, and Linux on many desktops and app servers), but they have different results.
    -- Never underestimate the power of very stupid people in large groups

    --
    We may not imagine how our lives could be more frustrating and complex—but Congress can. – Cullen Hightower
    1. Re:Loud advocates make the difference. by Anonymous Coward · · Score: 0

      If you measure popularity by research papers published, then BSD beats Linux hands down.

  92. How is BSD > Linux? by Broccolist · · Score: 1

    I've heard a lot about the various BSDs being "technically superior" to Linux, but I've never actually heard any BSD advocate point out specific ways in which it is better. I've also heard it's more stable and more secure .. but a properly configured Linux box that isn't using wacky new kernel features can stay up for years, also.

    Legal issues put aside, why would I want to use BSD? Thanks,

    Broccolist

    1. Re:How is BSD > Linux? by Anonymous Coward · · Score: 0

      One issue is that BSD is much more programmer friendly than Linux. It takes integrated, coherent programmer documentation much more seriously.

  93. Very simple test. by Anonymous Coward · · Score: 0

    Linux has been positioned to replace Windows 9x/NT. All of the little kiddies latch onto the fight against Microsoft. Back in the day, those same people would make fun of Apple. They're the same people who always need to feel like they're ELITE. I'm sure some of them have moved on to BSD already. Now they can make fun of Windows users, Apple users and Linux users! It's an elitist heaven. You may think it's not true, check out a few IRC channels. Lets use #linux, #freebsd, and #win2000. Go to each channel and ask what people think of the competing operating systems. You will see what I mean very quickly.

  94. support, support, SUPPORT! by tuffy · · Score: 2
    Linux support is all over the web. HOWTO sites are abundant. Precompiled software is abundant. Distributions are abundant. There's lots of places to get useful info about Linux, which equals support - and that's what people really want. Most software compiles on both, Linux binaries can run on BSD (on the proper hardware), but where's the support? There's some, certainly, but nowhere near as much as Linux has.

    Licensing is not the cause. Linux runs lots of software using BSD-type licenses (Apache has a similar license, IIRC), and that hasn't driven anyone away except for the die-hard zealots (who are in the minority). The real cause is a lack of support, and that needs to be addressed before BSD starts garnering popularity.

    Perhaps it can be addressed with commercial *BSD distributions, more *BSD web sites, or maybe just a new mindset in the community - perhaps the *BSD users don't want popularity. But the conditions won't change until the support arrives.

    --

    Ita erat quando hic adveni.

    1. Re:support, support, SUPPORT! by Anonymous Coward · · Score: 0

      It's curious, but most of the software that these big Linux sites rely on is not GPL'd. Apache, Perl, MySQL, Sendmail, etc. Tells you something, eh?

  95. BSD, Linux, and Debian by misleb · · Score: 1

    Something I just thought of that I think might sound interesting is that, as Debian Linux user I feel a bit left out of a lot of the Linux hype. Almost in the same way that BSD users are. And really, I like it that way. Debian is very strict. It has a somewhat closed develpment base and yet is completely GPL'd. Best of both worlds as far as I am concerned. I am not going to argue the benefits of GPL vs. BSDL. I will just say I feel more altruistic working under a GPL in general, and with Debian more specificly. I don't really care how popular the OS that I use is. I will use what I feel most comfortable with. Debian Linux is it.

    I hate managing BSD installations much in the same way as I hate Slackware Linux. So, for me, I would say that Debian has kept me from going to the BSD side. I think if I had the choice between Slackware and FreeBSD, I would go with FBSD on technical merit alone. But technical merit isn't enough when deciding between Debian and FreeBSD.

    As for the popularity of Linux over BSD? It is probably for the same reason that Debian hasn't gotten the mindshare that other distributions of Linux have. It is simply that most Linux distibutions cater to newbies. They are more inviting to novices. It is that simple. It has nothing to do with application or hardware support or penguins vs. daemons.. etc.

    The world is mostly full of idiots. If you cater to them, you are bound to get a larger marketshare. Bill Gates has proven this to be a winning strategy.

    So, anyone running RedHat or Slackware, ready to try FBSD, make sure you try Debian Linux too.

    -misleb

    --
    "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    1. Re:BSD, Linux, and Debian by Anonymous Coward · · Score: 0

      The reason people hate Debian is because it feels too much like BSD. And so do its advocates. They think they're smarter than us ex-Windows users are. It would be better if Debian and Slackware would just go away and convert to BSD, so that Linux can remain free of that crap, and allowed to grow to embrace the Microsoft market.

    2. Re:BSD, Linux, and Debian by mr · · Score: 1

      >It would be better if Debian and Slackware would just go away and convert to BSD, so that Linux can remain free of that crap,

      If BSD is crap...why are you not working on removing all BSD-derived source code from Linux? How dare your GNU/Linux be contaminated with such BSD crap.

      (What? That would be work, and you don't believe in work...just mindless flames?)

      --
      If it was said on slashdot, it MUST be true!
    3. Re:BSD, Linux, and Debian by misleb · · Score: 1

      I don't know if you have ever actually maintained a Debian system, but it isn't like BSD. The packaging system alone makes a huge difference. Not to mention the sysvinit aspects. You must be refering to the installation process. And probably dselect more specificly.

      Now, as for the advocates, yes, we are a bit elitist but for good reason. We don't want a perfectly good system ruined by dumbed down UI's and lazy users. With a little work and a few brain cells anyone can join the club. Just run Slackware for a year.. find out how much it sucks when you have to reinstall to upgrade your system and come to the dark side. You need to be a lowly newbie for a while before you can be cool. Kinda like being a freshman in high school.

      And I don't WANT to embrace the Microsoft market! I want to perform a hostile takeover!


      misleb

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  96. Linux vs BSD: Journal publications by Anonymous Coward · · Score: 0

    If you look at the number of white papers published over the last five years on Linux and on BSD, you'll see that the BSD papers far outweigh the Linux ones. That's not to say that Linux folks are all dull hacks, nor that the BSD ones are all researchers, but whatever the reason, there's a tremendous disparity in the reputable literature out there. One wonders why.

  97. Okay.. you proved your point by Anonymous Coward · · Score: 0
    And the point you made was... BSD programmers are rude isolationists that don't want to play nice with ANYONE.

    HA HA

  98. Re:NT stability by jaclu · · Score: 1

    >If NT were as stable as *BSD or Linux, do you think that the development community would switch over to NT?


    I like and use linux, but can't agree with you on this.

    One of the main reasons why peolple make the move NT -> linux is stability.

    If that was available in NT - Why would any NT shop bother to do the switch?

    It sure costs them a lot of relearning to go to a new OS, not many would do it just on license issues. (At least that's what I think)

  99. Ugggggggggg by tweek · · Score: 1

    Linux this...
    BSD this....

    Why the fuck does it matter? Use what works best for you. Hell use an MS product if it works best for you.

    I have a question. Why in the hell does it matter which is more popular? They both kick ass in my opinion and I have one of each ehre at the office. I *personally* use linux as my desktop because I started with it before FreeBSD and feel much more comfortable with it. It wouldn't matter a rat's ass to me if I had to use a *BSD and couldn't use linux. You wanna know why? (I know you don't but I'm going to tell you anyway)...

    Because I have the source to all the applications I run. For those I don't, FreeBSD supports linux binaries.
    Why must obviously intelligent people getting into cock measuring contests about which one is better. Quite honestly "better" is all in the mind of the person at the helm of the computer itself.

    So let's all get a fucking grip and put our dicks back in our pants and get over it.


    --
    "Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
    1. Re:Ugggggggggg by steffl · · Score: 1

      you care about popularity of OS you choose because the more popular (number of installations) it is the more hardware support it has. and you usually want hardware support (for good graphics card (that's more X issue than OS), sound cards, network card, usb devices, pnp cards, etc...). that's general situation, in some particular cases you indeed might not be interested in popularity...

      erik

      --
      ...all excited, don't know why...
  100. Why this colour scheme? Red for flamebait? by Anonymous Coward · · Score: 1

    I am getting angrier just looking at all this red!

    1. Re:Why this colour scheme? Red for flamebait? by Anonymous Coward · · Score: 0

      Why are you seeing red? Turn off colours, you fool, before you go blind!

  101. Re:NT stability by Kenneth+Stephen · · Score: 1

    If that was available in NT - Why would any NT shop bother to do the switch?

    But "shop" switching is a user-community switching - not developer switching - especially if we are talking about NT. My comment was about the reasons why the developer community showed a preference to Linux - thereby causing a user community expansion.

    --

    There is no such thing as luck. Luck is nothing but an absence of bad luck.

  102. Linux: the way the truth and the light by Anonymous Coward · · Score: 0
    I've always found the Linux-advocates much nastier than the BSD ones.
    One reason might be because BSD programmers aren't new converts. Look at any church. It's the new converts who are the most crazy.

    Another reason might be that BSD programmers don't seem to have fallen for the conceit that theirs is the only valid path to salvation the way the Linux people so often do.

  103. back ontopic by Anonymous Coward · · Score: 0
    His "whining" is a perfectly valid answer to the question why BSD is not that popular or omnipresent in the media. And was that not the original question ?? But thanks for proving his point.

    twi

    1. Re:back ontopic by Anonymous Coward · · Score: 0

      Yes and you seem to ignore the similar linux centric posts on this comment board. This and the fact that there are maybe 3 or 4 people participating that are actually developers or sufficiently involved to know what they are talking about because they are actally involved and not purely speculators.

  104. Ultimately, what's it matter? by Greyfox · · Score: 2

    It really shouldn't matter which you use. All the interesting source is open, so doing a BSD-like dist of Linux (slakware?) or a Linux-like dist of BSD should be quite possible. I've found porting C code between two UNIX systems is relatively straight forward. At this point BSD seems to be able to run Linux binaries as well. So what does it really matter?

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    1. Re:Ultimately, what's it matter? by Anonymous Coward · · Score: 0

      If system A can be used to create system B, but not vice versa, that A is more powerful. Because BSD runs Linux code, but not vice versa, the conclusion is obvious. Just like Linux running MS-DOS code.

    2. Re:Ultimately, what's it matter? by Anonymous Coward · · Score: 0

      The conclusion is obvious: Because BSD runs Linux code, There must be Linux apps that BSD doesn't have. Linux doesn't run BSD code because there are no apps for BSD that aren't for Linux.

      Notice:
      Linux runs Linux apps, but not Free, Net, or OpenBSD apps.

      FreeBSD runs Linux and FreeBSD apps, but not Net, or OpenBSD apps.

      NetBSD runs Linux, FreeBSD, and NetBSD apps, but not OpenBSD apps.

      OpenBSD runs Linux, FreeBSD, NetBSD and OpenBSD apps.

      Note that each OS (without fail) can run binaries for ALL the more popular (read more software available) platforms, and NONE of the less popular ones. You are quite correct, the conclusion is obvious, but it has nothing to do with relative "power."

  105. Not in my experience by Anonymous Coward · · Score: 0

    Sorry, but my experience has been 180 degrees. BSD users have been friendly, knowledgeable, and professional. I have yet to meet a Linux user that meets any of those three requirements.

    For the desktop give BeOS a try, after all it is the future of the desktop.

    1. Re:Not in my experience by Anonymous Coward · · Score: 0

      A completely proprietary OS with shallow hardware support. It's like OS/2 but without compatibility of binaries. It must be the future!

    2. Re:Not in my experience by Anonymous Coward · · Score: 0

      With obvious exceptions like Maddog and Linus, there just aren't very many Linux programmers who are professional. That's why we don't see many research papers from Linux. Contrast this with the stacks of BSD papers.

    3. Re:Not in my experience by Anonymous Coward · · Score: 0

      Never used it, eh?

    4. Re:Not in my experience by Magnanimous+Cowturd · · Score: 1

      I tried it - once. After much effort to get it to work on my hardware I was rewarded with an interesting but wholly unintuitive GUI.
      Apps? mini-apps? ANYTHING I could start up that was going to let me know I was in for an experience of a lifetime? Nope. Just a broken Internet browser.
      I had to switch operating systems to hunt around for anything I might download that would show off this wonderous system. Everything remotely interesting had a price tag on it.
      I'm sorry, but even Windows comes with a couple of gizmos to click on.
      Thanks, but no thanks, I'll stick with GNU/Linux.

      --
      The Supreme Art of War Is To Make the Enemy Look Foolish --- Li Atwater
    5. Re:Not in my experience by Anonymous Coward · · Score: 0

      Well, thank God you're gone. You're completely deluded. It's not about GUIs. It's not about money. It's about power and elegance.

    6. Re:Not in my experience by Magnanimous+Cowturd · · Score: 1

      Power and elegance? Where? BeOS gave me no indication it had anything to offer. My point was show it to me! I haven't time to waste on an operating system that forces me to beat "power and elegance" out of it.

      --
      The Supreme Art of War Is To Make the Enemy Look Foolish --- Li Atwater
    7. Re:Not in my experience by Anonymous Coward · · Score: 0

      1. Proprietary does not = evil. Too bad you will probably never realize that. Am I suppose to use Linux simply because it is open-source, never mind that is a horrible unstable and poorly supported platform? (but it's open source...you have to use the open source....open source!!!!)

      2. BeOS was designed to run on hardware built in the last 10 years. That's pretty sweet. It's the ONLY OS out there that is not carrying baggage from 25 years ago. Linux is still just another Unix variant, which means that the underlying technology is older than my grandfathers dentures.

      BeOS is the easiest OS to use. BeOS delivers on all the promises that Linux/GNOME, Mac, and Win95 have made and missed.

    8. Re:Not in my experience by Anonymous Coward · · Score: 0
      You call it 25 years of baggage. We call it 25 years of refinement and solid engineering.

      But I happen to agree with you that BeOS is very neat.

    9. Re:Not in my experience by screeching+weasel · · Score: 1

      Is this comment refering to the BeOS still?!?
      "a wholly unintuitive GUI"... what are you, a retarded four year old? what could possibly be unintuitive about Be's GUI? It's as simple and effective as could be. "Broken internet browser"?
      You must have been using an OLD OLD version or something.
      I urge you to give it another try. It really does rock.

  106. Once I asked a BSD question and... by Anonymous Coward · · Score: 0

    ...those awful BSD people made me cry!

  107. #openbsd by fr0g · · Score: 1

    This channel has been very helpful to me many of a time. Sure they will not hold your hand but thats not what I want. I either want an answer or point me in the right direction.

  108. Re:Perhaps the "friendlyness" of the groups long a by Anonymous Coward · · Score: 0

    If you think FreeBSD is small and tight, you will be in for a real treat when you get to OpenBSD. It's even smaller. In fact, in comparison, it's like FreeBSD is becoming the kitchen-sink distro, just like Redhat/Linux. People who want smaller, better designed Linuces don't go for Redhat or SuSE, you know.

  109. that's great when the manuals work! by Anonymous Coward · · Score: 0


    Take, for instance, icecast. Ever try getting liveice to stream to your icecast server? Lord. What a trip. The icecast server (whether liveice is using icy login or x-audiocast login) yells "kicking client - [stupid headers]". No information on this at all in the docs. So when you go out on a linux newsgroup or linux channel looking for help, people start flaming the crap out of you for being an idiot.

    First they say read the f'in manual, but you did that already. So they say 'get lost loser'.

    Then you remind them of that so called award winning tech support stuff and *WHACK* yer kicked and banned.

    I bet you if their mothers want to get online with Linux, they'll shape up and fly right though. :)

    1. Re:that's great when the manuals work! by Master+of+Kode+Fu · · Score: 1

      R'ing the F'ing M's is not always enough when the manuals are often quickly thrown together, incomplete and poorly-written. In any revolution, either political or software,everyone wants to be a general and no one wants latrine duty. Guess which category doc writing falls under.

    2. Re:that's great when the manuals work! by Anonymous Coward · · Score: 0
      R'ing the F'ing M's is not always enough when the manuals are often quickly thrown together, incomplete and poorly-written.
      That's one of the major differences between Linux and BSD.
  110. Re:Perhaps the "friendlyness" of the groups long a by Anonymous Coward · · Score: 0

    Cross-platform means that it runs on both BSD and System V, you know. From source code.

  111. Very well put by Anonymous Coward · · Score: 0

    Well put my friend. Sometimes the truth is obvious some people just can't see it.

    1. Re:Very well put by Anonymous Coward · · Score: 0

      Thanks. I'm hoping to have that post moderated up, as I can use the karma! (AC does get a bad rep)

  112. Bruce is Richard's disciple in obnoxiousness by Anonymous Coward · · Score: 0

    What, Brucey obnoxious! Say it's not so! Hell, he makes ESR seem like a puppy. If RMS kicked the bucket, or were assassinated by a Redmond-launched hit, then the rabid FSFreaks would not want for a slobbering saviour full of fire and brimstone.

  113. They don't say the GPL is the reason by Guy+Harris · · Score: 2
    An article over on Economic Times explains why BSD is as not as popular as Linux.

    At most, they quote somebody from Novell India as saying that "The reason why it is not as popular as Linux is the lack of commercial support".

    There's no place I can see where they attribute the difference in popularity to the license. I see a place where they make the factual statement that the BSDL and GPL are different, but I see nowhere anything in the article claiming that this is the reason for a difference in popularity - the sentence after the one about the license difference might, at most, be suggesting that, as a result of the license difference, "the BSD operating system" (although they don't say which particular flavor of BSD - one of the free ones, or BSD/OS) is inside some firewalls (however, there are plenty of "appliances" with Linux Inside, as well; some even have, I think, proprietary code in them, even if it's not in the kernel).

  114. Proof to indicate otherwise: by Anonymous Coward · · Score: 0

    Linux is used in "embedded" and other "unconventional" environments too.

    1. Procom Technologies CD FORCE tower units. They run some hoopty version of the Linux kernel (rebadged to call itself MESA, mind you) and support a variety of protocols for serving. They also have the kernel source goodies on the CD, for those interested in the GPL-compliance.

    2. Philips TiVo. I think that should be self explanatory based on all the recent coverage here on Slashdot. GPL-wise? Source on the web site, or you can send for it.

    "Flakey"? Go back to Redmond. Stop trying to turn the daemons and penguins against each other. Only M$ could possibly want that. Real Unix users shouldn't give a rat's ass and should bind together against the Great Satan that is Windows. That means BSD and Linux based systems working together to defeat it.

  115. Re:Only 650,000 Linux users by Anonymous Coward · · Score: 0
    Linux ranks so far behind MacOS and Windows in installed base it's laughable. They are about even with OS/2...maybe...
    MacOS X is going to really piss the linussies off as the BSD count soars. Tee hee!
  116. sublime by jbarnett · · Score: 1

    "In terms of sophistication, the BSD operating system is better than Linux. Its original kernel is highly advanced. It has always been popular with people doing their masters and doctorates in computer science research. The reason why it is not as popular as Linux is the lack of commercial support,"

    Does anyone else think the BSD community is subtly spreading FUD towards the Linux community. I use both Linux and FreeBSD and they both have their advantages and disadvatages, but I think the BSD community likes to display and bring up Linux disadvantages or the advantages BSD has over Linux whenever they can.

    They are both FREE and STABLE Unix systems for the lowend to highend hardware, but these hardcore BSD users need to stop thinking their OS is BETTER then Linux. In some ways, it is, in some it is not, we don't need both the Linux and BSD communities pited at each other. Both communities need to brag about what they do best and fix anything that is broken.

    Neither BSD or Linux will benfit from bashing and FUD-ing each other, they will benfit from advocating each other though.

    One (of the very many) benifits of Open source and Free software (as in speech) is a choice.

    You are free to choice. If you dislike something, you can either 1) change it, or 2) find a differnat OSS project that will fit your needs/wants. There is the opinion to FUD anything that you don't like, but this ONLY applies to closed source software.

    Everywhere I go:

    "see I am SSH-ed into this openBSD from my Linux workstation and th..."

    "Get rid of Linux, that is your problem, use FreeBSD as your workstation man, it is BETTER and doesn't crash as much"


    "Uh Linux has never crashed on me, and the problem is I had a surge on my Ethernet wired and it physically fired my ethernet card. My question was, can I fix a burnt PCI slot or do I have to replace the motherboard?"

    "uh, surge, a? Still FreeBSD is Better in alot of ways, for example, let me start back in 1972..."


    sigh... and this is a TRUE story, talking to some hardcore Free BSD user at college about a burnt PCI slot on my freind's motherboard. To this day he is still conviced that Linux physically burnt out some of my freind's hardware, even after the IT director admitted that there was some surges in the school network wiring... sigh

    I know this sounds REAL cheese, but "can't we just all get along?"

    --

    "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
    1. Re:sublime by Anonymous Coward · · Score: 0

      "Does anyone else think the BSD community is subtly spreading FUD towards the Linux community. I use both Linux and
      FreeBSD and they both have their advantages and disadvatages, but I think the BSD community likes to display and bring
      up Linux disadvantages or the advantages BSD has over Linux whenever they can. "


      Yeah, and I suppose the Linux community never does anything like that.

    2. Re:sublime by jbarnett · · Score: 1

      Well, yes to Windows maybe. But I have never seen any Linux users talk bad of BSD, Solaris, IRIX or AIX. Every Linux users I meet as liked a differant Unix, open source or not, just for the fact it is something new. Something differant then the penguin is good for the soul once in awhile.

      --

      "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
    3. Re:sublime by Anonymous Coward · · Score: 0

      I wish that were true. Just look around Slashdot and you'll see plenty of Linux screamers painting BSD with the same brush as they paint Microsoft.

  117. GPL vs BSD License by Scientist · · Score: 1

    The GNU Generical Public License is obviously much better then the BSD License. The reason for this is GPL forces the creator of a software package to release the feature back into the community while the BSD License lets those features be used for properitary purposes, therefore allowing those features to be hidden from the community.

    1. Re:GPL vs BSD License by Scientist · · Score: 1

      This comment could have been worded better and should have been free of spelling errors.

      Sorry.

    2. Re:GPL vs BSD License by Anonymous Coward · · Score: 0

      Um, kid, the virus issue is old.

    3. Re:GPL vs BSD License by Anonymous Coward · · Score: 0

      The GPL is not a virus it just wants to make sure that software and any features added to it remains in the public domain.

    4. Re:GPL vs BSD License by Anonymous Coward · · Score: 0
      Yeah, whatever. It's a virus in that it extends itself to cover code that its author didn't write.

      The BSDL keeps its own code free. It just doesn't infect anyone against their wishes.

      If you can't make a choice, you can't be moral.

    5. Re:GPL vs BSD License by Anonymous Coward · · Score: 0

      "public domain"? Are you crazy? Yes, its "free software," but it is NOT public domain. The GPL is composed of restrictions, not rights/freedom.

      In anycase, this is an old issue. However, the GPL is bitter sweet, for both users and developers.

    6. Re:GPL vs BSD License by GNUs-Not-Good · · Score: 0

      Repeat after me....

      "GPL is good...GPL is good"

      The cult meeting is now over. Kool-Aid is being served in the back.

  118. color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

    ...well maybe in UK

    1. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0
      Name three countries whose official language is English and which use "color". Heck, name two. There are oodles more that use "colour".

      Of course, "colour" is a perverse Gallic invasion, with no place in Latin. So even though you're in the minority countrywise, you can have philological correctness on your side.

    2. Re:color is spelt COLOR not COLOUR... by atdot · · Score: 1

      Name three countries whose official language is English and which use "color". Heck, name two. There are oodles more that use "colour".
      Of course, "colour" is a perverse Gallic invasion, with no place in Latin. So even though you're in the minority countrywise, you can have philological correctness on your side.


      for that matter, name one country.

      be carefull not to show too much ignorance

      @.

    3. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      Name one country? Easy: Texas. :)

    4. Re:color is spelt COLOR not COLOUR... by atdot · · Score: 1

      OK, good point. Name one country whose official language is English and uses "colour"

      hehehehe

      there may be one out there, but I cannot think of it.

      @.

    5. Re:color is spelt COLOR not COLOUR... by Daevcollie · · Score: 1

      Canada does and I think the U.K. does too.

    6. Re:color is spelt COLOR not COLOUR... by paul.dunne · · Score: 1

      How about ENGLAND?! sheessh...

    7. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      America has no official language. But when they spell the word, they use "color". So do about 1/3 of Canadians. All other countries use "colour", except for Texas, which usually just uses "black". :-)

    8. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0
      From The CIA World Factbook:

      Languages: English, Spanish (spoken by a sizable minority)
    9. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      Well, how about two and a half?

      America, Texas, and Canada. Canada's only half a country in anyone's book - they can't even agree on which *language* to speak for cryin out loud, so I suppose agreement on spelling is out of the question!)

    10. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0
      There are more Hispanics in America than Franks in Canada. And notice who is still spat on by the Anglos? Both, but more the Hispanics, who have no rights. It's time for American Hispanics to have the same rights as French Canadians.

      Monoglots are just ignorant.

    11. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      sorry buddy colour is spelt colour in Canada.

    12. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0
      Sorry, buddy, but there are plenty of Canadian authors who prefer color. It's about 3:1 or 4:1 against, but that's still an important number.

      Neither is wrong, although one is stupid. Why do you drop the "u" in "coloration"? Just leave it out altogether. Notice how many words don't have it, like horror, bachelor, vector, camphor, editor, dolor, factor, and millions of others. Cast off the false French influence. Hail Caesar!

    13. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0
      Citizens have the same rights I do. Trespassers have to convince us we're better off making them citizens than sending them home. "Give us your huddled masses" was fine back when we had more space and unskilled work than people.

      Learning a language is a huge undertaking, full of rote and other ways to squander a human mind, all accomplishing nothing more than conveying all my same old ideas to people stuck with a different native language than I am. But other than simultaneously starting to teach everyone's kids Esperanto and nothing else, there's just no way to fix this mess.

    14. Re:color is spelt COLOR not COLOUR... by higuita · · Score: 1

      ooohhh no.... another one i'm sick of this english speaking people that dont want to understand that other speak/write diferent from then... try to learn 2 other languages (not english related ) and you will be more open mind about this you are not the center of the world, you now!! grow up

      --
      Higuita
    15. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      Unless you speak three languages, you're an uneducated peasant. Like 99.98% of Americans, you have no notion of linguistic diversity or what it means to live in a multicultural society. Why don't you grow the fuck up?

    16. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      What's stupid is your willingness to be influenced by your southern neighbours (see, there's another word that is spelt "*our"). I think you Canadians should try to keep the stature of the English spelling instead of degenerating further into being just US vassals!

    17. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      My notion of linguistic diversity is that it's an unmitigated disaster. The resulting misunderstandings have caused death and destruction for millennia, and trillions of prime hours of otherwise blessed lives have been wasted memorizing redundant vocabularies rather than finding new ideas or learning to accomplish something.

    18. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      Yes, why couldn't we do something to halt this ugly trend? I think if a lot of people got together, held meetings, studied the issues, we might because to find a solution. I'm leaning towards killing everyone not like me. That sounds great. KILL KILL KILL!!!!!!

    19. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      Texas isn't a country. It's a part of Mexico, that the US occupies. But we're in the process of giving it back to Mexico, along with California.

    20. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0
      You, sir, are a loon. The notion that everyone who speaks my language is "like me" is particularly offensive. It smacks of those linguists who have declared that language (which just happens to be their livelihood) limits thought.

      I'm not claiming there's something wrong with people who speak different languages natively, merely that our failure to agreed on one (and thus we have to learn several to communicate with everybody) has been a colossal waste of life. I think English is awfully crufty and difficult even compared to other natural languages; I'd gladly switch to another if I knew everyone else would too.

    21. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0
      It smacks of those linguists who have declared that language (which just happens to be their livelihood) limits thought.
      Sapir-Whorf has been rather soundly discredited. Look it up.
    22. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      Discredited? by whom? S-W [relativistic linguistics] hypothesis stands today, as it did when they wrote it. Neither anthropology nor Cog sci has rebuked the theory strait on and certainly chomsky has not done so with his communist driven jargon.

    23. Re:color is spelt COLOR not COLOUR... by Anonymous Coward · · Score: 0

      The hypothesis has never been tested.

  119. Re:High Volume Web Sites by Anonymous Coward · · Score: 0

    Really man, four sites. Is that all you could come up with. A couple no name sites. No mp3.com or Yahoo, or Netcraft.com for that matter..

    Can linux run high volume sites. sure. But if you look for it, Novell, NT, SCO and many other Operating systems can as well. Pretty much anything other than BeOS with an Apache hack on it can server up high volume http. It's only file sharing...

    Yea, FSF will sue them. That will prevent any wrong doing, just look at the Caldera vs MS suit...

  120. what are you talking about? by Anonymous Coward · · Score: 0

    After a fresh install of FreeBSD 3.4 I could mount my dos and ntfs partitions right away.

    1. Re:what are you talking about? by Guy+Harris · · Score: 2
      After a fresh install of FreeBSD 3.4 I could mount my dos and ntfs partitions right away.

      I think he's trying to imply that they may have adopted it now, but rejected it originally.

      The CVS tree seems to imply that it may have been in FreeBSD at least as far back as 2.0, however; the comment from the initial checkin, with a date of Mon Sep 19 15:41:43 1994 UTC, says "Obtained from: NetBSD", so NetBSD may have had it even longer.

    2. Re:what are you talking about? by harlows_monkeys · · Score: 1
      Furthermore, even after FreeBSD got DOS filesystem support, it was only primary partitions. Extended partitions took quite a bit longer to come in.

      From the start, Linux did a better job of fitting in with whatever OS might already be on your PC, and did a better job of fitting in with existing hardware.

      There's no real polite way to put this, so I'll just be blunt: a few years ago, the FreeBSD were a lot more snotty than the Linux people when it came to cheap hardware. If you were the kind of person who thought that spending $350 for a SCSI CD-ROM was silly when an IDE CD-ROM was only $100 because you only use the thing for installations, then FreeBSD was not the system for you.

      The FreeBSD people have gotten a lot better in the last few years, and I believe they now try to support cheap commodity hardware well.

  121. one little prob. by CrAlt · · Score: 1
    "The day RedHat tries to hide moddifications is the day the Free Software Foundation sues them." And fails...This is also the same day that the GPL becomes worthless. This is the US of A. It dosnt matter who is right-It matters who has the most $$$. Look at etoys..look at OJ..and im sure you could find a 1000 more cases.


    The only real thing keeping Redhat strait is that they dont have 100% of the Linux pie. That is why I hope that SuSe,Slackware,Debian, Bob's big ass Linux Disto, etc... keep up the good work and keep making Redhat do some work.


    People need to remember that Redhat's share holders didnt sign on to better the linux comunity, they signed on to make some cash. And if fucking over linux makes their stock go up 200% then they would do it with out a 2nd thought.

    --
    I have to return some videotapes...
    1. Re:one little prob. by the+eric+conspiracy · · Score: 2

      This is the US of A. It dosnt matter who is right-It matters who has the most $$$.

      A very cynical view not born out by fact. Examples:

      STAC vs. Microsoft - Microsoft loses.
      Apple Records vs. Apple Computer - Apple Computer Loses.
      Dow Corning vs. various private parties. Dow Corning now bankrupt.
      Phillip-Morris vs. various private parties - Phillip Morris loses.
      Johns-Manville vs. various private parties - Johns Manville bankrupt.
      McDonald's vs. old lady who spills coffee - McDonalds loses.
      Exxon Corp (Oil Spill) vs. various parties - Exxon loses.
      Hooker Chem vs. Love Canal residents - Hooker Chem no longer exists.
      GAF vs. Woburn MA residents. - GAF loses.
      man who invents intermittant wipers vs. Ford. Ford loses.

      A number of these cases are quite questionable as to whether the large company did anything really wrong.

      While money allows you to buy a lot of nice fancy lawyers, jurys have a heavy bias against large corporations. If you go into a lawsuit against somebody like the Free Software Foundation you are in trouble right from the beginning.

    2. Re:one little prob. by Anonymous Coward · · Score: 0
      "The day RedHat tries to hide moddifications is the day the Free Software Foundation sues them." And fails... This is also the same day that the GPL becomes worthless.

      Is that so? Might I ask how you can predict this?

      This is the US of A.

      No, my narrow-minded little friend, this is the world. Linux was created by a Finn, namely Linux Torvalds. I am sure you have heard about him. Linux is not a US project - it gathers people from all over the world! Please, pull your foot out of your mouth now.

      It dosnt matter who is right-It matters who has the most $$$. Look at etoys..look at OJ..and im sure you could find a 1000 more cases.

      MS sure has a lot of money. That didn't help them when they were sued, though.

      The only real thing keeping Redhat strait is that they dont have 100% of the Linux pie. That is why I hope that SuSe,Slackware,Debian, Bob's big ass Linux Disto, etc... keep up the good work and keep making Redhat do some work.

      Look, RedHat would be sued to death if they pulled a stunt like that. You are too heavy into conspiracy theories, my friend.

      People need to remember that Redhat's share holders didnt sign on to better the linux comunity, they signed on to make some cash. And if fucking over linux makes their stock go up 200% then they would do it with out a 2nd thought.

      Yes, they are there to make money, but that doesn't mean that they are stupid fools who would pull such a stunt. FSF will sue and whoever is sued will lose. The GPL is there, and should you think about making money by breaking it, FSF will be all over you.

      You Linux bashers sure seem to know a lot about the future, though. I mean, you predict Linux' fall because SuSE and RedHat *will* do something nasty one day? Who bloody cares? Linux is NOT RedHat. There are countless distributions out there. Should RedHat fuck us over, we shall fuck them over.

    3. Re:one little prob. by Anonymous Coward · · Score: 0

      You know, you think we could let off of Redhat, just because they seem to be the most popular distro elitist linux users feel a need to accuse them of trying to bring the entire community under their control... if I was worried about anyone doing this the first company I'd suspect would be Corel (not that I do). Redhat GPLs everything they write for their distro (afaik), corel hasn't. Redhat is extremely easy to install over the net, Corel can't be. If I were me (which I believe I am) I would be more worried about companies such as LinuxOne than Redhat, which has done nothing but help linux's userbase grow immensely in the past couple of years. Just my $2e-2

  122. NT user community by Anonymous Coward · · Score: 0

    It's a circle duder. A few years ago the NT users were the arrogant SOB's talking smack about Netware and SCO, even though their OS sucked. Now the Linux users look like a mirror image of the 1996-7 NT user. Loud, arrogant, misinformed, generally stupid, usually VERY new to computing. On the other hand the NT user has matured and is realizing the shortcomings of his OS and how his OS can be a part of a larger whole (THE NETWORK!!) where individual operating systems are near meaningless. Nifty eh. Can't wait for the Linux user to grow up, they may be able to contribute something useful to the IT community before they faid into oblivion.

  123. Re:It's the organization by Anonymous Coward · · Score: 0
    Since, I've found NetBSD to be much better organised than Linux;
    Any BSD distro is more organized than any Linux distro. I'm not sure that's saying much. :-)
  124. Only one fact. by cmc · · Score: 1

    I can accept your article as one of mostly opinion. Except the "code stealing" bit. We [FreeBSD] have very little if anything at all that can be considered "Linux code." We have the GPL math emulator, GNU binutils... but then again, things like that are GNU code, not Linux code.

    So where do you get the idea that BSD programmers steal Linux code?

    1. Re:Only one fact. by Anonymous Coward · · Score: 0

      I love what Theo did on Open/BSD to GNU bc in order to fix the crud from the FSF. It's hilarious.

  125. It's the users by Anonymous Coward · · Score: 0
    I'll throw out my personal idea on the matter. Let me first start off and qualify myself by saying that I've been a BSD user/fan for quite a while, my first exposure to UNIX was BSD based and many of my mentors in my youth were pretty tightly affiliated with BSD in respect or another. I love BSD but I've run Linux for about 6 years now.

    I think that the majority of BSD's problems as social ones. I think the development used to be the root of those problems but they've seem to come forward in a lot of ways. It's really the user base. There is some kind of antisocial thing that takes hold in certain groups of geeks and nerds, they get a sense of superiority by being different. I say this as a former OS/2 user also, I've been there and know that. There is a good sized group of geeks who don't develop much, are fairly technical users, they get off on being different, and they draw some kind of selfesteem or superiority complex from it. The users of OS/2, *BSD, BeOS, and possibly some other platforms relish it, they are quick to enumerate the ways that their platform is superior (often without solid verification, but lot's of "technical" talk) they are quick to point out that they do everything they need and as it should logically follow these off-platforms with tiny software bases are supposed to fullfill your needs as well or you're not a "power user" like them, they view competitors with disdain and as inferior, they view users of thier competitors platforms as inferior, in short they are a harsh group to deal with and they don't promote their platform nearly as much as they hype it and try to spread negative things about their competitors' platforms. It's like they are jeolous, they get their eliteness by being on some tiny niche platform that only a few use and then they are jeolous of the success of others.

    Is BSD superior to Linux in a technical way? None that I can think of that matters much to an end user. (oops, I seem to have dropped my glove if you care to answer this statement. ;) There might be a few ways that matter in a more industrial environment but to my knowledge they haven't been verified, it's just sort of implicitely assumed to be true, particularly in the BSD circles. Despite numerous multi-month Linux uptimes, BSD's development model produces "better" code and Linux has weaknesses; all of which are never stated or listed off, the closest thing I have heard was that some of the device driver code in the linux kernel is pretty shoddy which isn't saying much because they are still devices that have some shoddy support where *BSD doesn't support them at all. There is also the, "we're not going to play with you anymore" syndrome, in Linux land if someone doesn't like something about Redhat then they build a new dist and include this that or the other to make things right, it's still Linux. Not the case in BSD land, after a conflict one group picks up their toys and goes home to play by themselves and then you end up with different distributions that are quite different, there is some parity but not much and there is nothing to keep OpenBSD compatible with FreeBSD or NetBSD. I think that is part of the whole superiority complex issue, again in Linux land there have been some fairly heated disputes on the kernel list about things but Linus makes a decision and we live with it (plenty of cool code isn't added to the kernel and lives as a set of patches, it's usually a pretty amicable situation, Linus says what needs to be done to the code to get it in the kernel or why it just doesn't belong and the hacker who writes it can distribute patches or fix it or both, take ReiserFS) they fork BSD when those problems come up and the user base goes along with it. (in my theory it is partially because it make yet another smaller niche to place yourself within) I could go on but I don't want to sound too contemptuous, I like BSD, I just wish the user base was more open, more friendly, and less egotistical.

    If BSD wanted to pick up they could do it. First, start a BSD kernel group that is separate from the distributions, this solves far more problems than you'd ever think it does. The only real reason to keep the two together is to have some kind of distribution consistency but UNIX is UNIX and there are certain things that are going to be included with UNIX kernels regardless of whether or not it's dictated by distributions. Unfortunately this means that you sometimes have to compromise when it comes to kernel conflicts... but we're all supposed to be adults here anyways so that shouldn't be such a big deal. Splitting the kernel off into a separate group helps this, conflicts become more public, fights are picked more carefully when they are public, more input is had, better decisions get made and FWIW I think the conflicts tend to be less personal and more technical. It also makes it easier to split the kernel without needing to split distributions, sometimes forks are good.

    Second, send some effort over to Debian, make that BSD kernel a drop in replacement for Linux. Far more users would try it out of they could simply download the kernel, compile it, add a few lines to lilo.conf, run lilo and reboot. The logical follow on to this is to start making the BSD tools run on linux and packaging them up separately from the kernel. Yes, I understand that the BSD experience isn't solely in the kernel or the tools... Think about going forward though, there was a time when a lot of people ran Linux on FAT partitions or off of CDs so that it wasn't painful to try it, think about that.

    Third, start standing and delivering. Once you can drop in a BSD kernel in place of a Linux kernel, the clear superiority of one over the other should start to shine through if it exists. If xBSD is aimed at servers then there should be be ample market for it if it is better at running servers. If yBSD is aimed at the desktop then demonstrate why it is better. Or hell, maybe you just want to be different and have a non-Linux kernel in your GNU/Linux system, that's cool too but don't tell me about how your kernel is better than mine just. That is where the true strength will really come from free software, when I can pick Linux, BSD, Hurd, mkLinux, FiascoLinux(l4Linux), etc.. as my kernel with each one catering to different applications and then I can pick from an assortment of tools (I can already do this) and then I can pick from a selection of interfaces (I can already do this) and my apps will still run for the most part, that's when we will truely start to take over the world.

    Finally, drop the damn ego, saying BSD is better doesn't make it so. Even if it is, who cares what I do with my computer? Saying negative things about other platforms doesn't build yours up any higher. The holier than thou crap will need to stop if BSD is to go forward, I've read articles in BSD netzines bashing Linux and praising BSD, pick some better advocates, or be very specific about how BSD is superior. The coolest thing about Linux is that at every convention, conference, LUG meeting or whatever that I've been to, I've generally meet some cool people that are honestly out to make computing a more fun, useful and reliable aspect of everyones life. They aren't all out on their high horse proclaiming how they've made it through the 36 chambers and are now a member of some elite group or something. I've been to a few BSD user group meetings and I meet a some arrogant pricks. This is a generalization, there are a lot of cool BSDers but there is a vocal group of jerks also, unfortunately since BSD is the underdog the vocal minority can make the whole group smell bad. The same thing goes with all the niche OSes, BeOS users generally seem abrasive, the OS/2 users that are left can bother a lot, I've meet some Amiga guys who were down-right insane. It's just a matter of knowing your role and I'm not sure there is much that the BSD community as a whole can do about it other than discourage it. Linux has the same problems, there is a vocal minority that can make Linux look bad but it has already achieved enough size and respect throughout computing in general that they can get away with it. Be social, include others, welcome them, encourage social behavior, BSD will only succeed because you love it and put that kind of care into how you treat it and its image, not because you hate linux or MS. Good advocacy goes a long way and unless you're already winning bad advocacy will put a halt to your cause.

    1. Re:It's the users by Anonymous Coward · · Score: 0

      But it's the kernel I care so much about. It's the rest of the operating system. I wouldn't want to have to submit to the FSF bloatware that you use on Linux operating systems. Better a Linux kernel and BSD o/s than vice versa.

  126. BSD wouldn't be as popular without Linux by Camelot · · Score: 1
    I am sure this will draw a few flames my way from *BSD advocates, but I consider BSD popular (a few million users ? Yes, that is popular to me) because of Linux, not despite Linux. Given that, I don't see *BSD folks have anything to complain about - except the fact that they're not leading the pack.

    *BSD lacks several factors that made Linux the big success that it is today. Linus, the license that can be corrupted (theoretically, at least), fragmentation.. The FreeBSD IPO (?) I heard would not have happened if there hadn't been Linux IPOs first; people are only riding the wave; *BSD is coming in the wake of Linux and getting more publicity, not less.

    Then there is the competition aspect.. *BSD is better because of Linux, and vice versa. Of course you might argue that *BSD would have more developers if it weren't for Linux, but that can't be proved.

    I have great respect for *BSD - but Linux deserves respect, too. It does not deserve to bashed simply because it's more popular.

    As a phenomenon, Linux is unique. *BSD would not have made it.

    1. Re:BSD wouldn't be as popular without Linux by Anonymous Coward · · Score: 0

      But BSD *has* made it. Without BSD, there wouldn't be a Linux. There wouldn't even be a Sun. And look where Apple is going.

    2. Re:BSD wouldn't be as popular without Linux by crimsun · · Score: 1

      Heh heh, I believe you have it reversed.

      *BSD has been quietly serving the Internet community at large for much longer than any distribution of Linux has been visible. Walnut Creek ftp, the distributing hub of several Linux distributions, has been dishing out gigs for years, and ISPs have used *BSD since... the inception of ISPs. Chat networks have preferred *BSD servers for their stability and security.

      This isn't to downplay Linux, just to say that the ftp from which you downloaded a Linux distribution was probably running *BSD.

      How then is it possible to say that *BSD wouldn't be as popular without Linux? =P

    3. Re:BSD wouldn't be as popular without Linux by Anonymous Coward · · Score: 0

      Well, more complete idiots use Linux than who use BSD. There's a barrier of entry requiring a triple digit IQ. That kills off half the populace.

    4. Re:BSD wouldn't be as popular without Linux by Camelot · · Score: 1
      It is true that I might not have given *BSD as much recognition as it would have deserved, and, yeah, of course Linux owes a lot to *BSD and Mother Unix in general - but that is not the issue.

      Some *BSD people feel that *BSD would be right where Linux is now, had Linux never existed, and this is what I disagree with (for reasons that I outlined in my previous post). *BSD (and other unices) have been silently running the world - and that is what they would still be doing, had Linux never existed. Microsoft would be free to reign in the desktop world, eating away the UNIX dominance in the server realm.

      As you can see, this has absolutely nothing to do with what *BSD had done before Linux entered the scene, and everything to do with what *BSD might have done if Linux hadn't done that. This is, of course, pure speculation.. but you should ask yourself: Would a BSD distribution be having billion-dollar IPOs ? I think not.

  127. Personal reason for not liking it: command options by Clonezone · · Score: 1
    My Dad did/does work for Bell Labs. I grew up using SysV, so, I got used to the SysV versions of the standard commands. I feel more comfortable with "ps -ef" than "ps -aux".

    --

    --

    He's seeing monsters. He's losing his mind and he feels it going.

  128. Re:Personal reason for not liking it: command opti by Anonymous Coward · · Score: 0

    What do you mean "ps -aux"? What's that silly minus doing there? :-)

  129. Kirk and Linux by Anonymous Coward · · Score: 0

    Yes, the only figure in the BSD world that comes close to Linus is Kirk, and he just doesn't have the cult following. He's over 40. He didn't actually write the whole kernel. But he's very good with trying to embrace all camps, with not flaming, and with being a trooper.

  130. Blame AT&T by David+Muir+Sharnoff · · Score: 1

    Linux simply got a head start while the BSD camp was distracted by the AT&T lawsuit.

    *BSD is growing just as fast as Linux. It's just a couple of years behind.

    I don't know what the long-term picture looks like. Either operating system could falter. Mostly growth of Linux is good for *BSD and vice versa.

    1. Re:Blame AT&T by Anonymous Coward · · Score: 0

      David, it would be more honest to say that *Linux was growing along with *BSD. Or to drop the stars. Look at SuSE/Linux, for example.

    2. Re:Blame AT&T by Anonymous Coward · · Score: 0

      BSD isn't growing just as fast as Linux. And it isn't a few years behind. It's many years ahead. Show me the operating system without BSD sockets, for example.

    3. Re:Blame AT&T by David+Muir+Sharnoff · · Score: 1

      Sorry, perhaps I should have been more clear. I was talking solely of market share and mind share.

      As for as technology goes, I think FreeBSD solves my problems the best. That said, I did my competative analysis nearly five years ago. I've been very happy with FreeBSD ever since and thus I have not done a detailed comparision since.

      Nothing I've heard from other people in the interm has made me think I would get a different answer now. I run an ISP (Idiom) and my analysis reflects my requirements. Here's how I think things stack up now...

      FreeBSD: focus on performance and stability (exactly what I want!). Note that stability requires security.

      Linux: focus on features, too many players and too much energy to be really stable. Lots of fun and what I would reccomend for most new unix users.

      NetBSD: focus on doing things right. Glad someone is, but I'll use something else until they finish :-)

      OpenBSD: focus on security and integration of encryption. Mostly follows NetBSD development.


  131. Hmmm. Should I give FreeBSD a Try??? by BweeDwee · · Score: 1

    This article is oddly timely for me since my subconscience lately has been bubbling up little whispers to ditch Linux and move over to FreeBSD. Is this irrational on my part? I love Linux, don't I? Ok, Ok, I know AM worried about all the recent IPOs and Linux certification and I do have this irrational fear that the suits aren't far behind and when the suits get involved the inevitable ruination waits in the wings. But to ditch something that's provided so much intellectual pleasure? Plus there's a whole new cast of characters in FreeBSD land - who are they? Are they friendly? Are they open to newbies asking a bunch of dumb questions?

    Aaahhhh! Maybe "those guys in the basement" as Steven King calls them aren't done figuring it out yet. I guess I'll wait a little longer.

    1. Re:Hmmm. Should I give FreeBSD a Try??? by Anonymous Coward · · Score: 0

      Try Open/BSD, or Free/BSD. Or both. You won't be unhappy. Well, unless you prefer Windows.

  132. Re:Linux=Newbies; BSD=Robust by Null_Packet · · Score: 1

    Linux is a great starting point for many, many new people in the Unix world. With that said, almost every single person I know that uses *BSD is someone who came from linux, not from another OS. OpenBSD for example comes locked-down out of the box. The ports tree in BSD lets you install anything after that. A good comparison is between a Redhat 6.1 install and an OpenBSD 2.6 install. Redhat's GUI frustrated me to no end, and there was no way to break out of it that I could see. Redhat does not have readily-identifiable links to it's docs from their main page- Open and FreeBSD do. Open and Free also use man pages- a central reference for any command in BSD. The 2.6 install was a little different, but I did not epxect it to be the same- so I printed out the install.i386 html doc- I never had to ask a fellow user a question when I installed Open 2.6. Let's Recap:

    Linux Pros:
    Easy install (for even the lamers)
    Lots of Software
    Lots of Documentation
    Linux Cons:
    >Not everyone wants or needs a GUI install.
    >Messy dependencies, especially with RPM's
    >HOWTO's written by my baby brother- seemily never profread

    BSD Pros:
    >Centralized Documentation
    >Ports Tree (ports.tar.gz rocks!) for *easy* installs of anything for BSD
    >Lean,mean installs- FTP installs from one floppy was never easier!

    BSD Cons:
    >New users don't like to read, especially docs
    >Linux users are used to gurus massaging them through everything- this is not the case with Open or Free
    >Gnome hasn't been ported to BSD (hooray!) due to problems with security and Gnome. (not sure if this is a con)

    Null_Packet


  133. Re:Linux=Newbies; BSD=Robust by Anonymous Coward · · Score: 0

    Some people came to BSD from VMS. No, really. It's true.

  134. Solaris UFS w/ logging by Anonymous Coward · · Score: 0

    I'm using plain old UFS under Solaris, but all of my volumes are mounted with the "logging" option. That alone is the best reason for using Solaris 7. I haven't done an fsck in over a year (Since before Solaris 7 came out).

    1. Re:Solaris UFS w/ logging by Anonymous Coward · · Score: 0

      ufs w/logging? maybe I'll have to install Solaris7 (x86) on my of my boxes to see it in action. The last version of Solaris I used day-to-day was 2.5.1 and 2.6 (when it just came out).

      Working in a FreeBSD shop, my Solaris knowledge is atrophying. --clark

  135. AMEN TO THAT!!! by Anonymous Coward · · Score: 0

    Finally someone with some sense :)

  136. Being at the right place at the right time by SerpentMage · · Score: 1

    I think the question of why Linux is more popular than BSD should not be over-emphasized. You could argue this point over that point.

    But it really is being at the right place at the right time. Linus is a popular person who has a good personality. People LIKE HIM...

    It is like asking why Microsoft is more popular than Apple or UNIX. Microsoft was at the right place at the right time.

    --

    "You can't make a race horse of a pig"
    "No," said Samuel, "but you can make very fast pig"
  137. I was there by Mr.+Protocol · · Score: 2

    No one seems to have mentioned that this article is shot full of errors. The first one's in the first paragraph: BSD stands for Berkeley Software Distribution. The company BSDI changed the D to Design, for their company name only.

    Bill Joy didn't write free UNIX. He wrote a lot of code, but Sam Leffler, Kirk McKusick, Keith Bostic et al. are not exactly slouches either. Not to mention the whole effort was overseen on a continuing basis by a design board of academics chosen by DARPA. You like the socket interface? Thank DARPA's board. They pounded Bill Joy really hard (probably for the first time in his career) until he "got it" that most of the brilliant things CSRG came up with originally had been tried and rejected by them severally at their own institutions. The Berkeley socket mechanism was the result of several go-rounds of this sort of thing.

    Here's another. "When Berkeley stopped funding the project..." Hoo-hah. Berkeley never funded the project. DARPA did. They did it because they got tired of paying all of their research institutions in parallel just to support their computing environments: they wanted a stable base of Internet code that would be used by everybody, and they figured they'd pay for it just until commercial versions became viable. When the Internet took off the funding stopped. CSRG hung on for a year or two looking for other funding, didn't find any, and folded. There was a tag end of work there, by the way: 30,000 lines of OSI networking code (think X.25 & Co.) was inserted. I think it's probably gone by now, but it left its mark in the data structures, at least.

    Then there's that amazing quotation: "In terms of sophistication, the BSD operating system is better than Linux. What flame-bait. This was definitely true in earlier days, but these days it's probably a push, for most applications. I believe that BSD may be better for truly huge server installations, but in comparison with the total installed base, this isn't a very high percentage.

    Looking back, I think the history of Linux and BSD can be compared with current theories of the early universe. Very small things result in huge differences later on. Frankly, I don't think the preponderance of Linux over BSD has squat to do with licenses. The BSD system was designed in an encumbered environment, with everyone under license. It took two years in court to get out from under the AT&T license, which was the exact opposite of free software ("You can exchange software freely! ...so long as the other guy has this license too."). Those two years were all it took to give Linux the edge. Linux was at that time clearly less stable than BSD, which had had fifteen years to get the kinks out. But Linux was freely available and BSD wasn't. That made all the difference. I daresay that in those days the only contribution of the GPL (and it was a minimal contribution) was negative. Several largish institutions (including, as I recall, Purdue University) wouldn't let GPL software onto their campuses because their lawyers got wind of the GPL, read it, said, "We have no idea what this would really mean in court. Don't you dare go there." And, let's face it, while you can't have a software revolution without thousands of individuals pushing things at a grass-roots level, that isn't enough. Big institutions have to pick it up and support it, too, or the revolution doesn't happen. The GPL has, arguably, been of assistance in preventing some large corporations from forking private versions of Linux, but it has been of no assistance in convincing large institutions to adopt the software in the first place. Quite the reverse.

    I grew up in a BSD world. (Truth in advertising: I was on that DARPA board.) I recommend FreeBSD for really large server applications. For smaller outfits, and for desktops, I recommend Linux enthusiastically. Not for the GPL, on which I'm neutral (now THAT makes me a rarity, I think!), but for the ease of acquisition, the base of available software, and the size of the support community. (My understanding is that ease of installation for many of the Linux distributions has a ways to go yet, at least compared to FreeBSD.)

    Those actively involved in development know that GPL or not, Linux and the BSD movement trade software back and forth all the time, freely, openly, and in an atmosphere of mutual support. The bigots for one side or the other are, in the main, out of the loop. I hope it stays that way.

    1. Re:I was there by davet · · Score: 1

      Well said, Sir!

      GPL or BSDL, developers worthy of the title will continue to exchange ideas, if not source code. There is at least one case where two projects with similar goals but different licenses (GPL and BSDish) do work together. Instead of beating up on each other, they work together and both projects are richer for it.

      Lets just keep the rabid advocates on either side occupied beating up on each other, not getting in the way of those of us who want to get something done.

    2. Re:I was there by Anonymous Coward · · Score: 0

      I would argue that, due to much superior SMP support, Linux or Solaris, or BSD/OS would be a better choice than FreeBSD in the HUGE server department. Unless you advocate clusters of single CPU machines. Please elaborate (informative, factual posts please, flamers go away).

  138. Re:FreeBSD vs. Linux stability. by Dj · · Score: 1

    Um, is this in the FreeBSD code though? All the message mentions is that it was discussed on the FreeBSD mailing list. By that token Linux must be unstable as it was discussed on the Linux kernel lists.

    Or is this just Linux Nu-FUD(TM).

    --
    "You know you want me baby!" - Crow T Robot
  139. UK, AUS don't matter, its the US of A that matters by Anonymous Coward · · Score: 0

    "name one country" It doesn't matter what the other smaller, insignificant countries use, right here in the good ole US of A we spell it COLOR.

  140. The problem is definitely the BSD license... by mjuarez · · Score: 1

    Yes, Linux was the right Unix in the right place at the right time, and it took away BSD's chance to rule the world. However, a lot of people I know who work or tinker around in Linux, myself included, would have already tried out BSD if it weren't so adamant about two things: First, you can do whatever you want with the source code, including making it closed-source and selling it off, and second, that requirement to mention the University of California at Berkeley to everything you do and later redistribute. First off, one likes to give credit where credit is due, and I'd say that 99% of GPL software gives credit to the original authors somewhere in the source code, even though they are not forced to. However, forcing people to put it in is not liked by the developers, and so, they favor Linux, besides that fact that, by now, Linux is plenty more popular.

    And second, it's a lot more "cool" belonging to a community where all involved cooperate and share their code, instead of hiding it and trying to sell it to you later. It's more of a sense of belonging to a truly free community, one that can't be tarnished by people taking all that software and selling it repackaged as closed-source.

    I think that, mostly, describes my feelings on the subject. Just my $0.02...

    1. Re:The problem is definitely the BSD license... by Anonymous Coward · · Score: 0
      Linux was the right Unix in the right place at the right time, and it took away BSD's chance to rule the world.
      BSD is not a meglomaniacal fantasy. They don't want to rule the world!

      And second, it's a lot more "cool" belonging to a community where all involved cooperate and share their code, instead of hiding it and trying to sell it to you later
      This is pure FUD. All the BSD distros share code freely. What the hell do we care if some embedded-BSD video apparatus has some supercool algorithm in their device driver, and they don't want to give it away because they invested serious bucks on developing it and it allows them to feed their children? We don't care. And of course, the same can happen with Linux.

      Damned FUDders.

    2. Re:The problem is definitely the BSD license... by Graymalkin · · Score: 2

      That is just bullshit, who decides not to use BSD because they have to add a comment about the original authors.

      --
      I'm a loner Dottie, a Rebel.
    3. Re:The problem is definitely the BSD license... by Anonymous Coward · · Score: 0

      It's like the Baptists who won't use BSD because of how many gay people are associated with it. Remember that thing a few months ago? I don't have the link anymore, but it was an attempt to make a Christian Unix, one without homosexual influence. I'm not kidding.

  141. #linux by Anonymous Coward · · Score: 0

    I know what you mean. I tried talking on #linux about some kernel issues (threading stuff) and they were complete assholes. This didn't hide the fact that they had know idea of the ansewr.

  142. BSD ports tree by Anonymous Coward · · Score: 0

    Is it true there's a BSD version of man just for the ports tree, called portman? And what happens if you ask it about Natalie? :-)

  143. Re:UK, AUS don't matter, its the US of A that matt by Anonymous Coward · · Score: 0

    And americans wonder why they dirty looks whenever they travel. :D

  144. Dude, you're my new hero by Anonymous Coward · · Score: 0

    Hit the nail on the head baby.

    FSF - Way of dino
    RedHat - Profit City
    Linux "purity" - Somewhere ahead of FSF

    Really, will the jury equate FSF to a little old lady. Sorry no. Reality bites, but that's the way it is.

  145. Re:UK, AUS don't matter, its the US of A that matt by Anonymous Coward · · Score: 0

    "And americans wonder why they dirty looks whenever they travel. :D"
    Whatcha up to catching flies?
    Yeah why should Americans travel? I mean we got it all right here.
    Q. Why doesn't the US take over the world?
    A. The welfare system is already screwed up enough

  146. The GPL is the fountain of youth by Anonymous Coward · · Score: 0
    Your two reasons are exactly why I'm using Linux and not BSD. To review: Linux was there for me to get started with, and the GPL ensures that any work I do will remain useful into the future. Sure, code released under the BSD license will be _available_ in the future, but the code may be assimilated into a more powerful, and yes, useful Borg. But once a Borg has privatized the code, they only need to make marginal improvements -- just enough to make the effort needed to duplicate the private code discourage those with their own ideas for improvement. When the Borg dies, the code is doomed to die with it.

    Contrast this with code written under the GPL, First, the GPL code base won't die. It may suffer amputations, but the organs will be available for transplant. Second, the speed of deveopment can't be retarded by assimilation into a Borg, it can only be accellerated.

  147. NetBSD, Linux, and Chronology by niemidc · · Score: 1

    On chronology: I recall NetBSD being available by early 1993; in fact I used it prior to using Linux. Minix and 386BSD were the real pioneers in this genre and date back long before the lawsuit with AT&T was resolved. Minix wasn't quite open source and was very limited; while 386BSD degenerated into a series of patches upon patches, and after a while full releases came out late to never. A lot of its users simply gave up and switched to NetBSD or Linux.

    By late 1993 Linux was way ahead of NetBSD in user base (perhaps 100,000 at that time). This is mostly because NetBSD was not aimed at general technical home users with PCs like Linux was, it was aimed at UNIX people. As a result:

    1) Linux was much earlier at taking advantage of PC hardware, without necessarily trying to make it look like real UNIX workstations. It arguably still does a better job of this, even compared to FreeBSD. This isn't necessarily an advantage if you are already familiar with UNIX workstations, but if you know PCs it is less confusing.

    2) Linux wasn't really UNIX. Linux developers haven't been afraid to add features or implementations that are different from standard UNIX design as long as the standard UNIX semantics continue to work. This may sound like a disadvantage, but it enabled Linux to gain a lot of users, and some truly brilliant developers, from the DOS/Windows world. By several estimates over half of Linux users had never used any kind of UNIX before. These DOS/Windows people added features and documentation that made future DOS/Windows people more comfortable, and it became self-perpetuating.

    3) Linux (in SLS, and in late 1993 Slackware) was much earlier in having distributions that could be installed fairly easily on typical cheap PC hardware. True, they were horrid by today's standards, but the NetBSD installation of the time was far, far harder. This locked in a fair number of users back in the 1993-1994 timeframe, before FreeBSD provided a BSD installation that was more or less as easy as those for Linux. Presumably NetBSD is much easier now; but back then hardly anyone who didn't already know UNIX quite well could have installed it. This is not intended as a criticism -- NetBSD simply did not aspire to be a mass-market OS at the time, and as a result, it wasn't.

    True, Linux networking wasn't really stable at all back in 1993, but for home use that didn't matter much yet -- in fact PPP was not even widely available at ISPs until about a year later, and by then Linux had workable support for it.

  148. Yet again... by Anonymous Coward · · Score: 0

    The BSD zealots continue to make me feel insulted, and remove my desire to try BSD. (I use Linux, but I'd like to try (Free)BSD)

    1. Re:Yet again... by Anonymous Coward · · Score: 0
      The BSD zealots continue to make me feel insulted, and remove my desire to try BSD.
      And the FSF zealots do the same to the rest of us regarding Linux. If I didn't know Linus personally, I'd throw the lot of you out. But you know what? The insult comes from within you, not the detractors. You are only hurting yourself.

      Go get a BSD distro and play with it. Ignore the loudmouths.

  149. Re:High Volume Web Sites by the+eric+conspiracy · · Score: 1

    Really man, four sites. Is that all you could come up with. A couple no name sites. No mp3.com or Yahoo, or Netcraft.com for that matter..

    Really. All I needed was one to prove my point. The man said NO high volume Linux web sites. Do you think I am going to sit here and do a flippin' web survey and list all of them? I have at least part of a life. As far as being no name, I think you look pretty foolish claiming Netcraft is a bigger name than any of the ones I listed.

    Novell, NT, SCO and many other Operating systems can as well.

    So what? I never said they couldn't.

    just look at the Caldera vs MS suit...

    Yeah, just look at it. The judge recently threw out all of Microsoft's efforts to prevent a trial. Last I heard the jury convenes in early February.

  150. Re:Personal reason for not liking it: command opti by TeChYMaN · · Score: 1

    FreeBSD does not complain about the hyphen. Linux, being the pain it is, does.

  151. Re:Linux=Newbies; BSD=Robust by reg · · Score: 1

    GNOME not ported?

    cd /usr/ports/x11/gnome && make install clean; some day...

    -Jeremy

  152. The devil rules. by Anonymous Coward · · Score: 0

    tt> ,,
    ,(&nbs p;).
    |\,--_ /|
    /_&nbs p;_`/
    /-.,-.`&nbsp ;\
    ||&nbs p;\\
    _\O|O| |
    (___)`--'_&n bsp;/
    `.______/`/& nbsp;
    `.__,& nbsp;,/
    /\
    |&nbsp ;|/\
    \_/`-'\/
    ,----`\&nbsp ;/
    \_,-----'\ \________/&n bsp;dugsong.


    sed is your friend. Dammit, /. fucks it up, but you get the point.

  153. [sigh] by Anonymous Coward · · Score: 0

    Next time, when you want to avoid the point entirely for the sake of your own useless, inflammatory rant, try throwing in some gratuitous references to communism, the Third Reich, and personal hygiene. As it is, this gets only a C.

  154. Re: and BSDers are nastier than Linuxers by Anonymous Coward · · Score: 0

    But how do they compare to Slashdot posters? That's the test of true nastiness.

  155. Re:FreeBSD vs. Linux stability. by Guy+Harris · · Score: 3
    See this URL : [ http://kt.linuxcare.com/kt19991220_47. html#1 ]for one such example..

    Oh, you mean the discussion that includes

    Erich Boleyn, an Architect in an IA32 development group at Intel, also replied to Linus, pointing out a possible misconception in his proposed exploit...

    ...

    There was a long clarification discussion, resulting in a complete turnaround by Linus

    i.e., that Linux later accepted the change:

    "Everybody has convinced me that yes, the Intel ordering rules _are_ strong enough that all of this really is legal, and that's what I wanted.

    ...

    Thanks, guys, we'll be that much faster due to this.."

    As for "others can be found elsewhere", please give references - perhaps they're also not bad implementations.

  156. Re:NT stability by Anonymous Coward · · Score: 0

    Well, one of the main reasons nobody tries to extend NT is that Microsoft will just step on your improvements. For example, you could hack on Gnome, and eventually users will see your improvements. Any alternative Window manager for NT is just going to break with the next service pack. Likewise with Mozillia, with IE staring you in the face, why bother?

  157. Bigots and Liars by Anonymous Coward · · Score: 0
    Oh here's all the kernel code Linux has from BSD
    I see you and yours have at last chosen to dispense with distraction, dissimulation, and disingenuity, plowing right through to blatant prevarication. In short, you're lying. Do as you were told. Grep the src tree, not the sys tree. If you do not produce those data, then we know what you're hiding.
  158. FUD Levels on High, Captain by Anonymous Coward · · Score: 0
    Reading through the many postings in this article, you're struck by how many damaging urban legends there are about BSD. You see these repeated by five or six people, and soundly rebutted by hard data.

    It would be a great service to the community if someone could summarize those points as they turned up here so that we don't have to go through this again.

    Could someone please do that?

  159. Re:Linux=Newbies; BSD=Robust by Anonymous Coward · · Score: 0
    GNOME not ported?

    cd /usr/ports/x11/gnome && make install clean;

    Thank for FUD killing!
  160. as much as used to like d.net by Anonymous Coward · · Score: 0

    by that logic, there are about 220,000 computer users in the world..

    nice try, but no. that simply won't work.

  161. well, thats the beer by Anonymous Coward · · Score: 0

    um, yea. im bitter. sure. really.

    oh, and by the way, sorry to hear that your mother dropped you on your head when you were a baby.

    idiot.

  162. BSD = Zen ; Linux Baptist Fundamentalism by Anonymous Coward · · Score: 0

    yeay verily ...

  163. Where to get FreeBSD ISO (cdrom) images by Anonymous Coward · · Score: 0

    ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/IS O-IMAGES/

  164. Linux promises free sex; BSD only free beer by Anonymous Coward · · Score: 0

    It's a no brainer. Linus Torvalds promises free sex to all Linuxers. Remember his famous quote: "the best free sex is Linux sex, not BSD beer"?

  165. um...how about the GPL? by pope+nihil · · Score: 1

    proprietary software for linux yes, but proprietary changes to the linux kernel would be illegal. unlike *BSD.

    1. Re:um...how about the GPL? by Anonymous Coward · · Score: 0
      And what the fuck is wrong with custom hacks to the kernel? You been listening to Jimmy Swaggert in one ear and Karl Marx in the other?

      Doesn't matter. It can all be done through loadable device drivers. Even though Lord Saint Richard says Linus has misapplied the GPL, it's still legal. We've had pseudo-devices since long before Unix.

  166. Re:Only 0.24% YUP 0.24% LINUX users. by Anonymous Coward · · Score: 0

    There is a famous stats site run by non-bigoted big dollars that counts 8 MILLION DAILY POPULAR browser clicks. The hundreds of participating news and entertainment web sites run banner click capturing software that feed ACCURATE and reliable figures that show Windows and Macintosh make Linux users look about as popular in comarison as Amiga fanatics. 0.24% was the monthly tally the last time I checked a few months ago. 0.24% Linux web users!!! Bwaaa hahhahahhaaaa Long live Apple!

  167. GNOME on BSD by Lazaru5 · · Score: 1


    Hmm...yes..I supposed technically there's not GNOME "port" and that's because "./configure && make install" works just fine.

    To ease this though, GNOME *IS* in the Ports Collection (Note 'Port' the noun != 'port' the verb) so a `cd /usr/ports/x11/gnome && make install` will fetch and build GNOME with all the necessary dependancies.

    Please post responsibly. Don't spread misinformation.

    --

    --
    My comments and opinions completely reflect those of anyone and anything I am remotely associated with.
  168. hey dickhead by Anonymous Coward · · Score: 0

    The manuals are often WRONG. Icecast/Liveice 1.3, for instance, when PROPERLY set up according to the manuals, will crap out on you with the error "stupid headers" in icecast. shout will work just fine. This was also true with the old PPP HOWTO - the documentation was wronger than a fucking wooden nickle but then I did it my own way and got it working in two minutes. The point is you're wrong, dickhead!

  169. freebsd sucks by Anonymous Coward · · Score: 0

    hey, u wanna know why nobody uses freebsd? because it SUCKS! that's why

    1. Re:freebsd sucks by Anonymous Coward · · Score: 0

      almost as hard as your mom sucks bill gates, eh flamer?

  170. Divided we stand. by cnflctd · · Score: 1

    Maybe Linux is more widespread because Linus isn't responsible for the whole OS? He just puts up a new kernel every few weeks, and lets others handle the packaging. But the BSDs do it all. And because, say, FreeBSD is presented as a single production, would-be distro-makers lack motivation to brew their own versions, ala RHAT, Corel, Mandrake, etc. Kind of like Apple's originally closed architecture, and IBMs quickie off-the-shelf, but ultimately more popular PC.

    Maybe that's why I like Debian. Every little .deb is maintained by dedicated volunteer(s), while RHAT is responsible for the whole ball of wax, just like FreeBSD is. Maybe the Linux motto should be "let's divide ourselves, and conquor."

    (Boy, this is written badly. instead of giving up, I think I'll post anonymously.)

    --
    I'm cool like a fool in a swimming p-p-pfft-pool
    1. Re:Divided we stand. by Anonymous Coward · · Score: 0

      God damn it! I'm sure I depressed the "post anonymously" button.

  171. Linux supports Java by Anonymous Coward · · Score: 0

    BSD is a poor cousin because of its poor Java support. Java is the only language that matters now. BSD ought to get onboard or it will be left behind.

    1. Re:Linux supports Java by Anonymous Coward · · Score: 0

      "Java is all that matters"? Ha! Hahahahahahahahhahahahahaha. Try again, bucko. Can't build a kernel with Java.

    2. Re:Linux supports Java by Anonymous Coward · · Score: 0
      All you need is a native code JVM (or a Java CPU) with a convention for mapping interrupts to method calls, and native methods (or special opcodes) for irregular bus I/O (as lots of crummy hardware isn't memory-mapped).

      What do you call Sun's JavaOS, anyway? It's being phased out, but it worked!

    3. Re:Linux supports Java by Anonymous Coward · · Score: 0

      "What do you call Sun's JavaOS, anyway?"

      A ridiculously bad idea? A disaster that almost happened?

  172. FreeBSD better than ice cream by Anonymous Coward · · Score: 0

    Let me start by saying that I am always right, and I have always been right. FreeBSD rocks and everything else sucks, so go ftp 3.4-RELEASE now, or better yet, buy the cds. No one likes being wrong, so quit being a schmuck and go get FreeBSD, now. Chicks will dig you and men will envy you, so what are you waiting for?

    1. Re:FreeBSD better than ice cream by Anonymous Coward · · Score: 0
      what are you waiting for?

      for you to shut the fuck up, of course.

  173. FreeBSD ufs w/ Softupdates isn't a journalling FS by Anonymous Coward · · Score: 0

    - Linux has several in testing.
    - maybe someday FreeBSD will have a jfs but *not* if it's seen as something Linux has and FreeBSD doesn't. It will be rejected on principle in that case.

  174. 2,000,000 users is some kind of failure? by SurfsUp · · Score: 2

    2,000,000 is an awfully big number of users. In no sense does it represent any kind of failure.

    Frankly I'm stunned by the swift rise of FreeBSD - I thought nothing would ever touch the success of the Linux movement. Being a relatively new Linux convert I'm willing to admit that I suffered from a kind of parochialism with respect to FreeBSD - when I heard news of it I kind of wanted not to hear it because, hey, I've already found the answer and it's Linux, right?

    I think I'm probably not alone in that: many of you probably have the same feelings (you know who you are:) Recently though my attitude towards the BSDs has changed from a kind of jealousy to admiration and respect. A lot of that has been due to the sympathetic and interesting coverage on Slashdot. A larger part of it is the obvious truth that there's a lot to respect technically in the BSD's - look at the security audits just for one thing. I now see the BSD's as another tool in the toolbox - it's what I'll do when I need a slimmer, tighter box that doesn't necessarily have to get all dressed up to kill.

    Now, I don't seriously believe that the BSD's will ever pass Linux in popularity, for reasons that are set out nicely in your article and are beaten to death elsewhere in this thread. But neither do I believe that there is room in this world for only one open OS, especially when they are interoperable. The BSD's will help us achieve world domination. They are but one more division in the open source army.

    --
    Life's a bitch but somebody's gotta do it.
    1. Re:2,000,000 users is some kind of failure? by Anonymous Coward · · Score: 0
      Being a relatively new Linux convert I'm willing to admit that I suffered from a kind of parochialism with respect to FreeBSD - when I heard news of it I kind of wanted not to hear it because, hey, I've already found the answer and it's Linux, right?
      That's how Unix people feel about Linux.
  175. Re:FreeBSD vs. Linux stability. by Anonymous Coward · · Score: 0

    Aren't you forgetting an important part? The part at the end where the source code is shown, that Linus didn't actually make the change, just made a comment saying that it would be nice if he could.

  176. FSF Liars by Anonymous Coward · · Score: 0
    I see the FSF zealots still haven't grepped the Redhat/Linux src tree (where the blazes is it? SRPMS suck dead donkey dick) for BSD programs. Well, I should say they haven't announced it. They probably grepped it and were embarrassed.

    We don't have to create BSD/Linux. It already exists.

  177. First mover effect by Anonymous Coward · · Score: 0

    It has nothing to do with proprietary forks. Linux was in the right place at the right time with a small, simple implementation of a UNIX-like API. BSD was complex, and originally required a licensed copy of the UNIX source in order to function. If OpenBSD and FreeBSD had been around in '91 or so, things might be different.

  178. Yea, verrily by autechre · · Score: 1

    I've been using ext3 (journaling ext2, still considered quite experimental) for a month now with no problems. I've been using Mozilla for even longer than that, so I guess I'm just that sort of guy :)

    In my eyes, BSD seems like the "safe" OS for servers, though this can also translate into it being the "boring" OS for people like me; I take backups and I want the new features now...if the developer says they work for him, OK. Everything always seems to work for me...perhaps it's the "Magic Ass" theory at work...


    --
    WMBC freeform/independent online radio.
    1. Re:Yea, verrily by Anonymous Coward · · Score: 0

      Take a look at NetBSD. Considering that it had USB, and varuious other hardware support months before Linux did, and generally is quicker on most platforms, there are lots of new technologies. It has a great memory manager too. Its just that the important features are not the ones that sound extreme and 'cool.' So BSD is safe, its slow adding code designed more for media attention than real usage.

  179. Why this infighting? by Red+Pointy+Tail · · Score: 1

    When you are threatened, it makes sense to close ranks with your allies and set up the fort.

    So why this infighting? Windows NT caught up in the enterprise share because IBM, HP, Sun, BSD are too busy trying to compete with each other (or selling their propietary hardware) to bother with improvement or innovation. Starting Linux/BSD camps wouldn't to help.

    Don't flame me, but I believe Win2000 represents a genuine threat to acceptability of Unix. Just because WinNT is crap now does not mean it will always be crap in the future - never underestimate M$ ability to improve and most especially to market and brainwash MIS managers. Also Win2000 got quite an impressive bit on the new features (rather if it really works still is yet to be seen).

    Personally, I would just like to see our most talented guys putting their effort to Linux all the way and, sorry to say, screw BSD :)

  180. Tell em George by datazone · · Score: 1

    Its all penis envy if you ask me.
    Its like that question you hear people ask: "do you think you are better than me?"
    if you say "yes" they feel offended, if you say "no" you acknowledge that you are as good or worse than the person. So, you damned if you do, and damned if you don't.

    Like the man said, "use what works best for YOU"

    --
    Its spelt "L-I-N-U-X", but pronunced as "Free Beer"
  181. Re:FreeBSD vs. Linux stability. by Guy+Harris · · Score: 2
    Aren't you forgetting an important part? The part at the end where the source code is shown, that Linus didn't actually make the change, just made a comment saying that it would be nice if he could.

    That part showed up after that issue of KT came out; I don't know whether it showed up after I checked it earlier today or not (I'd assumed that issues of KT are invariant after publication, and I saw that issue before the note was added).

    Some stuff in the FreeBSD archive indicates that they may have decided that the unlock optimization couldn't be done that way, either, although I'd have to plow through a ton of -current code and, perhaps, CVS logs to see exactly what they did do - see this message, for example, and this message.

    (And, the hypothesis in, as I remember, one of the linux-kernel messages nonwithstanding, the FreeBSD folk do have P6 machines - some of Matt's timing experiments were, as I remember, done on a Pentium III.)

    The comment in the code also suggests that it might be useful to have a way of building a kernel without the lock, if it truly can be removed on all but the early PPro's to which the comment refers.

  182. Way to avoid the issue. by Wakko+Warner · · Score: 1
    What about the mailinglist then? Since the core FreeBSD developers frequently post to the list, I'd say it's a pretty good barometer of the camp as a whole.

    I don't personally like what I've seen of it, either.

    - 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?"
  183. There will probably never be one by scabpicker · · Score: 1

    When an os is based on bsd, due to the license, the person releasing the os is allowed to call that program their own. Well, if I were going to try to make my buisiness have a billion dollar ipo, I would call my os something else, not BSD. This would make it seem that I had something that others did not have, and make my business have a percieved edge against the competition. I may be completely incorrect, but I believe I have heard that Solaris and BSD are related in the past somewhere this way (maybe through Bill Joy). Sun is not a billion dollar ipo company, but I wouldn't sniff at their value.

    --
    _this is not a signature_
    1. Re:There will probably never be one by Anonymous Coward · · Score: 0

      Where in the Linux licence does it state that an OS which uses the Linux source code must be called `Linux'? As far as I know, it doesn't, but I may very well be wrong.

      At any rate, the hype is based on the name, not the product. A Linux release called something other than `Linux' would lack the hype. Of course, Red Hat is increasingly soaking up the Linux hype, and may very well displace Linux as the focus of that hype. If that happens, the Linux name will lose its value, and Red Hat will then own the key piece of intellectual property (the hyped name).

  184. US taking over the world? by Anonymous Coward · · Score: 0

    Yep, that would be amusing. They fire off missiles that blow up their own tanks, stuff like that.

  185. ummm. you're not too bright by Anonymous Coward · · Score: 0

    ever here of a percentage?
    i would bet the statistical concept of a "sample" would apply..... dumbass

  186. Re:Linux=Incoherent; BSD=Integrated by Anonymous Coward · · Score: 0

    Agreed. I use both debian and FreeBSD and while the base Linux kernel has had a few more problems, they are still very similar in quality.

  187. Re:Linux=Newbies; BSD=Robust by Anonymous Coward · · Score: 0

    I agree with the fact that many have come directly to linux first (I myself came to BSD first because of running into so many IRC and shell servers running BSD [80% at least]).

    I do not, however, agree that many linux installations are easier. I found the FreeBSD install easy enough coming directly from using Windows NT. I even printed out the handbook and read it in school so that I could learn all the neat stuff about it without being in front of a computer terminal.

    I think there are a number of people who are biased to the system that they had learned first and after trying linux they they any deviation from what they had learned to be against user intuitiveness. I do not believe this as I used the sysinstall system to completely install the OS. I also used sysinstall to configure X -- and eventually figured out that using startx would start it. From there, it was just learning how to install ports with cd /usr/ports/$program/ make install or just using sysinstall to install packages.

  188. Re:Only 0.24% YUP 0.24% LINUX users. by Anonymous Coward · · Score: 0

    Counting HTTP requests severely biases the results towards users too ignorant to set up a proxy cache appropriately. And it's pretty clear that the technical sophistication to do this is not evenly distributed among users of different systems. Their "ACCURATE" figures are basically omitting entire countries, just ask ciwah.

  189. Shut the fuck up, moron. by Wakko+Warner · · Score: 0
    Call me back when you can compile your fucking BSD *kernel* without GCC, asshole.

    - 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:Shut the fuck up, moron. by Anonymous Coward · · Score: 0

      Irrevelant. There are many other compilers in this world. They don't make you name your fucking operating system out of them, nor give Richard Stallman head just because you used the VFS's compiler.

    2. Re:Shut the fuck up, moron. by Anonymous Coward · · Score: 0

      Are you suggesting that Jordan Hubbard gives RMS head?

      After all, FreeBSD uses gcc.

      Arguing was more fun before the education system went to hell. Please tell me you dropped out before getting a diploma.

    3. Re:Shut the fuck up, moron. by Arandir · · Score: 2

      Ah, yes. GNU advocacy at it's finest. Makes me so proud to use Linux. After all, there was no such thing as Free Software until the concept mythically sprouted from the forehead of Richard Stallman. Since then we have been freed from the bondage of, of, of... non-GNU software.

      After all, the GPL demands that all those who use gcc must worship Richard Stallman.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  190. When you're out of sticking points... by Wakko+Warner · · Score: 1
    ...point out spelling, punctuation, or capitalization errors. Isn't that one of the Usenet rules?

    - 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?"
  191. Request for Slashdot Poll by mvw · · Score: 2
    Who really believes that the success of Linux is due to the GPL? I am not. There is no reason to believe that his kernel project would have grown much different, if he used a BSD/XFree86 style license.

    I would really like to see such a Slashdot poll

    I bought BSD/Linux because

    1. it is cool
    2. my friends got it
    3. it runs stable
    4. it runs stable and comes with source
    5. it runs stable and comes with source under GPL
    6. it runs stable and comes with source under BSD license
    7. Hemos uses it

    My personal guess is that only those who actually program might rank the type of open source license so high that it influenced their decision. And these are a minority, I believe, maybe ranking in the ten thousands but not in the millions.

    1. Re:Request for Slashdot Poll by slim · · Score: 2

      I'd say the GPL has made a lot of difference to the way Linux is treated in the commercial world.

      The world is littered with non-free forks of free BSDs -- if hte original had been GPL'd, we'd all have got to share those changes.

      For example -- I remember a BSD based Internet gateway for novell networks. That will be a kernel hack, but the BSD world did not get to see the source.

      A couple of recent Linux examples are the Tivo kernel changes and the port to IBM System 390. It's unlikely that either of those sets of code would have been released as source if the GPL didn't force it.

      That said, we're seeing a lot of Apache code gifted from commerce (although there's a lot of proprietary stuff I'd also like to see freed). I'd say that Linux has proved to many large companies that freeing the source is not necessarily an act of selflessness. Now they've been forced to try it, they can go on to free source even when the licence says they don't have to.
      --

  192. BSD, Linux... stop the infighting. by Anonymous Coward · · Score: 0

    Around 1991-1992, I started getting into playing with UNIX variants. At this time, almost everyone and his dog has a commercial UNIX. Dell, Mt. Xinu (had source with it), Sun (Solaris 2.x was not around, so it was still SunOS 4.1.x, AIX was out, being a BSD with SVR4 extensions, and Apple's A/UX was out, System V to the core. NeXTStep was out, very much BSD. All of these either required fairly expensive hardware and/or the OS was priced too high for a humble University of Texas student. So, at that time, were two new varients that were free to play with. One was Linux (3 dists, TAMU, MCC, and SLS), and the other one was 386BSD, which the binaries came on 11 floppies, X and source, about 20-30. 386BSD from Jolitz was very stable, and from booting the compressed boot/root disk was amazing what it had on, on just one floppy. I promptly had 386BSD running, and posted for help for two small issues in the BSD/386 newsgroup (BSD/386 and 386BSD shared the same newsgroup. BSD/386 was BSDI's commercial UNIX.) I got the answer I needed quite quickly, and politely. (A bug in 386BSD would freeze the console until you logged in via a serial port, and did an 'su'. Bog knows why that fixed it.) I played with that, had docs on Linux, but I never started using Linux until about 1993. At the time, development was seeming to be stagnent on the 386BSD front, and Linux was _the_ OS to hack for. I soon got SLS, then Slackware (which I still keep a subscription to, as that distribution deserves my support). Soon after, 386BSD broke into two camps wanting different things -- FreeBSD for better x86 tools, NetBSD for better cross-platform portability. Around mid-1995, OpenBSD split off, mainly for personal differences, but for other factors as well -- having very good security, IIRC. Now, we have three BSD's, each very solid. (All have S/KEY built into the login sequence, so if you don't have an ssh client, you can still telnet in, using a one-time password algorithm, something I had to bolt onto Linux) All in all, neither is better, each has a different reason for being around, and the *BSD and Linux infighting is just plain foolish. Microsoft is the target, and all 4 OS's are now in the 'catch MS's taillights' mode, instead of going into new territory. Stop the infighting, and just write code, guys.

  193. Re:Disclosed Source by Tony-A · · Score: 1

    You _can_ find out what it does, rather than trying to guess from poorly written specs.
    Not as good as BSD/GPL licensed source, but _much_ better than nothing.

  194. Re:UK, AUS don't matter, its the US of A that matt by Anonymous Coward · · Score: 0

    Unless you're posting via a wirelss connection, hiding in some cave somewhere in the desert, in the company of a couple of escaped "Repubik of Texas" weirdos, then you need to be reminded Texas is not a country. The only interesting thing to come out of Texas was Mike Judge, the butthole surfers, MDC and the dicks.

  195. Re:UK, AUS don't matter, its the US of A that matt by Anonymous Coward · · Score: 0

    Texas joined the Union from a unqiue position: it already was a country. It has the constitutional right to withdraw from that union at any time it pleases and return to its status as an independent and sovereign nation.

  196. Linux, BSD, UN*X, are ALL inferior to..... by Anonymous Coward · · Score: 0

    RSTS/e

    That's right!
    DEC had this OS shit sewn up!
    (giggle)
    -johnny

  197. HE! Moderators! by Eon78 · · Score: 1

    Why isn't this whole damn flamebait tree set to -1? OR -99999 for that matter?

  198. 10 Million????? by Anonymous Coward · · Score: 0

    Where do you get these ridiculous numbers???

  199. Re:Linux=Newbies; BSD=Robust by gaj · · Score: 1

    > Linux is a great starting point for many, many new people in the Unix

    Agreed.

    > world. With that said, almost every single person I know that uses
    > *BSD is someone who came from linux, not from another OS. OpenBSD for
    > example comes locked-down out of the box. The ports tree in BSD lets

    Which is a *good* thing. Closest thing to this I've used in the Linux
    world is a bone stock Slackware, tho many feel Debian is also reasonable.
    RedHat, tho a very nice distro, need not apply here!

    > you install anything after that. A good comparison is between a Redhat
    > 6.1 install and an OpenBSD 2.6 install. Redhat's GUI frustrated me to
    > no end, and there was no way to break out of it that I could see.

    Um...you mean other than reading the clearly described choices on the
    install boot screen and choosing the non-GUI install?

    > Redhat does not have readily-identifiable links to it's docs from
    > their main page- Open and FreeBSD do. Open and Free also use man

    Um...other than the section titled "Linux Documentation" with links to
    LDP, Redhat manuals, etc.? Did you ever even *go* to their site?

    > pages- a central reference for any command in BSD. The 2.6 install was

    Um...last I checked (just now) so does Linux. Have you every actually run
    Linux? We also have the LDP and a well defined place to put app specific
    docs (/usr/doc). Works for me.

    > a little different, but I did not epxect it to be the same- so I printed
    > out the install.i386 html doc- I never had to ask a fellow user a
    > question when I installed Open 2.6. Let's Recap:

    > Linux Pros:
    > Easy install (for even the lamers)

    What is the point of the parenthetical there?

    > Lots of Software
    > Lots of Documentation
    > Linux Cons:
    > >Not everyone wants or needs a GUI install.

    Which is why many (most?) of us don't use 'em. Get your facts straight.

    > >Messy dependencies, especially with RPM's

    Or usefull ones, depending upon your perspective. For a home or small
    office user deps can be a godsend. I personally run Slack for the most
    part, and compile much of my own software, so it's pretty much a no
    issue for me. This point can be seen as either pro or con...thus there
    are choices ether way...the only choice that gets *really* messy is "both".

    > >HOWTO's written by my baby brother- seemily never profread

    Pot. Kettle. Black. Is any of this ringing a bell?

    > BSD Pros:
    > >Centralized Documentation

    Um... so man pages and /usr/doc doesn't count?

    > >Ports Tree (ports.tar.gz rocks!) for *easy* installs of anything for BSD

    This does work well. But most Linux distros have pretty damn easy package
    install tools as well. (RPM, apt, installpkg/upgradepkg)

    > >Lean,mean installs- FTP installs from one floppy was never easier!

    Um...deb comes damn close, and Slack can as well. Hell, even the much
    maligned Redhat can do a two floppy FTP install.

    So what. CD install is usually easier & faster.


    > BSD Cons:
    > >New users don't like to read, especially docs

    Looks like that is a con for a certain BSD user trying Linux anyway.
    Sheesh. *Most* people are stupid. It's a fact of life. This is a problem
    for anything more complicated than dialing a phone. Sucks to be them.

    Since this is the case, why not profit from making a no-brainer install
    for those to lame to even read the screen messages? Doesn't hurt those of
    us who don't need it.

    > >Linux users are used to gurus massaging them through everything- this is
    > not the case with Open or Free

    Well...some BSDers are happy to give help when asked, and some Linuxers
    are to lame or scared to admit they don't know it all to help. Works both
    ways. However, painting "Linux user" with such a broad brush is stupid.
    There are many more newbies running Linux than BSD. Comes with the 10+ times
    larger user base...even with the same percentage of newbies Linux would have
    around 10x more of 'em. "I canna' change the laws of physics, capn'" Er...
    make that arithmatic.


    > >Gnome hasn't been ported to BSD (hooray!) due to problems with
    > security and Gnome. (not sure if this is a con)

    Wa? What stops you from compiling it for BSD? Do your research, man. At least
    have enough facts straight to *appear* to know what you are talking about.

    --
    If your map and the terrain differ,
    trust the terrain.

  200. Re:Linux=Newbies; BSD=Robust by Anonymous Coward · · Score: 0
    Um...last I checked (just now) so does Linux. Have you every actually run Linux? We also have the LDP and a well defined place to put app specific docs (/usr/doc). Works for me.
    Don't be disingenuous. The standard centralized location is one reachable by a standard centralized command. That command is man. It is not netscape. It is not find combined with more. And it most certainly is not emacs, which isn't even part of the standard installation on some BSD distros. Thank God.

    No matter how you slice it, Linux has only about 10% the documentation that BSD has, and that that they have is usually a bad hack.

  201. Re:Linux=Newbies; BSD=Robust by gaj · · Score: 1

    Wasn't being disingenuous. I don't see what the problem with seeking appropriate docs in a standard place is.

    man works on Linux for basic stuff and much less than basic stuff. I'd love to see better man page coverage than there is...I'll readily admit that Linux man page support is less than it should be.

    Your attempts to "define" what a standard centralized location is is silly. For Linux, /usr/doc is the location for LDP and non-man page docs. Would I like the non-LDP stuff in man pages instead? Of course. And most of it is.

    As for the "not" examples...I'll grant netscape. I don't use it for docs. In the rare occasion that the docs I need are in HTML I use lynx. But I digress.

    I fail to see how seeking out and reading the READMEs is a bad thing. I also fail to see how find | less is any less standard than man. man is just a fancy-schmancy locate | groff | less anyway. A *nice* fancy-schmancy locate | groff | less, mind you.

    As for emacs, bleah. I, and more importantly my hands, prefer vi. Emacs is also not part of the standard install of some Linux distros. What does that have to do with centralised docs?


    --
    If your map and the terrain differ,
    trust the terrain.

  202. It's the GPL for me by Anonymous Coward · · Score: 0

    For me, the decision to use Linux was very simple to make.

    I do NOT want anybody to take my hard work and effort and take it proprietary.

    I have no problem with you making money off my work (go RedHat!) as long as the code - ALL the code - remains in the community.

    Linux, being GPLed, meets this requirement. BSD, by being hostile to the GPL and GPL-like licences, does not.

    Performance be dammed; I'll install a BSD over my cold, dead corpse.

    Incidently, BSD advocates, it was Brent Glass that helped me along to this conclusion. Because of him, I used my influence at a major manufacturing company (considering requiring all mission critical systems be open source) to convince them that the *BSDs were NOT open source - and they bought the argument.

    That's why Linux is beating you.

    1. Re:It's the GPL for me by Anonymous Coward · · Score: 0

      You're being a moron.

    2. Re:It's the GPL for me by Anonymous Coward · · Score: 0

      Merely using BSDL'd code is fine. It's contributing BSDL'd code (subsidizing proprietary projects as well) that's ethically dubious.

    3. Re:It's the GPL for me by Anonymous Coward · · Score: 0

      Wrong. It's contributing to the FSF that has ethical problems. It's coercive and immoral. The worst of all is the libraries. Virus hell!

    4. Re:It's the GPL for me by Anonymous Coward · · Score: 0
      1. Not all GPL'd projects belong to the FSF. Even if one does, you can always maintain your own fork.
      2. I can't coerce you to relicense your code. All I can do is persuade you by offering my own.
      3. Open source is the profession's only real hope for progress. Proprietary software rips off customers who don't know they could have better. How would coercing you to do the Right Thing be unethical?
  203. Re:UK, AUS don't matter, its the US of A that matt by Anonymous Coward · · Score: 0

    Well, it's a country that we should sell to Mexico, in any case.

  204. BSD? by Millennium · · Score: 2

    As I see it, there are a few reasons...

    1) PR. Not that BSD has bad PR. It just doesn't get as much of it as Linux does. Most people have at least heard of Linux, but you don't hear about BSD in the media very often. You can't use what you don't know exists.

    2) The license. Say what you will, but the non-quid-pro-quo has a lot of disadvantages, not the least of which is that it discourages development by independent authors. Look at it this way: a commercial company can do whatever it wants with BSD-licensed software, make it proprietary, and make a ton of money off the stuff (witness Solaris). Corporations have nothing to fear from BSD, the way they do GPL. An independent author could theoretically do this, but it's not practical; one person simply doesn't have the marketing power of a corporation and thus isn't going to be able to profit. Therefore, the independent author has no real choice but to keep his code free and Open-Source. This tips the balance of power, and means that independent authors usually end up working, in effect, as unpaid coders for the companies that leech off of BSD's work.

    3) Fragmentation. The fragmentation of BSD really isn't that bad. But it is there; you have three major versions (FreeBSD, NetBSD, and OpenBSD) and a few others (Darwin could, in a way, be considered one, though it's hardly a major variant at this point in time). Is this a Bad Thing? No. It's not good, but it's not bad. But it does scare most bosses. It scares them enough so that it doesn't take much extra FUD to sway their decisions (unless the bosses know what they're talking about, in which case it takes considerably more effort).

    Is BSD a bad system? Hardly; I don't have very much experience with BSD but I like what I've seen so far (though I think I'll stick with Linux all the same). But it does have a few issues. Linux does too; don't get me wrong, no OS is perfect, and they both have some way to go. It just happens that, for now, Linux is farther ahead. That might change, or it might not. Either way, it keeps things from being dull.

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

      The licence doesn't matter. And Linux is infinitely more fragmented than BSD.

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

      You say this without backing it up. I can take binaries from any linux box, and run them on this debian box (I'd have to have the required shared libraries, but GNOME isn't gonna run on BSD without GTK+ either). Now I can't move binaries from my OpenBSD box to my FreeBSD and have them work.

      How is Linux more fragmented (with facts or at least arguments this time)?

      Or did it just sound good to you at the time?

  205. NetBSD 1.4.1 ISO by Anonymous Coward · · Score: 0

    ftp://ftp.kando.hu/pub/CDROM-Images/netbsd/netbsd- 1.4.1-i386-alpha-sparc.iso (Only i386, alpha and sparc) ftp://ftp.kando.hu/pub/CDROM-Images/netbsd/netbsd- 1.4.1.iso (alpha, amiga, arm32, atari, hp300, i386, m68k, mac68k, macppc, next68k, pmax, sparc, sun3, vax) or: ftp://ftp.nuri.net/pub/FreeISO/netbsd/ ftp://ftp.se.netbsd.org/pub/NetBSD/CDROM-Images/

  206. NetBSD 1.4.1 ISO by Anonymous Coward · · Score: 0

    ftp://ftp.kando.hu/pub/CDROM-Images/netbsd/netbsd- 1.4.1-i386-alpha-sparc.iso

    (Only i386, alpha and sparc)

    ftp://ftp.kando.hu/pub/CDROM-Images/netbsd/netbs d-1.4.1.iso

    (alpha, amiga, arm32, atari, hp300, i386, m68k, mac68k, macppc, next68k, pmax, sparc, sun3, vax)

    or:

    ftp://ftp.nuri.net/pub/FreeISO/netbsd/
    ftp://ftp.se.netbsd.org/pub/NetBSD/CDROM-Images/

  207. Wow, you made a fake post...nifty by Anonymous Coward · · Score: 0

    I have done more OS installations than anyone I know. BeOS was far and away the easiest. Put in the CD, turn on the computer, select all packages and walk away. Five to ten minutes later I had the most incredible desktop OS in the world working for me.

    Sleek, elegant and powerful. Something I have not found in the free unix variants. They may be fine for web or mail servers but they just can't hang on the desktop. Even winblowz beats them for desktops.

    1. Re:Wow, you made a fake post...nifty by Anonymous Coward · · Score: 0

      Hmm.. I think that which OS suits you best for your desktop depends a lot on what you want from it and how much you know or are willing to learn about the system you use. That made me end up with a lot of different desktop systems at home, running a variety of operating systems. For things like an office suite I prefer to use an irix desktop with the apps running on a smp machine running freebsd. Most apps are either freebsd apps that I compiled myself, or binary linux or irix distributions of some kind. Why? coz the x server that comes with it together with the hardware it runs on make it a very fast and flexible x server platform. I also have both XFree 3.3.5 and a 3.99 snapshot runnimng on freebsd and linux, and actually, the freebsd one runs a few more apps then the linux one simply because it runs almost any linux app but also it runs all native bsd apps (which are often easily ported to linux tho) so thats not really a reason to choose either linux or freebsd for your desktop. Hardware support may be an issue, and when you have some weird pc hardware you may simply have no choice then either replace it or run windows, both of which usually cost money ;-) However, that doesnt mean that linux or freebsd dont support a lot of advanced hardware. Linux is a bit more active in this area, on the other hand, freebsd's code is much cleaner and better defined when it comes to standarisation, and if I run into vague hardware that is simular but not indentical to a device FreeBSD supports I usually have a much easier job getting it to work. This may not apply to most users tho, and I think the major things to consider for most users when choosing an operating system are besides apps being available for it to do what they want, the amount of knowlage it requires to get and keep the system running in a state that allows them to do whatever they wanna do with it, and in some cases if it is feasable to rely on a knowlagable person to maintain your system for you so you can just do your work on the technically best available platform for whatever you are gonna do with it. Be comes out quite well for multimedia purposes (tho imho irix beats it on that... but heh, that wont run on a pc) and I just got myself a copy and am figuring out where I can make some diskspace available for it so I can run it at home as well. I encountered it a few times and was quite impressed by how well it handles the realtime aspects of video and audio and user interaction on relatively low grade hardware. I can do quite the same with both linux and freebsd, but both require a lot more efford (and give you a lot more control over how it works if you know what you are doing)

  208. The problem here is... by Anonymous Coward · · Score: 0

    The problem here is that most slashdot users have trouble finding the power button on their computers. Few if any have ever used more than one OS, the one they try to ram down everyone else's throat (Maybe its NT, or Linux, or BSD, it doesn't matter).

  209. Re: This dude is dead on! Score 0?? I think NOT! by Anonymous Coward · · Score: 0

    Linux and BSD are growing slow because the morons in the channels will write a 5+line response, telling you in many word to RTFM. The answer some new users are looking for would require just half a line. Billions of nonsense is written every night on various IRC channels, but as of 1999 there is NO USEFUL BOOK on linux or bsd. The lamers in the channels are most likley not even competent to answer questions. Bill G. has NOTHING TO WORRY, until we figure out a way to "help". I wish, I could write a bsd/Linux book. Since I don't have access to gurus (so I can "translate" their knowledge to human understandable words) I also can be of no use to the cause. English is not my first language, please ignore spelling, Thank You

  210. userbase? by Anonymous Coward · · Score: 0

    Maybe that also has something to do with actual user base vs perceived user base

  211. Re: This dude is dead on! Score 0?? I think NOT! by Anonymous Coward · · Score: 0

    IRC is a complete loss. The medium is wrong for what you'r trying to do.

  212. I prefer Linux to ???BSD for historical reasons by dltaylor · · Score: 1

    Way back in the old days, I developed an antipathy to BSD because Berkeley insisted on charging
    license fees; I felt that we (in California, at least) had funded the development of the
    kernel and utilities and should be allowed free copies (media cost only), whether for personal
    or business use.

    Now that there are free versions, I may make use of BSD, but, until I find something that Linux
    won't do for me, I see no reason to add another OS to the mix (mostly Linux, one Amiga) that I run
    at home. For my professional use, Linux has broader embedded processor support. What is
    sad is that Linux' popularity has slightly opened the door for corporate use, but those %$*$#
    that "approve" technical decisions now have two names that they can remember (M$ and Linux);
    getting another name into that mindspace is hard.

  213. Please grow up by Anonymous Coward · · Score: 0

    Oh grow up. He is entitled to his opinion regardless of whether or not you agree.

    You don't have to insult him, and insulting him does not prove him wrong in any way.

    Why not try to at least provide a meaningful counter to his arguments?

  214. Re:FreeBSD ufs w/ Softupdates isn't a journalling by Anonymous Coward · · Score: 0

    softupdates (as in FreeBSD) is better than nothing, but it will still cause corruption if the system crashes while writing to the disk.

    True journalling can recover to a "known" state after a crash-- ext3 has this ability.


    I've heard that Kirk McKusick is working on adding true journaling or something like it into FreeBSD's ufs.

  215. Cool! by _Sprocket_ · · Score: 2
    I saw freebsd at compusa the other day...
    Cool!

    While I really enjoy using Linux and have no inclination to "jump" to BSD myself... I'm also of the opinion that BSD deserves some attention. Great to see it hit the shelves too.

  216. In short, you're proud of lying. by Brett+Glass · · Score: 1
    Incidently, BSD advocates, it was Brent Glass

    The name's Brett Glass, thank you very much.

    that helped me along to this conclusion. Because of him, I used my influence at a major manufacturing company (considering requiring all mission critical systems be open source) to convince them that the *BSDs were NOT open source - and they bought the argument.

    In short, you admit outright that you told a destructive lie to your employer or client. I hope you're proud of yourself. No, on second thought, it's quite obvious that you are not, since you've posted as "Anonymous Coward."

    It's obvious that you yourself believed that you would have had a more difficult time selling your employer on Linux vs. BSD if you'd been ethical enough to be truthful.

    --Brett Glass

  217. Moderate this fucker down. by tarp · · Score: 1
    Excuse me, but Bruce Perens is far from stupid. In fact, I'd fathom to guess that he's a genius.

    And the technocrat.net thing is his signature, you nitwit.

    --
    WorldServe Consulting

    1. Re:Moderate this fucker down. by Anonymous Coward · · Score: 0

      For quite a while, www.technocrat.net was responding with Debian Apache's hello-world document instead of Bruce "Sooper Genius" Perens' site.

  218. Threads, baby. by GeekWSpots · · Score: 1

    I would use it, but it lacks thread support - namely proper threaded SMP support. The other thing is that pesky non-automatic kernel config problem. I guess I'm a Solaris loser, but proper modules with hardware detection is a lot more fun than recompiling the kernel in production.

    To be more to the point, I'd use OpenBSD for more than just firewalls. I love OpenBSD.

    --
    Kyle Hodgson Systems Geek
  219. hmmm by Anonymous Coward · · Score: 0

    And you're saying you got the name right, right? Yeah, right...

  220. Re:Poppycock by Arandir · · Score: 2

    "The unwritten rule of the BSDL seems to be "you can make a proprietary version, but not a GPL'd version""

    The reason for this is that the GPL extends to third parties, the "viral" clauses in other words. No other license that I am aware of, proprietary or otherwise, does this (except for those few derived from the GPL). BSDL developers have no desire whatsoever to impose anything on third parties.

    However, there is nothing preventing you from copylefting your mods to BSD code. Just don't expect it to get rolled back into the source tree. If GNU will refuse, or even sue, those who would return modifications under BSDL, why should BSDL behave any differently?

    "They seem to resent the fairness we insist on."

    Enforced fairness is not fair. It is impossible to commit a moral act if you have no choice. If you choose to use a fairness enforcing license, that is your choice, but by making on airs of moral superiority by doing so is utter hypocrisy. That's like calling taxation charity.

    "Perhaps they're trolling for work from naive coders.."

    Okay, now I'm completely offended! My actions are my own, and it's none of your damn business what they are. It's interesting how Stallmanistas rant on and on about freedom, but once someone makes a free and conscious choice, they call us dupes and knaves. You guys don't know the first thing about freedom.

    --
    A Government Is a Body of People, Usually Notably Ungoverned