Slashdot Mirror


Another Step Towards BSD on the Desktop

linuxbeta writes "DesktopBSD is the latest easy to install BSD aimed squarely at the desktop. Installation screen shots. From their site: 'DesktopBSD aims at being a stable and powerful operating system for desktop users. DesktopBSD combines the stability of FreeBSD, the usability and functionality of KDE and the simplicity of specially developed software to provide a system that's easy to use and install.' DesktopBSD joins the ranks of PC-BSD and FreeSBIE."

71 of 536 comments (clear)

  1. BSD v Linux by Mantus · · Score: 5, Interesting

    Could someone point me to (or post) a lowdown on the potential benefits of BSD has over linux (or vice versa) that doesn't include wild speculation and unfounded cynicism?

    Isn't a BSD distro going to be about the same as a Linux distro? Does the kernel make that big of a difference?

    Note the question marks. I am asking.

    1. Re:BSD v Linux by debilo · · Score: 2, Informative

      Please note that this is not a "distro", it's a plain FreeBSD with the addition of a graphical installer and some other nice tools.

    2. Re:BSD v Linux by wigle · · Score: 2, Interesting

      - easier to use - ports system - init scripts - easy updating with cvsup and make *world - filesystem layout - stable, secure - kernel config - separation between base system and add-on software - license

      --
      ::wigle::
    3. Re:BSD v Linux by xlr8ed · · Score: 5, Funny

      that doesn't include wild speculation and unfounded cynicism?

      You must be new here...

    4. Re:BSD v Linux by fwitness · · Score: 2, Informative

      I'm not quite sure why you picked Myth as your example. Myth uses Qt, SQL, XML, and is written mostly in C++. I always thought of Myth as a wonderful example of what using standards can do. I can rarely find a good Linux program that doesn't require KDE or gnome, and requires some obscure library I've never heard of. Myth, on the other hand, runs on X alone, and a few sane dependencies.

      As to seperating the server, Myth already has seperate backend/frontend modules. It even supports multiple backends at the same time, distributing recording and plackback in a whole m->n relationship.

      I agree with all your other points, just not using Myth as an example. It ain't perfect by any stretch of the imagination, but it's an excellent example of using Linux and standards to produce something completely useful and unique.

      --
      -- I have fans? Wow.
    5. Re:BSD v Linux by alcmaeon · · Score: 2, Interesting
      "The hardware support generally isn't as good."

      I have never understood this criticism. I have never had a problem installing and using FreeBSD on any hardware I have tried it on. By contrast, I have NEVER gotten sound to work in any Linux distro on any hardware I own.

      "The software tends to be ported from Linux or just generally cross-platform."

      You must have something confused. I think the porting is in the other direction. However, FreeBSD can run Linux binaries.

    6. Re:BSD v Linux by Amiga+Trombone · · Score: 2, Interesting

      Isn't a BSD distro going to be about the same as a Linux distro? Does the kernel make that big of a difference?

      Well, since this article concerns a desktop implementations, I'd be inclined to say no, not much difference. It's probably more relevant to ask about the benefits of KDE vs, Gnome. Your average Joe user will rarely if ever open a command shell, and even if he does, most of the commands are very similar if not identical. Now for specialized applications and servers, there are probably some (marginal) advantages of one over the other, but if, like me, you only use your desktop PC as a desktop PC, KDE still looks and acts like KDE, regardless of what's running under the hood.

      On a PC I usually use Linux, because I'm used to it, and on a Mac, I use OS X, which is based on BSD. For my purposes, both are adequate. But does one have any inherent advantage over the other? None that I can tell. YMMV.

    7. Re:BSD v Linux by rbullo · · Score: 5, Informative
      --
      OH NOES!!! IT APPEARS YUO DO NOT HAVE ENOUGH MONEY TO PAY FOR DIS HERE PIZZA! WAHT EVER ARE YOU GOING TO DO!?!?
    8. Re:BSD v Linux by pluggo · · Score: 2, Informative

      Actually, in this particular case, you can fix things pretty easily. Corrupted Pythuon? Here's two fixes:

      # wget http://python.org/python-source.tar.gz
      # tar xzf python-source.tar.gz*
      # cd python-source/ && ./configure && make && make install

      -or-

      # export ROOT="/mnt/gentoo"
      # emerge -C python
      # emerge python

      * Not real URL

      --
      Pulling together is the aim of despotism and tyranny. Free men pull in all kinds of directions. It's the only way to mak
    9. Re:BSD v Linux by Mekanix · · Score: 2, Informative

      Could someone point me to (or post) a lowdown on the potential benefits of BSD has over linux (or vice versa) that doesn't include wild speculation and unfounded cynicism?

      I've been using FreeBSD exclusively on my Desktop for years. And I like it over any Linux-distro I've come across. Why?

      * The FreeBSD Handbook. Most (common) issues you'll ever encounter are addressed here.
      * Ports. It just works.
      * Stable. Haven't had a crash in ages that wasn't caused by overheated HW.
      * Logic. If something doesn't work out of the box and you need to go under the hood, I find FreeBSD much nicer to work with than any linux-distro I've come across.

      Now, FreeBSD isn't perfect and it's certainly not point'n'click friendly. You'll have to edit tons of config-files. And then there are some small issues that are having me looking at linux again.

      I'm "old" and tired, got a slow PC and don't really find it all that fashinating anymore to be building my own packages. It is possible to do binary upgrades on FreeBSD, but I'm always running into issues with updated ports and available binary packages are out of sync. Alas I've got to build those darn ports myself anyway. In this regard apt-get is so much better.

      Attaching mp3-player, cameras, usb-sticks, usb-harddrive have become a nightmare. For starters I can't get usb2 to work, so I can't really use my usb-harddrive. Since FreeBSD doesn't automagically make attached devices available for the users, so you'll have to dig into config-files and there I have no less than 3 different to fiddle around with (usbd.conf, devfs.conf, devd.conf). In usbd.conf it would look something like this.

      #MP3 Player
      device "MP3 Player"
          devname "umass[0-9]+"
          product 0x0301
          attach "/bin/sleep 5; rm -f /dev/mp3player; /bin/chmod a+rw /dev/da0; ln -s /d
      ev/da0 /dev/mp3player"
          detach "rm -f /dev/mp3player"

      Problem here is if I attach my mp3-player AFTER I've attached eg. my camera, /dev/mp3player would be linked to my camera instead. I've haven't been able to figure out a smart way to attach my usb-devices yet and the documentation is lacking. So right know I can only attach one device at a time.

      I think must linux-distro handles usb-devices better.

    10. Re:BSD v Linux by JonnyCalcutta · · Score: 4, Informative

      You are missing the point. Linux is a kernel and each distro is a Linux based OS. FreeBSD is _not_ a kernel - it is a full operating system. DesktopBSD is not just the FreeBSD 'kernel', with a 'graphical installer' and a 'gui'. It is the full FreeBSD OS with a few extra desktop-friendly tools added (I'm not judging it, just stating what it is).

    11. Re:BSD v Linux by rbanffy · · Score: 2, Insightful

      We could think of them as both distros. A Linux distro uses a Linux kernel and a bunch of other tools while a BSD "distro" uses a BSD base system (analogous to the GNU+Linux combo) and a little smaller bunch of user-friendly GUI tools.

  2. Would you like a LiveCD with that? by airjrdn · · Score: 2, Interesting

    Here's to hoping there's a LiveCD version. So far, the only LiveCD that recognizes my wireless card (Broadcom in an HP laptop) is Simply Mepis.

    1. Re:Would you like a LiveCD with that? by Ours · · Score: 2, Informative
      --
      "You superiour intellect is no match for our puny weapons" - The Simpsons
  3. Necessary? by wigle · · Score: 3, Insightful

    First of all, if you're using FreeBSD chances are you know how to configure an X11 environment. It's easy. Also, you have your choice of window managers; not everyone will choose KDE. Package management is already extremely easy with ports, especially with portupgrade. I definitely agree that FreeBSD with an official GUI would be awesome (the opposite approach of Windows, where the interface would simply be a frontend for scripts), but for a half-hearted attempt there's not much of a demographic.

    --
    ::wigle::
    1. Re:Necessary? by debilo · · Score: 5, Insightful

      What exactly makes you call this a "half-hearted attempt"? As far as I know, the author of DesktopBSD has been working on this project for months now with only little help from a few others, and he's been a victim of flames like yours above trying to ridicule his efforts several times now.

      . Until you've installed and tested it yourself, your post above is nothing more than a half-hearted attempt at a comment.

  4. Funny installation steps by ReformedExCon · · Score: 2, Insightful

    It's great how the fancy graphical installation screen crashes back to an ugly terminal font in Screen10. It kind of throws off the whole good vibe that I'd been getting during the previous steps. Also, why is there a Next button active when the installation script obviously wants me to press Reboot? Strange, to say the least.

    But when it comes down to it, installation is only the gateway to the system. It isn't the system itself. MacOS could have the world's worst installation system, but the OS itself runs so nicely that people just love to be running it.

    There should be no "Configure my Installation" step. It should choose a default "best-fit" confiuration based on the detected hardware (mostly screen resolution) and leave any further customization to the user to do later. It is more important to have the system up and running than to have it customized just so.

    And in the end, you're still dealing with BSD, which is great if you're running a server, but sluggish (response times to system interrupts is slow, compared to Windows and MacOS) when running in a user-centric scenario.

    I installed FreeBSD previously and didn't have any trouble there. The questions were just as straightforward as this installer and within an hour I had a full BSD installation with graphical interface to boot. It wasn't "ready for the desktop" in any sense of the term, though, unfortunately.

    --
    Jesus saved me from my past. He can save you as well.
    1. Re:Funny installation steps by vga_init · · Score: 4, Informative
      It's great how the fancy graphical installation screen crashes back to an ugly terminal font in Screen10.

      That's the bootloader, you nut. Even Fedora Core's bootloader uses that "ugly terminal font," just with different colors. Windows NT/2000/XP's bootloader looks like that too (and if you push the right buttons while booting your Mac, you'll get (you guessed it) a text-mode command prompt/boot loader (ie openfirmware). As with OpenFirmware, the FreeBSD bootloader can be configured silent so as not to display that menu). Sheesh. We give you KDE and you give us this hogwash about our installer. >:(

    2. Re:Funny installation steps by Fweeky · · Score: 4, Interesting
      "And in the end, you're still dealing with BSD, which is great if you're running a server, but sluggish (response times to system interrupts is slow, compared to Windows and MacOS) when running in a user-centric scenario."
      I'm sorry? I run both Linux, FreeBSD and WinXP desktops on a variety of hardware; "sluggish" isn't what I'd call FreeBSD. It plays a mean game of UT2004 too.
    3. Re:Funny installation steps by Fweeky · · Score: 2, Interesting

      Funny, when I'm booting Windows, I often find myself wishing it was more like *nix in booting, so I could actually, you know, *see* whatever the hell it does while booting up. Make slow bootups and breakages that bit easier to debug. Given that it's about the most fragile time in any OS, I like a bit of commentary.

  5. BSD or KDE? by vandan · · Score: 4, Interesting

    Screenshots are great, but only when they're relevant.

    People who are keen enough to be interested in BSD will already know what KDE looks like. It would be far more instructive to show screenshots of things that are unique to this particular distribution of BSD. How about showing the GUI tool for software installation, or samba configuration, or something.

    All I know now is that BSD runs KDE ... and I knew that before I looked at the screenshots.

    I like the KDE background, though ;)

  6. Re:Too bad, fragmentation of FOSS Desktop efforts by mrchaotica · · Score: 3, Interesting

    It would also help if we worked harder on well-defined and standardized APIs, so that it would be easier to get things working with each other. For example, a standardized hardware configuration API would help make "control center" type apps a lot easier to make, etc.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  7. Re:Too bad, fragmentation of FOSS Desktop efforts by compass46 · · Score: 5, Funny

    We're all on the same team -- only if we FOCUS our efforts into the OS with the best chance (Linux) can we defeat the DRM-infested, money-grabbing proprietary OSs like M$ Vista and Apple OS X.

    Must start using the one true F/OSS operating system... Oh wait, screw that. I like my BSDs here. Reason #1 why I use FreeBSD over Linux, I just want a Unix-like OS without a revolution packaged with it. Talk about bloat. :)

  8. Re:Convince me by Elshar · · Score: 2, Insightful

    No, noone is going to convince you. This isn't a sales pitch. (Why was that moded interesting? Its not).

    Also, BSD is NOT linux. Read for yourself what they do. Here they are.

    http://www.freebsd.org/
    http://www.openbsd.org/
    http://www.netbsd.org/

  9. Its not the kernel. by Some+Random+Username · · Score: 4, Interesting

    No, the kernel doesn't make that big of a difference, and the kernel is all that linux is. BSDs are complete operating systems. The reason I don't use linux is because every distro comes with a messy userland full of random assorted crap from various sources, and most of the core utilities are bloated, poorly documented GNU junk.

    The BSDs have sane, useful, documented and functional userlands, which makes them a joy to use. There is no reason that linux distros couldn't be made with a nice userland too, but nobody seems to have done it. It seems like most linux users have never used a nice unix system, so they don't realize what they are missing.

    1. Re:Its not the kernel. by Digital+Pizza · · Score: 3, Insightful
      ...most of the core utilities are bloated, poorly documented GNU junk.

      Thanks for reminding me of something: whoever it is within Gnu that thought it'd be a great idea to deprecate man pages in favor of info documents, even if it's Stallman himself, I seriously want to kick his ass!

      There. That felt better.

      BTW, I agree with the rest of your post as well.

      --
      We apologize for the inconvenience.
    2. Re:Its not the kernel. by jmking1 · · Score: 4, Insightful
      Pointing out the Linux is just a kernel, calling the userland utilities "bloated", "random assorted crap", and "GNU junk" without anything to back these claims, and stating that BSD is a "nice" Unix system with a userland that is a "joy" to use aren't legitimate arguments against GNU/Linux, they're dumb insults that add nothing of value to this discussion.

      The documentation issue was the only intelligent point made. However, it was surrounded by a bunch of crap.

      Oh, and your "This is /. you can't post anti-Linux things here" post has been done about 10000 times before. And it still gets modded funny. Wow.

    3. Re:Its not the kernel. by sn00ker · · Score: 4, Interesting
      is the driver support in BSD up to the same level as Linux?
      Mostly, yes. If it's not hardware that's running on the bleeding edge, FreeBSD drivers are often better than Linux drivers - in some cases, FreeBSD drivers exist where Linux is stuck using *shudder* Project Evil drivers.
      If the hardware is a year old, you're reasonably certain that it will be supported well in FreeBSD if it's supported in Linux. The caveat is hardware where there is no open-source driver, such as with nVidia and their persistent non-support of FreeBSD on amd64.

      External storage devices are a joy to use under FreeBSD. Provided you've kept the da and umass drivers, things as diverse as top-end Minolta cameras and cheap USB memory card readers will happily work. Even cheap USB bluetooth adaptors work, though I'm still wrestling with how to get my Palm to use one to connect to the 'net - not that that's any different to XP, which has managed to stop recognising my Palm entirely and has also stopped recognising the bluetooth dongle.

      Short version, if you want to live on the bleeding edge you want to be running Linux. If you're OK with waiting six to 12 months before you get the latest new toy (entirely new technology, not necessarily latest model. eg: NCQ-capable SATA drives), you are almost guaranteed that your FreeBSD box will recognise it, play nice with it, and have good man pages to explain how to use the drivers.

      Personal anecdote: My workstation at work uses the Intel ICH5 chipset for SATA. Three different Linux distros (this is 13 months ago) wouldn't install. Couldn't see the hard drive. FreeBSD 5.1 didn't care, which is good because I've long had a soft spot for the demon. Last night I finished converting my home servers to FreeBSD, from debian. Feels good :)

      --
      "God, root, what is difference?" - Pitr, userfriendly
    4. Re:Its not the kernel. by Anonymous Coward · · Score: 3, Informative

      I agree with you that man pages should not be deprecated (they serve their purpose damn well, and have a very long tradition).

      That said, texinfo has HUGE benefits for developers and users. It is a breeze for example to generate all sort of formats (pdf, html, text, info ...) for your manual, from the same .texi source. The integration with the autotools is also marvellous (make pdf, make html, make ps, ..).

      I think both man and info should remain, with man helping you when you just need to look at that cmdline option you forgot, and info giving you the full manual with chapters, examples, etc.

    5. Re:Its not the kernel. by 10Ghz · · Score: 3, Insightful

      So, does *BSD have a *BSD-GUI that is a "joy to use", or do they use some some "random assorted crap from various sources"? On Linux I use KDE, and I'm toying with Gnome, but apparently those are crap. Could you point me to the *BSD-equivalent?

      What compilers do *BSD's use? Is it "GNU junk" or something else? What about X? X.org would be "crap from various sources", so apparently *BSD uses some uber-leet BSD-Xserver, right?

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    6. Re:Its not the kernel. by TrekCycling · · Score: 2, Interesting

      I'd love to use FreeBSD, but then there's that whole messy Java issue. In other words that it's not supported for, nor does it run well on FreeBSD last time I checked. Partly because of the threading model of FreeBSD. I'm not sure if that's changed, but as a Java developer this made FreeBSD a non-starter for me.

    7. Re:Its not the kernel. by Eivind+Eklund · · Score: 2, Interesting
      I've worked with systems that include info for over ten years now. I still can't get used to it; the info browser (/usr/bin/info) is immensely clumsy, and the use of texinfo tend to make the man page a second thought, making the entire documentation set extremely annoying.

      My conclusion is that texinfo never grew up, and that the niche it tried to fill has been taken by docbook.

      Docbook has one significant technological advantage over texinfo: The omission of a standard command line interface to replace man(1). If you're going to use docbook to maintain documentation that's to be available from the command line - it comes as man pages.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
  10. Too bad, another OSS jihad. by Anonymous Coward · · Score: 5, Insightful

    "Face it, Linux has a head start and is enjoying far more corporate support (due partly to the fact that Linux is licensed GPLv2, which compells big companies to share back their improvements).

    We're all on the same team -- only if we FOCUS our efforts into the OS with the best chance (Linux) can we defeat the DRM-infested, money-grabbing proprietary OSs like M$ Vista and Apple OS X."

    Why must every good thing be turned into some kind of zealot-fest, rally to my agenda? How about we all simply enjoy the damn distro without trying to conquor this, push agenda that, holy-war upon everything that doesn't agree with me?

    1. Re:Too bad, another OSS jihad. by Aeiri · · Score: 2, Insightful

      Why must every good thing be turned into some kind of zealot-fest, rally to my agenda? How about we all simply enjoy the damn distro without trying to conquor this, push agenda that, holy-war upon everything that doesn't agree with me?

      Because essentially, the more support an OS has (especially an open source one), the more usability it creates, the more new ideas flow into it, the more hardware vendors create drivers for it, etc.

  11. You know BSD is dead by bahwi · · Score: 2, Insightful

    When is starts to fracture.

    For awhile there, we only had 3, and life was good. Now we have DragonFly, Darwin, and now DesktopBSD. Any system that splits up so much must be dead or dying!!

  12. Re:Too bad, fragmentation of FOSS Desktop efforts by fafaforza · · Score: 5, Insightful

    > Too bad, all that developer talent could have gone into making Linux better suited for the desktop.

    Every annum for the past 6 years, headlines claimed that it was the year of "desktop Linux." Yet nothing came of it save for a bunch of Windows-esque clones with no innovation. Then Apple came along and revolutionized the desktop experience. So maybe it is time for someone else to give it a go.

  13. USB Keyboard by teslatug · · Score: 2, Informative

    Have they fixed the bug where you can't select boot with USB keyboard because you're using a USB keyboard?

    1. Re:USB Keyboard by Anonymous Coward · · Score: 2, Informative

      A new keyboard mux is currently being tested for 6.0-RELEASE.

  14. Hmmm.. by dirtsurfer · · Score: 2, Funny

    "Welcome to the DesktopBSD Installation! This wizard will guide you through the process of installing DesktopBSD on your computer. Please take the time to carefully through all texts and explanations because improper settings can cause data loss."

    Always nice when you install a new OS and the first screen you see is a paragraph that has obviously not been proofread.

  15. Re:While we're on the topic... by RLiegh · · Score: 2, Funny

    Of course not! It's not the standard text editor!

  16. Re:Too bad, fragmentation of FOSS Desktop efforts by b17bmbr · · Score: 5, Insightful

    can we defeat the DRM-infested, money-grabbing proprietary OSs like M$ Vista and Apple OS X.

    dude, take it easy. turn off the che rhetoric for a bit, tell your poly sci prof to lighten up on the indoctrination, and be thankful that we have money-grabbing corporations or else we'd all be living in mud huts. from each according to their ability doesn't work in the real world. now, i'm no fan of microsoft, but tell me this: how many people do you employ? how much do you pay in taxes? how many people use your software to run their businesses, etc. i own two ibooks, and have run linux on my pc's since '98. however, profit is not a dirty word. people pursue profit and it stimulates innovtion. why is it that people bitch up and down about "evil M$", yet barely say a word about all the hardware companies? eh? aren't they money grabbing? you like your dual core pentium 4's, well, they ain't making them because they're nice people.

    --
    My problem? I was perfectly gruntled, until some numbnuts came by and dissed me.
  17. DON'T PANIC by ari_j · · Score: 2, Funny
    This wizard will guide you through the process of installing DesktopBSD on your computer. Please take the time to carefully through all texts and explanations because improper settings can cause data loss.


    Yep. Grammar notwithstanding, that's totally worry-free and friendly stuff, right there.
  18. Anything That Uses X-Windows by IAmMaxHarris · · Score: 2, Insightful

    Anything that uses X-Windows will not get widespread user adoption.

    DesktopBSD looks good for a BSD, but it's still at least seven years behind the market.

  19. Re:Too bad, fragmentation of FOSS Desktop efforts by Anonymous Coward · · Score: 5, Insightful

    Will you quit using the "Royal We"?

    OpenBSD is my main operating system, with some Linux on the side. I don't want BSD to be like Linux. That's why I use it instead of Linux. That's why people use BSD. It does the job for them in a way that they like better. If they wanted Linux, they'd use Linux.

    Both systems have their strengths. BSD is great if you want something lean. Linux is good if you want something very easy to maintain and don't mind a little GNU-bloat.* BSD is great if you want traditional Unix. Linux is good if you're not very philosophical and just want something that works. BSD is great if you don't want to recompile your kernel. Linux is great if you don't want to recompile your userland. BSD seems to consume less memory. Linux supports more binary-only software.

    The point is, they have different goals, different strengths and weaknesses. I'm not in any hurry to see them merge. In fact seeing people advocate that here on Slashdot annoys the hell out of me. And I can tell you, the BSD developers and Linux afficionados out there would find the idea stupid too. If you posted your comment to a developer mailing list, if there'd be any reply at all, it would be along the lines of, "No. That's ridiculous. Stop getting in the way of our work." Though perhaps more polite.

    * Yes, GNU has a noble goal but can be bloated. It's mostly bloated because it tries to be all things to all people. See the infamous GNU echo joke.

  20. Re:This is what they got right... by Kethinov · · Score: 2, Interesting

    Well I know you're opening up the whole KDE vs. GNOME can of worms, but I don't think you're a troll. I think it's actually worth discussing again, and again, and again... :)

    Anyway, I'd tend to disagree with you. I think right now GNOME is the better of the two, however I would have agreed with you last year.

    Basically as it stands, all the best apps are GTK apps. If you want to run a fully native desktop, you're only gonna do that in GNOME. Whenever I use KDE, I find myself enjoying it as a desktop, but hating it as a toolkit. And I always find myself running GTK apps, like Firefox, GAIM, X-chat, Evolution/Thunderbird, the list goes on.

    Now I do like a lot of QT apps. I personally think Konqueror is very nice, even though I hate the defaults. I also *love* k3b and some of the smaller KDE apps like kdf.

    That said, neither is perfect. But I think GNOME is improving faster than KDE. KDE is bloated, it has poor defaults, and QT is uglier than GTK (QT has too many borders! too many borders!). And GNOME is too lacking in features. Well, each release of GNOME goes a long way towards solving its features problem. Each release of KDE does little to solve its bloat, poor defaults, and ugly QT.

    Given that GNOME is cleaner, better looking, better defaults, is constantly tackling its weak spots, and most good apps are GTK, I can easily see why most distros push GNOME.

    But again, it's all personal preference. Both GNOME and KDE are fantastic projects and I wish distros didn't push one or the other but supported them equally. I use Fedora and personally I think Fedora's KDE support is excellent even though it defaults to GNOME.

    Anyway, I'll get back to coding in Kate and chatting on GAIM whilst browsing with Firefox in GNOME while burning a dvd with k3b... Unix desktops are not as simple as one DE, one toolkit, one kernel.

    --
    You're right, I wouldn't steal a car. But if it were possible, I sure as hell would download one!
  21. Download RC2 Here by LogicX · · Score: 3, Informative

    RC2 is actually out, just not listed on their download page. I found it on the Oregon Mirror, however that mirror is extremely slow -- (20K/sec).

    I'm hosting a mirror of DesktopBSD-1.0-RC2-x86-CD.iso

    --
    May this post be indexed by spiders, and archived for all to see as my Internet epitaph.
  22. Re:Too bad, fragmentation of FOSS Desktop efforts by Brandybuck · · Score: 2, Informative

    The BSD license isn't a packaged revolution. It's simply a notice of sharing. Sharing has been around even since before the cro magnon realized that a mammoth was too much for one hunter to eat.

    --
    Don't blame me, I didn't vote for either of them!
  23. GNUStep + [Net]BSD. by pschmied · · Score: 4, Insightful
    I keep thinking that the world would be better off if more developers payed attention to GNUStep.

    Why not do it in a sane way such as:
    • Pick your hardware support carefully. NetBSD is good for this as things either work really well (usually the case), or they aren't supported at all. (I can configure NetBSD to use my Atheros wireless card out of the box using ifconfig. In Linux I have to know to download a beta "Mad Wifi" driver.)
    • Concern yourself with building the building block app kits like Apple has done. One of Apple's programming examples is TextEdit, which ships with the OS! Apple is agile because they have all the tinker toys, they just need to glue them together now.
    • Work on the Gui integration bits (i.e. wireless network controls, network profiles, video resolutions, printer management, etc) but do it with a cleanly abstracted design. Make sure that each item works flawlessly with a common set of hardware before expanding hardware support or adding features.
    • Build a community of app developers who like consistent look and feel and adhere to UI guidelines.
    • Take advantage of cross pollination from Apple. Allow app developers to build for StepBSD and Apple reasonably easily.

    This is my hope for a desktop oriented BSD. I'm typing this from OS X on my powerbook, but I think the world still needs a compelling open platform.

    -Peter
  24. Research it yourself. by Some+Random+Username · · Score: 2, Interesting

    Linux is just a kernel, this isn't my opinion, its a fact. How did you want me to back that up exactly? The userland included with every linux distro I know of come from a variety of authors, have far too many useless options, have outdated, incomplete or non-existant documentation in a variety of formats, and have nothing in common besides being lumped into a distro. If that's not "random assorted crap" I don't know what is.

    If you don't know wether or not something is true, find out. Me saying its true in more words isn't going to change anything, learn to think for yourself. Its not hard to install a BSD and check out how EVERYTHING has an accurate and up to date man page. How man pages not being clear enough is considered a bug and is fixed. How the same group of people are responsable for the entire OS, and ensure consistant and sane behaviour from all userland tools. Compare it to your linux distro of choice, its not hard to see the difference.

  25. Re:Too bad, fragmentation of FOSS Desktop efforts by poningru · · Score: 2, Interesting

    but unfortunately it allows people to not 'share back' the stuff they took and improved.

    --
    Calm down people, its a religion not an operating system.
  26. Re:Too bad, fragmentation of FOSS Desktop efforts by Brandybuck · · Score: 3, Insightful

    but unfortunately it allows people to not 'share back' the stuff they took and improved.

    Sharing isn't the word your want. Sharing isn't about attaching strings to your generosity. The word you're looking for is "reciprocality". Please don't confuse the two.

    --
    Don't blame me, I didn't vote for either of them!
  27. Re:Too bad, fragmentation of FOSS Desktop efforts by Anonymous Coward · · Score: 3, Insightful

    I suspect Intel and AMD and most companies have much lower profit margins than Microsoft, and don't spend nearly as much time trying to screw the customer. There's a difference between an ordinary profit-seeking company, and a company that tries to squeeze as much money as possible from its customers -- and can get away with it.

  28. Re:Too bad, fragmentation of FOSS Desktop efforts by zsau · · Score: 2, Interesting

    Apple began to "come along and revolutionise the desktop environment" before Linux was a spark in Linus' eye. Almost all the technology that is MacOS X was either in the classic Mac operating systems or (for the majority) in NeXTSTEP back in the late 1980s. They just jazzed up its look a bit and switched parts of the kernel. It took NeXTSTEP over a decade to get to the stage it (as MacOS X) was in in 2001. Why should you expect a much more poorly-funded group of programmers to do the same in half that time?

    GNU/Linux, FreeBSD and other similar operating systems, however, have been designed with a different userbase in mind. Clearly, they excel in that domain. More recently (beginning after your six-years-ago date), desktop environments have either attempted either to court a different userbase (e.g. Gnome) or they have become so good that they are able to be attractive to that different userbase (e.g. KDE). Considering where they came from, and where we've suddenly expected them to go, Free desktops have made outstanding progress.

    Aside from that, there will be no 'year of desktop Linux'. It will just be that over time, a relatively large proportion of non-geeks will come to use Free desktops.

    --
    Look out!
  29. Re:Too bad, fragmentation of FOSS Desktop efforts by i_am_not_a_bomba · · Score: 2, Insightful

    Umm, I think using the word "revolutionised" is probably as over the top as claiming Linux running KDE or Gnome or whatever will "take over" the desktop market.

    My iBook (which is downstairs that i use every night), is no more or less revolutionary, better or worse than my PC that i use everyday that runs KDE.

    Both have things i love and rant about, that are new and different, both have things that shit me to tears.

    The difference? When i get shitty at KDE, or some OS application i think "It's free and look at the awsome stuff it does". When i get shitty at OSX, i think, "ooohh look the MIGHTY OSX being a pain in the arse, whats that? I need to spend *more money* on yet another stupid shareware application to perform some inane task like putting my iPhoto library into a different place?"

    Revolutionised indeed, a revolution would be holographic projectors that can read my thoughts or some awesome shit like that, little bouncing icons and an automatic window organiser is *not* revolutionary.

    (Sorry, just bitter after wrestling with OSX for a few hours yet again).

  30. Re:Too bad, fragmentation of FOSS Desktop efforts by Octorian · · Score: 2, Insightful

    Yeah, and my "Desktop Solaris" also looks like "your desktop Linux but with a different wallpaper" as well. (hint: I'm running KDE 3.4.1, with all the same software any "Linux user" would otherwise use as well)

    All that glorious "Linux software" you all gloat about is really not "Linux software". It's "UNIX-compatable software" and benefits users of just about any *NIX-like system out there.

  31. Re:Too bad, fragmentation of FOSS Desktop efforts by vhogemann · · Score: 3, Interesting

    Come on! The desktop is alredy here, both GNOME and KDE are very usable, and in some points better than Windows.

    The problem is how to integrate them to the underlying OS! Until recently there was no standart way to do it, every distro implemented its own hardware discovery scheme.

    Now we got udev, pmount, hal and others to help. Have you tried a modern desktop targeted distro recently, like Ubuntu for example? Get a usb drive, plug it and bang! It appears on the desktop MacOSX style.

    The only BIG problem left is easy, next-next-finish style, standart installation packages across every distro. But hopefully they'll handle this one too.

    --
    ---- You know how some doctors have the Messiah complex - they need to save the world? You've got the "Rubik's" complex
  32. Re:Too bad, fragmentation of FOSS Desktop efforts by BiAthlon · · Score: 2, Interesting

    I've seen teams require a regulation sized ball and a regulation sized field with paid and licenced officials to enforce the rules.

    Microsoft can field a team anywhere for any field. But it most likely won't be a winning team of super stars.

    Linux, BSD, and OSX have specific uses (Linux and BSD more so than OSX) and they shine at them. In my mind that's the difference. I don't want a whole team, I just want a really good Linebacker.

  33. Re:Too bad, fragmentation of FOSS Desktop efforts by theonetruekeebler · · Score: 2, Funny

    Most F/OSS I know of has capital-letter support build right in instead of being a value-added option you obviously were too cheap to spring for. You had to cut'n'paste to get "M$" into your post, didn't you?

    --
    This is not my sandwich.
  34. OS X == Desktop BSD by dick+johnson · · Score: 2, Insightful

    I know it's not a free download...

    But there already is an easy to use BSD for the desktop. It's called Mac OS X.

    Yes. Yes. I know it only runs on Apple hardware (at this point).

    --
    - dj
  35. Re:Too bad, fragmentation of FOSS Desktop efforts by brokenarmsgordon · · Score: 2, Insightful

    Hey now, don't reach too far, that Holy Grail of verbal sophistry just isn't worth it, Brunhilde.

    To use "in common with others" means that you and others draw from the same pool. There is absolutely no implication of a return.

    You don't share so you can get something out of it -- you share because it's the right thing to do. Imposing debt is not sharing.

  36. Re:Too bad, fragmentation of FOSS Desktop efforts by Himring · · Score: 2, Funny

    Well, I will not go toe-to-toe with a history teacher. I do appreciate the reply and clarification. Modern business, economics, etc. is indeed a balance. Too much government stifles/too little creates oligarchy.

    am well aware of the rise of the corporation. which by the way, was not capitalism.

    Yes, but was it capitalization?

    --
    "All great things are simple & expressed in a single word: freedom, justice, honor, duty, mercy, hope." --Churchill
  37. Re:I really hope they give free in pertuity. by Omnifarious · · Score: 2, Interesting

    I care about two main things...

    First, the existence of organizations like the BSA indicates a deep and troubling flaw in the legal system. When you have to encourage people to rat on eachother in order to enforce laws you have a system of laws that are broken and wrong.

    The deep and troubling flaw is the extension of copyright beyond commercial reproduction. Commercial reproduction is easy to find and deal with. Controlling it represents no big loss. Controlling copying at a personal level is inherently invasive.

    The second issue is this...

    If you ever look at the Windows platform, the home of proprietary software, the vast majority of programs on it do many things the users of those programs are not aware of, and are things that are not in those user's best interests. Basically, when you run a piece of proprietary software, you are giving control of your computer to someone else. It's no longer your computer.

    If OS X were GPL, I would most likely buy copies of OS X. I do not care if it is free of charge. But I do care that I know what it's doing when it runs, and that it's actions are independently verifiable and auditable. This is likely going to be a real problem when Apple adopts hardware-level DRM.

    Also, the GPL is a simple license. It states its intentions at the beginning in simple language, and the legalese is there to support those intentions in a clear and precise manner. It's the most pleasant to read legal document I've ever read.

  38. Re:Too bad, fragmentation of FOSS Desktop efforts by Tony · · Score: 2, Informative

    now, i'm no fan of microsoft, but tell me this: . . . how much do you pay in taxes?

    A lot more than Microsoft, it appears.

    --
    Microsoft is to software what Budweiser is to beer.
  39. Re:Journaling File System by Just+Some+Guy · · Score: 2, Informative
    However, in exploring it not that long ago, I found one glaring omission was journaling file system support.

    Are you sure you need journalling, though? FreeBSD's softupdates cover most of the advantages of a journal, and the background fsck (which mainly makes sure that unallocated blocks are actually marked as such) lets you boot quickly.

    I certainly don't think journals are a bad thing, but I've honestly not missed them.

    Regarding vinum: what do you like better about Linux's logical volume management? gvinum (GEOM-based vinum) has been pleasant enough for what I've asked of it.

    --
    Dewey, what part of this looks like authorities should be involved?
  40. Re:Too bad, fragmentation of FOSS Desktop efforts by bluGill · · Score: 2, Insightful

    For most of the mid 80s to mid 90s, every year you could count on some major prediction that next year would be the year of the network. Never happened, without any explosive growth networks ended up anywhere.

  41. Re:Journaling File System by bluGill · · Score: 3, Informative

    Short answer: because FreeBSD has softupdates, which for most people turn out to be just as good, and for some better.

    There are two ways to get the advantages most people want from a journaling file system. The obvious is to write a journal. FreeBSD instead spent time to make sure that meta-data could not get out of date in the first place, and thus there is no need for a journal. The latter is harder to implement, but has some significant advantages, and other disadvantages. For most people either will work fine, for those who have a case where it matters FreeBSD is implementing the journal. The real question is why nobody else is implementing softupdates so they don't need a journal in the cases where it is worse.

    Remember, this is not a case where journals are always better than softupdates. For some workloads journals are better, for others softupdates is better. FreeBSD will soon be the only one to let you choose based on your real-world needs.

  42. Re:Too bad, fragmentation of FOSS Desktop efforts by doc+modulo · · Score: 2, Interesting

    "The only BIG problem left is easy, next-next-finish style, standart installation packages across every distro. But hopefully they'll handle this one too."

    I agree, this is a big one. I think the best system is the one OS X uses, application folders.

    I like the fact that DesktopBSD has helpful "control panels" and configuration/installation wizards, it's good stuff.

    However, PC-BSD has application folders and that's why I'm going with that. I just think it's the most usable system of progam installation and more importantly, the easiest system for getting RID of programs. Getting rid of a program that's installed it's files all over your HD demands the help of a thing called a package manager or "uninstall wizard" which need a perfect log of where all the little files were installed to.

    In practice, the perfect installation log system is never perfect. It happens that it's either not recorded correctly or something changed after the installation which causes the uninstall to fail. If you want to be SURE you just install every program into it's own folder and you'll know that you've gotten rid of everything if you see the folder gone. It's conceptually easier to get your head around and it's just more usable in practice (drag the folder to another PC and it's "installed" there).

    Hopefully DesktopBSD will see the light, they're doing well in every other departement.

    Good luck guys.

    --
    - -- Truth addict for life.
  43. Re:Working on Athlon64 yet? by phoenix_rizzen · · Score: 2, Informative

    First thing to know about 64-bit systems, whether they be Linux, Windows, or BSD: avoid the nForce chipsets. They are not worth the hassle to get working reliably.

    That's your first mistake.

    Second thing to know about 64-bit systems, whether they be Linux, Windows or BSD: avoid the very latest, bleeding-edge, "I'm so cool, I got it first" technology. It's not worth the hassle to get working reliably.

    That's your second mistake.

    Third thing to know about 64-bit systems, whether they be Linux, Windows, or BSD: always, always, always research the hardware support before purchasing any hardware. It's not worth the hassle to get things supported after-the-fact. Doing this would have prevented the first two mistakes. :)

  44. Re:Yea, by phoenix_rizzen · · Score: 2, Interesting

    Hmmm, is it really so hard to:
    kldload snd_driver
    (loads every sound driver on the system)

    cat /dev/sndstat
    (read the output to see exactly which sound driver is being used)

    echo 'snd__load="YES"' >> /boot/loader.conf
    (tell the kernel to load the specific sound module at bootup)

    Remember, 95% of all device drivers in FreeBSD are compiled as modules and stored under /boot/kernel/, all there for the loading if you need them. You only need to recompile the kernel to remove drivers.

  45. Re:Too bad, fragmentation of FOSS Desktop efforts by mrchaotica · · Score: 2, Insightful

    POSIX is great, but it doesn't go far enough. POSIX + LSB + FreeDesktop.org is more like what I'm talking about, but even it's just a start!

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  46. Re:Yea, by Icyfire0573 · · Score: 2, Interesting

    not difficult at all, but as they say who wants to go CLI to fix sound, also when i installed freebsd 5.4 release last week kldload snd_driver didn't do anything for me and I ended up recompiling it.