Slashdot Mirror
Guessing Linux 2.6.0 Release Date
thorgil writes "Guessing about the linux-2.6.0 release date is hard, but here is a new angle (pseudo-scientific): I made a graph (gif) based on errors/warnings from John Cherry's (OSDL) compile statistics for linus' linux bitkeeper tree.
My guess is around 12th October, 2003. What is your guess and more important, why?"
is that you have way too much free time on your hands.
What is your guess and more important, why?
My guess is someone has a little too much time on their hands.
Why? Well, take a look at this.
September 11th, so the Linux Fraternity can 'honor' the brave freedom fighters and their stand against the evil corrupt capitalist empire.
It's ironic that slashdot would run a story about linux today at all. But what really surprises me is that Slashdot would continue operation today, even though they allegedly support the Online Demonstration Against Software Patents.
/. staff to immediately shut down operations and support the
I would urge the
demonstration, unless they really don't care about open-source software at all.
Maybe a great open source businessmodel?
1) Do free stuff.
2) ?
3) Call your local bookeeper and gamble on kernel 2.6.0 release-date.
4) Profit!
Don't you have better things to do with your time then plot BS stats?
I think someone needs to take up masterbation as a hobby.
To quote a famous game developer: "When it's done."
The question that really count is when will the first stable version of 2.6.x be out. I mean 2.6.35 or such...
Works for me. Hail Christopher Columbus! Hail Linus!
i know the date i know the date...
bash-2.05a$ date
Wed Aug 27 05:38:58 EDT 2003
But I don't think the "it compiles, let's ship it" is the criteria for releasing 2.6.0 A better way is to look at Andrew Mortons must-fix list. When most items are fixes, it can be released. ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/ must-fix/must-fix-6.txt
Should it be a linear best-fit? I'd be guessing that the number of errors/warnings will only approach zero? Much like tracking bugs.. On second thoughts, errors will more than likely hit zero but warnings we can live with.. :)
Anyway, interesting stuff
Is that your hero is probably Louis Skolnick.
I've just installed Linux. Does anybody know where I can download versions of Internet Explorer or Microsoft Word for this fine operating system?
If we're taking cues from Duke Nukem Forever and 3D Realms, then this new version will switch between using an OS2, Windows 98, Linux, Windows 2000, Mac and Linux Core before being released in 2068.
Oct, 12th is in about 6 weeks. So, because every IT project takes twice as long as you think, my guess is around Nov, 30th.
....Excuse me, but
You should be asking SCO when they will file their injunction to stop 2.6 from being made available anywhere except sco.com. I suspect they will need about 5 minutes to verify that their code is still in there, and after that you will be able to purchase 2.6 on the SCO website for $799. Hurry though! This is only an introductory price offer!
For those of use that are running the 2.5/2.6beta kernel, what should we do when we do find bugs?
Since when do compile time errors and warnings reaching zero mean that there no more bugs in a program? Most bugs are those the compiler doesnt complain about.
What are you waiting for?
This should have been a poll. Now, it just leads to endless ramblings.
I'd attempt the same thing to predict Longhorn's release, but the graph is going in the opposite direction.
So now we can start keeping eye on the schedule !
I can already see the Washington Post's spaculative banner headline:
"Linux Major Update late for two weeks ! What's up ? Is Linus falling behind ?"
This is by far and away one of the crappest submissions I've seen in a long, long time. ./ needs to get some form of quality control back, pronto.
slainfu
"I can't be a terrorist if you're sucking my bum."
Give me my daily dose of SCO!
this really reminds me of the 'wheel of fish' ...
q> when is linux-2.6.0 released?
a> ummm.. blah blah
q> absolutely wronggg! youre so stupiiid!
class he-man extends man!
Fair enough. My guess for the release date?
CowboyNeal.
Does it still use the SCO licensed code in it ? Or will it be removed ? or does the kernel will be rewritten from scratch ?
Endless ramblings?
But we wants our endless ramblings. This is slashdot.
Otherwise, I might have to do some actual work.
I don't have one
PROGRAMMERS DRINKING SONG:
...
99 little bugs in the code,
99 bugs in the code,
fix one bug, compile it again,
101 little bugs in the code.
101 little bugs in the code
(Repeat until BUGS = 0)
!
But about a month from now Linus will sit down to drink a cup of tea. When he finishes, he will proceed to pick his nose.
He will then reflect upon where he has been, the journey that has brought him along this path, and think ahead a little about where he'd like to go.
At this time the magic "penguin pixie dust" will be ready. He will then sprinkle it upon the CDR of people's contributions to the kernel.
At that time kernel 2.6.0 will be ready for us to excitedly embrace!!
Take the cheese to sickbay, the doctor should see it as soon as possible - B'Elanna Torres, "Learning Curve"
Because I own the source code.
Any release by any other organization is derivitive, unauthorized, malicious, capricious and bubblicious.
Any organization caught using an unauthorized release of the kernel will be billed at $700,000 per cpu, and the executives of the organization will be ordered to bend over and grab their ankles.
From past experience, this is totally feasible. So many of you execs have done this already. No, really.
Darling.
Here is my guess :
:o)
just after the release of Duke Nukem Forever
... according to your approach, MS Longhorn shall never be released. Your theory works real fine!
They already HAD 2.4? Should keep my eyes open. Darned.
The Andrew Morton must-fix list dates back from May! No use...
I'm in a Unix state of mind.
december 25 2003 (merry christmas)
"Testing? What's that? If it compiles, it is good, if it boots up it is perfect." -- Linus Torvalds
So now we're guessing the release date based on when it will compile without errors, eh?
burnallgifs.org
I would urge the /. staff to immediately shut down operations and support the
demonstration, unless they really don't care about open-source software at all. I think you'll find that the order of the day is shutting down other websites, not their own. Unless they ran a story about their own site in which case it would get slashdotted.. but that couldn't happen because then there'd be no site to..... recursive thinking.. brain.. hurting..
that's right. the phonIE payper liesense stock markup hostage scam is nearly overt.
it's hard to imagine anybody paying money for that infactdead BugWear(tm) crud peddled by the felonious kingdumb.
no matter. more breathing. consult with/trust in yOUR creator. vote with (waht's left in) yOUR wallet. join the planet/population rescue program. that's the spirit, moving you.
the daze of the georgewellian fuddite southern baptist freemason theft/murder brotherhood are #ed.
pay attention. it's quite affordable, plus you could help to save yourself/all of us, from the corepirate nazi billyonerrors softwar cesspool.
for each & every harmed innocent, there is a badtoll that must be repaid by you/us. the felonious execrable will not be available to make reparations.
as always, lookout bullow.
When the kernel itself is declared "released" is irrelevant to most people. If you really want the latest and greated, you can always download whatever the current version is, whatever it's called, and use it.
What's important is when most distro companies (other than bleedinge edge Gentoo and "we don't need no steenking 2.x kernels" Debian) will start building their distributions around 2.6-final instead of 2.4. For that, it's quite obvious at this point: The spring refresh cycle. (The fall cycle may have a few optional pre-release kernels, but the real action will be the spring.) Sometime in the April timeframe we'll see Red Had, Mandrake, and SuSE releasing 2.6-based versions. Hopefully they'll also have funness like KDE 3.2 and so on by then, which are just as important to most people.
When Linus says "ok, I'm done, let's work on something else" isn't important. When Red Hat says "we'll give you a support contract on this now", THAT'S important.
--GrouchoMarx
Card-carrying member of the EFF, FSF, and ACLU. Are you?
Maybe I do... Oh wait... Yeah I do...
Warning: This sig contains a small bug. ==> *
With Duke Nukem Forever on the other disc.
When I am king, you will be first against the wall.
I don't think it will happen during the next 6 weeks, there are still some major things to be done. IDE still does not work as module (some circular dependencies in symbols), ISDN is still somewhere between the no longer working old model and the not yet complete CAPI support, just to name two.
seriously... that shit doesn't fly at most commercial software companies. why are people checking in code with compile warnings? why aren't they compiling the code and fixing the problems before checking in the code?
Five bucks on November!
Lisp is the Tengwar of programming languages.
Because that's my birthday!
Beeep!! wrong!
Guess again?
Warning: This sig contains a small bug. ==> *
follow the documentation in the kernel source on how to submit bug reports.
It will be the 21st century..
(I want to die quietly in my sleep like my Grandad - not screaming in terror like the passengers on his plane..)
"You lied to me! There is a Swansea!"
I don't worry. Mandrake Cooker is a really under estimated "bleeding edge" distro. After all, I'm currently running 2.4.22-0.8mmdk, and its a lot better than the 2.2 kernel that shitian is using.
"When it's done." I think this is a good "guess" for two reasons:
a) it's 100% accurate.
b) It didn't cost me precious hours of my life to come up with this answer.
I'll now continue to invest my time in more important stuff...like reading slashdot.
(Hey! They say it's "Stuff that matters!")
...is that the real date is 11th October 2003 because Linus wants to give me this so cool present for my birthday.
> Next bet: when will be 2.7 tree be opened?
;)
Perhaps after 2.6.0 stable is released?
If it takes a long time to get 2.6.0 stable developers will start to complaint that they are not allowed to make new features. Then there are 2 options: feature creep in the new 2.6 testseries (a new MM 8) ), or start a 2.7 tree. The thirth:
Linux is a waste of time!
Who cares when 2.6 comes out?
And.....what is this think called 'slashdot'? I was trying do some shopping on something called ebay, but couldn't remember their address. The search engine sent me here.
or some phonIE scriptdead corepirate nazi ?pr? ?firm? stock markup bootlicker
.asp for va lairIE's whoreabull pateNTdead PostBlock(tm) devise?, used against the truth/to protect robbIE's payper liesense stock markup bosses/corepirate nazi 'sponsors'. yuk.
that's right, after the walking dead finish exterminating themselves, & sadly enough, some of us, it won't take long to clean up this cesspool of greed/fear execrable.
we're calling it the planet/population rescue program (formerly unknown as the oil for babies initiatve).
the Godless wons are helping by continuing to show where their hearts lie.
what's wrong with folks selling their kode? if it causes convenience, & interoperates with all the other kode on the planet, we say, no harm, no foul, so long as you fail to employ gangsterious/felonious practices to asphyxiate the 'competition'. sabotaging your free version of anything is a tad dastardly. if there's value added, without FUDging up the compatability, we'll pay. same with music. no more gouging dough though.
fortunately, mr stallman et AL, etcetera, is now offering comparable/superior software, to the payper liesense spy/bug wear feechurned models, in almost every circumstance. there'll be few, if any more softwar billyonerrors, as if there's a need for even won. tell 'em robbIE. you are won of the last wons whois soul DOWt, right?
back on task.
what might happen to US if unprecedented evile/the felonious georgewellian southern baptist freemason fuddite rain of error, fails to be intervened on?
you already know that too. stop pretending. it doesn't help/makes things worse.
they could burn up the the main processor. that would be the rapidly heating planet/population, in case you're still pretending not to notice.
of course, having to badtoll va lairIE's whoreabully infactdead, pateNTdead PostBlock(tm) devise, robbIE's ego, the walking dead, etc..., doesn't slow us down a bit.
that's right. those foulcurrs best get ready to see the light. the WANing daze of the phonIE greed/fear/ego based, thieving/murdering payper liesense hostage taking stock markup FraUD georgewellian fuddite execrable are #ed. talk about a wormIE cesspool of deception? eradicating yOUR domestic corepirate nazi terrorist/gangsters will be the new national pastime.
communications will improve, using whatever power sources are available.
you gnu/software folks are to be commended. we'd be nearly doomed by now (instead, we're opening yet another isp service) without y'all. the check's in the mail again.
meanwhile... for those yet to see the light.
don't come crying to us when there's only won channel/os left.
nothing has changed since the last phonIE ?pr? ?firm? generated 'news' brIEf. lots of good folks/innocents are being killed/mutilated daily by the walking dead. if anything the situations are continuing to deteriorate. you already know that.
the posterboys for grand larcenIE/deception would include any & all of the walking dead who peddle phonIE stock markup payper to millions of hardworking conservative folks, & then, after stealing/spending/disappearing the real dough, pretend that nothing ever happened. sound familiar robbIE? these fauxking corepirate nazi larcens, want us to pretend along with them, whilst they continue to squander yOUR "investmeNTs", on their soul DOWt craving for excess/ego gratification. yuk
no matter their ceaseless efforts to block the truth from you, the tasks (planet/population rescue) will be completed.
the lights are coming up now.
you can pretend all you want. our advise is to be as far away from the walking dead contingent as possible, when the big flash occurs. you wouldn't want to get any of that evile on you.
as to the free unlimited energy plan, as the lights come up, more&more folks will stop being misled into sucking up more&more of the infant killing barrolls of crudeness, & learn that it's mo
Hofstadters law:
"Everything takes longer than you expect, even when you take into account Hofstadters law."
Douglas Hofstadter, "Godel, Esher, Bach", ISBN: 0465026567
Think I'll be forgiven for not realizing that was today? I expected OSDN to shut down, but no...
You can't judge a book by the way it wears its hair.
just in time for revolution(s) ..
I fuse with Mercer every single day...
... in all the vacation you mentioned, he is able to guess the correct 2.6 kernel release date.
".Sig Stealer" was here
How much influence has SCO on the developers, e.g. make them response to the SCO FUD instead of fixing bugs in the kernel? That's also a sort of "denial of service" attack.
Well dickhead, you can easily install a 2.4x kernel on that 'ancient' release called Woody. Do you actually read the install instructions?
What is even better Mr Mandrake Weanie is that you can just download the latest kernel source and compile it and then install it.
And fuck me you can even just uprade your whole release if ya want to. So much fud is spread about Debian.
Now when it's not released on October 12, the press will start writing about the "delayed" new version of Linux. Remember the pre 2.4 days?
all joking aside, I would guess likely early january , or late december more specifically December 31 or Jan 1st.
:)
Engineers generally don't like to remember when they released things. It's "efficient" to do it on month/year boundries. Think about the multiple times linus will be asked to reference this date mentaly, "what have you been doing since 2.6?", etc....
I hope that more work is put into the inital testing phase than what happened with 2.4.
However, that burden is mainly on US and not linus. Get compiling
didn't Linus said that 2.6 was being released when x86 code was stable?
And other archs maybe would have to wait some minor versions?
Considering this and the graph predictions, my guess is 3-4th week of September.
I'm a chainsmokin' alcoholic sociopath, so-ci-o-path
Rather than say that there must be 0 such compiler warnings/errors, I'd like to see what statistics would be produced if used on a 2.4/2.2 kernel. At least then we'll have something to compare the numbers to.
Ever since I've been using the kernels for RH 9, I've found I can't use my cd-rom drive because I get messages like "hdc: lost interrupt" after which the system locks up. This was no the case when I was using the 2.4.20 kernel (linus' tree). I have a hunch it's to do with IRQ's but have not the further technical knowledge to diagnose. Has anyone else had similar probs? Anyone know what I should do about it? (see below)
/proc/interrupts
Thanks to any help,
Tim. (tim_allen AT optusnet DOT com DOT au)
bash-2.05b$ cat
CPU0
0: 301781 XT-PIC timer
1: 1250 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 14 XT-PIC EMU10K1
4: 914252 XT-PIC serial
8: 1 XT-PIC rtc
9: 0 XT-PIC usb-uhci
11: 4 XT-PIC usb-uhci, eth0
12: 51452 XT-PIC PS/2 Mouse
14: 12074 XT-PIC ide0
15: 20451 XT-PIC ide1
I have hda on id0 and the cdrom (hdc) on ide1 along with my other hard drive (hdd)
I bought RHL 9 only to discover part way through the installation that my AMD K62/ FIC VA 503+ combo is too old to take that. I'm stuck with RHL 7. Now, we have another new kernel, and more tempting releases of distros on the way, leaving me in the dust. I keep wondering why RHL 9 detected everything, booted X, and allowed me to wander through the graphical install like a kid in a candy store, picking applications, making decisions, and then at the end, before writing all that to my partition, gave me the bad news. What kernel did they use for the graphical install? why couldn't I have RHL 9. This box would probably handle XP, but my wallet can't. Arrrg!
"I'll take Linux Kernel release dates for 200"
Sanity is the trademark of a weak mind. -- Mark Harrold
I'm with you, though. I think Linux and its users would be much better off if the developers imposed a bit more process on themselves, and didn't rely so heavily on the "keep tweaking and releasing until it seems to be right" model.
It really sucked last year when my 21st birthday was also on the Monday of exams week. OSU's present to me? The toughest exam (EE) I've had there yet, at 7:30am nonetheless. But don't worry, after that, the rest of the week was a blur.
Berto
Not that I think it's the greatest language or anything, but my experience with ADA was that vastly more stupid things that programmers (in this case me) do show up as compile time errors. Almost to the point where if a program compiled it was bug free. Of course it's still possible to have a logical errors, but whole classes of what would be run time errors in C are compile time errors when ADA is properly used with things like range checking.
How 'bout now?
How 'bout now?
How 'bout now?
How 'bout now?
How 'bout now?
I missed it....
If you do what you always did, you get what you always got.
It looks like SCO is being DOSed again.
Microsoft Windows runs on stress and frustration.
I'm going to guess it'll be delayed until the SCO code is publicly released so any problems can get cleaned up. Possibly in October we'll get a "gold level" release that would be the final kernal minus SCO fixes, that way if SCO loses it can just be rebranded without losing any worktime and if SCO wins the claim can always be made that as soon as the problem was shown it was fixed and never made it into the "final" kernal. Linus has been accused of being arrogant at times (mostly by folks with rejected code) but never accused of being stupid.
It doesn't matter what you wrap your emotions around, Reality is a brick wall specifically designed to scramble eggs
To quote a famous game developer: "When it's done."
Daikatana wasn't exactly the hit everyone was salivating over...
You can accomplish anything you set your mind to. The impossible just takes a little longer.
1. It will be released around Thanksgiving.
2. It will have a serious data-eating bug like Linus's other Thanksgiving kernels.
Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
Just glancing at the graph, it doesn't look like a linear curve to me. Is a least squares fit the appropriate tool for this? It appears to me like it is leveling out.
2.6.0-test* seems solid enough for daily use, although if you have a laptop with a Synaptics touchpad, there seem to be some problems with the driver for that (I've not been able to get mine recognized but I prefer the USB mouse anyway.)
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
I "fell asleep" last night. And in that sleep I was visited by three ghosts of linux. Well to make a long good story short and not as good, they told me that if i didn't change my ways and always use linux for everything then tiny Tim Torvolds would DIE.
That and 2.6 would be released on September 21, 2003.
Well.. maybe. Or Maybe not. But Definitely not sort of.
I like the the prediction approach. With more data and more advanced models this should definitely be applicable. Statistics can really be used for lots of stuff.
:-(. Clearly, at least two of the curves are nonlinear, or at most piecewise linear, and can thus not be well approximated by a line. Probably some kind of exponentially decaying model would be more appropriate, and also probably more intuitive since the amount of errors should be huge in the beginning and then decrease rapidly in the beginning and slowly at the end.
However, I don't think your predictions are correct
You're right, just because it compiles doesn't mean it's done, but if it compiles successfully for a while it does mean that not too much new is going on and it might be ready for a release.
All measurements of this kind have inaccuracies. Do you have a better one? If so, then let's hear it.
USB is still a bit flaky, anything using USB devio could have problems, and ISO transfers don't work.
The correct answer is, when we think it's about ready.
the 2.4 kernel still isn't "done".
thank God the internet isn't a human right.
is that this is a slow news day.
- It will be released when it is finished and not a moment sooner
- Complex systems that work,
These are good quotes... good wisdom but besides just applying that to the kernel development (and subsequent demands of release dates and more concrete info) you should remember how BAD Ultima Ascension was. Even if it was a standalone game, the bugginess, horrible gameplay, laughable dialog (and voice acting), non-immersive world (gee, I guess these NPC's really do just exist for my pleasure) and shallow, linear plot and story it would deserve perhaps a 3 (out of 10).always come from simple systems that work.
They never come from complex systems that don't work.
Being a part of the Ultima world and franchise it ranks at about a 2. (that includes a spanking for Origin/EA not learning their lessons from 8 as well). As being the Final and self touted "tier of loose ends" it deserves about a .5 for the way it mis-handled the plot and mysteries up to that point.
Oh yeah... did I fail to mention it took 6 years to make?
me too, btw
Based on the 2.4 experience with the memory mapper changing horses well after 2.4.0, I'd be careful making predictions.
Also, Linus is now full time at OSDL (+).
Also, Alan will be going back to school (-). Good for him, though.
I'll go out on a limb, though, and say
which is evidently Finnish Independence Day."Provided by the management for your protection."
i say early 2004, although the test kernels are looking quite good
I'd bet you could do this on one of those online betting sites. I guess you could use that graph to calculate odds for betting.
I don't know enough about the Linux dev process to comment on it, but in software I've worked on there's typically time tacked onto the end of the schedule to do performance testing and tweaking.
- First they ignore you, then they laugh at you, then ???, then profit.
That's good stuff, man! See, you think he's talking about December, but it turns out he means Decimal! HA! You can't make that shit up.
Fork, knife, spoon!
Take a close look. He uses Least Square, but really it looks more exponential, so probably the version will get very close to perfect, but they will NEVER release it
What Would SCO Do?
If he's ready by October 15th he should wait to release it then. That's doing to be a date of massive sucktitude. SCO raises their linux "prices" and Microsoft drops support for older MSN protocols and bans uncertified third-party clients. Also, it's my birthday and I want a good birthday present.
...all forms of online protest, including turning off your server to protest or boycott anything. If you shut off your server as a form of protest, then you owe me licensing royalties. If you run your server, well then you owe SCO royalties since they own all operating systems.
it should be either:
(Repeate until BUGS == 0)
('=' is an assignment operator, '==' is a comparison operator)
or:
while (BUGS > 0): sing(...)
I used to have a sig, but I set it free and it never came back.
That linear fit model is just plain wrong. Problem identification (and therefore problems fixed) are both non-linear in nature, for what should be obvious reasons. Three bugs, roughly three times the chance of finding one per unit time. Of course the kernel is divided into rough sections and those working on networking code are not likely to hack the vm, but this applies equally for each portion of the kernel.
d bugs / d time = bugs
(or if y = bugs and x = time)
dy = y dx
Solving this is left as an exercise for the reader.
I am setting up a market-based delphi poll to predict linux kernel releases. My partner, Admiral Poindexter, and I will be contacting a select number of you to participate in this endeavour. Please have $1000 ready to invest. BTW, if you have predictions on when the King of Jordan will be deposed or when the next terrorist strike will occur, we are interested in that as well. Thank you, and have a Total Information Awareness day.
My guess is that regardless of the state of 2.6.0, that RH X will ship with a 2.6 based kernel around Halloween. I base this on the fact that RH 9 already contains alot of 2.5 code which has been back-ported and the fact that RH usually issues a release around Halloween.
So, does the person who guesses closest receive a free copy of the 2.6 kernel?
cause its my birthday. As good a day as any.
Slashdot is corporate-owned. It's a business. It makes money. They're not going to shut down their business for a day when they could be posting more SCO, "Microsoft hole," anime, and amateur rocket stories.
"Sufferin' succotash."
The 2.4 kernels took 7 months to go from testing to 2.4.0. If the first 2.6 test kernel was in July, the first 2.6 kernel might be in Feb 2004.
- Simple Firewall and Proxy (yes, but I only have so many machines)
- Apache server, XML/App server, File server (fun stuff and dev stuff)
- Development, workstation and fun desktop (audio, video, games and testbed)
I have considered getting a very small (and cheap) computer that is a dedicated firewall with access control, dhcp and perhaps some throttling mechanisms in place... how much can I put into the kernel especially if it is diskless but uses flash? Sorry, just popped into my head after reading this.Never mind the release date! When are we going to see the next SCO article?
This sig no verb.
Just a suggestion
I think that FROZEN or just TESTING is a good label. However, we are talking about its eventual release not what it is now (2.6.X-testN (or PreN))
Cheers
The guy who took the time to make that chart is a fucking nerd.. and I thought I was bad..jesus..
Will wonders never cease?!
'cos It's my birthday! ;-)
NumDays = NumOpenBugs/(bugsClosed-bugsOpend)*time period
Very simple, and suprisingly effective for large projects where the bug finding and bug closing rate is very close to constant over a period of time (lets say a week)
So basically this says, that as long as your bug openning rate is higher than your bug closing rate, don't even bother predicting a ship date, but once you are closing more than you are openning - you can predict a date.
The nice thing about this is all though it is a rough metric, it tends to guess long - and it is something simple you can get any pointy hair boss to buy into (and even script it so that they can determine for themselves what the "ship day" is likely to be)
I have mod points and I am not afraid to use them
GIF? GIF? we dont need no stinkin' GIF image!
use PNG man!!! sheesh!
Here in the US, we have patents covering European protests... please report yourself to the police and prepare all your documents and paper trails to forward to the local US embasy.
Anyone who's taken differential equations will tell you that when the rate of change of a quantity depends on itself, then the quantity will change exponentially.
So maybe we should really be talking about bug "half life?" How long it takes for the number of bugs to drop in half.
Yes, I think a lot of things have been fixed or fixes are underway and mostly working.
And there are also some problems nobody wants to attack...
Gentoo was too incomplete for my taste. I use Debian (Sid/PPC and Sarge/X86), OpenZaurus, OpenBSD, and my own custom-made bootable Linux disc.
When I get a G4 or Sparc64, I'll give Gentoo another shot.
You can't judge a book by the way it wears its hair.
unless you run LFS.
Wasn't J. Pointdexter working on this problem over at DARPA? Creating a market of people betting on the next kernel release?
"I honestly would vote libertarian if their candidates weren't usually total cooks."--slashdot poster