Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Debian 3.0 (Woody) May 1?

Posted by CmdrTaco on Sat Apr 06, 2002 10:04 AM
from the best-gets-better dept.
dex@ruunat noted that this morning, in a message to the debian-devel-announce mailing list, Anthony Towns, Debian's Release Manager, wrote: "I'm becoming increasingly confident in woody's release readiness. So, to go out on a limb: Debian 3.0 (codenamed woody) will release on May 1st, 2002." Congrats to all the debheads putting this thing together. I have a blank CDR waiting ;)
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Yes! (Score:3, Funny)

    by corebreech (469871) on Saturday April 06 2002, @10:13AM (#3295222) Journal
    I'm confident in my woody as well, so much so I'm ready to release it too!
    • Ah but what license is you're woody going to be released under?

      Can you recompile you're woody after its been 'released' ?

      Still confident about releasing you're woody ?

      Hadn't you really better wait till you're girlfriend gets home ?

      After all you're woody might be up against 'stiff' opposition...
  • is that I loathe and detest dselect. It's meant to be the advanced option, but I cannot abide the awful choices for navigation keys, the entirely illogical page layout, and the horrendous switching of views that goes on every time you hit a key or try to select or de-select a package. I've given up even trying to understand it, and just take whatever the hell it wants to install. Afterward I go through with apt-get remove/update/dist-upgrade/install, in that order.

    Don't get me wrong -- this is a minor bitch about an otherwise great distro, and it's very much IMNSHO. I seem to be moving more and more to FreeBSD these days, but whenever I need or want Linux I always pick Debian. It's easy, it's stable, I absolutely love apt-get install/dist-upgrade, and and and...yeah, it's pretty much all great. I think I'll be waiting w/CD-R in hand, too.

    (One other minor complaint, something I found on my box at work: why the hell does suidperl conflict with lynx? I had to install lynx from source, because Debian kept removing it when I installed suidperl for a webmail package I was testing. Anyone?)

    • by macshit (157376) <miles&gnu,org> on Saturday April 06 2002, @11:13AM (#3295410) Homepage
      Check out the aptitude program (you'll have to install the package of the same name) -- it's really good and getting even better fast; the author really seems to be on the ball (it used to be pretty bad, so if you tried it before and dismissed it, try it again). Not only does it provide a great full-screen apt interface, but it also has a command-line mode that improves on apt-get!

      This is the package management interface that debian's been waiting for, IMHO.

      [another alternative is `deity' (ne `console-apt'), but though it's rather colorful, the UI basically sucks; aptitude is much better.]
      • by macshit (157376) <miles&gnu,org> on Saturday April 06 2002, @12:07PM (#3295580) Homepage
        Since I really do think aptitude rocks, I'm going to reply to myself to point out a few of the cool features it has, beyond the nice user interface:
        • It tracks which packages were installed `automatically' (e.g., to satisfy a dependency). If such `auto' packages later become unnecessary because nothing depends on them anymore, they will be uninstalled automatically.
        • It has a powerful and useful search system -- you can search not only for package names, but for descriptions (and other package fields), various special attributes, and boolean combinations of these things. For instance, the search string `(lib)~i!~M!-dev' will find packages who's name matches the string `lib', and are installed, and were not automatically installed (see above), and who's name doesn't match the string `-dev'.
        • These search expressions can be used not only in interactive searches (which, incidentally, are incremental, like Emacs's isearch), but also to limit the set of packages displayed, or to perform various operations in command-line mode. I could use the command `aptitude remove "(lib)~i!~M!-dev"' to remove all packages matching that expression (but I won't, since that it happens to match libc6).
        As you can see, although aptitude is great for the non-expert user, because of the simple and intuitive interface, it's not just for them. Even when I want to install something from the shell, I now always use aptitude's command-line interface instead of apt-get, because of the above features.
  • I did a fresh install of Woody (debian/testing) on one of my machines this morning and it seems the pine and pico sources have disappeared from the packages list. Yes, I do use non-US and non-free packages so that can't be the problem.

    For the rest, it runs quite well, but I still prefer debian/unstable because of the more recent packages.
    • From [debian.org]
      http://packages.debian.org/unstable/editors/nano .h tml
      "GNU nano is a free replacement for Pico, the default Pine editor. Pine is copyrighted under a slightly restrictive license, that makes it unsuitable for Debian's main section. GNU nano is an effort to provide a Pico-like editor, but also includes some features that were missing in the original, such as 'search and replace', 'goto line' or internationalization support. As it's written from scratch, it's smaller and faster.
      "
    • try this package: http://packages.debian.org/testing/admin/pine-trac ker.html
    • The pine source is in ... a source package! That's right, the source is in the (non-free) archive, just no binary packages. Unfortunately, this means you can't install it in the standard way (yet), but you shouldn't have much trouble with

      apt-get build-dep pine
      apt-get source --compile pine
      dpkg --install *.deb

      There's also a pine-tracker package, which apparently reminds you to upgrade when appropriate. I hope the standard tools make this unnecessary some day.

      • I see no purpose of duplicating the source in a so-called "deb" file, when all users of every Unix including Mac OS X can get the Pine source in it's raw, unaldultered form from the official site

        Let's say you want the sources for six different packages. Let's also say you want to keep them current.

        With Debian source packages, you use "apt-get" or some other tool to subscribe to those packages, and then every time you update your system, you get the latest versions of those packages. (The latest versions in Debian, of course.) I update my system at least once per week; would you prefer to run an updating tool once per week, or would you prefer to visit six different FTP servers once per week?

        And the source packages always reflect the source used to build the matching binary packages. If there were no source packages, and you wanted to build a package yourself, you would need to seek out the exact version on your system. Maybe you just want the newest version, so it may be no problem, but what if you have a computer running an older version and you just want that source version?

        Debian's "stable" version has stable packages. If the "raw, unadulterated version from the official site" has a bug introduced in a new version, you will get that bug if you get the new version; with Debian, you won't get that bug in the "stable" version of the system because people will check it out and will not include it. (If you really want it, you can pull it in from the "unstable" version of Debian. So there is no down side.)

        steveha
  • by m0i (192134) on Saturday April 06 2002, @10:55AM (#3295359) Homepage
    Not planned:
    -KDE 3.0
    -Apache 2.0
    -XFree 4.2

    Not good, eh?
    • by Daniel Stone (535956) on Saturday April 06 2002, @11:01AM (#3295380)
      Why the *hell* is this not good?

      KDE3 is not yet tested enough for a Debian stable release, trust me. Neither are the debs, packaging issues can play a significant part in some problems. I'm personally waiting for 3.0.1 or 3.0.2 before I start deploying it throughout work, although I tracked KDE3 CVS for some time at home (I can deal with segfaults, and it makes it easier to package if you only have to make slight changes every time, instead of being hit with one big lot in the tarballs).

      apache2 is NOT NOT NOT ready for prime time. I would not deploy this in a Debian stable release; luckily, neither would Thom. When I maintained it, I always said it would wait until after woody, and luckily it will. The GA was only announced today, and so Thom would have to upload it as NEW, which means it wouldn't make it into woody, even if it could. Even offering it side-by-side with Apache 1.3.x in a stable series is irresponsible.

      As for XFree86 4.2, Branden's been too busy with fixing up 4.1.x to do 4.2.x well. XFree86 is one of those dead core packages that need to just WORK every single time, and cannot screw up. There was never enough time to give it the thrashing it needs; I think that having XF4.1.x in a stable series is a pretty sweet effort; Branden deserves a pat on the back. He has a reputation for quality, well-tested packages, and I somehow doubt he'd shatter that this close to a release. Plus, we'd all rip his arms off and beat him to death with the limp end if he did.

      Thanks for listing the good points of Woody.
      • by Overfiend (35917) on Saturday April 06 2002, @09:46PM (#3297389) Homepage

        As for XFree86 4.2, Branden's been too busy with fixing up 4.1.x to do 4.2.x well. XFree86 is one of those dead core packages that need to just WORK every single time, and cannot screw up. There was never enough time to give it the thrashing it needs; I think that having XF4.1.x in a stable series is a pretty sweet effort; Branden deserves a pat on the back.

        Well, I myself am not exactly thrilled that woody won't have 4.2 in it, but:

        • As you said, I've been busy with getting 4.1.x stable. For Debian, this means much more than it does for some vendors. In woody, we support 11 architectures: alpha, arm, hppa, ia64, i386, m68k, mips, mipsel, powerpc, s390, and sparc. For how many of these machine architectures do Slackware, Mandrake, or Red Hat have 4.1.x, let alone 4.2, available? XFree86 themselves don't test or prepare distribution tarballs for several of these architectures. Debian is the de facto portability laboratory for XFree86 on Linux. Sure, I'll grant you that a lot of people, the kinds with the overclocked Pentium 4's and the latest GeForce card, really don't care about portability, or supporting architectures they've never heard of. But portability is important to me and it's important to Debian. I refuse to treat non-i386 users like second-class citizens. Those who want CVS HEAD, are best advised to learn how to check it out and type "make World". I'm sure that Pentium 4 overlocked to 3 GHz will compile the X source tree pretty quickly. :-) The single most amazing thing about all the hate mail I've received for not having 4.2 Debian packages ready -- aside from the fact that I started receiving it about two days after it was tagged upstream -- is that people seem to be laboring under the delusion that I have some kind of secret tools locked away in a vault, and that I am the only person who has the power to create packages. Sure, I'm probably better at doing XFree86 debs than most people, since I've been doing it for so long, but there's no great secret. I'm sure that with half an hour of manpage reading, a reasonably intelligent person can learn everything he needs to produce XFree86 4.2 debs for himself that will work well enough to satisfy his impatient self. Hey, I like to see the latest and greatest of everything, too -- that's why I use apt-listchanges, but I don't go haranguing the Debian developers to package up a new upstream version when I can clearly tell that they're working on other things for the project.
        • On a related note, 4.2 just plain won't work on some of Debian's supported machines because we need the PCI Domain support, which is currently a branch in XFree86 CVS and did not make it into the 4.2 release. So for us, releasing 4.2 doesn't just mean releasing 4.2. It means releasing 4.2 plus some very large patches in very critical parts of the server code. You really, really want a good long opportunity to shake that sort of thing out, since Debian's 4.2 may not behave exactly as XFree86's 4.2 does.
        • I don't just package the thing tagged xf-4_2_0 and leave it at that. I track hotfixes commited both to the latest release's branch and to HEAD, and incorporate them into Debian's packages if they work and if they make the packages better from a quality standpoint. Ask ATI video card users about 4.2.0 and "composite sync" sometime. (This isn't to dog the XFree86 Project. Software has bugs. Software releases with bugs. But, knowing about the default composite sync issue which affects so many users, it would be irresponsible of me to ignore it.)
        • I didn't expect it to take until May for woody to release. Back in January, I felt sure that there was no way Anthony Towns would accept 4.2 into woody; when I sounded him out at the time about it he sounded kind of skeptical. Needless to say, the longer it takes woody to release, the worse a decision this is, but I don't have control over the release process. (Strictly speaking, Anthony doesn't either -- meaning, he can declare a release, sure, but he can't force people at gunpoint to fix the remaining release critical bugs. And Debian's philosophy has been to release when "it's ready", not when some marketroid tells us to, and thus just live with whatever whopper bugs happen to be in the release that day.)

        So, that's why XFree86 4.2 isn't in woody.

        • Debian does changes to the code, applies patches to make it work (including bugfixes/security patches that are sent upstream but not yet included in that release), and ensures that everything follows the Debian packaging guidelines. Debian code is sometimes vastly different from regular code, and it needs to be tested. In the case of XFree, with the most complicated build system and source tree I've seen since... well, ever, fortunately, it takes a long time to make sure everything works.

          Slackware, on the other hand, compiles XFree, tars it up, and puts it on the CD. It does not have to be maintained, patched, updated, or tested. This is ok, if that's what you want, but Debian does a lot of work and a lot of changes, and it can require a lot of testing.

          This is why Debian is widely regarded as a quality distro. No releasing alpha software in stable releases, no jumping version numbers to look competetive, just code, quality code, quality distro. Slackware lets you worry about that on your own.

          --Dan
  • Last time I installed Woody, about 2 months ago, the kernel was still at 2.2.20. Have they finally gone 2.4.x yet?

    (I've sinced moved on to Unstable and use my own kernel)
  • by ttfkam (37064) on Saturday April 06 2002, @12:30PM (#3295654) Homepage Journal
    Yes, I have heard that there are bf- prefixed images that have the 2.4 kernel and ReiserFS/ext3 support.

    I have been patient with Debian. I have been persistent with Debian. I come bearing the news to Debian webmasters everywhere that the "bf-something Woody install" is not obvious. Not only in name obscurity when a Debian newbie would only know to look for 2.2 or 3.0 disc images, but also in placement on the website.

    I have gone searching in vain for this bf-something install. I have looked in all of the obvious places on the website under such topics as "Getting Debian," "Debian on CD," and ""Download with FTP." This is bullshit. If this is everyone's definition of publically available, I must have missed that day of class. I even download some of those potentially nifty netinstall CD images in the hopes that they simply weren't labelled correctly with the magical bf- prefix.

    Believe me, I have gone through a lot more effort than most casual visitors to the Debian site would have gone through. Unfortunately this is one area that Debian could learn from RedHat, Mandrake, SuSe, et al in that the others provide an iso image, you download it, you burn it, and off you go. If the newer install with the updated kernel works so well, why hasn't the old installer been mothballed? Why would the old installer be offered? If the new installer has problems that preclude its replacement of the old installer, then the appropriate answer to my previous post would have been "they're working on it and it should be ready when 3.0 is released."

    Is it a work in progress? Sure! I acknowledge that. I am used to that. I have no illusions that any Linux distribution is without its rough edges. But how much effort is it really to have in the download area, clearer instructions for creating a up-to-date install disc? All I see is the same old crap that makes me jump through hoops and auto-detects nothing (another gripe that I will forget for now simply because I know my hardware well enought to answer the endless series of questions) while making use of journalled filesystems far from the simple case it should be.

    By all means, prove me wrong. By all means, show me an obvious link that demonstrates me to be a dullard who cannot read a web page. I am not above humility. Otherwise I will assume that a clean and complete Debian install is bullshit, must first be excavated by a Debian veteran who knows how to find it, and/or is of no use to the general public. Debian may be a great distribution, but that's pointless if most people can't install easily without sacrificing popular features (like journalled filesystems) or hunting through mailing list archives without really knowing for what they search.
    • You obviously haven't looked in the directory which contains the woody install disk images, because it's plain as day. The instructions for finding this and a description of what it's about are in the "Installing Debian/GNU Linux 3.0 (woody) for i386" guide that IS linked to from the woody webpages, which are linked from an obvious place on www.debian.org. Here is the direct URL since you're so dumb: http://www.debian.org/releases/woody/i386/install. en.txt [debian.org]

      Here is the url to take you directly to the bootable 2.4 disk images.
      http://http.us.debian.org/dists/woody/main/disks-i 386/current/bf2.4/ [debian.org]

      ISO images for woody aren't provided yet since the package list is currently changing; however, the instructions on the debian CD site and the scripts there will make you an ISO of this unrelased software easily. If that's not enough for you you can try some premade images from a source like http://www.linuxiso.org/debian.html [linuxiso.org] Hell, there's even DVD images floating around. You can buy a preburned one here: http://www.linux-cd.com/store/cgi/store.cgi?client =14491123&action=serve&item=woody.html [linux-cd.com]

      Premade ISO's won't be available for woody until it is released. "Official" ISO's are available for previous relases from the official site at http://www.debian.org/CD/ [debian.org]. Minimal images designed to replace a set of boot floppies, "netinst" cd's, are also linked to from that site at http://www.debian.org/CD/netinst/ [debian.org]

      I find it ironic that you seem to be capable of writing a novella about how inept you are at reading. You seem to know exactly what you want, but since www.debian.org doesn't show it to you in big bold letters on the front of the page, why you didn't click on the search button is entirely beyond my comprehension.

      I will give to one of your points: that the default installer can be improved. For the woody release, it was decided "if it ain't broke don't fix it." The next release will contain a better one. If you really can't wait, make a woody netinst cd with the Progeny installer. Or can you not type "apt-get install pgi" successfully? Someone will probably make one of these available with the progeny installer after woody's release.

      Think you can put together a better debian website? Why don't you sign up [debian.org]?
      • Thank you for the info but once again I must point out that none of this information is apparent from the main web page (or its primary links). If individuals (like myself) are looking into a distribution's feature set, they will not see journalled filesystems as an option; They will see it as an option for Linux, but not Debian. What's the difference? With RedHat, for example, you can set up a kickstart disc to handle bulk, unattended installs of RedHat Linux (since v5 or something like that). Journalled filesystems are available by default in the RedHat installer and therefore are available to kickstart.

        Now let's look at Debian: install must be manually performed for each workstation/server and an extra setup tax is imposed to get it working with a journalled filesystem (to beat a dead horse). Therefore Debian doesn't support journalled filesystems. Linux supports them and Debian tags along for the ride.

        With regard to Ext3 being "safer." How do you figure? Have you come across more failures (catastrophic or otherwise) with ReiserFS or XFS vs. ext3? Is it safer because you can revert back to ext2? I have not seen the former and don't consider the latter to be an advantage or inherently safer. FWIW I used XFS for months on several boxes both at home and at work and never had any problems. Why did I even try XFS? Because it was easy to setup with SGI's custom installer for RedHat.

        And as the AnonCoward mentioned, what does recompiling a kernel have to do with the quality of install programs or a person's choice of distribution? For the record, I can and have patched and recompiled my kernel. I can also program in C, C++, Perl, Java, and a few others. I am well versed in multi-threaded and multi-process programming as well as distributed programming. What are your credentials?

        Now that the big-dick thing is out of the way, I feel it necessary to point out that Debian's big advantage over RedHat (aside from being completely volunteer-driven) is maintenance after install while RedHat is historically easier to install. Recently with utilities such as up2date and red-carpet, RedHat has become much easier to maintain. So what is Debian offering me other than a warm, fuzzy feeling? People in general don't start or stop using a particular distribution (or Linux or BSD) because of a warm, fuzzy feeling.

        RedHat (and others) are finally catching up with maintenance. If this "if you can't recompile a kernel" crap continues to be spewed from the Debian community, you may find that it gets ignored not because of technical inferiority but because most people don't care about comparitive excellence as long as the job gets done. An easy install program is the first step in making sure you keep people's attention long enough to demonstrate technical excellence.
  • May Day (Score:3, Funny)

    by Anonymous Coward on Saturday April 06 2002, @12:50PM (#3295723)
    A fitting release date, since everyone knows all Debian users are commies.
    • by rusty0101 (565565) on Saturday April 06 2002, @10:19AM (#3295239) Homepage Journal
      Like anyone else does so?
      Mandrake 8.2, RedHat 7.2, ...

      Release numbers for packaging distributions are, and should be numbered by the people maintaining the distribution, to reflect their own perception of whether the release is a major, or minor improvement over the previous release.

      For Linus and co, the enhancements to the kernel that moved it from 2.2 to 2.4, were minor changes, things like adding USB support, do not warrent a major version number. If the scheduler or virtual memory manager gets a major improvement, that would probably warrent a version 3.0, or so.

      With Debian, the kernel is not the only thing that gets improved by moving from potato to woody. Updates to the user interfaces; Gnome and KDE; many packages, OpenOffice, ssh, and others; as well as the improvements to the kernel, moving from 2.2 to 2.4; suggest that this will be a Major improvement to the Debian Distribution.

      Then again, they may be looking at other distribution version numbers and thinking that the public will percieve Debian 2.4 to be less "market" friendly than Debian 3.0.

      After all, I wasn't in on the decision to version the software, and these are only my opinions. I could be wrong.

      -Rusty
      • If the scheduler or virtual memory manager gets a major improvement, that would probably warrent a version 3.0, or so.

        Which is why they changed the VM in the middle of the 2.4 series :)

      • Updates to the user interfaces; Gnome and KDE; many packages, OpenOffice, ssh, and others; OpenOffice isn't in Debian (yet).
        • The version numbering is on the distribution package, not the OS. Linux users generally recognize that the Kernel is the OS, not the collection of packages that sit on top of the kernel, or even the collection of modules that get plugged into the kernel.

          A distribution such as Debian, Redhat, Mandrake, SUSE, Slackware, or any of the dozens or even hundreds of others in existence are a combination of one or more kernels, with a collection of software that sits on top of the kernel to make a potentially useful collection of software for users or server administrators.

          What that collection consists of will depend upon the maintainer of that package.

          The User Interface may be anything from terminal interfaces such as supporting vt100's attached to serial ports, through complete desktop interfaces consisting of Gnome, KDE, BlackBox, WindowMaker, or other Window Managers riding on X, or any other Windowing system that the package maintainer chooses to use.

          There are efforts to port the BeOS ApplicationServer interface to run on the Linux 2.4 kernel. The collection of software that runs under such a port would generally be different from that which will run on a Mandrake distribution using X11r4.x, with a KDE or Gnome window manager.

          Likewise if someone really likes the BeOS interface that has been ported to Linux, but does not like the Linux 2.4 kernel for some reason, they are welcome to port it to a BSD, or Hurd varient kernel, or whatever kernel they choose to use.

          Just because the latest version of some software may be available from some official web site does not mean that that version will play well with the collection of software you already have on your system. A package is a collection that the people distributing that package included it in the distribution was found to work at a satisfactory level with the other software included in the distribution.

          These decisions are far from perfect, and users are generally considered welcome to roll their own distribution by building a boot/root disk and downloading and compiling from source, the software that is available from the official web sites.

          Another reason that people chose to use packages is that the developer can indicate in the package what software is required to make this software work, as well as providing recomendations as to what software and documentation might be handy to have around when installing, setting up, and using the software in the package.

          If an individual was required to review the offical web site for every package to verify that they had all the required or recomended software, it is unlikely that more than a handful of people would have a system running at all.

          On top of this as the "latest version" that is not in a package is generally considered to be bleeding edge software, is is probable that the system would be continuously in a very unstable state.

          Then again, if you choose to build and run your system with the latest version of everything, that's your choice and I happen to think that you deserve the respect you will get for a stable system, or the lack of respect you might get from an unstable system.

          That's my opinion, I could be wrong.

          -Rusty
        • What the heck do user interfaces and packages have to do with an operating system? Why would any developer include packages when latest versions can be downloaded from the official web sites? Linux people, I'll never understand them.

          Point for point:
          In the case of the Debian Operating System, they are more significant than the fallacious significance of a kernel to the entirety of an OS. Some reasons include the desire for permanence and local reproducability of an instance of an OS enviroment, as well as potential scarcity of Web connectivity. The final statement is not a question. If you are referring to AI, then I am amazed that there are "Linux people" that are beyond the comprehension of the average HomoSapiens Technophilia. If you express puzzlement over the preferences exhibited by Linux-based OS bigots, then perhaps I can help point you in a direction to enligtenment. If youd rather remain Linux segregated, then go in peace; we are done here.

          The confusion over the importance of UIs to OSes in my experience indicate an affinitty for Unix. Perhaps it would be a better world if an OS were naught but embedded daemons. There was a revolution, for better or worse, in which the "Personal Computer" lead the forefront, resulting in the sanctity of computer becoming debased. Now computing is a public phenomenon, and has at the very least benefitted from economies of scale. Your elitism against common "lusers" seems naive.

          As for "packages", I can only assume that that you are a BSD fan. You already implied that you don't use a package independant Linux distribution, and I infer from your championing Web downloads that you aren't likely a commercial Unix weenie. Commercial Unices do tend to be use packaging systems in my experience. If I am correct in considering you a BSD fan, then statstically I can consider you a FreeBSD user.

          Why exactly do you find Linux people inferior? Unless you are among the minority of kernel hackers, you likely find the userland inferior. UIs differences between BSD and Linux based "Unices" being as trivial as the are, the only deficiency apparent from your message is that of many packaging systems associated with Linux. In that case, May I suggest that you give Rock Linux [rocklinux.org] which doesn't use packages, but rather compiles binaries from officail sources, much like FreeBSD ports. It isn't makefile based, but maybe spending time with it will enlighten you, or at least elucidate your perceptions of Linux's apparent shortcomings. Note that FreeBSD also offers packages, so your criticism isn't very valid as it stands. Perhaps you have more fruitful criticisms to offer. Most likely, IHBT, IHL, HAND.

          In any case, Debian news items should contain a disclaimer that Debian is not Linux! Debian is a very modular and comprehensive system that offers Linux, just like it offers GNOME and Emacs. Debian needs GNU, but it doesn't need Linux, and there are plenty of Debian users that aren't "Linux people". Debian can just as easily look like VIM running over the Hird. I look forward to a stable Debian/NetBSD running on SGI MIPS R5K hardware, hopefully decades before Debian "Soldier" release 4.0.

          -castlan
    • by castlan (255560) on Saturday April 06 2002, @10:47AM (#3295330)
      Which kernel would that be? A BSD kernel perhaps? OpenBSD is at 3.0 last I checked, so that works out, unless you believe that Debian/NetBSD is more realistic.

      Facetious, perhaps, but you fail to acknowlegde that Debian is a "kernel independant Operating System" that is popularly based on Linux. There is nothing stopping debian users from chosing KDE if that is their preferred desktop environment, just as there is nothing stopping x86 users from choosing The Hurd if their hardware supports it.

      Debian has a larger scope then you seem to realize. Distinction from the Linux kernel is the best reason I can see for supporting a Major release increment to 3.0, as otherwise I would much prefer a more conservative path better utilizing the range of our decimal counting system under the auspices of 2.x.

      While I hope my post has contained a modicum of sensibility, I fear that this is not the case.
    • I guess for most users, it would make more sense to name the distribution after which version of Gnome or KDE that is bundled.

      From a technical point of view, the most important single package is probably glibc, as that is what most other packages talk to.

      If they should name it for my convenience, they should call it Debian 21. It will be the first stable Debian featuring Emacs 21, which is my primary interface to the system.
    • Hehe, I can't see any reason for that. But since there are going to be lots of big releases that are not going into woody, (KDE3.0, Apache2.0 (allready out), Openoffice 1.0, Mozilla 1.0, GNOME 2.0, to name a few), it strikes me as odd that they didn't call this 2.3. Besides, what happened to Linux 2.4, they still think that it isn't mature enough to be installed as default...?

      One argument is of course that the size of the distro has about doubled since 2.2, but I'm kind of curious about the version numbering nevertheless.

      That being said, Debian is my favorite distro, and woody's going into my machine regardless of version numbers.

    • Re:Blank CD-R? (Score:5, Informative)

      by Malc (1751) on Saturday April 06 2002, @10:23AM (#3295247)
      Yes: 1 blank CD-R to boot from.

      Why bother downloading 8 images when most of the stuff isn't going to be used? Well, I speak for myself there... I need a portion of the distro. Use 1 disk to boot from, and then apt-get what I need. Which reminds, I need to clean out some 530MB from /var/cache/apt/archives of packages that I've apt-getted in the past.
      • if you have a fast connection. if not you might want to build a local repository. this would take much more than one cdr. apt-getting 600 megs of stuff over a modem is not a happy thing.

        on a side note. many people say with respect to debian: just apt-get blah and it will install it. they never say apt-get blah and if it fails try apt-get -f. if that fails try touching the file it's looking for, etc. point: apt-get doesnt work 100% of the time-especially when you're not using potato. when it fails, a new user will find it confusing and might be turned off by all the posts where people say: oh well that always works fine for me.

        this is not a troll, but a serious comment. apt is a great thing, and when it works correctly it is wonderful. this is also not ment to slight the debian developers. they work hard to make sure all the packages work together and all of the dependancies are met.
      • Re:Blank CD-R? (Score:3, Informative)

        Heck, there are also netinst cd's availabe. These are CD's that have only enough stuff to get the disk partitioned, the base os, and network drivers installed. The rest you get from apt-get. The netinst cd's are usually less than 50MB to download, compared to 650MB for a full cd iso image.

        The first netinst cd for debian that I ever saw was here [debian.org]. Now, we also have this one [debian.org] and this one [sourceforge.net].

    • Use a Netinst Image! (Score:4, Informative)

      by WD (96061) on Saturday April 06 2002, @10:52AM (#3295344)
      Please, just try a netinst [debian.org] image.
      It's about 30MB, and only retrieves the necessary packages off of the internet / other sources.
    • Funny.. in 5 years of Linux use, I have yet to see a kernel segfault.

      Oh, and you missed a step :

      3.5 - Go to local PC shop, and buy a copy of Windows XP Professional for the princely sum of $296.99 (not the upgrade).

      Alternatively you could spend the same money on Blank CD-R's (going by Amazons prices, I estimate you could get about 740) and burn many many copies of Linux for you and your friends :)

      If you were REALLY against free software, you could even sell them at $1/CD and you would make a tidy profit.
    • by Anonymous Coward
      Does this "Windows XP" you speak of work on my Pentium 66mhz machine? Because I use that as my IP Masquerading firewall and FTP/SSH server and I think it needs an upgrade. It has 250mb of HDD space and 32mb of RAM, will Windows XP suffice? Does it do IP Masquerading properly?

      Oh and also, will it run on my two Apple machines? I might look into it.
      • What a waste of a perfectly good CD! I would prefer to precisely scratch the reflective media off using a microscope and write a script to read the bad sectors. Then you could store DeCSS or even the Linux kernel superimposed on an XP CD. Who says trash CDs are useless?
        • LOL.... I like your spirit!!! Now the question is, what to do with Anonymous Coward's PC after he trashes it by installing XP on it. I was thinking in the line of a good hammer or possibly a cup of graphite dust sucked in by the input fan.
    • KDE 2.2.2 , 3.0 prolly wont make into unstable until 2.2.2 has passed to testing. Its the same situation with Xf86 4.2.0, untill 4.1 makes it into testing, then there is no 4.2.0 for unstable.
    • Re:vs Mandrake ? (Score:4, Insightful)

      by njdj (458173) on Saturday April 06 2002, @10:45AM (#3295323)
      Debian includes more applications. And it's cheaper (even if you buy the CDs). It tends to be lag behind other distros when new stuff comes out (for example the current Debian stable distro, 'potato', is still using the 2.2 kernel - Woody will be the first Debian stable release based on 2.4). Part of the reason is that a Debian release is tested on 11 different architectures including Sun Sparc, 68000, alpha, etc whereas Mandrake is available only for 4 architectures (and most distros are just for Intel). OTOH this extra testing uncovers bugs that other distros just ship; Debian is widely believed to be the most stable and most nearly bug-free of all distros. Mandrake's main distinguishing feature is its GUI. It's supposed to be the easiest distro to learn and use. Debian is at the opposite end of the GNU/Linux spectrum in this regard, you need to be comfortable with the command line to like Debian.
    • Debian is different in that:

      • It is supported by Volunteers and therefore holds no Capitalistic motives (I do not mean to sound like a Marxist) in their software development cycles.
      • They are extremely conservative in the quality of their distribution. Generally, they have fewer bugs than the rest. This also means that they avoid the bleeding edge technology until there is a little less bleading to do.
      • They have a lot of packages. Possibly more.
      • They run on more Hardware Platforms than Mandrake.
      • apt-get is superior to RPM in conflict management and versioning control.

      I started with RedHat and Mandrake back four years ago. Went to Slackware so I could get things configured the way I wanted them. And ended up at Debian because it was the best of both worlds.

      Generally, if Debian-Stable is too slow for you, run Testing or Unstable. That will get you the very best of the bleeding edge software, along with all the bloodshed that goes along with it.

      I have been running with Testing for about a year plus. Last month I was really disgusted with Debian. After looking at the other Distros out there. Debian still rocks!!!

      • Not only does some moderator need a flogging, but this post should be distilled into a Slashdot Advocacy summary that all Debian Related Slashdot News items automatically link to. This would really make the comments for Debian items much less trifling.

        I'd remove all of the political/economic theory references in the first point, and maybe just illustrate how Debian quality isn't compromised by profit-motive based considerations, or externally imposed deadlines.

        Also worth mentioning is that Debian is not Linux, unless you want it to use Linux. If it can be phrased lucidly and marketably, a bullet might be spared for the "Open Organization" of the Debian Project, with it's clear policy and democratic operation which gave rise to "Open Source" as we know it today. That last bit might not be worth mentioning, as this document would ideally be less propeganda than a premptive strike against ad Nauseam misguided advocacy and "Linux" postings in Debian topics.

        If such a document were to be made, would there be any way to float it by the Slashdot powers that be? If I weren't wasting my time, I'd gladly write it, and submit it to Debian Proper for approval. Is there any red tape trail that might end with an automatic footnote/link to Debian related items on Slashdot?
    • Re:vs Mandrake ? (Score:4, Informative)

      by Glanz (306204) on Saturday April 06 2002, @11:19AM (#3295424)
      They are both excellent. It's like comparing apples and hamburgers. I have both on the drive (no win$low os in sight)... Mandrake can be made to install .debs and Debian can handle rpms, so I have the best ot both worlds. The APT labyrinth in debian is not easy to learn. You hit the wrong button and you're in for a 500MB download. I have used Debian since the very beginning of debian. Mandrake, however, is the only rpm based distro I like, the community is strong, and they are truly open. The PreZ of Mandrake, LeMarois, is a fine person, and devoted to Open Source.
      The ideal is to have both Debian and Mandrake. That way you can take your time learning Debian.
    • Debian is very "UNIX'y" in that IMHO it more resembles real System-V in it's look and feel, boot behavior, and compiler functionality. I really like it myself. I have messed with RedHat a bit and really don't care for it at all compared to Debian. I think Mandrake is more Debian-Like, and may be superior in its ease-of-setup for a total newbie, but once you start running on weird non x86 platforms Debian really shines because for all intents and purposes it appears to be and acts just like the x86 versions.
    • Go Here [slackware.com] and read Q0.

      I hardly consider a version jump to be a "dark spot." Version number schemes have absolutely DICK to do with the quality of the distro. I'm still a happy Slackware user, and I don't see that changing any time soon.
    • by Anonymous Coward
      Gnome 2.0 - Just got released. Doesn't belong in a stable distro. It needs testing first.
      KDE 3.0 - See above.
      Mozilla 1.0 - See above.
      Apache 2.0 - See above.
      XFree86 4.2 - See above.
      Linux 2.4 - It's in woody. If you want it, just run testing instead of stable. It'll be in stable on May 1, according to the above article. Or did you read it?

      If you really want the above software, get it from sid/unstable. And don't bitch if it breaks.
    • I was running XFree 4.0 on Potato with a 2.4 kernel a long time ago. Just compile the stuff and stick it in /usr/local. You don't have to use just Debian packages. Its compiler setup is great and it is trivial to compile most tarballs.
    • Right now, the non-x86 developers are furiously trying to compile/patch a few pesky yet important packages on whatever platform they work with. I have been using 3.0 "testing" for over six months, and have Linux and Hurd working on X86, and Linux on a HP 9000 715/80 PA-RISC box, and a StrongARM SA110 Netwinder machine. In each case it works great! "Unstable" is a misnomer in that the OS itself is not unstable (doesn't crash), what is unstable is that the packages are constantly being updated so an apt-get upgrade might list 1000 new updated packages every week! With something like 9500 packages in Woody there is a lot going on all the time.