Slashdot Mirror


Debian 3.0 (Woody) May 1?

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 ;)

97 of 327 comments (clear)

  1. Yes! by corebreech · · Score: 3, Funny

    I'm confident in my woody as well, so much so I'm ready to release it too!

    1. Re:Yes! by cheekymonkey_68 · · Score: 2, Funny

      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...

    2. Re:Yes! by Shiny+Metal+S. · · Score: 2

      I'm confident in my woody as well, so much so I'm ready to release it too!

      See what one AC replied to my comment in the past discussion, very good one.

      --

      ~shiny
      WILL HACK FOR $$$

  2. Re:Version numbering? by rusty0101 · · Score: 5, Insightful

    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

    --
    You never know...
  3. Re:Blank CD-R? by Malc · · Score: 5, Informative

    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.

  4. The only complaint I have about Debian by Saint+Aardvark · · Score: 2, Interesting
    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?)

    1. Re:The only complaint I have about Debian by macshit · · Score: 5, Informative

      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.]

      --
      We live, as we dream -- alone....
    2. Re:The only complaint I have about Debian by macshit · · Score: 5, Informative
      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.
      --
      We live, as we dream -- alone....
    3. Re:The only complaint I have about Debian by Electrum · · Score: 2

      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.

      Is this a feature of aptitude, or of the package database? If I install aptitude today, will it tell me which packages were automatically installed using apt-get?
    4. Re:The only complaint I have about Debian by zmooc · · Score: 2
      Dont use it then.

      Although I think you're right, shouldn't this be considered a rather horrible way of working? It should be rather easy to create a dselect-alike program which is a lot more intuitive. This don't-use-it-then attitude is keeping a lot of people from using Debian (and a lot of other distrios for that matter) for the simple reason somebody didn't think about the user interface very well. It even keeps away a lot of us slashdotters; every time there's an article posted about Debian, there are multiple people complaining about dselect. I think this is the overall problem with Linux-adoption; a lot of developers don't think about good and consistent UI's or decide to `build the UI later'. In general I think developers are doing a real good job, but it's those few programs that are `hard' to work with which keep a lot of users away...

      --
      0x or or snor perron?!
    5. Re:The only complaint I have about Debian by redcliffe · · Score: 2

      I dunno, I installed using dselect on Debian about 4 years ago when i was 14.... I didn't find it a problem. Mind you I only had 16 packages because I downloaded it on a 28.8

    6. Re:The only complaint I have about Debian by macshit · · Score: 2

      Unfortunately it's a feature of aptitude, not the underlying apt libraries -- so if you use apt-get to install something, you may end up with automatically installed stuff that isn't marked as such.

      Also, as you guessed, when you first start out using aptitude, all of your previously installed packages will be considered `intentionally installed'.

      However, one result of aptitude's cool search system is that it's not too unpleasant to go through and retroactively mark those things which should be marked `auto' -- the example search string I gave in my previous post actually is one I used while doing that:

      aptitude markauto "(lib)~i!~M!-dev"

      of course in practice I used slightly more hairy search strings, and had to tweak the results, but it was surprisingly painless -- and to tell the truth, rather fun. However newbies had better use aptitude from the start, since they might not be so amused by this kind of thing... :-)

      Hopefully this functionality will be moved into the apt libraries in a future release.

      --
      We live, as we dream -- alone....
  5. Re:I have the way out! by Chicane-UK · · Score: 2, Informative

    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.

    --
    "Hey! Unless this is a nude love-in, get the hell off my property!!"
  6. Does anybody know what happened to the pine src? by _Ash_ · · Score: 2, Interesting

    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.

  7. Re:I have the way out! by Anonymous Coward · · Score: 2, Funny

    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.

  8. Re:Kde by evilned · · Score: 2

    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.

    --

    "My head hurts, My feet stink, and I dont love Jesus." -Jimmy Buffett

  9. apt-get is nice... by gimpboy · · Score: 3, Insightful

    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.

    --
    -- john
    1. Re:apt-get is nice... by gimpboy · · Score: 2

      actually, this was the case about 5 months ago. i have worked with rpm based systems for quite a while. one of the cool things about apt is it was designed to be independent of the package system. in fact i've been using apt4rpm to manage redhat systems for quite a while. consequently the same issues occure on both debian and redhat.

      i still use it because the convenience outweighs the negatives, but the issues i mentioned above are commonly ignored when expounding the praises of debian.

      --
      -- john
    2. Re:apt-get is nice... by psamuels · · Score: 2, Interesting
      i have worked with rpm based systems for quite a while. one of the cool things about apt is it was designed to be independent of the package system. in fact i've been using apt4rpm to manage redhat systems for quite a while. consequently the same issues occure on both debian and redhat.

      No, the same issues can potentially occur on both debian and redhat.

      Whether they do or not depends on the quality of the packaging job. It has very little to do with apt, dpkg, or rpm. The beauty of the Debian package archive is much much deeper than the fact that it is compatible with apt. The fact is that the Debian package collection is much better maintained than the equivalent RPM packages from a lot of sources, thanks largely to the Debian policy manual, and the fact that policy violations are considered serious bugs and usually fixed pretty fast.

      A lot of people seem to think apt-get is a magic bullet. It's not. It's a very nice interface to a package archive which was already a work of art.

      --
      "How can you claim that you are anti-crack, while still writing a window manager?" — Metacity README
  10. Re:Blank CD-R? by mjh · · 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. Now, we also have this one and this one.

    --
    Key to financial independence: Spend less than you earn. Save and invest the difference. Do it for a long time.
  11. Re:vs Mandrake ? by njdj · · Score: 4, Insightful

    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.

  12. Kernel :Version numbering? by castlan · · Score: 5, Insightful

    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.

  13. Use a Netinst Image! by WD · · Score: 4, Informative

    Please, just try a netinst image.
    It's about 30MB, and only retrieves the necessary packages off of the internet / other sources.

  14. Re:Hurry! by Daniel+Stone · · Score: 2, Informative

    Thom has the debs available, along with vhost-base, at pandora.d.o, and they're stable, and good, and stuff, but they will NOT go into woody.

  15. What you won't get in woody... by m0i · · Score: 3, Informative

    Not planned:
    -KDE 3.0
    -Apache 2.0
    -XFree 4.2

    Not good, eh?

    --
    have you been defaced today?
    1. Re:What you won't get in woody... by Daniel+Stone · · Score: 5, Informative

      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.

    2. Re:What you won't get in woody... by Inoshiro · · Score: 2

      "I think that having XF4.1.x in a stable series is a pretty sweet effort"

      Slackware's had it in 8.0 since 8.0 was release, way back on the 20th of June, 2001.

      --
      --
      Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    3. Re:What you won't get in woody... by Overfiend · · Score: 5, Informative

      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.

      --
      Address-collecting spam robots don't know how to crack ROT13. Do you?
    4. Re:What you won't get in woody... by Sentry21 · · Score: 3, Informative

      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

    5. Re:What you won't get in woody... by Jagasian · · Score: 2

      It's the price of rock-solid stability. If you want "latest-greatest", then run Debian unstable. Just because its called unstable doesn't mean that its definitely going to be unstable, but running Debian stable definitely means that you are running one pure rock-solid stable and secure Linux.

      If I was going to show Linux off to my friends, I would show them Debian stable. Tons of great easily installed free software, all ontop of an ultra stable, ultra secure OS.

      Crashing or getting hacked doesn't make for a great first impression.

  16. Re:Version numbering? by gorf · · Score: 3, Funny

    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 :)

  17. Re:Does anybody know what happened to the pine src by staili · · Score: 3, Informative

    From
    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.
    "

  18. Re:Hurry! by Daniel+Stone · · Score: 2, Informative

    alien does this.

  19. Re:I can say one thing for them by Accipiter · · Score: 3, Informative

    I am seriously switching from slackware to something else, for the lack of tgz nowadays.

    Try here. They have a good repository of recent stuff bundled as Slackware .tgz packages.

    --

    -- Give him Head? Be a Beacon?
    (If you can't figure out how to E-Mail me, Don't. :P)

  20. Re:I can say one thing for them by Accipiter · · Score: 2

    Go Here 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.

    --

    -- Give him Head? Be a Beacon?
    (If you can't figure out how to E-Mail me, Don't. :P)

  21. Re:vs Mandrake ? by tacocat · · Score: 3, Informative

    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!!!

  22. Re:way out necklace for ya! by Harumuka · · Score: 2, Offtopic

    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?

    --
    What do you think of MusicCity now?
  23. Re:vs Mandrake ? by Glanz · · Score: 4, Informative

    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.

    --
    Rien n'est plus beau que le creux du 0.
  24. Re:way out necklace for ya! by Glanz · · Score: 2, Funny

    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.

    --
    Rien n'est plus beau que le creux du 0.
  25. Is the kernel really that important? by Per+Abrahamsen · · Score: 2

    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.

  26. Re:Version numbering? by rusty0101 · · Score: 2

    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

    --
    You never know...
  27. Re:Version numbering? by KjetilK · · Score: 2
    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.

    --
    Employee of Inrupt, Project Release Manager and Community Manager for Solid
  28. Re:Version numbering? by Ramsed · · Score: 2, Informative

    Updates to the user interfaces; Gnome and KDE; many packages, OpenOffice, ssh, and others; OpenOffice isn't in Debian (yet).

  29. Re:but when will we see.. by Anonymous Coward · · Score: 2, Insightful

    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.

  30. Re:Version numbering? by castlan · · Score: 3, Interesting

    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 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

  31. is Woody still using a 2.2.x kernel?` by mrm677 · · Score: 2

    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)

  32. Re:vs Mandrake ? by The_Dougster · · Score: 2, Interesting

    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.

    --
    Clickety Click ...
  33. Non-X86 ports are the major holdup by The_Dougster · · Score: 2, Informative

    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.

    --
    Clickety Click ...
  34. Just add slackware, the compilers work fine. by The_Dougster · · Score: 2, Insightful

    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.

    --
    Clickety Click ...
  35. Re:Does anybody know what happened to the pine src by steveha · · Score: 2

    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

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
  36. Re:Does anybody know what happened to the pine src by styopa · · Score: 2

    Actually Galeon is not completely dead in Debian. You can install it from the unstable tree. Also it will only uninstall Galeon if Mozilla increases by a milestone, ie .9.8-.9.9.

    --
    Disclamer - Opinion of Person
  37. Parent was poorly moderated. by castlan · · Score: 3, Insightful

    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?

  38. Unofficial Packages by styopa · · Score: 2

    For those of you who are unhappy with the purity aspects of Debian there is at least one place that I have found that has some unofficial packages like mplayer and the flash plugin for Mozilla.

    I haven't had any problems with the packaging that has done by the maintainer.

    --
    Disclamer - Opinion of Person
  39. I want journalled filesystems on Debian! by ttfkam · · Score: 3, Interesting

    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.

    --

    - I don't need to go outside, my CRT tan'll do me just fine.
    1. Re:I want journalled filesystems on Debian! by evil_one · · Score: 2

      I sit in on #debian on OPN. Almost all the helpers (myself included) have been helping guide people through ext3 upgrades since Alan Cox included it in the -AC kernel tree.

      --
      Desperation is a stinky cologne
    2. Re:I want journalled filesystems on Debian! by ttfkam · · Score: 2

      Thank you. I may forego ReiserFS and use ext3 instead, but be sure that you recognize the difference between your list and those of other major distributions:

      Download most recent version
      Install most recent version

      Voila!

      --

      - I don't need to go outside, my CRT tan'll do me just fine.
    3. Re:I want journalled filesystems on Debian! by Talla · · Score: 2, Informative

      If you go to the Debian netinst-page (http://people.debian.org/~ieure/netinst/), and read the release notes, you'll see that if you select option 3 when you boot, you'll get the bf2.4 image. I did this myself, and it works. When you format the drive during install, you can select ext3.

      As mentioned in the faq, you need a system that supports "ElTorito" to get this menu. Your options are to edit the CD-image so it boots from bf as default, download the floppies, or install 2.2 and upgrade. You don't need to compile the kernel, btw, you can just use dselect, and select one of the many precompiled 2.4 packages.

      I have used various Redhat and Mandrake versions for the last 3 years, but recently switched to Debian, and have never looked back.

    4. Re:I want journalled filesystems on Debian! by GoRK · · Score: 5, Informative

      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

      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/

      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 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

      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/. 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/

      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?

  40. Debian without Linux. by castlan · · Score: 2

    There was a nifty presentation given in support of Debian/OpenBSD, which likely still has the slides available for browsing via the web. Since then, it seems that Debian/NetBSD has more chance of (initial) implementation.

    I am pleased as well, because AFAI can tell, NetBSD has a bit more to offer Debian than OpenBSD at the moment. This is in no way a value judgement of the merits of OpenBSD versus NetBSD; I actually slightly prefer OpenBSD at the moment as a distinct OS. But it looks to me that NetBSD has a few architecture related bits that if incorporated into Debian could prove fruitful for the entire Debian Universe. Foremost is their modular alternative to Debian's vestigal runlevels. To date, NetBSD still offers greater architectural diversity than OpenBSD for maximal Debian distribution. Finally, OpenBSD's strongest trait, Security through correctness, would definitely be shattered by tearing the OBSD kernel from its solid and familiar userland, and abandoning it, dazed and confused, into the wild forests of Debian. NetBSD is a much more suitable candidate for transplant to date.

    After the initial foray into BSD, then the further effort to incorporate OpenBSD and FreeBSD kernels will be much less daunting. Out of curiosity, where is Debian for OpenBSd offered?

    One thing that baffles me to date, is why would anybody want a FreeBSD kernel in Debian? I'm not too clear on what Debian/FreeBSD has to offer that couldn't be better had elsewhere. After all, the Userland would still be Debian. Linux is IMHO more SMP accomplished than FreeBSD. What else does the FreeBSD kernel offer that can't be had in NetBSD or OpenBSD?

    -castlan

  41. The way I heard it... by The_Dougster · · Score: 2, Interesting

    Was that "Woody" is such a major improvement over "Potato" that they felt it was justifiable to go to the next major version number; i.e. 3.0.

    --
    Clickety Click ...
    1. Re:The way I heard it... by FredGray · · Score: 2
      Was that "Woody" is such a major improvement over "Potato" that they felt it was justifiable to go to the next major version number; i.e. 3.0.

      I would argue that a new major release number would have been very justified for potato; there were major upgrades of gcc and glibc relative to slink. Woody has the same default gcc as potato and only a minor upgrade to glibc.

  42. Re:Does anybody know what happened to the pine src by evil_one · · Score: 3, Informative

    try this package: http://packages.debian.org/testing/admin/pine-trac ker.html

    --
    Desperation is a stinky cologne
  43. Re:vs Mandrake ? by The+Pim · · Score: 3, Funny
    It's like comparing apples and hamburgers. I have both on the drive.

    That can't be good for the drive.

    --

    The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.
  44. Re:Does anybody know what happened to the pine src by evil_one · · Score: 2

    If you updating using apt-get update instead of dselect, it won't remove galeon at all - it'll put mozilla on hold until the packages are in sync.

    --
    Desperation is a stinky cologne
  45. Re:Does anybody know what happened to the pine src by steveha · · Score: 2

    Also, the GNU Public License (GPL) requires you to release source code when you release a binary package. The .DEB source packages comply with this requirement.

    Also, the Debian project has mirror servers all throughout the world. If I made some package that went into Debian, I would want the world to use Debian servers to grab the source, rather than having the whole world beat on my FTP server every time I came out with something new.

    steveha

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
  46. Didn't they promise to fix the release cycle? by RelliK · · Score: 2

    One of the things Debian people were supposed to fix was the abyssmally slow release cycle. Well, it's still abyssmally slow.

    --
    ___
    If you think big enough, you'll never have to do it.
    1. Re:Didn't they promise to fix the release cycle? by Phil+Hands · · Score: 2, Funny

      That'll be fixed in the next release of release-manager.deb

      --

      Debian: GNU/Linux done the Linux way
    2. Re:Didn't they promise to fix the release cycle? by psamuels · · Score: 2, Interesting
      Seriously though, we are releasing woody which is twice as big considering the number of packages than potato. Yes, all previous Debian releases doubled the number of packages, but hey, we're up to eight thousand now, cut us some slack!

      And also almost doubling the number of architectures. Potato supports i386, m68k, alpha, sparc, arm, powerpc. Woody supports these plus mips, mipsel, hppa, s390, and ia64. Keeping 11 sets of binary packages in sync and relatively bug-free is not as easy as it may seem.

      Yeah, this sounds like it's going for the worse, but the new system (read: the "testing" distribution) would allow us to release woody+1 by the end of the year. This wouldn't be that bad, would it? :)

      One might note that as AJ has said in the past, the long release cycle this time was due to some fundamental changes like the package pool and crypto-in-main. Still, I'll wait until woody+1 is released before I applaud the newfound efficiency of the release cycle. (:

      --
      "How can you claim that you are anti-crack, while still writing a window manager?" — Metacity README
    3. Re:Didn't they promise to fix the release cycle? by wickidpisa · · Score: 2

      People take one look and say screw that, I'm not running that outdated distro.

      Who cares? Which should they care more about, making a stable high-quality distribution, or how many people use it? One of the benefits of Debian being non-profit is that they don't have to worry about market share, they can concentrate on improving the system. Debian unstable is far more stable than any "stable" release on RedHat or Madrake that I have used. Does the naming system hurt Debian's public image? Yes. Does it hurt the system? No, and that's what's important.

  47. Re:Does anybody know what happened to the pine src by The+Pim · · Score: 3
    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.

    --

    The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.
  48. Re:Woody? by reverius · · Score: 2

    If you haven't been following Debian's last few releases, you missed Slink and Potato. Coming up after Woody is Sid.

    They seem to have a habit of actually using names from Toy Story...

  49. Re:I have used ext3 for months now in Debian. by ttfkam · · Score: 3, Interesting

    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.

    --

    - I don't need to go outside, my CRT tan'll do me just fine.
  50. Re:vs Mandrake ? by mickwd · · Score: 2

    Why is Debian cheaper when Mandrake is freely downloadable from lots of places ? And freely useable and copyable ?

    This isn't a point against Debian, but one possible reason for the stability of the packages it uses is that distributions like Mandrake have included more "cutting-edge" versions of packages, which have therefore been "tested" by a much greater number of people, and had the opportunity of bugs being found and corrected.

    Not that there's anything wrong with the extra stability Debian has. If I was running Linux on a server, I think I might well use it. I've also considered it for my desktop, but right now Mandrake is good enough for me.....

  51. LinuxFromScratch by ttfkam · · Score: 2

    This is of course the type of thing that makes the LinuxFromScratch distribution so popular. However, would you suggest setting up a Debian box manually without an install program? Just compile and install the basic system utilites. Compile and install dpkg, apt, dselect, and the rest.

    My point is that when I want to learn more about the inner workings of Linux in order to look behind the curtain, I use LinuxFromScratch. Unfortunately LFS doesn't scale when you want to setup more than one box (dozens, hundreds, thousands, etc.). No one uses LFS for a company-wide install because it would be a huge timesink on install and a maintenance headache for IT after it's deployed. After all, how can you be sure that they are all the same configuration if they are all done by hand? People make mistakes. This is another reason why installers exist (It's the primary reason computers exist, but that's another argument). People have already written fine installers for Linux that simplify the process and let people get to what they want to do which most likely does not include hacking the inner workings of Linux. They want to get the web site up, the mail server up. They want to get on with their job which quite often has nothing to do with computers.

    You shouldn't have to be an expert with Linux or be a programmer in order to use Linux. You shouldn't even have to be a novice if it's just a workstation. You should be knowledgable if setting up a server -- especially if it's connected to the Net -- but a workstation? Can I do it? Sure. Do I want to go through this just to use another distribution? Hell no!

    Take a cue from SuSe: bootable CD that lets you demo Linux without even installing. Why? Because unless the user gets past the install process easily, technical superiority be damned, the user won't be using it long enough to recognize it as better.

    --

    - I don't need to go outside, my CRT tan'll do me just fine.
  52. Re:Does anybody know what happened to the pine src by The+Pim · · Score: 2
    this source package seems to have disappeared also

    It's in testing. Where is it missing?

    --

    The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.
  53. Re:I can say one thing for them by the_2nd_coming · · Score: 2

    they did....lsb 1.0 made rpm 3.0 format the standard packageing format

    --



    I am the Alpha and the Omega-3
  54. Woody 2.2r6 was released a few days ago by green+pizza · · Score: 2

    http://people.debian.org/~joey/2.2r6/

    Gobs of security fixes, few misc fixes, stability fixed. 2.2r6 is the second update of Potato in 2002. Not exactly cold.

  55. Re:Version numbering? by jannic · · Score: 2, Informative
    The version number of a new debian release is assigned by the Release Manager. In this case, Anthony Towns, the Release Manager for woody, announced that woody would be Debian 3.0 in an email to a mailing list on Jul 1, 2001. In this mail, he wrote:

    "As you've noticed by a careful analysis of the subject line, the woody release will be numbered Debian 3.0, in recognition of the large number of changes made since potato. This is, to put it mildly, a somewhat controversial decision, but it's one I get to make."

    So, while the change from 2.2 to 3.0 indeed indicates that this release includes major changes, this is may not be the opinion of a majority of all debian developers.

    Personally, I think that many things have been changed since potato, and it's appropriate to call the new version 3.0. And I agree with Anthony in the following sentence: I think by the time it's released it'll easily live up to that number -- and by that I mean the "3", not the ".0".

  56. You rock! by ttfkam · · Score: 2

    At long last! Not the most elegant or obvious solution (in my opinion) but quite acceptable under the circumstances (I already have copies of the netinstall CDs).

    Thank you very much!

    --

    - I don't need to go outside, my CRT tan'll do me just fine.
    1. Re:You rock! by GoRK · · Score: 2

      It does quite clearly state this on the Netinst CD webpages and on the on-disc texts that the discs have multiple boot images.

      BTW you could have asked nicely.

  57. which version of gcc? by green+pizza · · Score: 2

    Looking at:
    http://ftp.us.debian.org/debian/dists/woody/m ain/b inary-i386/Packages
    I see both gcc 2.95 and gcc 3.0 are included as part of the standard packages. But my question is this:
    which version of gcc will be used to compile the binary (precompiled) release of Debian 3.0?

    1. Re:which version of gcc? by GoRK · · Score: 2

      Short answer: Whichever each package maintainer prefers for each package. I.e. whichever produces the best and most stable code.

      Long answer: Different architectures that Debian has ports or in-progress ports for may be unfit under the 2.95 compiler (SH4 comes to mind. Ugh. 2.95/sh4 sucks). Different architectures can specify default compilers or overrides for package compiles, as can the packages themselves. 'gcc' will normally run 2.95 out of a stock woody install unless you change your app-defaults to run the gcc-3.0

      Quibble: Both compilers produce working and interoperable code. It's not like a lib compiled with gcc-3 will have problems being linked with a program compiled with gcc-2.95. It is logical and quite a good thing to have both choices. I think you'll find that other binary distributions are compiled with a myriad of gcc's.

  58. Re:Does anybody know what happened to the pine src by styopa · · Score: 2

    If you apt-get install mozilla first and mozilla has had a milestone update then it will remove galeon. I don't use dselect when dealing with unstable because I only want a few things from the unstable branch, galeon, lastest mozilla, nautilus, and evolution.

    --
    Disclamer - Opinion of Person
  59. Re:Blank CD-R? by xanadu-xtroot.com · · Score: 2

    Why bother downloading 8 images when most of the stuff isn't going to be used?

    Even some of us "Linux"-heads are still hancuffed to modems. I'll have to wait for CheapBytes to get 'em and go from there. 50 meg of KDE3 overnite isn't a big deal. A gig or two....

    --
    I'm not a prophet or a stone-age man,
    I'm just a mortal with potential of a super man.
  60. Re:Version numbering? by wickidpisa · · Score: 2

    Why would any developer include packages when latest versions can be downloaded from the official web sites?

    Why? I have about one thousand packages installed on my computer, it would be impossible to keep track of them all and update each one individually. Instead a simple "apt-get update; apt-get upgrade" will do it for me. Yes there are times that I do not have the most current version, but I have the added benefit that the packages are checked for compatibility before they are put in. On my boxes running unstable, I often get programs updated before my friends who run other distros because they haven't even heard that a new version came out. I used to be hesitant to a system like debian's too, but after using it for a week or two I don't ever want to go back.

  61. Re:Does anybody know what happened to the pine src by wickidpisa · · Score: 2

    I actually had trouble with this in Potato over the weekend, and I found something interesting. While all the mirrors (that mirrored source packages as well) had the pine source in there archives, the package listing did not list it. I don't really know why this would happen, but I checked around and found a mirror that had it listed and used that one.

  62. Re:Version numbering? by Publicus · · Score: 2

    Personally, I don't care what version number they use. It's Debian, and that's all that matters.

    --

    My Karma was at 49, then they switched to words. All that work for nothing!

  63. Re:Does anybody know what happened to the pine src by Daniel · · Score: 2

    I see it in unstable and testing. (albiet in non-free, of course)

    dburrows@auric:~$ madison pine
    pine | 4.44-3 | testing | source
    pine | 4.44-3 | unstable | source

    You do realize that this is different from the "pine-src" package, right?

    Daniel

    --
    Hurry up and jump on the individualist bandwagon!
  64. Re:but when will we see.. by Daniel+Stone · · Score: 2, Informative
    We're not re-releasing potato; woody has:

    Mozilla 0.9.9 (is 1.0.0 even released?)

    GNOME 1.4, and also GLib/GTK 2.0

    KDE 2.2.2, with KDE3 debs to separately available

    Apache 1.3.x, because apache2 isn't close to being production-ready

    XFree86 4.1.x

    Kernel 2.4.x has been here since the dawn of time
    I think you're bark^Wlooking up the wrong tree (har har har). Try seeing what woody actually has, some day.

  65. Re:Does anybody know what happened to the pine src by Daniel · · Score: 2

    After that I looked at the list of packages, pine4-src (or whatever the name is) isn't there.

    That's because it's a source package, not a binary package. Type "apt-get source pine" and you can download it (assuming you have deb-src lines in sources.list)

    Daniel

    --
    Hurry up and jump on the individualist bandwagon!
  66. Re:I have used ext3 for months now in Debian. by styopa · · Score: 2
    So what is Debian offering me other than a warm, fuzzy feeling?

    There are several different things that I feel that Debian offers over the other distros.
    • 11 Stable, supported architechtures. All of which are given equal priority.
    • Linux, Hurd, and BSD versions of Debian. Pick
    • A sain process of releasing new software into the system. Start in unstable, work its way into testing, move testing to stable. As opposed to spewing out new releases every time something big happens. Slow, sure, but at least I know that it has been tested properly.

    It isn't perfect, so what, neither is RedHat (or others). Sure, by this time the journaling filesystems have been tested and are pretty stable. I myself have been using ext3 for quite some time now. I agree that it would be nice to have a journaling filesystem as a primary installation option, but I also understand that it will, most likely, get done in a update release. Right now Debian is in a bug squashing mode, not adding new features to the system. The attention placed on removing release critical bugs over constantly adding new features is one of the things that I find most appealing about Debian.
    --
    Disclamer - Opinion of Person
  67. Calling a spade a spade by ttfkam · · Score: 2
    You obviously haven't looked in the directory which contains the woody install disk images, because it's plain as day.

    Mmm hmm... I grant that I could have been more diligent here. I guess I'm just used to every other major distribution not needing a manual for their install -- self explanatory, complete, and all that. But yes, I needed to RTFM here.

    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.

    Very good point. My primary focus was on the netinstall images for precisely this reason.

    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.

    Yes, by all means, type in "ReiserFS" into that search box. Please tell me how many documents I must go through in order to find relevent info. But I digress, my main complaint was the fact that Debian's installer is about three or four years behind Caldera, RedHat, SuSe, Mandrake, etc.

    I finally finished getting through the network install (writing this with a Mozilla nightly on Woody) and I must say it was one of the most painful experiences I have had with Linux in years. My god, setting up BIND with a few domains was easier than that and that is by no means a compliment.

    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."

    Nice. If it actually gets through the install without crashing, no matter how likely you are to meet a minotaur during the process, it ain't considered broke.

    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?

    Much akin to telling a Linux newbie that they're stupid for not knowing to type "ls" at the bash prompt or why the current directory isn't in the default execution path. Wake up! Before you mentioned it, I had no idea what the Progeny installer was or where to find it or that I should have been looking for it in the first place. The reason you know this is because you use Debian, are familiar with Debian and its satellite distributions, and have known it for long enough that you forget that others don't know it yet.

    While you're at it, why not go yell at some 5th graders because they don't know how to solve Algebra problems yet. After all, since you know Algebra, they should be expected to know it too.

    Think you can put together a better debian website? Why don't you sign up?

    Good point. Although I think Debian would be better off having this Progeny installer worked on. The best installer is one that doesn't require documentation to use in the simplest case. Note: I am NOT saying that documentation isn't important. What I was looking for what something akin to RedHat's "Workstation" or "Server" install. Hell, I would have settled for something as easy as the "Custom" install. But in the end you're right. I should put my code where my mouth is and help out.
    --

    - I don't need to go outside, my CRT tan'll do me just fine.
  68. Almost forgot... by ttfkam · · Score: 2
    Or can you not type "apt-get install pgi" successfully?

    At the time? No. I had to install it first. Hi chicken! Meet my good friend, Egg.
    --

    - I don't need to go outside, my CRT tan'll do me just fine.
  69. Re:I have used ext3 for months now in Debian. by ttfkam · · Score: 2
    11 Stable, supported architechtures. All of which are given equal priority.

    Impressive but not as important or appealing to the >90% of Linux users who are on x86.

    Linux, Hurd, and BSD versions of Debian. Pick

    Hurd is probably not a good example at this point as a case study. The first version of Debian's distro for the Hurd has yet to be released (or reach code completion let alone bugfixing or profiling).

    A sain process of releasing new software into the system. Start in unstable, work its way into testing, move testing to stable. As opposed to spewing out new releases every time something big happens. Slow, sure, but at least I know that it has been tested properly.

    Sane process, yes. However I was under the impression that "testing" was a recent development. Please don't refer to it in a manner that suggests that it has always been this way.

    I never said that RedHat was perfect. In fact I have mentioned to the contrary in several posts. I also acknowledge that Debian is in the final stages before release. Believe it or not, but this rant began in the "Better Installer for Debian?" article from a few days ago and I spilled it into this one to make sure the conversation didn't die from age.

    However bugfixing should not be an excuse for the installer being at least a year behind for journalling fs in the install and three or four years behind in most other parts of the installer (RedHat 5.0 was easier to install). I imagine that it is because Debian setups are so easy to maintain that install becomes increasingly rare (or maybe the experience of installing was so painful that users avoid it at all costs by keeping a clean system).

    At any rate, could someone provide a link or an email address to someone or some project that is working on this. Belive it or not but I would like to help out and not just complain. Considering how verbose I can be, I at least could help on in runtime context documentation.
    --

    - I don't need to go outside, my CRT tan'll do me just fine.
  70. Re:Of course It's ready by commodoresloat · · Score: 2
    As a user, I'm pretty confident in woody, I'm using it myself at work at at home, .... It's testing pretty damn solid as far as I can tell. Been using woody on half a dozen desktops at work, for about 6 months and while at first there were definite gnome problems which thankfully have dissapeared waaay into the past. And it's a pity that galeon wont be there, but I suppose it is a little unstable (gotta love the crash recovery though!)

    Is it just me, or does it sounds like this guy is talking about an orgy?

  71. Graphical Debian Installer (here now!!!) by Jagasian · · Score: 2

    If you are interested in trying Debian out, but are afraid of installing it, then try out PGI, the graphical autohardware detection Debian installer. Make sure to check out the screenshots.

    In my opinion, once the default Debian installer becomes idiot-proof, Debian will take over as the lead Linux distro.

  72. dselect was the saving grace for debian! by hawk · · Score: 2
    I can't be the *only* one who liked dselect, and has never seen anything that does what it did (does) nearly as well--now can I? OK, the hostility I received when asking ab out a fix for the inability to search from a remote screen was annnoying (hostile response was that it was a ncurses bug, and therefor not his problem--even though it froze the session beyond recovery), but aside from that, the ability to choose *which* program to use to satisfy dependencies was nice.


    portinstall in FreeBSD is getting some of that now, but still needs some refining (such as listing all the choices before asking you one by one whether or not to install them :).


    Still, dselect wasn't enough to keep me with debian. Between the politics and the age of the packages, I got fed up. Now there is the "testing" distribution, but there used to be no middle ground between a hopelessly out of date stable and the unstable distro that you could count on knocking out your system about twice a year.


    hawk, happily with FreeBSD for the last few years, but still using debian on smaller older systems