Slashdot Mirror


Debian 6.0 Released In GNU/Linux, FreeBSD Flavors

itwbennett writes "After two years of work, the Debian Project has announced the release of Debian 6.0. 'There are many goodies in Debian 6.0 GNU/Linux, not the least of which is the new completely free-as-in-freedom Linux kernel, which no longer contains firmware modules that Debian developers found troublesome,' says blogger Brian Proffitt. And in addition to Debian GNU/Linux, Debian GNU/kFreeBSD is introduced as a technology preview. 'Debian GNU/kFreeBSD will port both a 32- and 64-bit PC version of the FreeBSD kernel into the Debian userspace, making them the first Debian release without a Linux kernel,' says Proffitt. 'The Debian Project is serious about the technology preview label, though: these FreeBSD-based versions will have limited advanced desktop features.' The release notes and installation manual have been posted, and installation images may be downloaded right now via bittorrent, jigdo, or HTTP."

53 of 250 comments (clear)

  1. to put it bluntly.... by Anonymous Coward · · Score: 2, Interesting

    FUCK YEAH!

  2. NetBsd kernel...what's the advantage? by aaaaaaargh! · · Score: 3, Interesting

    I used to run NetBSD on an old PP Mac booted from a zip drive in the nineties. It was running great but since then I haven't looked at it again. I know that the 3 free BSDs (open-, free- and net-) are security audited and support old hardware very well. But I wonder what advantages the kernel itself brings. So my potentially stupid questionis:

    What's the advantage of running Debian with a BSD kernel instead of linux?

    1. Re:NetBsd kernel...what's the advantage? by Anonymous Coward · · Score: 2, Informative

      ZFS and DTrace come to mind, but those are only the easy examples.

    2. Re:NetBsd kernel...what's the advantage? by bk2204 · · Score: 5, Informative

      You can find some of the reasons here. Among them are ZFS, jails, and pf. I've used Debian GNU/kFreeBSD in the past and found pf significantly easier to use than iptables and tc.

    3. Re:NetBsd kernel...what's the advantage? by snookiex · · Score: 2
      They also point to a benchmark made in Phoronix. here is an excerpt from the conclusions:

      Of the 27 tests that were carried out with our first Debian GNU/kFreeBSD benchmarking session, in 18 of the tests Debian GNU/Linux 32-bit was faster than Debian GNU/kFreeBSD 32-bit. However, with many of those 18 wins, the GNU/kFreeBSD results were very close to the GNU/Linux numbers. With the 64-bit versions, Debian GNU/Linux did even better and was in front 23 of the 27 times compared to 64-bit Debian GNU/kFreeBSD. These 64-bit results were certainly quite interesting and it looks like the FreeBSD kernel can be better tuned for a 64-bit environment. Debian GNU/kFreeBSD 64-bit though did have strong advantages with the x264, 7-Zip, and Gcrypt CEMLLIA256-ECB Cipher tests over the Linux kernel.

      --
      Open Source Network Inventory for the masses! Kuwaiba
    4. Re:NetBsd kernel...what's the advantage? by tomhudson · · Score: 2, Funny
      It's kind of funny that you talk about jails being an advantage ... from your link:

      the upcoming reiserfs and xfs, or

      definitely jailed, and a real killer :-)

      ... but don't you think you could come up with something a bit more recent? Linux has changed a bit since then.

    5. Re:NetBsd kernel...what's the advantage? by vlm · · Score: 2, Informative

      What's the advantage of running Debian with a BSD kernel instead of linux?

      If you want to make money, and don't want to contribute back to the free software economy, its easier with a BSD license than a GPL license. Other than that...

      Quite an oversimplification.

      Yet, not bad for just 27 words. If you can do better given that constraint... A laundry list of unique features, license differences, and the (very few) device drivers that work better under BSD than linux, would probably be too long and complicated to be a "summary".

      I would go further and state its within the set of questions where if you are able to successfully implement the answer, you are capable enough not to need to ask us the question, or alternately its within the set of questions where if you actually needed to know the answer, you would have already figured it out via very hard experience on linux, although knowing it is a bad question in advance would probably have been impossible because it would have taken more data to evaluate the question than to answer it...

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    6. Re:NetBsd kernel...what's the advantage? by rtfa-troll · · Score: 5, Insightful

      ... it has always befuddled me as to why they didn't 'just use' BSD instead.

      To be honest, believing exactly the argument you gave companies mostly they did until the last few years. However, you never knew about out because they didn't publish the code. The reason for this is that there is no need to and if they do release their code, their competitors can use it, so their lawyers advise them against. After a few years they either get so wildly successful (JunOS / OSX / Microsoft TCP/IP stack) that they keep their own completely proprietary branch and never help anyone else or they get abandoned (IPSO / AlchemOS / BSDi / SunOS / etc. etc.)

      The thing is, that the because of the effects of copyleft, the Linux people cooperate and release code and so, even though the resources put into Linux are much less, there is less duplication and so more is achieved. This has become much more visible recently with Android and other successes and means that corporate types have begun to see copyleft as a platform which makes limited cooperation with potential competitors possible and safe.

      If you are choosing a system for your own platform, this becomes a good reason to choose an AGPLv3 base as much as possible and, if you have any proprietry code, layer that separately on top. Your work on the commodity underlying components can be safely released and will move forward with the rest of the community. Whatever investment you put in will be preserved instead of becoming obsolete.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    7. Re:NetBsd kernel...what's the advantage? by Morth · · Score: 3, Informative

      Are they using glibc or the freebsd one? Because one of the developer advantages of the BSDs are that kernel and libc are more in sync. Ie. there's no system calls in libc that are not in the kernel, and vice versa.

    8. Re:NetBsd kernel...what's the advantage? by Joe+Jay+Bee · · Score: 3, Interesting

      One of the things I appreciate most about it is the proper OSS sound support, with mixing that actually works out of the box without having to deal with shit like PulseAudio or the clusterfuck that is Alsa.

    9. Re:NetBsd kernel...what's the advantage? by Hatta · · Score: 2

      I like those advantages. What I really want to know is what the disadvantages are. Is all my software likely to work on Debian FreeBSD?

      --
      Give me Classic Slashdot or give me death!
    10. Re:NetBsd kernel...what's the advantage? by TheRaven64 · · Score: 3, Informative

      Working, in-kernel, low-latency, sound mixing is another one. No messing around with portaudio or ALSA, sound Just Works(tm).

      --
      I am TheRaven on Soylent News
    11. Re:NetBsd kernel...what's the advantage? by TheRaven64 · · Score: 3, Interesting

      So why is ZFS the only feature ever mentioned? I don't care about ZFS, only servers want that

      Indeed. There are absolutely no use cases for ZFS that aren't on the server. For example, no average user would want easy-to-use snapshots - being able to easily revert a file from an earlier version is a server-only feature. They definitely wouldn't want to be able to do simple incremental backups just by streaming the disk changes with something like zfs send / receive - only server users care about that. Data integrity is probably an enterprise feature too - no one on a desktop wants checksums in their data, because data loss only matters to enterprise users.

      --
      I am TheRaven on Soylent News
    12. Re:NetBsd kernel...what's the advantage? by TheRaven64 · · Score: 3, Interesting

      If you really want snapshots, LVM is probably easier

      A comment like that implies that you have never worked with ZFS. Snapshots are simple, are constant time, and don't have a performance overhead, and don't require any preconfiguration. A fairly typical ZFS setup has a cron job that takes snapshots every hour and preserves hourly ones for a while, daily ones for a bit longer, and then monthly ones, so you can always go back and find the file that you deleted by mistake.

      and works on all filesystems

      So does ZFS, if you decide to run another filesystem in a ZVOL (but why would you? We're talking about end users.

      The trouble is to come up with a good usecases for snapshots on the desktop, especially since a good backup solution is still needed in case of hardware failure

      zfs send / receive makes backups trivial to a NAS. Just take a snapshot, and you can then send all of the deltas between that snapshot and the previous one to a remote drive, over SSH (for example). Then, on the NAS, you also have the snapshots, as well as the latest version, so you can revert to earlier versions easily.

      --
      I am TheRaven on Soylent News
  3. Well done! by cavok · · Score: 2

    Thanks to all the involved people, we have another cornerstone of the Free Software.

  4. Good job Debian team by JackieBrown · · Score: 4, Informative

    This looks like a solid release. I only use stable for as long as it takes for the new queue to start start dumping back in Sid but I appreciate the hard work that has gone into this.

    And the new artwork really rocks. I was shocked to see plymouth working out of the box with my nvidia card. The consistency from grub to kde launch is really stunning and makes the whole bootup feel seamless.

  5. I love it! by no+known+priors · · Score: 3, Insightful

    I'm a Ubuntu user, but I know where it comes from. Debian has been the dream operating system of mine for ages. Easy to install thousands of packages, stable, safe, etc. The only trouble is, when I first tried to install it in 2007, I couldn't get it to work with my wireless card. Ubuntu just worked. I'm going to guess that it wouldn't work now either; my wireless card is one of those Intel ones with the locked up firmware so that I don't start spamming the airwaves... (If I recall correctly the software is ipw2200, or similar.)

    Anyway, one thing I note from the press release, is that it is still including OpenOffice.org 3.2.1. I wonder when they'll get LibreOffice (Ubuntu will get it in the 11.4 release).

    Great job Debian!

    --
    Appended to the end of comments you post. The maximum is 120 characters.
    1. Re:I love it! by vlm · · Score: 2

      I'm going to guess that it wouldn't work now either... (If I recall correctly the software is ipw2200, or similar.)

      So, you bothered to link to a page explaining in extreme detail both that it works, and exactly how to do it line by line, but you're guessing it wouldn't work?

      I think you're trying to write in a very complicated manner that you're not sure if your laptop has a ipw2200? I have second hand knowledge that the instructions on the wiki do work quite well if you're unfortunate enough to own a ipw2200 card.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    2. Re:I love it! by mmj638 · · Score: 3, Interesting

      it is still including OpenOffice.org 3.2.1. I wonder when they'll get LibreOffice

      Debian's OpenOffice uses patches from Go-OO (now merging with LibreOffice) anyway, so in some ways it is already more similar to LibreOffice than to stock OpenOffice.org. It opens .docx documents very well, for example.

      This is also true of Ubuntu's, and generally other distros' OpenOffice packages.

      LibreOffice itself came into existence too late for an actual LibreOffice version to make it into Debian 6.0.

      I expect it will be a smooth and uncontroversial transition from Debian 6.0's Go-OO enhanced OpenOffice to Debian 7.0's LibreOffice. I'm guessing they'll no longer use the OpenOffice.org branding for that particular variation of it though.

    3. Re:I love it! by clang_jangle · · Score: 4, Insightful

      That's the whole reason Ubuntu exists though, for people who lack the time or ability or whatever to just install and configure Debian (which exists for people who lack the time or ability or whatever to just build gentoo, which exists for people who lack time or ability or whatever to just create their own private distro from scratch, which of course is for people who lack time or ability or whatever to just go ahead and code their own custom OS using vi or emacs...).

      --
      Caveat Utilitor
    4. Re:I love it! by vlm · · Score: 2

      I'm not sure what card I have, it just works at install time in Ubuntu.

      pop open a terminal, "lsmod | grep ipw2100" if you see something you have a 2100. "lsmod | grep ipw2200" if you see something you have a 2200.

      Take a look at the output of dmesg, it'll probably have a lot of verbal sorta-english commentary on your wireless card.

      If I knew more Ubuntu, I could probably tell you how to figure out which firmware files it has installed and loaded.

      Does it count as a "google hack" to flip the laptop over, find the model number, and google for that and the words "debian install" or "linux wifi"? Maybe that would be too elite for the average "google hack".

      An interesting addition to future releases would be some kind of "as it boots" analyzer to grep for known troublesome devices and provide commentary, such as that wiki URL if certain strings are seen in dmesg or lspci. For all I know, d-installer already has that, I haven't installed in quite awhile (Debian being one of the few (only?) OS available in the entire computational world where upgrading from previous releases just works)

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    5. Re:I love it! by Seumas · · Score: 2, Interesting

      In other words (from personal experience):

      Slackware, Gentoo, Debian, etc - are especially great if you're a young geek who has plenty of time to enjoy debugging and playing with everything to get the simplest functionality out of your system (like sound or the right resolution to display properly on your screen).

      Ubuntu is especially great if you're an older geek and you need to be doing actual work rather than spending two entire weeks figuring out why an obvious LineMode configuration isn't working and your screen resolution is still totally screwed despite it and fighting against countless hurdles to get sound cards working properly with all of your applications, etc.

      Both are entirely valid and I wish I had more time in my life to keep being the first guy, but many (and it's growing every day) need to spend less time configuring and tweaking and working around bugs in linux and more time doing our actual work or projects (or working on our own bugs in our own software).

      Debian was my first real linux, about twelve years ago. It powered a really big project that I ran for more than a decade, almost flawlessly. Development can be glacial and Debian foundation bureaucracy can be navel-gazing and counter-productive . . . but god damn, the outcome is something to aspire to. And now, I can get a lot of that with someone else's spit and polish in Ubuntu.

      Gentoo, on the other hand. Well, it's good that there's a linux-based outlet for obsessive compulsives. :P

  6. Works well, but significantly higher requirements by drinkypoo · · Score: 2, Informative

    Squeeze has significantly higher minimal install requirements than Lenny, to the point it wouldn't fit on my Dockstar or my Dt360. So if you are using Debian because it's small and light, don't upgrade.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  7. Some CPU microarchitectures dropped from Debian... by ornia · · Score: 5, Informative

    It's interesting to note, that while Debian has traditionally supported more CPU microarchitectures than any other mainstream GNU+Linux distribution out there, they have decided to officially stop supporting multiple microarchitectures with the release of Squeeze. The dropped architectures are alpha, hppa, and arm, the latter of which is replaced by the new "Embedded" ABI of ARM, which Debian calls armel.

    Although kfreebsd-i386 and kfreebsd-amd64 have been added, these are not true new CPU microarchitectures in and of themselves, as they are compiled to standard x86 and x86_64 respectively, but obviously with the fairly radical change of not using Linux at all with a different GNU libc requiring all packages to be recompiled. This is the same situation as we have traditionally seen in the never-officially-released hurd-i386 port of Debian (which makes sense to call Debian GNU I suppose, as the Hurd kernel is part of the GNU project already) which seems to be missing so far with Debian 6.0 so far, pending a decision to potentially drop it as well.

    All in all, amazing work by all in the Debian project. It remains an incredibly impressive feat that such a project can have no corporate oversight or ownership yet maintain such an impressively influential, relevant, and useful place in the operating system ecosystem. Even with dropping a couple of architectures, Debian still supports more computer types than most people even know exists, and continues to provide package updates that many many other operating systems base their repositories from. Also wonderful to see the website be updated!!

  8. Re:First release without a linux kernel?? by guppysap13 · · Score: 3, Informative

    GNU/Hurd has never been released in Stable. It is available in Unstable, but isn't complete enough for them to upgrade to Testing and Stable yet. GNU/kFreebsd however, is now an official Stable release with Squeeze (6.0).

  9. Are they mad? by Moldiver · · Score: 2

    Are they mad at Debian? The thing that annoys most on Linux are the gnu-parts in the userland. Why should someone with a nice and well-designed bsd-userland use the gnu-tools instead?

    Or is this some kind of âoewe can do itâ?

    1. Re:Are they mad? by Anonymous Coward · · Score: 2, Informative

      Don't use it then. You're not forced to and you have a choice. Personally, I can't stand BSD's userland tools and prefer GNU's.

    2. Re:Are they mad? by hedwards · · Score: 2

      To be honest, that puzzles me as well. The big advantage that pretty much everybody else has over Linux is that they consider the kernel and userland to be tied together with only minor patching to the OS between releases. It makes it a lot easier to do performance tweaking and bug fixing if you have control over the entire base install. It also means that if you send into the mailing list with a problem you can concisely tell them what OS version you're running and they'll have a reasonable understanding of what your software environment is like. If you get a kernel panic you're still likely to have to have to look at the core that you get to figure out what exactly happened, but that's mostly because drivers vary from machine to machine.

  10. Re:Debian/BSD love nest found in Route 40 flophous by icebraining · · Score: 2

    So if you had to run Linux, you wouldn't?

  11. Re:Yeah! by icebraining · · Score: 3, Informative

    Is this not one of the fastest Debian release cycles?

    Not really. It's been two years since Lenny, which was two years after Etch.
    http://en.wikipedia.org/wiki/Debian#Release_history

  12. Re:yay. two more variants that nobody will want. by johnw · · Score: 4, Insightful

    Can you provide an actual example of Debian fans complaining in the way you indicate, or is it all in your imagination?

    Debian tends to be the way it is because Debian users (and builders) like it that way. Of course they do end up being rather smug as well, but complaints about those who choose to use lesser distributions are notably absent.

  13. Re:Works well, but significantly higher requiremen by DieByWire · · Score: 3, Informative

    Squeeze has significantly higher minimal install requirements than Lenny, to the point it wouldn't fit on my Dockstar or my Dt360.

    I'm running squeeze on a dockstar right now by booting from a USB stick. Some smart people made it easy for the rest of us.

    --
    Never shake hands with a man you meet in a fertility clinic.
  14. Re:yay. two more variants that nobody will want. by ffreeloader · · Score: 5, Interesting

    What a load of bs.

    I started with Debian as total Linux noob back when Woody was the official release. I've stayed because Debian stable is so stable, and because the APT system is about as good as installers get. I've never had to wonder whether something wasn't working because it was buggy, or because I lacked the requisite knowledge to configure it correctly. That alone made learning Linux much, much easier and far more straightforward. I'd used a couple of other distros before I heard of Debian, but even simple things in the gui didn't work on them because of bugs and I got very frustrated with them. I never knew if any problem I ran across was a bug or because I'd done something stupid. With Debian I could know with a high degree of certainty that the problems I encountered were my own stupidity, not someone elses.

    Debian was a breath of fresh air compared to all the bugs in other distros and Windows. I've played with Ubuntu a few times, but always abandoned it because it's not gotten any better over the years. It's always buggy, buggy, buggy. If I wanted a buggy OS I would have stayed with Windows. And, I find fewer bugs and newer software in the vast majority of cases in Debian testing and unstable than I do in Ubuntu.

    --
    "while democracy seeks equality in liberty, socialism seeks equality in restraint and servitude." de Tocqueville
  15. Re:yay. two more variants that nobody will want. by rl117 · · Score: 5, Informative

    You should be aware that Debian is not allowed to use the trademark "Firefox" and also have the ability to apply patches such as security fixes(1). It's not called "Iceweasel" out of anything but necessity. You think this is a Debian-specific issue? Well, no, it's actually a major problem for all other distributors as well(2).

    1
    2

    So the links are 5 years old, but the issues surrounding the trademarks haven't changed or gone away. Distributions shipping "Firefox" have abrogated their ability (and responsibility) to be able to apply changes and security updates to the software without the explicit concent of Mozilla Corporation.

    Not exactly free software when it comes on those terms, is it?

    Regarding the kernel, I assume you're referring to the non-free firmware removal. Maybe you haven't been fully informed that the non-free firmware was actually removed from the upstream kernel sources as well. As a result, the Debian kernels are far from "non-standard", they are standard!

    Regards,
    Roger

    [FFS Slashdot, it's 2011 and you still can't handle UTF-8!]

  16. Most RC-free release in a long time by gringer · · Score: 4, Interesting

    I'm amazed that they stuck this release freeze out long enough to get the RC bugs for the testing release down to what looks like the lowest since the graph began tracking testing in 2004 -- I would like to believe that this means squeeze will end up being the most stable/reliable release so far.

    Now that the release is done and the freeze is over, an upgrade of the Linux kernel (from 2.6.32 to 2.6.37) in unstable should be soon to follow. Also, Firefox (probably 3.5.9 -> 4) and LibreOffice (OOO 3.2.1 -> LO 3.3).

    --
    Ask me about repetitive DNA
  17. Re:Some CPU microarchitectures dropped from Debian by hedwards · · Score: 3, Informative

    I'm guessing that there are more developers interested in maintaining the m68k port than the Alpha port. Or at least that's how that typically goes. Unless you've got a strange OS like NetBSD which is obsessed with running on absolutely every possible architecture from mainframes to wrist watches, some platforms tend to not have enough people with the hardware and interest to keep updating the branch.

  18. Compelled by FSF diff than by church or gov't? by perpenso · · Score: 2, Insightful

    What's the advantage of running Debian with a BSD kernel instead of linux?

    If you want to make money, and don't want to contribute back to the free software economy, its easier with a BSD license than a GPL license. Other than that...

    That's a somewhat FUD'ish response. There are plenty of BSD users who contribute back. I'd say that one advantage is that you don't have a 3rd party (FSF) dictating terms to you, in particular a 3rd party that is on a quasi-religious campaign. I know the FSF claims otherwise, but they are not the free'er license. Restriction are restrictions, whether or not those restrictions have a socially beneficial goal and are altruistic. As GPL v3 introduced some controversy and drama, what will GPL v4 introduce. Some may not want to have to deal with it.

    Now I realize some GPL fans are probably feeling their emotions rise and some zealots have already stopped reading and have started composing their flames :-), but if a church or government was compelling you to do good and altruistic things would you consider that freedom? Why is being compelled by the FSF any different?

    1. Re:Compelled by FSF diff than by church or gov't? by perpenso · · Score: 3, Insightful

      Lets say your company adopts a BSD project and a GPL project..... The difference is that on the GPL you can only keep the code in house if you do not want to give out improvements. BSD? Rip, sell, earn money, do not contribute back. Or... at the least you can do that. Which does not help the community.

      Well for a limited definition of "helping the community". GPL'd projects have directly benefitted by incorporating BSD code and indirectly benefitted from the knowledge and experience of UC Berkeley's pioneering work in developing a *truly* free and open UNIX implementation. Apple, Sun, SGI and other have advanced the world of computing using BSD based code *and* they have also given back in various ways *including* giving code to the community. For example Apple HFS, which I believe has been incorporated into FreeBSD. And some have argued that some GPL folks take without giving back. One key BSD developer writes:
      "GPL fans said the great problem we would face is that companies would take our BSD code, modify it, and not give back. Nope -- the great problem we face is that people would wrap the GPL around our code, and lock us out in the same way that these supposed companies would lock us out. Just like the Linux community, we have many companies giving us code back, all the time. But once the code is GPL'd, we cannot get it back. Ironic."
      http://kerneltrap.org/OpenBSD/Stealing_Versus_Sharing_Code

      Basically I'm saying that the meme that GPL gives back and BSD does not is false. Things are far more complicated than that.

    2. Re:Compelled by FSF diff than by church or gov't? by Pharmboy · · Score: 2

      I think the short summary is that I can't change OS X any more than I can change Windows, no matter how much BSD code is in it.

      To be fair, there is still Darwin. Apple only releases source now, and could do more, but that is still infinitely more than MS does with their source code.

      --
      Tequila: It's not just for breakfast anymore!
    3. Re:Compelled by FSF diff than by church or gov't? by gratuitous_arp · · Score: 2

      That's a somewhat FUD'ish response. There are plenty of BSD users who contribute back.

      He was not arguing that the number of users who contribute is too small. If you want to use/improve code and *not* contribute back, it is easier to use code that is under a BSD license. Juniper and Apple are the two big examples of what he means. I'll grant you all of the contributions that these companies may have made over the years; to argue over what they have or have not contributed would be missing the point. The point is that the opportunity exists to take someone else's code, modify it, sell it, and never contribute back or tell your users what has changed, because this is permitted by the BSD-family licenses.

      Arguing against this is analogous to arguing against a law forbidding murder (or theft, etc.) because hardly anyone does it anyway.

      I know the FSF claims otherwise, but they are not the free'er license. Restriction are restrictions, whether or not those restrictions have a socially beneficial goal and are altruistic.

      The GPL gives freedom to the community (or to the code itself) over freedom to individual users. I agree that this is not always conveyed accurately by the FSF. These restrictions are the very reason why I, and I suspect many others, license our code under the GPL or contribute to GPL software. A restriction is not bad simply because it is a restriction. Some restrictions are particularly good, which I will talk about later. You haven't argued against this yet, so I will assume you know what I mean. I can clarify if necessary.

      I agree that a BSD license is more free. The freedom taken away by the GPL involves other people's ability to "leech" from the community. Everyone likes this except the leeches and those who simply don't want to be told what they may or may not do. I can understand both of these (very different) approaches to not liking the GPL, but I don't share either of them. (For the record, I am not suggesting that you are a leech; the argument you are advancing fits into the second camp.)

      I don't *need* to be told not to leech, and I appreciate that I have a recourse against those who do.

      if a church or government was compelling you to do good and altruistic things would you consider that freedom?

      No, I would consider it the underpinning of a civil society. Not all freedom is good. For instance, giving other people the freedom to commit horrendous acts (child abuse, murder, theft, etc.) without retribution is not a good thing. Realizing this, many governments have laws against such things.

      I do not need compulsion in order to act with, at minimum, a basic civility toward my fellow creatures, but I recognize that there are some who do -- we call them sociopaths.

      Why is being compelled by the FSF any different?

      Same thing holds for the FSF. I don't need to be compelled to see the value in the GPL. It expressed the wishes I have for my code very well. I think I am primarily glad that the GPL exists for these reasons:

      1) I know that my code is legally protected against those would take advantage of me, my work, my code, and my community.
      2) I have a legal recourse if others do attempt to take advantage of the above, and there are powerful, user-made organizations that can protect the community as a whole.
      3) I know that the community will continue to thrive as a result of this security.

    4. Re:Compelled by FSF diff than by church or gov't? by Plombo · · Score: 2

      That's a somewhat FUD'ish response. There are plenty of BSD users who contribute back. I'd say that one advantage is that you don't have a 3rd party (FSF) dictating terms to you, in particular a 3rd party that is on a quasi-religious campaign. I know the FSF claims otherwise, but they are not the free'er license.

      The FSF does not control or even sponsor the Linux kernel. And the Linux kernel is the only component that is replaced in Debian GNU/kFreeBSD. As the name would imply, the FSF-controlled GNU software is still there.

  19. Re:Firefox Updates by TaoPhoenix · · Score: 2

    Wait, is this the reason that when I tried to upgrade Firefox "like normal" on ubuntu I couldn't do it without major new package component upgrades? I'm the arctypical nervous newbie, and I went to go get an update, and got back messages that it wouldn't update without other new pieces.

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  20. Re:Debian6.0 squeeze screenshots Tour by Seumas · · Score: 2

    Wow, in all the years I used Debian, I barely ever used a window manager. To the point that when you sai d"here are some screenshots", I was expecting a page full of screenshots of the command line (which is where I literally spent 99.9% of my twelve years with Debian). Seeing Debian used with a window manager like that almost feels like going to a strip club and seeing your sister come out on the stage!

  21. Re:Firefox Updates by rl117 · · Score: 2

    This is one probable reason. If there's a security problem, then the distributor has the following options:

    - wait until Mozilla releases a new version containing the security fix [but this may contain other, unwanted, changes]
    - backport the security fix, but then get explicit approval from Mozilla before being allowed to make the release [may take too long]
    - backport the security fix immediately, but don't wait for approval from Mozilla [but requires renaming to something other than "Firefox" to be compliant with the trademarks].

    Additionally, Firefox and its related components are so complex and intertwined than it's often simply not possible to backport a security fix. In this situation the only choice is to upgrade everything to the latest version.

    From Debian's point of view, you don't really want to push major new versions into a stable release, and especially for a security update. You want a minimal, targeted, testable fix which fixes a single issue only. That's one of the reasons why Debian chose to rename "Firefox" to "Iceweasel", because otherwise it is simply not permitted to release a security update.

    It's also worth pointing out that distributors such as Debian also make changes to software to better integrate it into their system. "Firefox" would prohibit that as well, which is one reason why it's very much a standalone application that doesn't integrate properly into any desktop environment, and reimplements a whole bunch of the common functionality they provide.

    Regards,
    Roger

  22. The other way around... by Anonymous Coward · · Score: 2, Interesting

    For the past few years I've been working on going the other way around from Debian/BSD. My system has a Linux kernel but a whole lot of BSD binaries (I've replaced GNU coreutils, tar, gzip, findutils, init, etc. with BSD versions).

    Not everything can be replaced, but a lot of the userland works pretty well with BSD versions: some programs stupidly assume GNU tools and need to be patched, but it's been working fine.

    1. Re:The other way around... by godrik · · Score: 3, Interesting

      I actually see two main things coming out of the freebsd kernel on debian.

      1/ having a really good kernel without the stupid port system.
      I know that sounds like a troll. But I really elieve linux is a crappy kernel. It is supposed to be monolithic so everything got thrown in the kernel. And now, we realized it is not going to work, so we start using micro kernel types techniques such as network manager, udev, hal... That's not the way to go with a monolithic kernel.

      On the other hand freebsd has an awful packing system in my opinion. I need to install weird packages all the time and I don't want to spend so much time compiling everything. I think debian really rocks at having a lot of packages that are overall well compiled with appropriate dependencies. I expect a lot out of debian/freebsd

      2/ using a different kernel is likely to activate different code path. That's a great thing for debugging purpose. As parent said, that will help to find GNU dependent code and probably linux dependent assumption. That's a good thing for make our tools more reliable.

      Debian: here is an attaboy from me!

  23. Really excited, then... by CAIMLAS · · Score: 3, Interesting

    I got really excited when I read this at first, but then I realized it's probably going to have many of the same bugs that the FreeBSD kernel has surrounding the various subsystems (jails) and drivers (recent Intel ethernet crashing, USB, etc. that still don't work for the better part of a year), as well as crippling limitations as it regards adaptability on filesystems (ext*, NTFS, NFS - all limiting) and the like.

    i wonder if they managed to get ZFS to work fully with the userland utilities written? That would be the biggest point that might pull me over to give it a go.

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  24. Will this complicate licensing? by walterbyrd · · Score: 2

    In the post scox-scam era, licensing is such a BFD. I have to wonder if there will any complications over conflicts between BSD and GPL licensing.

  25. Re:All by Hognoxious · · Score: 2

    Huh? I'm still waiting for 5.0 to finish compiling!

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  26. Re:Why? by Tacvek · · Score: 2

    I find GNU Make generally superior to legacy Make implementations, especially if I am avoiding the autotools.For example, I can set up completely automated header detection and tracking, not needing "make dep" runs or the equivalent.

    The GNU project's 'less' is my preferred pager, despite the fact that I don't use most of it's advanced features.

    And then generally I prefer to have the GNU userland because mst of the utilities have extended features, that various scripts may be taking advantage of (the whole reason why having a 'gawk' application, or 'gsed' application is still relatively common on BSD systems). If I'm going to install GNU awk as 'gawk', and GNU make as 'gmake' anyway, why not just install them as 'awk' and 'make' and be done with it?

    The documentation for GNU is generally just fine, as long as you reference documentation with 'info' rather than 'man', (info will display the TexInfo manual if present, and falls back on the man page automatically).

    Of course I'd also be very interested to know about what you find incomplete about the GNU userland. (If nothing else it tells me to look for versions of those utilities in my distro. It is surprising hard to find any information trying to directly compare BSD and GNU userlands.

    --
    Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
  27. Re:Some CPU microarchitectures dropped from Debian by lucifuge31337 · · Score: 2

    What are we supposed to do with our old Alphas? Just set them on fire? Not that I have one any more.

    I think that's the point. As much as I like diving into old hardware, at some point I started getting rid of it because of space limitations and the simple fact that it's not feasible, even with new distro support, to do anything of consequence on it that can't be done cheaper (read: electric power) and faster on even the wimpiest of several year old cast off (free or nearly) servers and/or laptops.

    --
    Do not fold, spindle or mutilate.
  28. This is great by Trogre · · Score: 2

    Thank you again, Debian team, for providing the most stable (in the no-unexpected-changes sense of the word) distro I know of.

    One question though:
    Grub 2 as default - for the love of all things good, why?

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  29. Re:Some CPU microarchitectures dropped from Debian by petermgreen · · Score: 2

    If you're going to drop Alpha, why not drop m68k?
    They already did.

    There comes a point where the slow march of software "bloat" gets too much for older hardware and/or there is no longer sufficiant porters to keep the port in what debian considers a releasable state. It's sad but that is the way things go in a project like debian.

    Arm was a special case because they kept support for the majority of arm devices but did so through a new port due to some serious deficiancies in the old arm linux port. It was always planned that offering two different arm ports in the same release was a transitional state that would only last one release.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register