Slashdot Mirror


FreeBSD As A Workstation For UNIX Newbies

JT writes: "OSNews features an article introducing the FreeBSD operating system to newbies and Windows users. The article describes the installation, its GUI, application base and it has some more information about Unix and *BSD in general." Since Linux (at least the varieties with cute installation routines) is often presented as the *nix beginner's best choice, it's good to see articles like this one pointing out a broader range of choices.

78 comments

  1. Re:Bin Laden KILLED!!! by Anonymous Coward · · Score: 0

    No, you are fucked, punk.

  2. [yahoo.com] by Anonymous Coward · · Score: 0

    Looks like the thing that displays the [yahoo.com] after the HREF needs to be fixed.

  3. Maybe, maybe not... by ichimunki · · Score: 5, Interesting

    Unlike Red Hat, there is nothing on FreeBSD that takes away the true hacker-only nature of the system.

    The partitioning, as the article points out is mostly manual, but only if you can't dedicate your drive... if you can dedicate you press one key and it does a default partition scheme, ditto mount points. This is not a problem for any but the types who can't RTFM long enough to find out what page of the FM they're on.

    The package system vs. ports is slightly confusing, especially since so much stuff appears in both places, how do you know which to use when and why? I'm sure this confusion is cleared up by reading the Handbook in depth. Ditto the fact that the ports system isn't just a system for getting and compiling tarballs-- it's a whole packaging system unto itself, just a bit more CPU intensive than rpm.

    Speaking of the handbook, here's my favorite line (from memory, may not be exact) "recompiling a kernel is a rite of passage for Unix users". There, they said it, plain and simple you *will* recompile the kernel... and they're right, the generic kernel has no support for sound, so off to the config files you go. Hello make and make install! FWIW, they're 100% right, compiling a custom kernel is just too important not to learn to do it on either BSD or Linux systems.

    IMHO, FreeBSD is not a suitable system for a computing newbie, unless they have a patient, available hacker friend. It might be a good introduction to x86 Unix for someone who's used a Unix mainframe at school/work (where someone else was the sysadmin). And it might be a good introduction to Unix for an advanced Windows user. And for the hacker? Of course it's a great choice, especially that ports system. I've not seen a Linux distro with that level of commitment to the offsite code base.

    But best of all, no one's running around saying it should be called GNU/BSD! And with good reason, if you're used to the GNU binutils and BASH, you're in for a bit of a surprise with FreeBSD.

    --
    I do not have a signature
    1. Re:Maybe, maybe not... by jquirke · · Score: 2, Interesting

      Sorry to nitpick, but the default kernel that came with 4.4-RELEASE does include support for sound, in the form of modules.

      It supported all the hardware out of the box on my notebook, with the exception of APM (and obviously not ACPI).

      Still, I agree, to get the most out of FreeBSD you need to build a custom kernel :-)

    2. Re:Maybe, maybe not... by Anonymous Coward · · Score: 2, Informative

      You no longer have to compile your kernel in order to support your sound card. Just add the kernel module. You can usually get along fine with the GENERIC kernel unless you want to make use of apm, but being able to build a more compact kernel than the GENERIC one is one of the triumphs of open source unix. The rc startup files are organized in a sane fashion too, so configuration's simpler. But the best part about FreeBSD is that they actually try to keep the man pages up to date so that you don't have to always run off to that gnu info monstrosity or various well-hidden HOWTOs and FAQs.

      I tried installing Slackware but gave up in disgust. It's disorganized as hell, but at least it only needed 1 cdrom for the (re)install. For some reason it had trouble finding and/or mounting my plextor cdrw that I use regularly with freebsd without a hitch.

      Unix is not for people who want to be spoon-fed everything.

    3. Re:Maybe, maybe not... by Anonymous Coward · · Score: 0

      As for linux, I'm still trying to find one with a network install floppy image that isn't corrupted.

    4. Re:Maybe, maybe not... by swright · · Score: 1

      I cant agree with all of this - a newbie may have to be handy with a command line, but aside from that its easy...

      the ports tree - a complete piece of piss to automatically download/compile/install anything in it (and there's a lot...)

      compiling the kernel - complete piece of piss... 2 lines or somethings...

      pratical stuff like setting up NAT, firewalling, stuff like that, takes seconds...

    5. Re:Maybe, maybe not... by scott4000 · · Score: 1

      that's odd....did you try the acpi module?

    6. Re:Maybe, maybe not... by Thatman311 · · Score: 0

      piss=good?

      --
      Silly Rabbit...Sig's are for kids.
    7. Re:Maybe, maybe not... by Anonymous Coward · · Score: 0

      I guess so.. But I wouldnt have thought that..

      -ac

    8. Re:Maybe, maybe not... by kesuki · · Score: 1

      It is definitely "a good introduction to x86 Unix for someone who's used a Unix mainframe at school/work (where someone else was the sysadmin). And it might be a good introduction to Unix for an advanced Windows user."

      It was almost 5 years ago when I as an advanced windows user who had used unix at college (mainly for USENet.) Anyways, at the time I got my second PC and began to network the two, and for a few months it worked fine until an update to dial-up networking changed my network config and broke the network. I wasn't able to resolve the issue, so I looked into linux. Well after about a few days of trying linux I had heard about FreeBSD. I went out and tried it, and it worked a lot better for me. I was able to understand it a lot better, and even got sound working (eventually.) The important thing is that I got it to dialout to my ISP automatically and share the internet connection across to my other computer something I hadn't figured out how to do with windows at the time.
      While I have tried other linux distros since then FreeBSD has still been my favorite OS. While I ditched the dialup a long time ago, I still use FreeBSD at the heart of my home LAN.
      as of posting this my uptime on my server is
      10:01AM up 134 days, 22:50
      Linux has it's merits too, but if you're not satisfied with it try BSD.

    9. Re:Maybe, maybe not... by swright · · Score: 1

      oops, maybe that phrase is only used in england,

      'piece of piss' = 'very easy'

      isn't language a wonderful thing...

    10. Re:Maybe, maybe not... by ichimunki · · Score: 1

      You know I'm looking at the Handbook again, and either it's been changed in the last few days or (more likely) I totally missed the sentence that says you have TWO ways to install sound, listed first is kldload, then they mention recompiling the kernel. I think I'm probably biased in favor of recompiling custom kernels because they are usually smaller, faster, and that has to be better for everyone involved. Besides, having to monkey with the module load process is no more fun than putting that effort into recompiling.

      --
      I do not have a signature
    11. Re:Maybe, maybe not... by Arandir · · Score: 1

      The Handbook is now in version 2. It didn't ship with 4.4-RELEASE, but it is online and you do get it with cvsup. Perhaps the old handbook didn't mention it. I certainly haven't seen any mention of sound modules, so I'm assuming this is new.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    12. Re:Maybe, maybe not... by Guy+Harris · · Score: 3, Informative
      And with good reason, if you're used to the GNU binutils and BASH, you're in for a bit of a surprise with FreeBSD.

      Yes, the binutils are surprisingly different from the GNU ones:

      > uname -sr
      FreeBSD 4.1-RELEASE
      > cc --version
      2.95.2
      > ld --version
      GNU ld 2.10.0
      Copyright 2000 Free Software Foundation, Inc.
      This program is free software; you may redistribute it under the terms of
      the GNU General Public License. This program has absolutely no warranty.
      Supported emulations:
      elf_i386
      > as --version
      GNU assembler 2.10.0
      Copyright 2000 Free Software Foundation, Inc.
      This program is free software; you may redistribute it under the terms of
      the GNU General Public License. This program has absolutely no warranty.
      This assembler was configured for a target of `i386-unknown-freebsd4'.
      > nm --version
      GNU nm 2.10.0
      Copyright 1997, 98, 99, 2000 Free Software Foundation, Inc.
      This program is free software; you may redistribute it under the terms of
      the GNU General Public License. This program has absolutely no warranty.
      > ar --version
      GNU ar 2.10.0
      Copyright 1997, 98, 99, 2000 Free Software Foundation, Inc.
      This program is free software; you may redistribute it under the terms of
      the GNU General Public License. This program has absolutely no warranty.

      ...

      (No, that hasn't changed in later releases.)

      Yes, it's not GNU/BSD in the sense that most of the utilities are not GNU utilities, but the BSDs do use the GNU toolchain.

    13. Re:Maybe, maybe not... by Guy+Harris · · Score: 2
      that's odd....did you try the acpi module?

      There's an ACPI module in 4.4-RELEASE? (That's what he's running, not 5.0-current.)

    14. Re:Maybe, maybe not... by Anonymous Coward · · Score: 0

      kldload snd_pcm.ko
      kldload snd_yourchipset.ko
      cd /dev
      ./MAKEDEV snd0

      cat "yourmotherwasahamster.au" > /dev/audio

      Don't know the module name?

      ls /modules

    15. Re:Maybe, maybe not... by Anonymous Coward · · Score: 0

      4.5's GENERIC kernel will include the apm device so that you can 'shutdown -p now' and 'zzz' successfully without having to recompile the kernel. Lately I've compiled a minimal kernel and configured the kernel loader to load all the various driver modules (the ones which won't automatically load on their own) before my kernel even starts. Works great.

    16. Re:Maybe, maybe not... by Anonymous Coward · · Score: 0

      You'll notice that a number of those tools are hardlinks to the same program. Less redundant code that way. Love it.

  4. Kudos to OSnews by DeMorganLaw · · Score: 2, Informative

    Kudos to OSnews.com for promoting FreeBSD as a serious alternative to Linux for users looking for an alternative OS. FreeBSD is fast, stable and has a great many experienced users willing to help out newbies. Sysinstall is easy to get going (just 2 floppies), supports FTP downloads of software packages, and resolves dependency issues quickly. However it is still no where near as easy as the GUI installer for current releases of Mandrake and Redhat. FreeBSD can run practically anything written for Linux after installing the Linux Binary Compatibility Pack.

    1. Re:Kudos to OSnews by scseth · · Score: 1
      I agree. I have always thought Linux made for a great personal computer, while FreeBSD was a very effective server. After being an end-user on Solaris, SunOS machines, FreeBSD was my first admin. Having admin'd on Solaris, Linux, and even WinNT/2K I still prefer FreeBSD and in fact run it on my personal web/email server.

      Altho - I wouldn't mind if FreeBSD stays in obscurity to most. Popularity could result in more complex hack attempts, exploits, etc. So go ahead, give linux to the world and lets keep FreeBSD to ourselves ;)

    2. Re:Kudos to OSnews by Anonymous Coward · · Score: 0

      I would not be willing to download a third, maybe a fourth install floppy image just to have a stupid GUI installer. I can't think of anything lower on my wishlist. I tried installing Solaris once, but gave up after I learned that I needed 64 megs just to bring up the "web enabled" installer! Pitiful.

    3. Re:Kudos to OSnews by Anonymous Coward · · Score: 0

      On the other hand, I've twice installed a complete FreeBSD system with two floppies and 33.6 kbps isp connection. I started at 10pm, started it downloading and installing the binaries by 10:15pm, went to bed, and rebooted to a working system the following morning. Ain't no substitute for that.

  5. Let's get things straight here by ScumBiker · · Score: 1

    First off, before the trolls get to it, no, *BSD IS NOT DYING. Ok, I'm donme with that part.

    I've been using FreeBSD since early 1994 and have grown up with ti, so to speak. Even back then, I tried Linux and ended up learning FreeBSD. I'm really glad to see people writing for newbies.

    --
    --- Think of it as evolution in action ---
  6. Tried running FreeBSD 4.4 TWICE recently... by Anonymous Coward · · Score: 0, Troll

    In the past 2 weeks, I have tried running FreeBSD 4.4 *twice*. The first time I installed it, I couldn't find XFree-4.1.0 in the package list, so I installed the default 3.3.6. After installation, KDE2 was giving me random errors, losing title bars, etc.

    I reformatted, installed Slackware 8. 2 days later I had a change of heart and tried FBSD 4.4 again.

    This time I found XFree-4.1.0. KDE2 ran just fine. I figured out how to change my shell from tcsh to bash (thank you chpass). I even got a kernel to compile properly (after only an hour of console-flipping between LINT and MYKERNEL)!

    And yet - recompiling the kernel killed BSD for me. Why?

    The kernel wouldn't boot. And the instructions in the FBSD handbook on how to recover from a bad kernel didn't work, because the sendmail daemon kept locking up whenever I tried to run the original generic kernel.

    The biggest reason I was recompiling my kernel was to get my Soundblaster PCI64V (ES1371) card to work so I could play my MP3's in XMMS...

    But since the FBSD bootloader is damn near impossible to configure (unlike Linux's LILO), I couldn't hack my way out of FBSD's crap.

    I've since returned to Slack8, and won't be returning to FBSD until (at the earliest) 5.0 is released late next year. Configuring the kernel is a pain in the ass, although compiling it is slightly easier than on Linux. But that doesn't matter if the fscking kernel doesn't work!!

    The ports collection is nice though - when the system runs... Although it sucks donkey balls if you're still on dialup (as I am).

    1. Re:Tried running FreeBSD 4.4 TWICE recently... by prisonernumber7 · · Score: 1

      Ever considered typing /kernel.GENERIC when the bootloader comes? You know, you can even do a 'ls' there, if you can't find it.

      Oh and /boot would be a clever place to be looking for a way to configure the boot loader.

      I would say rtfm, but oh well, I was just as stupid to reply to this obvious troll post. Please give me a -1 for that.

      --
      && aemula C. ab stirpe interiit
    2. Re:Tried running FreeBSD 4.4 TWICE recently... by Arandir · · Score: 2

      I had no problems with my ES1371 (SBPCI64). I just added the line "device pcm" to the end of my kernel config and it Just Worked(tm).

      I think you real problem is that you want FreeBSD to work just like Linux. Well it doesn't. Otherwise it would be called FreeLinux. It took you a while to figure out all the arcana under Linux, so expect to spend some time figuring out the FreeBSD arcana. On the plus side, FreeBSD has top notch documentation. Try perusing it.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    3. Re:Tried running FreeBSD 4.4 TWICE recently... by Anonymous Coward · · Score: 1, Interesting

      Heh, funny thing:

      No, I didn't type /kernel.GENERIC. I RTFM page, just as you suggested, at http://www.freebsd.org/doc/en_US.ISO8859-1/books/h andbook/kernelconfig-trouble.html and did boot kernel.GENERIC when the bootloader showed up. Too bad that didn't work...

      Oops.

      And I already knew that the bootloader was in /boot. How clever indeed.

      As for RTFM -- how the hell do you think I even got the kernel to compile right in the first place? It wasn't by guess-and-check, that's for sure. No, it was by reading Chapter 9 of the handbook at www.freebsd.org, following every word, and reading every word of LINT and determining what I needed based on what was in MYKERNEL and what wasn't (but was in LINT). If there's a better way than RTFM'ing, I don't know what it is.

      Oops.

      What's more, it was hardly meant as a troll post - it was a brief user's experience post. It just happens to be a bad experience, which follows past experiences (tried FBSD-4.3 in September - couldn't even get a kernel compile to work then, so we're making progress here).

      I didn't even mention how the amazingly-useful updatedb binary (and the corresponding locate command) is stored in a directory that isn't even in root's path by default - thus, to find these normally-standard tools, you need to do a find / | grep updatedb. This shouldn't be necessary...

      What amazes me most about the BSD community is just how arrogant its userbase semes to be (prisonernumber7 isn't the only BSD user I'm including), regardless of how much documentation somebody reads. I have yet to meet a helpful, non-egotistical BSD user. Linux users aren't much better (and in general, IMHO aren't quite as knowledgeable as *BSD users) but the difference is that Linux users are generally more smug about their OS choice rather than acting like complete assholes...

      I didn't learn Linux by not reading documentation. On the contrary, that's all I did - I learned by reading docs I found online -- the HOWTO's in particular. In a little over a year I've gone from knowing nothing about any of the UNIX variants, to breezing through a Linux certification and simultaneously teaching other students in there (thanks to docs I'd read earlier on the 'net), to teaching a friend of mine how to run a Slackware box (and used a number of my own scripts to compile & install the latest KDE sources, along with tons of other packages, since it was Slack7.1, which is rather old).

      If it weren't for the vast ocean of Linux documentation online, I would've never been able to setup a 486 as a router with some strong iptables rules and a DNS server...

      I wanted to move on from Linux to FBSD because I'd read that it was even more stable, reliable, and faster than Linux, all while having a packaging system that puts Linux package-management to shame. And all of those things seem to be true.

      But there's no useful info available (except in some big, recently-released book that sells for $50 in Borders that discusses using FBSD4.4) on how to exploit that power. And for as similar as FBSD and Linux are, there are far more differences than I was originally expecting.

      Funny I couldn't find much documentation beyond the FBSD handbook. Yes there are several email lists and Usenet groups - but when you're looking for an answer to what should be pretty simple problems, it should be pretty easy to find - after all, it's been asked thousands of times in the years since FBSD was started, right?

      So why is it that literally hundreds of searches on Google, manual sifting through Usenet, and searching through freebsd.org's mail archives don't turn up answers?

      Christ man, you remind me of my roommate last semester. Snide, arrogant, and always "looking down" at those whom he talked to.

      No wonder that one guy here is always posting that *BSD is dying...

      Mod me down, I don't care - I'm going to play with a *nix that has real support without such absurd levels of geek chest-beating.

      BSD just lost a potential user (and now an outspoken critic of BSD). But knowing BSD users, they don't care - they're too busy pretending they're God to help potential users understand how their system works.

    4. Re:Tried running FreeBSD 4.4 TWICE recently... by Anonymous Coward · · Score: 0

      Well, I tried adding

      device pcm

      to my kernel config too... Unfortunately, I didn't get far enough to test whether or not it worked. :(

    5. Re:Tried running FreeBSD 4.4 TWICE recently... by Ded+Bob · · Score: 2

      Without seeing the error logs, I cannot comment on your problem. I found FreeBSDhelp on Efnet to be quite useful.

      The kernel wouldn't boot. And the instructions in the FBSD handbook on how to recover from a bad kernel didn't work, because the sendmail daemon kept locking up whenever I tried to run the original generic kernel.

      You couldn't boot into single-user mode?

    6. Re:Tried running FreeBSD 4.4 TWICE recently... by Thornae · · Score: 2

      Funny I couldn't find much documentation beyond the FBSD handbook. Yes there are several email lists and Usenet groups - but when you're looking for an answer to what should be pretty simple problems, it should be pretty easy to find - after all, it's been asked thousands of times in the years since FBSD was started, right?

      So why is it that literally hundreds of searches on Google, manual sifting through Usenet, and searching through freebsd.org's mail archives don't turn up answers?


      <Sigh>... Sadly, your experiences are all too common. Particularly the impatience of the poster whom you responded to. In general, *bsd users are no more or less arrogant than *linux users. However, it's the outspoken minority that cause troubles.

      I've said it before, but it bears repeating: the single most valuable resource you can get when installing/trying out a new OS is access to a friendly expert who doesn't mind you asking potentially dumb questions - and who'll let you repay them with a few beers or equivalent.

      I, too, have struggled with the -questions archive, searching for answers. Eventually, I found them, either in the archives or in sections of the documentation. But it wasn't easy. Nowadays, I just drop a line to one of my mates who knows lots about FreeBSD, and make a note to thank them later in some tangible form.

      If you've not got a similar friend, some of the IRC channels may help. FreeBSD-questions tends to be rather overwhelming, although there aren't too many arrogant answers there.

      Personally, I find FreeBSD to be a useful OS and a rewarding learning experience. But I doubt I'll stop asking dumb questions of my friends any time soon. I hope you'll find some similar form of help, and not be discouraged by a few terse lines from a less patient person...

      --
      |>
      Here be Dragons
    7. Re:Tried running FreeBSD 4.4 TWICE recently... by Anonymous Coward · · Score: 0

      I tend to agree with you on the XFree side of things. But as far as kernel recompilation goes
      i found FreeBSD's way of things muuuuuuuuuch more
      comphrehensive and easier than Linux's. The thing i like about FreeBSD is that it's lean. Once you get used to the BSD way of doing things you
      simply can't go back. Many people prefer for
      example the graphical kernel config options.
      I always found that confusing. I find it a LOT easier to just edit -ONE- file and then do my recompile. No rpm's to be worried about, no glibc
      issues or dependencies no nothing. It is simply
      BEEEEEEUUUUUUUUUUUUUUURIFULL!!(did i mention no lilo -v etc bullcrap?)

      It is all a matter of what you're used to.I went the BSD-way when linux was around 2.2.XX something
      and still on that horrible horrible ext2fs. After
      ext2 chewed up 3 of my HDD's i decided to try something new.But when i got more into BSD i decided that it was sooooooooo much easier to maintain.

      Of cource now with XFS coming the linux way i think i may be giving linux another chance on
      my servers too. So far i have only used it as
      my desktop choice. But things are indeed looking
      a lot brighter with IBM and SGI coming into play
      on the linux side.

      I just hope the BSD team will be able to offer those FS choices on BSD too as a choice.

    8. Re:Tried running FreeBSD 4.4 TWICE recently... by Anonymous Coward · · Score: 0

      Some in the core are in the process of being talked into offering support for a journaling file system in addition to the FFS workhorse, but much will depend on licenses, free time, and interest.

  7. Preferances by Alien54 · · Score: 2
    Given the Varieties of *nix out there, I tend to actuall prefer FreeBSD.

    I've even gone out of my way to pay for CDs etc.

    --
    "It is a greater offense to steal men's labor, than their clothes"
    1. Re:Preferances by atrin · · Score: 2, Informative

      The problem is Linux gets too much attention from the mass-media. My H'friends joke about me being the only one who uses FreeBSD. It's really hard to make someone feel, apreciate the "clean" feeling of FreeBSD, being built as _one_ project. That is why the dox are that good too. But for a newbie, who DOESN'T want to be a hacker, but only to understand the implications of "everyinthing is a file" (although he doesn't know it yet) and _maybe_ do some programming using sockets Linux is not much different from FreeBSD. Besides, the problems which arise with making a Linux box work smoothly get one to RTFM.
      So FreeBSD is a good choice but not the best for newbies.

  8. FreeBSD myths. by pschmied · · Score: 5, Informative
    O.K. There always seems to be a number of out right false hoods perpetuated about FreeBSD. More often than not, they are not malicious. More often than not they are perpetuated by casual FreeBSD users. Let me set the record straight.


    "The ports collection sure is great! I just wish that FreeBSD had some kind of package management that didn't require building from source."

    It so happens that FreeBSD does have package management that won't ever invoke gcc.

    Try the package management tools (man pkg_create(1), pkg_delete(1), pkg_info(1), pkg_update(1), pkg_version(1) for more specific info).

    In fact, FreeBSD is so bad-ass that you can type something like "pkg_add -r mozilla" and the system will download and install the latest mozilla. Carefull though, some packages require that you specify the whole version (i.e. pkg_add -r lyx-1.1.6.3). This will get all the dependancies you need in most cases.

    The only real reasons to build from the ports are:

    1. You need specific compile time options. (Install a custom Apache on RedHat then with FreeBSD's ports and come back and tell me which is easier)
    2. You have a multi architecture workplace and you want to use a central distfile repository. (Please note that this is rare.)

    "FreeBSD is less user friendly than Linux"

    This is highly subjective. I taught a class this summer to a group of people at my University who had never installed Windows, much less anything else. By the end of the first week, they were able to install FreeBSD, compile a kernel, and successfully manage packages. By the end of the second week, they all had their desktops going with the productivity apps they wanted. By the middle of the third week, I couldn't hold their attention because they were having too much fun playing with the OS.

    FreeBSD belongs to the "it just works" school of computing. I don't know how to describe it. I've never had to worry about whether or not FreeBSD would correctly auto detect my USB optical mouse during the install (I've had a number of Linux distros both succeed and fail). FreeBSD Just Works(tm). No dicking around. "Does your system have a USB mouse attached to it?" "Yes?" "OK, we'll make sure and load usbd." If I've had "device pcm" in my kernel config file at build time, my sound has always worked.

    As a workstation, FreeBSD performs very well. I don't have benchmarks for you, but I've never had a FreeBSD machine that has felt slower than any Linux distribution on the same hardware. Incidentally, FreeBSD starts notably quicker than any Linux distro newer than Slack 2.0.


    I feel really good about the state of FreeBSD. They have made things easy by design, not by GUI abstraction. If you judge ease as being a point and click installer, then Linux will win every time. If you judge ease as simplicity and consistancy, FreeBSD is a clear victor.


    -Peter

    Just my $0.02

    1. Re:FreeBSD myths. by Anonymous Coward · · Score: 0, Flamebait

      It just works? That's been my impression of linux. With *BSD, the kernel and userland are tightly integrated. With linux, the latest, snazziest kernel is duct tape'd to various gnu utilities. Documentation? Ha!

    2. Re:FreeBSD myths. by pschmied · · Score: 3
      It just works? That's been my impression of linux. With *BSD, the kernel and userland are tightly integrated. With linux, the latest, snazziest kernel is duct tape'd to various gnu utilities. Documentation? Ha!


      Touche! :-) I think we are argueing the same point. FreeBSD tends to Just Work(tm) (in the sense that it doesn't require any extra fiddling). Linux tends to just work (in the "just barely" sense). Not to bash on Linux though. There are some very inventive hacks that work quite well. I, however, prefer the more conservative nature of FreeBSD.

      Incidentally, I had the opportunity to install and play with NetBSD the other day (I'm thinking about ditching my PC for an iBook.), and I found it to work much the same way as FreeBSD. That is, it found all my hardware, and Just Worked (tm). In the past when I've used OpenBSD, it has done well too. I should take a look again as they've released a few times since I've played with OpenBSD.


      -Peter

    3. Re:FreeBSD myths. by wilton · · Score: 1

      I couldn't disgaree more !!!

      I have been using Linux & Free/OpenBSD for many years.

      It have never had so much trouble installing an OS as FreeBSD on my laptop. The USB keyboard was recognized, but wouldn't work, no matter what I tried. It would also be nice if they gave the option of installing X 4.1 or 3.3.6 (?)

      After 3 days of fighting, with a system that never worked properly I installed Mandrake 8.1. Everything worked first time (X, USB, PS/2, digital camera,sound etc)

      Using urpmi to install apps and dependencies makes it a breeze.

      I'm sure FreeBSD would make an excellant webserver, probably faster and more stable. However on a laptop, or a home system with more 'exotic' hardware Mandrake Linux was up and running fully in less than hour.

      --
      per mere, per terras
    4. Re:FreeBSD myths. by Arctic+Fox · · Score: 1

      I'm running FreeBSD on my Sceptre (think Dell Inspiron clone).
      I re-compiled my first kernel to get the sound card to work, adding a line like "device pcm" or something.
      The only problem I have is KDE start up takes two/three "startx" to start. Some kind of DCOP server startup problem. Hunting through google didn't help. Anyone?

    5. Re:FreeBSD myths. by Anonymous Coward · · Score: 0

      Part of the reason why took so much pleasure in crushing my Slackware install CD was that I couldn't even find a "live" device node for a usb mouse. After looking through all the docs, HOWTOs, FAQ's, kernel modules, and usenet messages, I came to the conclusion that the driver didn't want to be found if it existed at all. The SysV style initialization scripts helped to make configuration as painful as it can get.

    6. Re:FreeBSD myths. by Anonymous Coward · · Score: 0

      Mmm...only a fool.
      FreeBSd is fun but Linux is GREAT!

  9. BSD is WINNING by WaffenSS · · Score: 0, Troll

    Hello, This my first post lol :) Anyway, i want to say that BSD will win the server martket in couple of years, maybe 7 or 10. Right now Windows is getting pounded by hackers and most likely windows will go down. Second runner up will be Linux which will be the leading market in server OS and desktop OS. You know what happens when you give people to much power and money? They get corrupted. What will most likely happen is all the linux distros like Suse and Redhat will start charging. And who knows maybe they won't linux no more, but something else. Third runner up will be *BSD. Don't you see people that this is a cycle? For now windows is winning, then linux, then bsd, then something else will come out. Who knows maybe solaris or something else.

    1. Re:BSD is WINNING by Anonymous Coward · · Score: 0

      a) GNOME runs on FreeBSD too, and idiots who would run GNOME on Linux servers would do the same stupid thing if they were running FreeBSD.

      b) There are plenty of exploits for FreeBSD too, since most of the outward facing servers are the exact same code (bind, sendmail, apache, openssh).

      please think before posting.

    2. Re:BSD is WINNING by sithlord2 · · Score: 1



      They making games, videos for them?

      Linux is joke because they make applications for it ??

      I think you're the joker here...:-)

      --
      ...You are over-qualified and under-paid. If we give you a raise, we will break the cosmic balance of the universe.
    3. Re:BSD is WINNING by Anonymous Coward · · Score: 0

      Gnome is one big exploit. What's with this "/opt" and why is it filling up my root partition?

    4. Re:BSD is WINNING by Anonymous Coward · · Score: 0

      No, BSD is already dead. So if it wins, happy day, but it will have to come back from the dead. Sorry!

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

      Hmmm...

      Solaris is dead too then huh? Damn all of those enterprise servers and all. Very interesting

  10. Re: .. I've ran since 4.3 as a production workstat by maquaro · · Score: 5, Informative

    I won't deny that not have a FreeBSD user around to help answer questions can be very agrivating. I happened to be enlightened by a co-worker to the finner unix points of FreeBSD. I moved from RH6.2 -2.2.19 to FreeBSD 4.3-Release. I have since removed Windows completely from my computer except for a VMWare window of 98. (Windows was meant to run in a Window(TM)). Besides, with the improved jail capabilities of FreeBSD we have all but moved our entire unix OS's to 1(one) box. It actually runs about 7 virtual OS's, namely dns, imap, dynamic-www, smtp, database, information processing. The ideas that sold me on FreeBSD over Linux were, ports/packages, 1 distribution, stablility.

    Starting with 1 distribution, the OS has benefits out of the box. All kernel code is under peer-review. One person can't just say I want this to be this way. Any major additions are under peer scrutiny. Also the members of the core development team only got there because they have been and were submitters to FreeBSD for a long time. With have 1 distribution all the channels of the distribution talk to on another. You don't see Suse talking with RedHat. I didn't think so.

    The stability issue is tied into the 1 distribution also. I feel sorry for Linus. He make a great kernel, but he can't do squat to make the surrounding distribution work if it breaks. The distro is only as good the surrounding subsystems. In my opinion FreeBSD leaves newer features in the CURRENT tree structure a little longer than Linux. Thus when a release version is created the release versions tend to have less problems.

    Finally the ports and packages. It took me a few months to fully understand ports versus packages. I actually install the bash-2.05 package on any new installation so I can use the shell from the start. The packages can be accessed from /stand/sysinstall. Once the OS is installed just browse for the package of your choice. The package is a snapshot of the current packages at the time of release. You can even change the settings in sysinstall to fetch older packages, if you want. The ports are great because you can search through a selection of software that you can be sure will work in freebsd. FreeBSD works on it's Linux compatibility, not getting people to code on FreeBSD unless they develop exclusively on FreeBSD. If you can run it on Linux, changes are it will be available on FreeBSD in a little time. BTW, the ports directory/tree is created every day at 9AM EST. New changes everyday.

    "You must unlearned what you have learned!" - Yoda

    --
    What I am I once was. What I now become I long to be. Life is a journey not a destination.
  11. Re: .. I've ran since 4.3 as a production workstat by Anonymous Coward · · Score: 0

    Wow. A *helpful*, *informational* post from a BSD user.

    Not another BSD user saying "you're a Linux user, so you go back to playing in your sandbox and we'll play in ours"...

    *THIS* is the kind of person BSD needs if they want to bring new users to their OS and community.

    People like you, sir, are all too rare in the *BSD community...

  12. waiting for 5.0 by Anonymous Coward · · Score: 2, Informative

    I love freebsd, but I'm putting it on hiatus until 5.0 comes out. It's not a good choice for a laptop workstation, that's for sure, unless you have the blandest of vanilla laptops. I demand cardbus. :-)

    One thing not many people have mentioned is how clean and simple the base installation is (after you've installed it). Core system with X windows, add what you need afterwards. This is a clean methodology, it allows a newbie UNIX user to find out exactly what the system *is*. if they went for a default linux install, however, they'll end up with 500+ packages to deal with. I have problems telling what is a 'system' package and what is an 'add-on' package on my linux laptop. If it wasn't for up2date or ximian's red carpet, a user would be screwed, security-wise.

    mike

    1. Re:waiting for 5.0 by Kwikymart · · Score: 1

      You'll be on hiatus till about November next year at the very least

      --

      Buying a Dell computer is equivalent to dropping the soap in a prison shower.
    2. Re:waiting for 5.0 by hearingaid · · Score: 2
      One thing not many people have mentioned is how clean and simple the base installation is (after you've installed it). Core system with X windows, add what you need afterwards.

      This is partly true. However, even the minimal install does contain programs that you can rip out in special-purpose systems, like firewalls. The annoying part is that they don't get included as ports, but rather just left there. I wish the default sendmail install was listed in /var/db/pkg to make it more removable.

      However, I know that I'm probably too obsessed with maximizing available disk space. :)

      --

      my old sig used to be funny, but then slashcode ate it and now it's not funny anymore

    3. Re:waiting for 5.0 by Anonymous Coward · · Score: 0

      Too true. Requiring sendmail is silly. Plus, if you delete it, a make world will recreate it. Systems with only absolutely necessary dependencies would be wonderful. Sigh.

    4. Re:waiting for 5.0 by elbuddha · · Score: 2


      Requiring sendmail is silly.

      Agreed.

      Plus, if you delete it, a make world will recreate it.

      Not true. Uncomment "NO_SENDMAIL= true" in make.conf, problem solved.

  13. It just works? by Laplace · · Score: 2

    Ok, then tell me how I can use my PCI Modem with FreeBSD (no, it is not a winmodem). I've never been able to get it work work under BSD, and I haven't found any clear instructions on how to get it to work.

    --
    The middle mind speaks!
    1. Re:It just works? by pschmied · · Score: 3, Informative
      Ok, then tell me how I can use my PCI Modem with FreeBSD (no, it is not a winmodem). I've never been able to get it work work under BSD, and I haven't found any clear instructions on how to get it to work.


      Really? What modem do you have? I've got the ActionTec Call Waiting PCI modem and it worked fine.

      Check your dmesg (dmesg |more). Look for something like the following:

      sio0: [ActionTec 56k FAX PCI Modem] port 0xdc00-0xdc07,0xd800-0xd8ff,0xd400-0xd4 ff mem 0xe2001000-0xe20010ff irq 11 at device 7.0 on pci0

      sio0: moving to sio4

      sio4: type 16550A


      Actually, a good place to start would be to type "dmesg |grep sio" at the command prompt. I bet that FreeBSD has probably found it already. Remember that the serial interface "sio4" corresponds to /dev/cuaa4. You might also check to make sure you have enough software serial ports enabled in FreeBSD (do you have two unused serial ports on the back of your machine? I disable mine in the BIOS, but if you need them, you can just enable com3 & com4 which are disabled in a standard install. Read the handbook section on building a kernel. It's easy. I promise.)

      I hope this helps. If not, you can always send an e-mail to questions@freebsd.org. They are generally quite helpful.


      -Peter

  14. Re: .. I've ran since 4.3 as a production workstat by scott4000 · · Score: 2, Insightful

    The level-headed people are the ones who have traditionally been the "FreeBSD community." Over the last couple of years, a large amount of very vocal people, known as "zealots," have moved to FreeBSD from OSes such as Linux, and then they go around preaching FreeBSD in the same loud way they promoted Linux. Please consider where such users came from before judging everyone that uses FreeBSD. Thank you.

  15. the sendmail problem by Anonymous Coward · · Score: 0

    Actually, it probably wasn't locking up the system. If you'd waited, it would have completed booting. You can ctrl-C the sendmail startup and it will keep going. It's an address resolution problem.

    1. Re:the sendmail problem by Anonymous Coward · · Score: 0

      That's a possibility - I only waited about a minute or 2 for sendmail to start up (on a P733, 512MB RAM) -- I don't know what the resolution timeout is on FBSD...

      Still, if it is a failure to find its own IP address (again, quite possible), then why wasn't this occurring *every* time I booted FBSD (since sendmail was being started at bootup even before I attempted to boot my new kernel)?

      Hmm - with X-mas break coming up soon, maybe I'll give FBSD yet another shot, despite my original statement that I wasn't going to touch it until 5.0 is released... :)

  16. I dunno by Ratbert42 · · Score: 3, Insightful

    I install and run OpenBSD and FreeBSD (as well as Redhat Linux and Windows NT/2000) on servers all the time. But I'm like a one-legged man on a pogo stick when it comes to installing either as a workstation. OpenBSD apparently even makes me manually add the X package after the install. FreeBSD is a bit better, but the configuration is all very manual. To contrast, Redhat Linux correctly detects my mouse, video card and monitor and makes it somewhat hard to continue the install unless the settings actually work.

    Out of my team of 10 developers, I doubt more than 3 other guys would be able to get FreeBSD running as an X workstation without someone to help them. And all of them, even me, would lose interest before getting it working. I can feel my interest waning right now. I'd rather play with OpenBSD's new pf than pretend it's 1996 and manually configure XFree86.

    1. Re:I dunno by Ratbert42 · · Score: 2

      OpenBSD apparently even makes me manually add the X package after the install.

      Ok. I was wrong. Booting from the CD makes it easy to install the X packages. Well, not as easy as Redhat Linux, but easier than ftp-ing them and untaring them in the right place.

      I got X running on OpenBSD on a laptop in about 20 minutes. The main problem was finding the mouse device and protocol (/dev/wsmouse0 and wsmouse). I picked the wrong video card, but the right driver (ATI) and made a wild-ass guess at the monitor clocks (not sure it matters at all).

      Still not for a beginner, but frankly I found the OpenBSD 3.0 install easier than the FreeBSD 4.4 install.

    2. Re:I dunno by Arandir · · Score: 2

      FreeBSD detected my mouse automatically, along with my sound card once I made snd0. X is a different story.

      There's a good reason for this: X isn't part of the operating system. It's a separate project with one set of sources for all supporting OSs. Many Linux distros like to write their own X configurator. But FreeBSD sees X as someone else's project and doesn't touch it. Making the base system automatically configure X would be like making the base system automatically configure sendmail. That's not its job.

      X comes with some configuration utilities that work quite well, as long as you know what hardware you have. I use these, even under Linux. But that said, I see no reason with a FreeBSDXConfig port/package available for newbies. I just don't know how well it would work. I haven't installed Redhat in a very long time, but I have had problems with Mandrake, SuSE and Corel trying to detect my video cards. Come to think of it, I had a bitch of a time with Windows detecting my Rage128. The problem is that there is no standard way of determing video hardware capabilities. Methods that work for most cards can crash or reboot a system with other cards.

      The way around this hassle is to do what Microsoft does: get the OEM's to preinstall the operating system. My friend had a computer that generic off-the-shelf Windows would NOT install, but where the OEM CD of Windows would. Overall, I think Mandrake, SuSE, Redhat, etc., do a *much* better job of hardware detection than Windows does, for precisely this reason.

      [sorry for the rant]

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

    Seems to me that most people are comparing FreeBSD to Redhat/Mandrake. Let's not forget that Debian Linux is not only fast (starts up much faster than other distro's) as well as being stable and secure thanks to apt. Packages can be installed from source or binary, AND with just one command .....

    Problem is, all these features don't make a system newbie friendly, but why the constant in-fighting, we're all *nix users here :)

    1. Re:BSD and Linux by Guy+Harris · · Score: 2
      Seems to me that most people are comparing FreeBSD to Redhat/Mandrake. Let's not forget that Debian Linux is not only fast (starts up much faster than other distro's) as well as being stable and secure thanks to apt. Packages can be installed from source or binary, AND with just one command .....

      ...and, like {Free,Net,Open}BSD, it's a volunteer project, not a commercial product. If somebody wants to compare the BSDs to a Linux distribution, Debian is probably the most appropriate one with which to compare them.

    2. Re:BSD and Linux by PONA-Boy · · Score: 1

      ...and, like {Free,Net,Open}BSD, it's a volunteer project, not a commercial product. If somebody wants to compare the BSDs to a Linux distribution, Debian is probably the most appropriate one with which to compare them.

      If you look at Linux distributions in comparison to *BSD, Slackware is the most *BSD-like of them all. I grew up on Open Source Slackware and found it very comfortable switching from Slack to *BSD. and it is _not_ a large commercial organization, either. Patrick (as in Volderking) has maintained a good "leg" off the Linux family tree while sticking to traditional UN*X roots...

      -PONA-

      --
      +that's funny...I don't FEEL tardy.+
  18. XP ????? by oscarcvt · · Score: 1

    I liked the article, its great for newbies to have more references.

    However, i disagree with this guy, he says XP is "the most complete OS" he's used. WHAT?? Truly HE must be a newbie., not that theres any thing wrong with that but I thought it was kind of a contradiction, i dont know about you guys?

  19. KDE and DCOP error. by pschmied · · Score: 2

    Usually this has to do with your network settings (yes, even if you aren't on a network).

    Check your /etc/hosts and make sure that 127.0.0.1 points to your host name as well as "localhost"

    Hope this helps.

    -Peter

  20. Re:Maybe, maybe not.../ What about mailing lists? by LM741N · · Score: 1

    Duh! In the worst case, boot up your Windows machine and subscribe to the FreeBSD mailing lists. Then you won't need any local hacker friends. Just be sure to set your mail client to "text only". Otherwise you'll get flamed:) Rob.

  21. Re: .. I've ran since 4.3 as a production workstat by Anonymous Coward · · Score: 0

    It takes some people a long time to "grow up".

  22. Re:Netcraft now confirms: *BSD is dying by Anonymous Coward · · Score: 0

    Netcraft now confirms: "*BSD is dying" posters are complete wierdos.