Slashdot Mirror
Linux 2.2.5 Released
Insomniacs of the world unite: Linus has bestowed kernel 2.2.5 upon us. Looks as though some sparc64 fixes were applied,
some IPv4 and IPv6 updates were included. This should prevent lock-ups on sparc64 machines, hopefully. Don't know about ega fbcon, though.
Can't wait for 2.2.5ac1, though...PLEASE USE A MIRROR. Sorry to shout, but it's very important that the
files can be mirrored, and that the hardcore kernel hackers can get their patches.
This still is the dev branch for all practical purposes. At least until RedHat and Suse are shipping with it. :)
we must be cutting edge!
Patch, definitely patch. Grab Matt Welsh's Running Linux box, it's very clear, or read the man page, but definetly patch! You'll thank yourself for learning this simple command when you see how much time you've saved.
When I apply the 2.2.5 patch, it runs for a while but then stops with a:
patching file `drivers/char/stallion.c'
patching file `drivers/char/synclink.c'
patch unexpectedly ends in middle of line
patch: **** unexpected end of file in patch
Should'nt they be working???
Your problem might be that you didn't succeed in downloading the entire file. Check the size and/or try downloading again.
One should always be using the newest kernel :-)
At least there is not so many patches to apply, when you do it as soon as they appear.
Usually I don't upgrade until a few kernels later.. then its too late to patch (unless I want to download many patches).
Downloading many patches is still faster and easier than down loading the whole kernel. Just applying the patches one at a time from the oldest to the latest and then compile. Believe me, you will be pleased with the amount of time and effort you've saved
That's not unsettling, that's service. :)
2.2.4, the first 2.2.x release for Sparc, has
a serious problem somewhere that leads to a
complete lock up of the system - only a power
cycle clears it. With luck, 2.2.5 will fix this
for Sparc and Sparc 64 platforms.
A new update is good news - when was the last
time Windows xx was updated? It's not as if they
don't have any bugs to fix...
My suggestion is that you don't download the patches with Netscape. The annoying unzipping feature in Netscape doesn't seem to work correctly.
I'm all with you ... might as well, gives me someting to do when i am not compiling gnome libs, or a new gtk.... etc :)
I don't understand the problem here. My connection is nice and fast. I just download the kernel source in a minute or so and recompile. Does patching make recompiles faster? If so I'm definitely interested.
There's a script you know. It'll even patch multiple patches...
/usr/src
You bung your patches in
then from there run linux/scripts/patch-kernel
simplicity itself...
What was the biggest patch size ever for kernel upgrade (no including ac patches) ???
:)
timson40@bunt.com
Dark_Hour
too lzay for an account
ALSA! http://alsa.jcu.cz
Many of the people that download whole tarballs also scratch their previous sourcetree before unpacking and compiling the new one. Hence they loose all the .o files which were good from the previous kernel, and those have to be recompiled again. .c file changes, only that file has to be recompiled. So yes, patches to accelerate compilation as well.
This is not the case with patched kernels: if only one
I like good thinking, This was good thinking.
Hence I will patch!!
Keep up the goodwork. Linux isn't dead it just smells funny
They fix various error returns. If you have an
ES1370 but not CD audio, try setting the various
line inputs to record and turning them up. Not
all vendors put CD on the same input.
Right now I have tv on my cd input and the cds on
line in 1 and 2
I use two computers with USB, a Dell laptop for work and a homebuilt workstation at home. The laptop runs NT and the workstation runs Linux. It looks like USB isn't in *my* near future :|
Chris
mtnbkr@mindspring.com
Alan Cox has I2O mostly working.
Hi guys,
a -faster-kernel-since-two-months-!!!.
does anyone know how to make a 2.2.3ac4 kernel load my aic7xxx SCSI Module(without troubles)?
I have a nice hardware wich isn't FULLY Exploited yet (SCSI Drive 8GIG with lot of RPMs, CD-R, scanner) and I don't want to by a *NEW* SCSI
adapter..
BTW it does work with the precompiled kernel of RedHat 5.2 (2.0.36-7 if i'm not mistaken). Is it
my SMP (Dual PPro) the problem or what !?
A-guy-who-wonder-if-he-is-dumb-or-not-made-for-
I have also been having problems loading the AIC7xxx driver as a module.
With 2.0.x I used to get that it was loading the driver multiple times in a row (failing on the second time).
With 2.2.x It just hangs on resetting the SCSI bus.
When compiled in the kernel, it works without problems.
What's the deal with AC patches anyway? Does it includes a series of changes that is just being updated to the new Linus kernel or what? Where I can find more information on the 'static' code of AC patches? Thanks.
I wasn't specifically talking about one distribution over another, I just meant that even if the kernel itself is stable, it's quite a big job to get all the software around that kernel working properly, and it requires the efforts of the major distributions to go into a code freeze. Of course the kernel is stable for us early adopters who don't mind fiddling (in fact enjoy) and getting everything to work properly, but the very fact that we have to do all that stuff to make it work, gives it the flavor of the dev branch. :)
yea no joke, 2.0.x forever! ;)
and 2.0.37 is expected soon
Except my child doesn't have a birthday every other week...
Seriously, for all of us "lusers" out there who only have a 28.8 modem connection, please just downloade the patches off of a mirror. You are really wasting bandwidth, and making it harder for others to get in, when you download the complete source every time.
I'm holding off getting 2.2.5 because I haven't
been able to compile 2.2.3 due to the error:
"No module off found for kernel 2.2.3"
Anyone know what causes this?
I've updated two RH machines, one with 5.1, the other with 5.2 - not alot of work required. Some of the latest packages required building (as the rawhide site built them with glibc2.1) but the whole process was trivial.
Kendall Hunter
hunterk@sprocket.colorado.edu
As long as nobody knows about the bug it's as stable as can be. Every OS has hiddens bugs.
http://www.cheap-bytes.com
You can get RedHat 5.2 delivered in two business days for 7.14. It comes with latest kernels, gnome, kde, RedHat updates, and some other bonus stuff. You just don't get documentation or RedHat support.
Too late, MS already split up.
-SegFault posting AC from school
I'm not sure about the sparc64 platform, but
sparc has some lockup problems with 2.2.4
(probably sparc64 too, if I read the 2.2.5
change log correctly.) Certainly not production
quality yet, but it's getting there.
Compiling the kernel on a fast machine (e.g.
PII 266) only takes a few minutes, so it isn't
a problem. However, it takes forever on my
Sparc 20 clone at work, so it's a right pain
(but an important pain until the Sparc kernel
stabilises.)
If your current kernel is working fine, stay
with it and skip the next few releases.
6 kernels in 2 months. Oh, i'll wait for more changes. I think that there's no reason to release this 2.2.5 yet. Reboot your machines. I'll make my uptime grow with 2.2.4
6 kernels in 2 months. Oh, i'll wait for more changes. I think that there's no reason to release this 2.2.5 yet. Reboot your machines. I'll make my uptime grow with 2.2.4. It's like 2.1.x was (i never used this shit). One kernel per day adding some features and various bugfixes. WHEN 2.2.X WILL BE REALLY STABLE???
So, use 2.2.4. There's no reason to use 2.2.5.
You probably need to set some initialization stuff in /etc/conf.modules. I have the following lines to make my aha1520 SCSI and my (non-SCSI) SoundBlaster-16 work. There's more info in the Documentation/sound part of the linux distribution.
# Use these options when loading talias char-major-14 sb
options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
he SCSI module
options aha152x aha152x=0x340,11,7,1
# How to set up the SoundBlaster card
I'm running 2.0. something, but seeing as how it's the only version of the only one that can run on the same partition as windows (Zipslack) I don't really have a choice unless I want to blow $60 on partition magic
-Adam Sears (adamone11@@yeat.com)
Not Anonymous, not a Coward
Here is the contents of my /proc/pci file:
>SCSI storage controller: Adaptec AIC-7861 (rev 1).
> Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. Latency=32. Min Gnt=4.Max Lat=4.
> I/O at 0x9000 [0x9001].
> Non-prefetchable 32 bit memory at 0xe1001000 [0xe1001000].
But my adapter is a AHA-2940AU... Weirds messages.
Where is (are) the best how-to compile linux kernel tutorial(s) on the net?
Can you be a little more specific? When/where do you get that error?
You can also check out www.techni-cor.com/redhat
This release is a bzip2 file? What do I need to do extract/decompress it?
I suggest not using precompiled kernel RPMs. I tried it once, and I completely destroyed my Operating System. (Using precompiled kernels makes it signficantly harder to revive your operating system)
My little story involves reinstalling, and reformatting. (For unknown reasons, I was never able to revive my OS into a manageable state)
http://www.linuxhq.com /usr/doc somewhere
Or if you installed the documenation it should be in
I (sabri@selwerd.cx) also did not have too much trouble upgrading from 2.0.36 (RH5.2) to 2.2.1. The only "problems" I had was ipchains but then again, that was only a RTFM problem :-)
...or do you prefer like that,
User: - Hey there is a new bug that's biting me!
Developers: - Humm. This is not extremely critical for us to provide a "hotfix", so you're gonna wait some six months for the next service pack or a couple years for the next release.
Want a stable system? Don't bother with the release-of-the-week. Wait a couple months, read the change logs, update when some change affects you. Doing otherwise and complaining about too uent releases is not only stupid but ungrateful to the guys working on the kernel.
fiddling=/usr/src/linux/Documentation/Changes
Except that LinuxHQ hasn't had the 2.2.5 summary on it at the time of this writing. Three days now? Wonder what's with them...
How is an IEEE standard proprietary?
from 10.6 megs (bz2 2.2.2) to 10.9 megs (bz2 2.2.5). Soon I'll need a faster connection to upgrade. Guess its about time to try patching.
Let me try. Here are lots and lots of less than and greater than signs:
.0.
:end are ignored as well.
1 less than : "
1 greater than : > ">"
4 greater thans: >>>> ">>>>"
Mixed: >>>>>>>>>>>>
And finally a constipated look:
>
Preview...submit...yikes! Bugs!!!!
Get me the insecticide!
Spaces, begin:
Rob - are you reading this?
When is USB support planned to be integrated into
the standard source tree of the kernel?
I know that there is a patch, but it is only a
patch, in an early development stage, with support
for only a few of the hundreds USB devices.
These days, with all the excitement around USB, it
is a big ashame that there is no support for USB
in Linux. Does anybody work on this seriously?
We're mirroring linux kernel and have got both
2.2.5 and the patches.
ftp://ftp.cs.unm.edu/mirrors/linux-kernel/v2.2
We've got slots for 100 friends.
Chris Faehl
cfaehl@cs.unm.edu
You see, "AC" is actually short for "Anonymous Coward". Each "AC" patch is actually a patch from one of the anonymous cowards who posts to SlashDot (like me, for example. I fixed the TCP/IP denial of service bug, your welcome). We prefer anonymity because we're just a bunch of egoless programmers, who don't want any credit or money for our hard work.
I hope this has helped you.
Don't upgrade then. You may not need the bugfixes and/or enhancements the new kernels provide, but somebody out there does. I generally skip 2 or 3 kernel versions unless there is something I need immediately.
This question came up on the kernel devel list last week. The answer is that the mirror sites can choose how they want to update. Most use rsync now, but some choose to ftp mirror.
Talk about instant gratification.
- A.P.
--
"One World, One Web, One Program" - Microsoft Promotional Ad
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
Download, Compile, Reboot, Repeat!
'Nuff said.
Linus was projecting some time during this fall to start 2.3, but you never know.
SegFault
I know that there is a mailing list for Linux kernel development on Sparcs. That would probably be a place to ask.
See http://www.linux.org/help/lists.html and look for "sparclinux" and "ultralinux" lists.
The top of the page has instructions on how to subscribe.
Subscribe to linux-kernel-patch and have them emailed to you :)
See http://www.linux.org/help/lists.html for details.
SegFault
At this point, waiting is the right choice. 2.2 is settling out faster than 2.0 did (remember, 2.0 had EIGHTEEN kernels in three months!), but there will probably be a few more before it's really stable.
2.0 took 29 revisions to be really solid. Then it took another 5 revisions to be fixed again after 2.0.30 screwed everything up (groan).
Send mail here if you want to reach me.
Posted by aalain:
...must...download...must...compile....
--Alain
Posted by stickymn:
I have Red Hat 5.0(not installed yet), and want to know the best way to upgrade to 5.2 with the latest kernel. Not to sound cheap, but I goofed and paid for 5.0 at a used bookstore, under the impression that it would not be difficult to upgrade. I a newbie to Linux. please email me at morrist@biperf.com
Posted by !ErrorBookmarkNotDefined:
Besides that TCP vulnerability, that is.
-----------------------------
Computers are useless. They can only give answers.
Posted by FascDot Killed My Previous Use:
Don't delete the old downloads! INSTALL them. And patch up to the next version if you need to.
You're wasting bandwidth.
Posted by Myrdraal:
Hi, for those of you who don't know, you can snag the changelist at http://edge.linuxhq.com.
-Myrdraal
Can anyone explain in English what effect the change to the es1370 an es1371 sound drivers was.
--Some-guy-who-would-like-to-have-CD-audio.
I guess this is a bit late and nobody reads this.
/usr/src/linux/scripts/patch-kernel
.gz and .bz2 patches and automatically from say 2.2.0 to 2.2.5.
However it's not necessary to apply all those patches by hand. For example I have a download directory where I download all the patches then I simply write:
$ pwd
/home/amlaukka/stuff/kernel
$
and whoopla it patches the kernel up to the current version. Works with both
Nobody knew the bug was there. It's a rare case, and one that requires a malicious exploit to cause any harm (when was the last time you saw a naturally-occuring zero-length fragment?) The bug was discovered and fixed before word about it hit the net. I was running 2.2.4 (the relase that fixed the hole) when I read the first advisory. The bug was, therefore, fixed as soon as possible after it became general knowledge. That's not foot-dragging, that's speedy coding, and it's to be congratulated.
With the appropriate binaries, you can cross-compile from your PII to your Sparc20 and cut down a whole pile of problems.
Heck, a lot of kernel work is done via cross-compiling for older architectures.
--
Ben Kosse
Remember Ed Curry!
Get the patches (preferably in bzip2 format) -- they're smaller, and therefore save bandwidth on wherever you're downloading it from. Even if you don't care, saving bandwidth where possible is acknowledged to be A Good Thing. Once you've applied the patch you will have the same code as if you'd downloaded the full tarball, so compilations will be exactly as fast (or slow) as they normally are.
--
W.A.S.T.E.
W.A.S.T.E.
same here, my machine is running 2.2.1 without any trouble, and i'm really starting to like my uptime now that it's into its second month (check out my stats page).
rifling through the changelogs didn't reveal anything that makes me wanna do the kernel dance, but these rumored TCP DoS attacks worry me slightly. any specifics on this?
http://www.geek-girl.com/bugtraq/1999_1/1079.html
i found it, tee-hee. details of the bug and its exploit.
That's not true for everyone. I always just dowload the whole kernel. It's much easier than patching. I usually get about 120 KB/s to most
mirrors, so 10 MB is only 2 minutes. It's not worth dealing with the patches.
Not everyone uses a modem, remember.
Yes, 2.2.4 at least as 2.2.4 had a tcp bug which could be exploited. :)
otherwise nothing that great
Gav
It was always a good idea to check out LinuxHQ and read the latest Changes to see if you need to upgrade. 2.2.4 had a TCP explot fixed.
I'm still running 2.2.1 on my machines, and I'm wondering if there's any compelling reasons to upgrade to 2.2.5.
I'm not having problems with 2.2.1, so I'm not going to upgrade unless I need to for some reason.
I can't believe that - that's so lame! How are
those of us with 7 arms supposed to use all our
mice simultanously!
Linux is falling so far behind...
_grin_
actually, the dependencies are handled very well, as near as I can tell. I mean if a file changes, it is smart enough to figure out what depends on that. if something major changes, it will probably need to be rebuilt, but there is no need to rebuild stuff that didn't change any code.
Did you mount a military-grade, variable-focus MASER on an unlicensed artificial intelligence?
I think I have seen some that were a couple of hundred K...
Did you mount a military-grade, variable-focus MASER on an unlicensed artificial intelligence?
Ah, the infamous finger memory bug :-) Who knows how many times I have typed Linux instead of Linus.
Did you mount a military-grade, variable-focus MASER on an unlicensed artificial intelligence?
Up at 152.2.167.46 in /pub/linux.
posted on behalf of Jeff Brubaker @ UNC Chapel Hill by -c-
I2O is what?
Its spelt "L-I-N-U-X", but pronunced as "Free Beer"
actualy there is documentation on the CD, and if you no want to do that, you can get it in html form on RH website.
Its spelt "L-I-N-U-X", but pronunced as "Free Beer"
... and there were licensing fees involved. Is this wrong? I thought that was the reason USB support on linux was so slow in coming.
support gun control: take guns from cops
While previewing this one, I found another problem, though. (It's probably the same one.) The "Preview" function replaces the actual code with the HTML equivalent.
PKG
------------------------------
Common sense is not so common.
Turambar
------------------------------
Common sense is not so common.
--Voltaire
They'll will never stop, it's too much fun!
I trust you read the stuff on patching (look under Yikes!) I hope you didn't mean it literally when you said you deleted the old kernel and got the new one.
Good luck!
I'm sure I put a "less than" symbol between the space after -p1 and the two dots.
i.e. "../patch-2.2.x"
Hmmm... I thought using "Plain Old Text" as my posting option would mean that when I type a greater than or less than symbol, then they wouldn't be interpreted as HTML????
Every time I type a "greater than" or "less than" using "Plain Old Text", they show up OK in the preview, but disappear in the actual submission!
Hmmmm.... OK.
Using "Plain 'Ol Text [tm]"...
Greater than - >
Less than -
Preview....OK so far...
Hmmm.... Preview that again... nyargh! Bugs!
This is the last I'll say on this.
rgds.
Kev.
I was just going to post something to that effect.
I'll second that anyway.
You mean to say you _download_ 10+ megs of source every time there's a new release? Woops! There goes the world's bandwith :)
/usr/src/linux ../patch-2.2.x
1) D/l patch-2.2.x.tar.{gz or bz2}
2) gunzip or bunzip2 patch-2.2.blah..
3) cd
4) patch -p1
5) compile/bake for 20 mins (cooking times may vary according your computer speed).
rgds.
Kev.
There was one little bug that kept it from compiling if you had enables BSD process accounting. Affected quite a lot of people, but a patch was out within minutes of the 2.2.4 release. Other than that, I assume that Linus released this to get a bunch of little things fixed before he left town for a couple weeks.
The AC Patches are a collection of patches that Alan throws together for testing purposes. I consider them to be "almost production" quality. He often fixes important bugs in the release kernel, so they're usually not a bad idea. There's always a ton of new features in them. Right now, it's the closest thing to a development branch of the kernel. You can get them ftp.kernel.org (or any of the mirrors).
Actually, the exploit went way farther back than 2.2.1, back to the middle 2.1.X days (around 2.1.80 or so). Unlike Microsoft, the exploit was patched in a timely manner. -Dave
Just put all the patch files (still zipped if you like) in /usr/src (or where ever linux/.. is), and run that script. No muss, no fuss, no 10 meg download.
That's not true for everyone. I always just dowload the whole kernel. It's much easier than patching. I usually get about 120 KB/s to most mirrors, so 10 MB is only 2 minutes. It's not worth dealing with the patches.
Yeah, now multiply yourself by a thousand and think how those poor servers feel. This isn't about whether it's a pain for you in particular to download the kernel, it's about not taking up a huge chunk of bandwidth so that other people can get in. ftp.kernel.org goes down hard every time a new kernel comes out, and I've met more than one sluggish mirror.
At least try the patch first. If it doesn't work, then you can snarf down the whole thing, but at least give it a shot.
Hit freshmeat.net and do a search for bzip. It'll come up.
Hrmmm...with luck like that....QUICK! Invest in Microsoft!
"What do you mean, invalid parameters? 9000Gigs of RAM and it can't answer a simple question!" -- Earthworm Jim
Usually, I like to see a bit more delay between non-development releases. For instance, my fiancee can't be talked into more than about one kernel compile a month.
I kinda liked the long delays between 2.2.1 and 2.2.2. I'm sure people running production servers also appreciate the stability. Things seem to be accelerating again, but I'm hoping that's just due to the relative timing of vacations....
--Joe--
Program Intellivision!
Was there some sort of brown-paper-bag issue in 2.2.4? I know Linus was about to go on a two-week vacation, so did he release this to fix some real showstoppers?
When I checked LinuxHQ, I didn't even see 2.2.5 mentioned yet, and the changelog at Cutting Edge Linux didn't hint at any real showstoppers. Even Alan Cox's diary didn't mention that 2.2.5 was iminent. A search of the Linux Kernel mailing list archives was similarly unenlightening. (I was looking at http://www.tux.org/hypermail/linux-kernel/latest/ ... is there a better place?)
So what's the rush? This almost feels like a development kernel patch cycle....
--Joe--
Program Intellivision!
I just went through all 14 of the ftpX.us.kernel.org, it seems like half of them still havent got kernel 2.2.5. The ones who got the kernel seem only to have the fat tar ball (10 meg download).
My suggestion to kernel ftp mainterns would be to download the patch before downloading the tar ball. Since most ppl visit your fpt servers to get the patches and not the full load. It might be a wise suggestion to hold the full tar ball 24 hours before releasing (since it would be bound to cause a lot of bandwidth problems).
Thank you.
--
In /usr/src
.gz
.bz2
/usr/src/linux
1. with files ending in
gzip -cd patch-2.2-whatever.gz | patch -p0
2. with files ending in
bzip2 -cd patch-2.2-whatever.bz2 | patch -p0
If your patching the kernel inside
Then instead of patch -p0 above, use patch -p1
That's all. (Remember all offical kernel patch releases are incremenatal patches - so you have to patch one after the other).
EG: if you have kernel 2.2.1 and wish to go up to 2.2.5. You have to patch your current kernel, to 2.2.2, 2.2.3, 2.2.4, 2.2.5 in that order.
Good luck.
--
My sparc64 has 60 days 23:27 on 2.2.0.
I'd say "stable".
2.2.5 is working great on my HP Kayak (which
has some pretty bizarre peripherals), so let's
see how it does on the Sparc. Wish me luck!
-fb Everything not expressly forbidden is now mandatory.
Yes, as a matter of fact, there is steady constant work being done on the USB subsystem, it's being done mainly by one advernturesome soul who is in school right now. You can check his progress at the web site. You can always find information about inportant projects at the Linux Documentation Project. I know they have keyboards, hubs, mice and several interfacec cards working right now. They are doing some weird crap too... the guy that's doing it noticed that his code puked when he added the seventh mouse...
Even so, I think it is a good idea to always run make clean after patching, so as to force everything to be recompiled.
I haven't had a chance to keep up with sparc64 dev at all. How is stable is the kernel in that hw environment now?
More specifically, does anyone have any production experience on that hw?
Sorry to have to yell, but....
USE PATCHES!!!!!
Thank you.
If corporations are people, aren't stockholders guilty of slavery?
tsia
Huhu!!
That's real nice... Don't even need unzipping...
Thank you!
...and I just installed 2.2.4. I will have to get to it later.
I have a woman and money. Life is good.
thanks...did not know about that
I have a woman and money. Life is good.
Just because RedHat doesn't ship with it doesn't mean it's not the stable branch. Redhat has nothing to do with whether or not a given kernel is stable. If Linus calls the minor version number even, I call the kernel STABLE.
If I'm not back again this time tomorrow...
Wow those guys are moving fast.. Does anyone know when 2.3.x will be started?
Doviende
"The value of a man resides in what he gives,
and not in what he is capable of receiving."
--Albert Einstein
2.2.4 fixed it.
Doviende
"The value of a man resides in what he gives,
and not in what he is capable of receiving."
--Albert Einstein
Doviende
"The value of a man resides in what he gives,
and not in what he is capable of receiving."
--Albert Einstein
Also, my other machine is Slackware 3.6, and the scenario was the same....make xconfig, make dep, make zImage, reboot, and that's all the configuration it required.
Why the heck are all of these RedHat people having so much trouble? They can't run anything that isn't a binary in an rpm? maybe that's a little harsh, but I can't figure it out.
Doviende
"The value of a man resides in what he gives,
and not in what he is capable of receiving."
--Albert Einstein
How long did it take last time for the devel branch to start? I thought it was something like a month or two.
-matt
Hrm...it seemed shorter. Oh well, I can't wait for 2.3.xx. I personally dislike this whole stable thing. Where is the fun if you don't get to test out new drivers that are probally going to crash your system?
-matt
subject says it all
The lesson here is quite simple:
Any new software release may contain major bugs that the developers missed. If you really need a stable system, don't upgrade to the latest release until it has had time for the bugs to settle out. Sure, the developers try to make every release bug free, but they're only demi-gods (i.e., only mostly perfect).
Fortunately, for Linux, this means wait a few days, possibly a week.
Of course, many of us don't need absolute perfectly stable systems. Hence, we're free to upgrade the moment the latest compiler, kernel, or whatever hits the mirrors, and we just might be the ones to find the brown-paper-bag issue that the developers need to know about. In other words, running a brand new software release and looking for problems is one thing that non-programmers can do to help the free software community.
i've never had any trouble with scsi in the kernels, but i've always compiled it in, rather than using modules. (the only drives i've got are scsi, so i have to.)
i've got one machine with an onboard aic78somethingorother. the only problems i've had with it are with the 2.2-pre5 up to 2.2.1 kernels not reading my disk geometry correctly. (scsi compiled in.)
is there anything else in your system that might cause problems? a device that's not sharing irq's cleanly maybe?
Personally, if you are that far behind in kernels, I would download the complete source. But then again, maybe 4 short downloads are better than one long one. Good luck!
"The sad thing about artificial intelligence is that it lacks artifice and therefore intelligence." --Jean Baudrillard
Greetings,
Sometimes it feels like it...
Cyberfox!
I fixed that BSD process accounting bug in the source myself. Will the 2.2.5 patch die if I've already done some of its work?
Geeze I just compiled 2.2.4 yesterday!! :P
you people love to keep me busy
-----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d? s: a-- C++++ UL++++ P++ L+++ E- W++ N o-- K- w--- O- M+ V PS+ P
Are the mirrors of ftp.xx.kernel.org mirroring via ftp? The news seems to indicate that they are. I would suggest using something like rsync to keep the mirrors up to date instead.
Nope.. Sorry.. It's becoming a standard.. It's already standarized in its self..
I ate my tag line.
-=Ellis (D)25=-
jesus, i still have 2.0.36
--
hellraiser ( @linuxfreak.com || @nac.net )
awk 'BEGIN { printf "Just another %s hacker\n", ARGV[0] }'
2.0.0 was out on june 9th, 2.1.0 was out on sep 30th (all 1996), that makes almost 4 months.
In those 4 months came 22 releases in the 2.0 series, in the 2.2 series we haven't seen more than 6 releases, so 2.2 seems to stabilize faster, and so we might see 2.3.0 soon.
- nr
Linux Mandrake has a set of kernel-2.2.3 RPMs available. My only hard-drive is through my aic7xxx SCSI adapter. All you need to do is install the RPMS (that's install.. NOT upgrade) for the new kernel, run mkinitrd (Apparently scsi_mod is compiled into the mandrake kernel, so you don't need to use with-scsi-modules). edit /etc/lilo.conf to allow you to boot linux and oldlinux (or whatever), run lilo and reboot. I'll probably put a kernel 2.2.5 RPM up soon if Mandrake hasn't already done it, check my website.
--
: tedd
If you bothered to look at the contents of the patch file, you will notice that the majority of this patch falls into 3 distinct changes.
i. New device drivers for support of additional serial cards. One of these drivers is huge with many comments. New drivers are always being added - it is called progress
ii. Minor source code changes that do not remove functionality (replacing obsoleted calls and removing include files no longer needed).
iii. Modifications to the Sparc and Sparc64 architecure trees - most users won't need this either.
How many slashdotters actually bother to check the contents of a patch to see what has changed - having worked as a support engineer for 9 years I wager that the answer is 'Not Many'.
Awww... we don't want this guy wasting his money on top of it, do we? :)
because I just downloaded and compiled 2.2.4 a few minutes ago.
While I'm at it, my apologies to the Spartans for betting on them.
--Last Exit To Babylon
Couldn't wait, huh? I think Alan must have heard you. :-)
To those of us running on the SPARC and PPC architectures, this is our only stable version. Then again, I've been running Ultra-Peguin (64-bit/Sun) off the 2.1.X series kernel it came with, for over a month, and it has yet to crash. The only problems have been with the X server. Considering Sun was dragged kicking and screaming to X, the Slowlaris version sure works better.
Changes aren't permanent, but change is.
I upgraded everything from 5.0 last week. I couldn't get Glibc to compile up, so I RPM'd it; apart from that , even Red Hat give specific simple instructions on how to upgrade. How simple does it have to be?
Maybe gnu/linux becoming mainstream is a *bad* thing......?
Acting stupid isn't much fun when there's someone around who knows better
Who's Linux, and since when did he or she become the head kernel honcho?
:P~~~~~~~~~~
2.2.1 is by far the least stable kernel I've ever used. In the year I've run linux, it's crashed once -- and that was while using 2.2.1. Of course, that was probably because it was the first kernel I ever bothered to compile, and I'm pretty sure I managed to screw some option up somewhere.
I'm wondering if I should upgrade this time though. I usually have a nice t1 to download things on, but I only have a modem right now. I feel so technologically inferior. *sigh*
okay so i downloaded 2.2, and saved it to my hard disk and i was going to install it over the weekend, then 2.2.3 came out! So i deleted 2.2 and got 2.2.3, and i don't remember 2.2.4 comming out, but i guess now i'll have to delete 2.2.3 and get 2.2.5, only for tomorrow, they will have 2.2.6. When are they going to stop?
Look out honey, 'cause I'm using technology; Ain't got time to make no apology
make clean (make-kpkg clean) really *should* be run to make sure your kernel compiles correctly, new features etc
It's just like seeing your child grow and have birthdays.
If new Linux kernel (with new patches) would come out once in year we would still be running what 1.x.x ? Linux evolves and noone forses you to download it.
isn't it funny how this 2.2.x series is labeled 'stable'?
he who has the fastest cart always has the best lie.
what was that major tcp exploit thats in 2.2.1 through 2.2.3, even some 2.1.x kernels?
sounds like microsoft's 'stable'
he who has the fastest cart always has the best lie.
maybe if you would work on trying to remembe what you just read, you would be able to see that i mentioned the 2.1.x crap. and you call that 'fast'?
lol.
he who has the fastest cart always has the best lie.