Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Debian

Debian 2.2 (potato) Freezes 254

Chris Frost writes "The Debian Project began the freeze of its next distribution release, 2.2, today." Hit the "Read More..." link to read the full press release. This has been a long time coming, and it's good to see another stable release in the future. I've been running potato for some time now, and I'm eagerly anticipating woody, the next unstable release.

------------------------------
The Debian Project
press@debian.org
http://www.debian.org
Martin Schulze
January 16, 2000
------------------------------
The Code Freeze for Debian GNU/Linux 2.2 has begun

"The code freeze for the next Debian release, code named "potato", has begun", says Richard Braakman, current Debian Release Manager. He expects the freeze process to take about two months. Until the new version is released, there will be three distributions available on our servers: `stable', `frozen', and the new `unstable'. "The new `unstable' distribution, code named woody[1], was created today", continues Richard. The `frozen' and `unstable' distributions start out with the same set of packages. While `unstable' will be updated rapidly, `frozen' will have only bugfixes applied in preparation for its release. [1] Debian releases are code-named after characters from the movie Toy Story. Woody is the main character, the cowboy action figure. >> About Debian The Debian project is an organization of many users who volunteer their time and effort. Its tasks include maintaining and updating Debian GNU/Linux which is a free distribution of the GNU/Linux operating system, and the development of the Debian GNU/Hurd operating system. >> Contact Information For further information, please send email to the Debian Press Team, press@debian.org, or visit the Debian homepage at http://www.debian.org/"
This discussion has been archived. No new comments can be posted.

Debian 2.2 (potato) Freezes

Comments Filter:
  • by Anonymous Coward

    Woody - coming soon!
  • by Anonymous Coward
    Consider this:

    Waiting is not a Productive Thing(tm). Waiting encourages more waiting. Think of it this way, while we're waiting for kernel 2.4, well by the time it's out, XFree 4.0 will be just around the corner, so we'll wait for that.

    Then something Even Better(tm) will be coming out Real Soon Now(tm) so you may as well wait for that too.

    *bzzt* =) Just make sure it has drop in compatibility. Nuf said.
  • by Anonymous Coward
    When (estimate) could we expect to see a release with Xfree86 4 and KDE2 included?

    obviously neither are complete yet, but are getting close. And when released, what effect will that have on things?

    I've been a loyal linux user for a short while now (about 8 months), preaching the virtues to anyone who would listen. But I'm considering giving up the ship and going back to windoze just cause it's so damn hard to accomplish anything in linux (permissions, changing to root anytime you want to do anything, no programs, compiling everything yourself and needing to go find libraries to do it when they work at all) and I'm getting worn out on it.

    this is a serious question. I'm on the fence here.

    I've heard the new X and KDE will revolutionize the OS, and I'm wondering a) when can we see them, and b) will they really make it worth continuing?

  • by Anonymous Coward
    I'd assume those facilities are significantly changed from 2.2 to 2.4, and thus you will have to get new
    packages for those with a new kernel package as well. Given the way that Debian works, that could
    be an automatic upgrade: select the kernel and the other stuff comes in too.


    All very true, but that's hardly the same thing as potato today being 2.3-ready like you claimed, now is it? I suspect that was the other poster's point, anyway.

    It's just like my endless complaints (up to about 2 months ago, when potato bootdisks finally were released) about slink not supporting my system. All the debian people pointed out that potato *did* support my system, which hardly did me any good since I would have had to install slink first to upgrade to potato (at the time; that's since changed, and one thing I hope Debian continues is to make their unstable branch directly installable), and I couldn't install slink because it didn't support my system.

    So, what if I'm on a box sufficiently USB-dependent that I can't install w/o USB support (say, USB NIC)? Am I going to have to wait another three years for a USB-capable, truly Linux 2.4-ready Debian?

    This endless stability does come at a price.
  • by Anonymous Coward
    Free software gives you that. As long as there are a few people interested in running it, there is
    sufficient force for it to be maintained. You don't have to put up with some marketing department
    discontinuing your favorite product.


    I don't really see that as being different from Debian, where I have to put up with the "marketing department" never even releasing my favorite product because they're so busy hunting bugs that it's out-of-date when they ship.

    Of course, one could also argue that the Debian development style isn't free, given the refusal to admit new maintainers into the club....
  • So, waiting for a release for the most part is a moot point. You can install Debian whenever you want,
    and have the lastest of everything, or have something that's thoughly tested(MUCH more then other
    distros). And, "unstable" for the most part, as alot of people will tell you, is alot better then other
    distros .x releases.


    There's only one problem with your argument: it's *NOT* a moot point.

    Take me, for example. I like Debian, and prefer to run it. I have a box which won't even boot w/o a 2.2 kernel.

    Guess what? That means I couldn't install Debian until November, when beta boot disks for potato finally came out.

    It's easy for you to say that it's a simple matter to upgrade if you want, but the problem is that that's a specious argument--it's not always a simple matter (or even possible at all) to upgrade, because the base you'd be upgrading from may not work.
  • by Anonymous Coward
    Standard Debian Disclaimer:

    Debian is made up of volunteers.
    The "organisation" debian does not put together a distro designed to grab market share, but to be a great system.

    Dselect perhaps may not be for everyone. BUT YOU DON'T NEED TO USE DSELECT- just skip that step and apt-get the whole system.

    Slashdot comments have VERY low standards regards to debian.

    Please do NOT comment unless you know what you are saying.

    Incidently- Debian is one of the best systems around for those who are in the right frame of mind to use it. That includes me, and everyone I know :)

    NOTE: I am not a "Debian developer"
  • by Anonymous Coward
    I don't like them.

    Do you?

    How can I avoid dealing with them completely? There are so many of them when I go out into the world. I go to a resteraunt, and ask the waitress if she used Debian, and she doesn't even know what it is........ ARGGHH... where can I get some service in this town.
  • Yes, you are correct and Ian Jackson, the dselect/dpkg designer and coder has said as much. This is why Debian now has console-apt as replacement for dselect and why DPKGv2 is being developed as we speak.
  • by Anonymous Coward
    You forgot the best way to please your girlfriend:

    Upgrade from NT to Linux to replace your Microsoft with a Woody!
  • Yep. That's why Windows is everywhere.

    Linux has to lose the elitism and make an idiot proof installer if it ever hopes to displace Microsoft.

    We're here to make a good system which is powerful, configurable, flexible, and, above all, usable. This mentality that we must somehow "beat Microsoft" is misguided.

    If we make what amounts to an OSS version of Windows, then what was the point? We've "beat Microsoft" at that point, but in so doing have become just like them, albeit a much poorer version.

    What in God's name is so difficult about dselect? There is one problem with dselect which I can think of, and it isn't because of dselect: it's because of maintainers who screw up their dependencies, and that's going to be a problem regardless of what package manager front-end is used.

    Make good software because it's good software, not to "beat Microsoft." When you make something idiot proof, you attract idiots, which isn't very beneficial.

    I'm not trying to be "31337" here, either. I'm just sick of people saying that "if it isn't idiot proof and/or like Windows, then it's worthless and the users and developers are just trying to be elitists."

    Elitism is a good thing, just as descrimination is a good thing. It just has to be appropriately applied. Not hiring someone because he's black is probably very stupid; I can think of very few situations where that's appropriate (e.g. acting). On the other hand, I can think of very few situations where it is appropriate to hire someone because he's put five million piercings on his body, has tatoos all over himself, dresses like he lives in a dumpster, has orange hair, and has marbles surgically implanted under each eyebrow. Unless the guy will never have contact with clients and is really good, I don't want him in my business.

    If Linux hopes to ever displace Microsoft, it needs to be a good system, with good users, with good functionality, security, and flexibility. Making a OSS version of Windows is a waste of effort.

  • I've been running one computer on unstable and one on stable. You *do* notice the difference, but almost anything that breaks is fixed the next day. Its usually little things like innd an inewsinn both having a conf file that clashes.

    I have to say, I like console-apt, only a couple of gripes which I can ignore.
  • I got that too. I assumed my mirror wasnt updated.

    Just use 'potato' as the name.
  • I hate that.

    At least you didnt ask her if she wanted to see woody.

    (apologies in advance)
  • Its probably not going to make it as the default installer for Potato, but its pretty good. IMO it just needs a "tell me what packages depend on this" function, and to be a bit more robust with poor connections (it freezes if downloading stops)
  • "Debian is rock solid while Mandrake isnt. Mandrake people make linux look bad"

    Use what you like, and stop moaning. Just becase Debian only increase the minor version for each minor release is no reason to bash them.
  • Yes, but it lists the packages this package depends on, not what packages depend on it. I want to see what I can remove without causing a cataclysm :)
  • You can buy unstable on a cd from many vendors who are listed on debian's web site. http://www.debian.org/distrib/vendors

    --
  • This more or less means downloading the OS from scratch. Trivial on a T1, non-trivial on a modem.

    There is some truth to this, but it's quite possible to do Debian on a modem (I did), or with something less than a T1.

    In my case, I used a 2.1 install disk essentially as a base-system installer, and built up the rest of my system over the course of a week or so. If this is your first Debian box, this is a good way to fly. It's better to assemble a system slowly and see how things click into place than to try to load everything at once. My download sessions would run 8-10 hours. I've got dual phone service, (one of which is never in use, one of which is <g>). So it works. As stated, apt-get update and apt-get download -d can be scheduled for automatic execution (remember to echo a 'y' or linefeed to the latter for cron jobs).

    Other alternatives:

    • Use the Zip disk transfer method. This is built in to dselect and/or apt, thought I haven't used it. You select packages on your base system, put the request on a removable disk, download from a faster connection, and transfer to your box. 100-125 MB of debs is a pretty good set of SW, this method works pretty well.
    • Go to where the bandwidth is. Take your box to a location that has bandwidth (office, install fest), and do your major installation from that point. You'll still have to do incremental upgrades, some of which can be substantial (mine run from ~100 KB to ~100 MB depending on activity and frequency).
    • Utilize a shuttle machine. If you've got a laptop, you can use it to mirror or download debs and transfer them between spots.
    • Share from your local connection. If you have multiple machines at the end of a slow pipe, share the debs between them so you don't have to download repeatedly over the same connection.

    Other points to recognize: with Debian, more debs => more bandwidth required. Because each package has a probability of being updated, you are essentially required to provide more bandwidth to keep your system up to date. More arguments for keeping lean selection on board. If you're not using a package, lose it. Your updates will go faster.

    You also don't have to upgrade your system. "If it ain't broke...". You should stay current on security alerts, but otherwise, if what you've got works, stick with it. Under unstable, there is a rather alarming frequency with which things break (does anyone out there have a successfully installed emacs19 or emacs20 from the past four months?), though usually this just means that the upgrade doesn't install. A --force usually works, though you're taking a risk.

    What part of "Gestalt" don't you understand?

  • <g>

    What part of "Gestalt" don't you understand?

  • Corel's Linux distro is built around Debian. It's one of the most slickified distros out there -- if you believe MSNBC's writeup [msnbc.com]. If you want Debian package management without the krufty interfaces, give it a whirl.

    What part of "Gestalt" don't you understand?

  • First, do you mean "why do distros come with one installer" or "why do they come with one package manager". There's a difference.

    The installer is somewhat insignificant -- you want a piece of software which can boot the system, partition disks, set up some reasonable base defaults, and connect you to a package management system. Ideally you only need do this once. To date I've heard of bootstrap installs (you've got a running system and build a second under it), RH, Debian, YAST, etc., Windows-based installation programs, etc. There are several flavors of installer built around RPM, dpkg, and whatever it is that Slack uses. Reasonably moot issue. Why does everyone seem to have their own? Probably a combination of NIH and support (we support our installer...).

    The package management system is a different horse. This is what you're relying on to maintain, upgrade, and verify your system over time. In large part it consists of a package database, some method for identifying dependencies and/or relationships, and possibly some way of resolving them. This isn't a task which is easily split among several systems on a single box.

    There are tools for managing packages from one system under another. 'alien' is one such tool, and it permits RPMs to be installed under Debian, and vice versa. But AFIAK, you lose many of the benefits of integrated package management. Ultimately with today's package management architectures, someone's got to rule the roost, and peered administration isn't supported.

    Got any better ideas?

    What part of "Gestalt" don't you understand?

  • This means I may not have to sit through 70+ meg updates on my 56k modem! I like the sound of that! :)

    Thou it does present a problem... which version to stick with until woddy final is out? Frozen or ongoing potato? I think I'll have to choose frozen, just so I don't have the huge downloads i mentioned.. (or so I hope, anyway.)

    that, and I don't have to change my apt.sources file to use frozen. :)

    bash: ispell: command not found
  • > I may be wrong, there may be a patch for USB kerboards under 2.2.x

    There's a near full backport of the usb subsystem to 2.2.x, actually. Try www.suse.cz/development/usb-backport/ [www.suse.cz] for a patch to update 2.2.14 to 2.3.39's usb stuff. not sure how solid it is, as i haven't tested it yet, and it's better to have the usb stuff in a "stock" kernel than depending on patches, but maybe this might make it into 2.2 upon release of 2.4? or am I just dreaming again? :)

    bash: ispell: command not found
  • rpmfind (see rpmfind.net [rpmfind.net]) is a database/service that will find the files in the packages for you. It's quite snazzy.

    You can use it via the web interface (above) or via the CLI tool [rpmfind.net].

    ...j
  • by Chris Johnson ( 580 ) on Sunday January 16, 2000 @11:38AM (#1367100) Homepage Journal
    "I was so excited when potato froze, I got a woody"

    :)


  • (Hedwig? Is that an alien from Star Control 2?)
    I believe you're referring to the Utwig [gamestats.com]..

    -- Does Rain Man use the Autistic License for his software?
  • Start by reading the installation instructions [debian.org] ;)

    It was a long time since I installed Debian, but I think the problem is that you also need to get the base system, which basicly is a large tgz-file containing the most basic parts of a GNU/Linux system. From there you can use apt to download everything else.

    I'm not sure how well the potato boot disks are working, you can always use the slink disks instead, and then install potato from there.

  • Funny indeed. I've never managed to install *anything* without a hitch, except for FreeBSD (which I can practically do blindfolded now).

    The real question, though is how easy it is to stay up to date once it's installed, since you're likely to be doing that much more often than actually installing/reinstalling (if you're not a windows user, anyway). Again, I find FreeBSD's cvsup && make world mechanism to be as near hands off as one can get. Simply beautiful.
  • just use 'potato' as yr source. That way you don't have to change it as the mirrors update.
  • Isn't he the guy who writes the best-selling kid's books?

    Explain your cryptic reference, and I'll explain mine:

    Go play Star Control 2; you obviously haven't yet.
    ---
    pb Reply or e-mail; don't vaguely moderate [152.7.41.11].
  • :) You are correct, sir. All part of the humor.

    However, thanks for the Star Control link! (I love those games... Any game that uses mods for sound must be cool.)
    ---
    pb Reply or e-mail; don't vaguely moderate [152.7.41.11].
  • by pb ( 1020 ) on Sunday January 16, 2000 @10:22AM (#1367107)
    This is why I use redhat: no frozen potatoes.

    Maybe if I had a microwave card for my computer, I wouldn't care, but I find it's too much trouble to constantly be heating and stirring those frozen potatoes. They take forever to heat up, and even after that, they don't always have that even consistency.

    So I use RedHat 6.0, even though I don't know if I have to microwave a "Hedwig" or not. (Hedwig? Is that an alien from Star Control 2?) However, I guess if I used Debian, I could just try to Slink around the whole issue...
    ---
    pb Reply or e-mail; don't vaguely moderate [152.7.41.11].
  • by sjames ( 1099 )

    However I *do* think that having the latest kernel permits certain conveniences as far as default packages and installation set-up goes.

    Agreed. Perhaps some sort of Potato and 1/2 would be in order? There are some really nice features in the new kernel. It's not too hard grab and install those but it would be nice to have it integrated into apt without having to configure for unstable. Now it's just a matter of figuring out how ;-) Perhaps if it were split off like non-us is done now and somehow, supplimental CDROM handling is added? The biggest problem I have now is that the fast install over fat pipes at work doesn't work so well over 56K at home (not that that's Debian's fault).

    WRT to firewalling, the new way is iptables. There is an ipchains compatability module that allows the tables to be handled through ipchains. I'm using that on several boxes now with good results.

  • There's nothing wrong with an installer that has an expert mode, a normal mode, and install wizard. Again, to deliberately exclude those not already deep in the fold is the very definition of elitism.

    I just don't see it. There are several different distros that all give you a good Linux system. Some are targeted at professionals, some to business, and others to novice home users. There IS a need to make the home versions more friendly, and it appears that the work is being done. Perhaps you should write the perfect install wizard for novices?

    One thing I DO know for certain is that all of them are easier than SLS was when the kernel was in the 0.9x versions. Of course having to download off of a BBS at 9600bps didn't help either.

  • Funny. I've installed a few dists lately + freebsd. Debian's was the only one that went without a hitch.

    And dselect does NOT suck. Its just complicated.
  • If you want only potato, use "potato" instead of frozen or unstable.
  • and aptitude (just a few minutes ago, in fact), and i like dselect better that either. I miss the info displays; the sorting by availability, priority, and name; the hold feature; the ability to undo mark-for-(un)install without resetting everything; indication of obsolete packages.

    Aptitude author speaking.

    Part of the reason that you don't see some of the features you mention is that I'm working on things in approximate inverse order of difficulty. Most of what you mentioned (except for the undo feature) is almost trivial to add, so I haven't yet :). But I believe that I have info screens (latest version, press Enter); I have grouping but not by priority yet (I consider that a dselect misfeatures, but the grouping order will become configurable, hopefully within two versions) -- so that's a legitimate complaint; hold definitely works (you can hit '-' on a package that's being upgraded or just hit '=' anywhere); undo is another thing I really want, and obsolete packages should actually be fairly easy to check for with the right APT magic. In fact, I think I'll go add that now. Expect it today or tomorrow in the 0.0.5 release.

    Daniel
  • I think the current plan is to try to get this working while woody is unstable.

    Daniel
  • Potato will also come with several alternative package management frontends including gnome-apt, console-apt, and aptitude.

    Daniel
  • You didn't read the first sentence of my assertion that it's not as much of a problem, did you? I said that it wasn't that much of a problem *if* (or iff if you want to be precise :) ) you aren't being charged for bandwidth or connection time.

    Obviously, you are.

    Daniel
  • Don't worry, i noticed aptitude is still in 0.0.x releases, so it's nowhere near finished!

    No problem. Sorry if I gave the impression I was jumping on you, but you're the first person who's provided detailed feedback (aside from "looks cool".. :) )

    My complaints were more directed towards capt, which is much more developed

    Actually, depending on your point of view, I may be extremely close to having a superset of capt's features. OTOH, I haven't explored that program deeply; it looked like maybe it had more in it than met the eye immediately..

    The "undo" i was referring to is how in dselect if you push +, then decide you don't want to install it after all, you can hit _ and it'll be in the state it was before the +.
    Hmm. You're referring, I believe, to being able to purge packages? I'd think console-apt could do that..aptitude can (in fact, the default binding is '_') -- you just won't be able to tell what you did till the next release (I just added an indicator for it a few minutes ago ;) )

    Just checked and you're right, console-apt doesn't have a purge mechanism. It's about two lines of code, so I have no idea why it's not there. (well, actually I do have one idea: purge facilities may not have been in libapt when console-apt was started)

    i would've thought that to be as trivial to add as anything else.

    What you're talking about is. If you look at the TODO for aptitude (don't take it too seriously, some of that stuff is just random ideas I came up with when I was planning the program), one of the top items is multilevel undo support. The main reason this is tricky is that selecting a single package can potentially cause a cascade of modifications to package states, so code to save the old state, track the new one, and find the differences is needed. Not too hard, but in the spirit of Aptitude I'm going to make it ridiculously general and solve several other annoyances in the same fell swoop. Unfortunately, this complicates the problem significantly and I've been too intimidated so far to do it :-) I'm running out of other features that I want to add, though, so this may go in sometime in the next few weeks..

    What would be really nice would be to pick first sort by status/priority/availability/section/whatever/none , then second within those groupings sort by status/priority/availability/section/whatever/none , third yet again, and last by name/download size/installed size/whatever

    I assume you mean 'group' here instead of 'sort' -- for me 'group' implies that the packages are placed in a separate, collapsable subtree, whereas 'sort' just implies that they get sorted within the subtree.

    This is *definitely* on the Aptitude TODO. I estimate that it'll get into 0.0.6 but I'm trying to avoid promising anything about release schedules :)

    The internal infrastructure to do most of that is actually already present; I just haven't written the configuration code yet (which is going to be hairy, since C++ doesn't make classes into first-class objects so to build association tables you need factory routines and..argh, my head is hurting already :) ) If you're willing to edit and recompile the code, line 372 of testscr.cc defines the grouping order. (be warned: it has more parentheses than you'll see anywhere else outside a Lisp program, partly because I was thinking in somewhat Lispy terms when I wrote that code..)

    As for sorting..I was originally going to provide more of this, but grouping worked out so well that I may just stick with the alphabetical sorting I'm doing now.

    All in all, it's good that so many package selection programs are available, so people who hate one can use another.
    Absolutely correct.

    Daniel
  • by Daniel ( 1678 ) <dburrows&debian,org> on Sunday January 16, 2000 @01:43PM (#1367117)
    (Disclaimer: I'm not a Debian developer; I just hang out on the mailing lists and in the new-maintainer queue..)

    There are two things to note:

    First, this isn't an official "Debian strategy", although many users end up doing it; in fact, it's a periodic occurance on debian-devel for someone to start a huge thread predicting the End Of The World As We Know It[tm] due to the slow release schedule, and for just about everyone else to agree that things need to speed up. There are several proposals to restructure the archives and make it easier to cut new releases more often; it looks like (I believe) they'll be in place before Woody.

    Second, this isn't as much of a problem as you think, as long as you aren't being charged for modem time and/or bandwidth. I've tracked unstable for long periods of time over a modem. The trick is to set up a cronjob to download stuff in the middle of the night. Also, if you want to use less bandwidth, you can download less frequently than once a day (say, once every week or two) or upgrade individual packages that you want a newer version of.

    Daniel
  • by Daniel ( 1678 ) <dburrows&debian,org> on Sunday January 16, 2000 @01:56PM (#1367118)
    A startup company named RedHat has announced that it is shipping a new distribution of the Linux operating system. For unknown reasons, it has chosen to number this version 6.0.
    Sun Microsystems, a new contender from Palo Alto, California, has released a hitherto unseen operating system, Solaris.
    And finally, a dark horse company named Microsoft in the city of Redmond, California, has announced that it will soon be releasing an operating system known as "Windows", with versions starting at 2000.

    Daniel
    PS - apologies if you didn't mean what I thought you meant :)
  • by Daniel ( 1678 ) <dburrows&debian,org> on Sunday January 16, 2000 @02:13PM (#1367119)
    Wait for the official potato release -- the boot-floppies are still in progress (do they even work right now?) I think 'base via http' is going to be in the final version if it's humanly possible, from what I've heard on the list :)

    Daniel
  • I dumped core and broke my woody...
    --
  • I brought up this issue on a Debian mailing list some time ago, but objections were raised to the idea of overriding packages (which I called "fake installing"). I now think we need a more fundamental solution. We need a distribution-independent install system that can adopted by program authors who distribute original packages (whether in source or in binary form). Distributions could provide their own versions of software while allowing users to replace these with whatever version they want, all without confusing the distribution's package management frontend.
  • And to criticize without trying to fix it yourself is the very definition of l00serdom. 100s34! U 4 n07 krAD!! First Post!
  • Bah. Debian was known for having a great installer back when Slackware was king. It's why I switched after all. They're not being elite, just resting on their laurels. But then, Corel has one of the easiest installers, and being Debian-based, I could hope that the Debian mainstream will just adopt it. The QT package selector really puts dselect to shame too... but I wish it was based on gtk instead.
  • The 586 compilation crap that Mandrake spouts is such bullshit. It gets you about 10% improvement in speed at most. Talk about hype.

    Hmm.. so you would rather NOT have that 10% increase? What, you're too proud to take better advantage of your processor? Come on... haven't you ever felt that you were getting slightly cheated by installing RPMs built and optimized for the 80386 rather than your 80686?

    --

  • A "stable" release is thoughly tested, sometimes TOO thoughly tested =) But when you have something that's critial on being rock stable, these are they way to go to start. And if there is a program that you need a later version because of mroe functionality, you can do that too.

    A Redhat release is just as stable as a Debian release. The reason that Debian takes so much longer to release is that they include many more packages. That is good because you can find the packages you need on the CD, without the need to retrieve them via rpmfind. But I think that most people would give that diversity up to have more up to date packages.

    It's also not true that you can just grab an updated package if you need it. Any current Slink user can tell you that. Package maintainers tend to make updated packages just for unstable, since that's what they run.

  • > Yes, but it lists the packages this package
    > depends on, not what packages depend on it.
    > I want to see what I can remove without causing
    > a cataclysm :)

    apt-cache showpkg packagename

    look for the Reverse-Depends section
  • > most major distros are at ~6.x, nuff said.

    Nuff said about you, I'm afraid.

    When Solaris went from version 2.6 to 2.7, they decided to instead adopt 7 as the number of the version.

    Windows NT has version 4.0 and Sun was afraid that clueless people would assume that NT was better because 4.0 is bigger than 2.7

    Real Managers of course know that NT is a better server because it also run MS Office, which they (think they) know.
  • Until now, I used to have a fresh potato every morning when I came in to the office.

    Soon, I'll have a woody every morning after I come in the office. It sounds very exciting!
  • The last time I looked, the Debian pcmcia-cs package was built in synchrony with the kernel package. That means that when Debian builds a kernel package for 2.4, you'll get pcmcia-cs with it. I don't run the other stuff you mentioned here, and thus have indeed not tested it. The systems here are pretty generic server/desktop machines with a DSL connection and an external router.

    I'd assume those facilities are significantly changed from 2.2 to 2.4, and thus you will have to get new packages for those with a new kernel package as well. Given the way that Debian works, that could be an automatic upgrade: select the kernel and the other stuff comes in too.

    Thanks

    Bruce

    * ISDN
    * Anything NAT-related (the ipchains -> netfilter transition)
    * PCMCIA-CS stuff
    * All the IP routing stuff

  • Geez. Given that it's a free software product I'd hope you could get it on your system even if nobody packages it for Debian.

    It appears they are making changes that will let them admit new maintainers again. A lot of previously manual processes for managing maintainers seem to have been automated recently.

    Thanks

    Bruce

  • I am running kernel 2.3.36 at the moment on my dual-processor system, and 2.3.31 on a monoprocessor. I've also tested the release kernel, of course. The development series of kernels build and run fine under the Debian distribution, any changes needed to support the new kernels and symmetrical multiprocessing already seem to be in place.

    Thanks

    Bruce

  • by Bruce Perens ( 3872 ) <bruce@perens.com> on Sunday January 16, 2000 @01:49PM (#1367134) Homepage Journal
    I would think that people who comment on an industry where the only continuous theme has been "nothing lasts forever" would at least see the stupidity in "free development always anything."

    You touched on the point without seeing it. In a world where we're used to nothing lasting forever, wouldn't it be nice to have control over how long things last?

    Free software gives you that. As long as there are a few people interested in running it, there is sufficient force for it to be maintained. You don't have to put up with some marketing department discontinuing your favorite product.

    Thanks

    Bruce

  • by Bruce Perens ( 3872 ) <bruce@perens.com> on Sunday January 16, 2000 @07:20PM (#1367135) Homepage Journal
    You don't have to get rid of dselect (although I hope you will eventually want to). It's only the front-end of the package system. I think Storm and Corel both wrote their own front-ends, too. As far as I'm aware they all work with the same backend.

    I'd like to see more work on gnome-apt. A panel full of check-boxes is all you'd really need to set all the flags that dselect manipulates. The calls are there in libapt.

    Thanks

    Bruce

  • by Bruce Perens ( 3872 ) <bruce@perens.com> on Sunday January 16, 2000 @10:24AM (#1367136) Homepage Journal
    Debian "potato" runs Technocrat.net, perens.com, linuxvc.com, and my other sites. Although the web sites need the usual content management, the systems pretty much manage themselves. I've been doing an upgrade to the latest "unstable" version over the net every few days for the past several months, and the result has been admirably stable. Any failures around here seem to be problems in the PC hardware.

    There will doubtless be some humor around the code-name of the next unstable version. You can refer to downloading it as "getting a woody" :-)

    Thanks

    Bruce

  • by roystgnr ( 4015 ) <`gro.srengots' `ta' `yor'> on Sunday January 16, 2000 @10:26AM (#1367137) Homepage
    In the interests of collecting all the flood of "look, beavis, he's anticipating wood" jokes in one place, and simultaneously preventing the uninterested from having to read all of them, I request that all such jokes be submitted as replies to this.

    Thank you for your consideration.
  • by Morgaine ( 4316 ) on Sunday January 16, 2000 @04:01PM (#1367138)
    Given the pedigree of Debian, I'm a bit bemused at my own experience with it around the time of the hamm/slink transition. After many years of running various RedHats and a couple of years of Slackware prior to that, I didn't expect many surprises. In fact, I expected even greater stability, if that were possible, because of that super pedigree thing (not really possible, since I never had any instability nor any other trouble with RH, but I expected good things anyway).

    Alas, I persevered for 4 weeks during which I had to update numerous libraries (some repeatedly) in order to get Netscape and other quite normal stuff to work, always following the appropriate installation procedures for the item in question. Towards the end of this period, things got so bad that not only would Netscape no longer work properly, but the GIMP wouldn't come up at all. In utter frustration, I dumped the whole lot and went back to RedHat.

    I have no idea what went wrong but it did, badly. This doesn't concern me too much personally (I'll try again when potato is released), but I can't help wondering how Linux newbies are coping with Debian, as opposed to Debian newbies that are fully-fledged Unix old-timers. If I managed to screw it so thoroughly then there must be quite a bit of rope available for hanging oneself in the distro.

    [Yes, of course it was all my fault. I'm merely wondering how it was possible for it to happen at all, against a backdrop of more than just a little experience and a total lack of such problems with other systems, spanning Linux, many Unixes, and BSD. Very bemused.]
  • In fact, I've been using the 2.2.x kernels with Debian 2.1 (Slink) since May. (Which is when I first installed Slink). Works fine.

    Note that kernel 2.2 was a huge change compared to 2.0. On the other hand, 2.4 is more like an incremental release (don't forget that 2.2 was released only a year ago). So Potato and the Penguin should live happily together ;-)

    ___
  • Can somebody please explain what's involved in the ftp install? I downloaded the rescue and root disks, hoping that will work but it didn't. I got to the point where it asks where to install the system from. I select netfetch but it fails. It didn't even ask me for the NIC driver yet! What am I missing?


    ___
  • Aww, c'mon, give dselect more than just one try. I hated it at first, but after I learned the basic keystrokes I started to actually get the hang of it, and after learing the advanced keystrokes I've grown quite fond of it. It's much easier, IMO, to deal with dselect and see exactly what's going to change and what needs downloading and explicitly state which packages shouldn't be upgraded unless necessary than to have to deal with apt or dpkg on the commandline and take lots of leaps of faith.

    I use dselect almost exclusively now, especially when doing updates (so that I can hold packages which I don't really need to be upgraded, rather than having to do a 100MB download once a week).
    ---
    "'Is not a quine' is not a quine" is a quine.

  • Second, this isn't as much of a problem as you think, as long as you aren't being charged for modem time and/or bandwidth.

    I'm in England, we have metered local phone calls. Any time my computer dials online, I am being charged. To pay for (at a guess) a day or two of solid online, slowly grabbing new debs, would cost about an order of magnitude more than a CD of the same files.
  • shouldn't that be

    :set flame
    aBesides, real men use vim. :-) [esc]
    :set noflame
    :x
  • by Julian Morrison ( 5575 ) on Sunday January 16, 2000 @12:30PM (#1367144)
    It's a cool idea to say "grab the CDs of the (heavily dated but rock stable) release version, and tell apt to download the upgrades" but when most of the packages have gone through several releases, this more or less means downloading the OS from scratch. Trivial on a T1, non-trivial on a modem.
  • Not going to go into too much detail, but every day is a new day, or was with potato. One day you dist-upgrade and everything is broken, the next all broken packages have been patched. Its a day to day war when you run the unstable line, once you get everything (the bare base) rocking and rolling, the rest is pretty easy. I deffinitly don't recommend unstable releases for those who don't know how to hack a package to fix it themselves. It is however good to note that a new stable branch is up and running, my stable slink hasn't had an upgrade in months, however my many "unstable" boxes run just fine with potato.

    --Malachi

  • Since we don't actually sell our own CDs, there's no real point in us producing the CD images ourselves.
  • Upgrading from 2.0 to 2.2 should be much easier than from 1.2 to 2.anything, because you don't have to deal with the libc5->libc6 upgrade. Just running apt-get update; apt-get dist-upgrade should do most of the hard work for you.
  • I've been running potato for some time now, and I'm eagerly anticipating woody, the next unstable release.

    Erm, why exactly? I find it interesting that people rush to install the latest release of a distribution. Surely you can keep your packages up to date in the mean time? Why exactly does installing the latest release improve your system?

    I don't actually use a distribution, having compiled everything on my system myself. But if I did, I certainly wouldn't want to install something over my carefully crafted system. What would be the point?

    "Sir, I'd stake my reputation on it."
    "Kryten, you haven't got a reputation."
  • I agree wholeheartedly. I've been using Slack for about 4 years, and I love it. Just tell it where to install, what packages to install, hit FULL, and in about 10 minutes you have a functioning Linux system. I've never had a problem with Slackware that couldn't be fixed very easily.

    -- Give him Head? Be a Beacon?

  • "Woody is as hard as a.... "

    Frozen Potato?

    -- Give him Head? Be a Beacon?

  • I used to have a server named "Woody" where I worked. Despite all the obvious potential, I didn't put two and two together until one fine day, when, after a brief outage, I announced brightly: "Woody's back up!"

    I'd also like to point out, on a political note, that Al Gore may have invented the internet, but he's not getting the uptime that Bob Dole gets, with his woody. If I were running Woody, the box would HAVE to be named "Viagra".

    "Moderation is good, in theory."
    -Larry Wall

  • by HomerJ ( 11142 ) on Sunday January 16, 2000 @11:14AM (#1367160)
    The one thing that I've thought that separated Debian from the rest was not how SLOW the releases come, but how quickly they come.

    A "stable" release is thoughly tested, sometimes TOO thoughly tested =) But when you have something that's critial on being rock stable, these are they way to go to start. And if there is a program that you need a later version because of mroe functionality, you can do that too.

    Tou can just as easily update packages buy pointing to "unstable", or now "woody". I can get updates to programs AS THEY ARE RELEASED. I don't have to wait for the distro to update everything themselves every couple months. Or if I really need something, hunt down a package, or get teh source and compile myself. I can just type "apt-get dist-upgrade" and my system is the latest it can be.

    And with the large number of packages, I can be sure that whatever piece of free software(speach and beer), that they will ALL update with that one command. And I can rest assured that although I didn't compile that myself, it's not only a safe program to run, but it's configured to correctly work on my system. How can you go wrong? The more packages the better.

    So, waiting for a release for the most part is a moot point. You can install Debian whenever you want, and have the lastest of everything, or have something that's thoughly tested(MUCH more then other distros). And, "unstable" for the most part, as alot of people will tell you, is alot better then other distros .x releases.

    Just one thing though, Debian "stable" releases change so much from .x release to .x reelase, maybe they should just use whole numbers for release versions?

  • Slackware is, IMNSHO, one of the easiest distributions to install - simply because it's very, very hard to get yourself into a situation that you can't get out of.
    I've had RH and TurboLinux (bletch!) stop in mid-install more times than I can remember. Debian took me forever to figure out (this was, admittedly, the 1.3 release, I believe). The graphical installers of the latest distros just annoy me. But Slackware works every time - and there's always some way to shoehorn it onto whatever hardware you have.

  • I'm running Slink with a 2.2 kernel right now. Had to replace a very small number of tools that were kernel specific (xosview, for example).
  • As a long-time Debian user myself, I think that it's great that potato has finally gone into release after so many delays, but it looks to me like the exact same thing as last year is happening: slink (debian version 2.1) was released in early march, with the 2.0 kernel, even though the 2.2 kernel had been available for some time.

    Considering that the 2.4 kernel should be out in the near future (another month and a half or so) and the freeze is quite likely to last at least that long before a release is made, how long before debian catches up to the newer kernel series?

    Will there be an updated potato using 2.4 after the new stable kernel is released, or will we have to wait another year to catch up again?

    --Cycon

    (Incidentally, I have been using potato as the OS on my primary without any problems for months now, but it's the servers that I have to manage that I'd rather see kept up to date...)

  • by Cycon ( 11899 ) <steve [at] thePr ... lAmateur DOT com> on Sunday January 16, 2000 @11:11AM (#1367173) Homepage
    You don't actually run a system with the vendor-provided kernel, do you? I have 2.2.13 running on slink and potato systems just fine -- in fact, the potato system is using 2.2.13 with the ext3 patch.

    Of course compiling and replacing the distribution kernel is non-issue, but the problem with having an entire distribution released with an older kernel is that you lose the ability to add in and use certain features that are only available with the new kernel.

    For instance, a linux firewall is controlled by ipfwadm for the 2.0.x series kernels, ipchains for the 2.2.x series kernels, and there will be a new system (whose named elludes me for the moment) for the 2.4.x series of kernels. In order to administrate a newer kernel you need different tools, and therefore different packages.

    A better example perhaps would be USB support in the 2.4 kernel. With a release based on the 2.2.x series of kernels you lack USB support for items which may be of use during an install -- such as the keyboard, or mouse (for setting up X graphically). I may be wrong, there may be a patch for USB kerboards under 2.2.x, but I think you get the idea of where I'm going by now.

    Simply put, I by no means wish to critisize the debian project for any issues that have aroze in getting potato out the door, I think everyone there is doing an outstanding job, considering the volunteer-based nature of the distro (as opposed to the corporate-funded efforts of Redhat, SuSE, Caldera, etc.) -- However I *do* think that having the latest kernel permits certain conveniences as far as default packages and installation set-up goes.

    --Cycon
  • It's not a contender for proprietary distributions such as Red Hat

    What, exactly, is proprietary about Red Hat? Everything they do is GPL'd back into the community. Do you mean more *comercial* distributions?
  • by platypus ( 18156 ) on Sunday January 16, 2000 @10:43AM (#1367183) Homepage
    "My woody has an uptime of 107 days"
    or
    "My woody never goes down"
    or
    "We offer 24/7 support for your woody"

    oh well, you asked for it...
  • Thats why there are a bunch of distros. If you want an easy installer, use one of the distros that comes with one. Me, i like dselect.
  • Well, the point that I was trying to make was that it is silly to talk of absolutes in the computer world, because the whole industry basically reinvents itself every couple of years. That is how the industry survives, that is how technology progresses, and that is why computers are such a vital part of the world today.

    Also, we already have the ultimate control over how long things last. The only reason that things change so much is because people continually clamor for specific technologies. Technologies that we like, stay around. Those that we don't, never make it, whether they are good or bad, open source or proprietary. That being said, free software dos increase the granularity of the decision process, from one made on a macro level to one made on a micro level.

    Finally, it is very, very silly to say that free software always leads to a better product, which was what the original poster wrote. Just because I have control over the product (which I agree is a great thing) doesn't automatically guarantee that the product is better.
  • my reply is always the same: i should not have to "learn to install software" or "learn a package manager" -- in my opinion, these are things that should be essentially transparent to the enduser.

    ITYM "end-luser".
    Well said those colleagues of yours! Plain and simple: if you are unwilling to learn how to use something, and properly at that, there's nothing we can (or should) do for you, so don't waste our time and go back to pestering M$loth Support.

    Seriously, there's nothing that gets to me more than unwillingness. Inability, need a helping hand, those are FINE by me, and will get all due sympathy. Unfortunately, unwillingness also gets due sympathy too - nil!
  • I wanted a woody, but all i could get was slackware. My girlfriend was really disappointed...

  • Anyone notice? Potato is not only release 2.2 of Debian GNU/Linux, it's also the long-expected version 0.3 of GNU/Hurd (the first of Debian GNU/Hurd). Check the binary-hurd-i38 6 [debian.org] directory. Admittedly, many (if not most) Hurd deb packages are actually binary-all packages (and some are plain useless under the Hurd) — one Hurd developper jokingly said the Hurd would take its revenge by committing a lot of Hurd-specific binary-all packages.

    True, the Hurd is still far from stable now (and moving this tree from frozen to stable will sound something like a joke), but this is an important landmark nonetheless.

  • by Overfiend ( 35917 ) on Sunday January 16, 2000 @11:58AM (#1367206) Homepage

    the latest Xfree86 packages (3.3.6) for potato seems to be broken, at least in my system... all fonts are screwed up, and that makes X unusable.

    This is the first I've heard of this problem. I've gotten enough feedback already on the 3.3.6 packages to know what the common problems were, and this is the first I've heard of any font trouble. Please file a bug report describing the problem. How exactly are the fonts screwed up? What font packages do you have installed? If you can help me to find out what the problem is, then I can help you to fix it. It could be with your system, or it could actually be a bug in one of the X packages. If the latter, then the sooner you report it, the better, and Debian 2.2 will be improved for everyone.

    Branden Robinson, Debian XFree86 package maintainer

  • by coyote-san ( 38515 ) on Sunday January 16, 2000 @11:57AM (#1367208)
    One of Debian's primary goals is system *stability*. This is boring for the technically competent home user, but utterly critical in the enterprise.

    Potato will lose little by not providing the new kernel by default - it is easy to upgrade your system later. However it keeps a kernel with a year's worth of field testing on it. Bugs undoubtably still remain, but it will be many months before 2.4 is as stable as 2.2 today.

    The same thing applies to XFree86 4. By staying with the current XFree86 3.3 version Debian will lose some new features, but it will have a well tested X subsystem. If things go well people can upgrade later, while corporate users aren't affected by 4.0 (relative) flakiness.

    Finally, an analogy I often use is to hiking gear. The whole purpose of hiking gear isn't to "look cool" (although that's always nice), it's to get me into the remote backcountry *and back.* That's why I might test out new gear on local trails, but I use ratty old gear when I'm going to be many hours away from help. The cost of a shoe falling apart isn't $100, it's a bloody foot torn to shreds by hiking barefoot in the Rockies for miles, so I stick with things I know are reliable even if they're slightly outdated.
  • I truly commend Debian for keeping with a good versioning system. They've kept with a good system while others such as SuSE, Red Hat, Mandrake, Slackware, etc. have crept up to such high obscene numbers as 7.0. It disgusts me ;)

    Chris Hagar
  • I've been using debian since bo (1.3), and found it even then, having never sat at a linux console before (though i'd had shell accounts on slack for some time), it was still relatively easy to install. At the time I was doing it with a friend, as I was advised and advise myself, never install linux alone the first time. apt was introduced in hamm or retroactively in slink, i can't remember. (i went straight from bo->potato after being lazy for a while, with apt.)

    I find dselect/dpkg and now apt to be a very easy, self-explanatory set of programmes. But linux itself isn't yet for the clueless. You need to have some understanding of computers before you install it and that won't change for probably another year.

    RedHat attempts towards it, but its too difficult in redhat to upgrade and install packages and dependencies for new users who've never heard of freshmeat.
    #include <signal.h> \ #include <stdlib.h> \ int main(void){signal(ABRT,SIGIGN);while(1){abort(-1); }return(0);}
  • I've been trying to mess around with potato on and off for the last few weeks and have had nothing but problems getting it installed, despite the number of people saying things like "I've been running potato for months with no problems..." Things like broken package dependencies, inconsistent Package files vs. what's actually on the site, etc. Only just the other day did I manage to actually get a potato installation to complete successfully, and apparently it's because the developers were preparing to freeze it...

    I've been wanting to play with Debian for some time (I usually run RedHat because it stays fairly recent and usually works) but running slink was like being stuck in the stone age. I hope the Debian fellows have some kind of plan for more frequent updates, or at least more in line with the rest of "the Linux world." (i.e. not having your stable distro using Kernel 2.0 with glibc 2.0 when 2.2 and 2.1 have been out and stable for almost as long as your distro.)

    -=-=-=-=-

  • The Debian community is hopeful that this will be a nice big woody.

    Since it's unstable you may have to play with your woody before it works.

    What'll they do when their woody freezes?

    Is that enough?

  • > Will there be an updated potato using 2.4 after
    > the new stable kernel is released, or will we
    > have to wait another year to catch up again?

    Well the whole point of the freeze is to lock
    things in for testing. Moving a new kernel in,
    after the freeze, would defeat the whole purpose
    of the freeze and stable.

    AFAIK Debian policy is ONLY to update stable
    for security fixes.

    Of course, unstable is always available and anyone
    who uses potato should be able to download a
    woody kernel package and install it with no
    fuss. Unlike the old 1.3->2.0 jump, there should
    be no huge, distribution-wide differences so
    packages should be compatible.

    Personally, I compile all my own kernels anyway.
  • I remember them saying in a slashdot interview [slashdot.org] that they were going to implement a new system of keeping packages in stable release up to date with the release of potato (question #5 in that interview). Does anyone know what the status on that project is?
  • The problem I see with the debian version numbers though is that they can get mixed up with the kernel version. Or atlest that happened to me. But I like low version numbers much better than the big ones.
  • Here's what I've been doing, and it's worked great for me on every machine so far.

    I install the base system as slink, usually from floppies (many machines don't have CD-ROMs, because they really don't need them). I go through the whole config. process as usual, except that I switch to a virtual terminal to use fdisk instead of cfdisk.

    At the point where it first puts me into dselect, I immediatly quit. I hate dselect, and have only tried to use it once...never again! :)

    The first thing that I do is to edit my apt sources file to use the FTP links, and also to include non-us and KDE. Of course, I also change it to use "potato" instead of "stable".

    Then:

    apt-get update
    apt-get dist-upgrade

    This will take a while :) I then apt-get a few very important packages: less, compiler, assembler, and console-apt. Console-apt is invoked by using "capt" at the command line, and it's a million times better than dselect. Hit "?" if you need to know the key commands.

    This system has made Debian installations very easy and fun for me. Every now and again, I do an "update" followed by "upgrade", to get all the latest packages.

    I hope that it works for you.
  • by autechre ( 121980 ) on Sunday January 16, 2000 @11:04AM (#1367258) Homepage
    It's not really a matter of "installing a new system". RedHat gives you this feeling by having you shutdown your computer, boot from the new distro floppy, and do an "upgrade install". And it's certainly a lot better than, say, installing Win98 as an "upgrade" to Win95.

    With Debian, the difference in which version you use is in which FTP (or HTTP) directory you choose for your package source. To "upgrade", you simply change your /etc/apt/sources to point to the new FTP directory. Now, whenever you update your packages, you'll get them from the new directory. It's a much smoother process than anything else I've ever used. This is a testament to its great package management system.

    When Debian upgrades a package, if it notices that you've changed any files (such as edited configuration files, which is to be expected :), it asks you:

    1. Keep your version of this file? (default)
    2. Install the version from the new package?
    3. Show the difference between the 2?

    This is only a small example; it's really quite nice. Debian is also nice to use in the same manner as you (eg, install the base 28M system, and compile everything else yourself).
  • by DrToxic ( 137937 ) on Sunday January 16, 2000 @01:00PM (#1367270)
    Lurking behind every Red Hat site is a Woody user.

    HEADLINE: Woody penetrates server market, Microsoft falls flat.

    For the first time ever, Finnish Wood is better than Norwegian Wood. (With apologies to Linus) :)
    [Hint for those under 30: Look at http://rmb.simplenet.com/publi c/files/faqs/said.html [simplenet.com]]

The best defense against logic is ignorance.

Working...