Slashdot Mirror
Linux 2.4.22 Stable Kernel Released
An anonymous reader writes "Marcelo Tosatti has officially released another stable 2.4 Linux kernel. 2.4.22 was released early this morning and includes a lengthy list of fixes. It follows the last stable kernel in this tree, 2.4.21, by a little over two months."
That feature is still in development. If you really need it, perhaps you should use Windows 2003 until the 2.6 kernel comes out.
*downloads and sends check to SCO*
I'm curious if anybody has experienced dramatic performance increases running X when switching from 2.4 to the 2.6 testing branch of the kernel.
A musician without the RIAA, is like a fish without a bicycle.
If it ain't broke...
'Running' winders is like running a dirty toilet.
"Flyin' in just a sweet place,
Never been known to fail..."
...and no popcorn...!
WTF is it with this machine I bought that doesn't give me my popcorn when I give it kernels?!
Ah, forget it. I'll go back to closing and opening Windows and see if it's more likely I'll get some fresh air in the house.
Vos teneo officium eram periculosus ut vos recipero is.
For those of you who use bittorrent, try:
linux-2.4.22.tar.bz2
patch-2.4.22.bz2
Choose yer poison: Prophets or Profits
Kai Makisara:
o Change Kai Makisara's email address
I was wondering when someone would get around to this.
Summary of changes from v2.4.22-rc2 to v2.4.22-rc3
@lt;len.brown:intel.com>:
o ACPI update
o ACPI build fix
o linux-acpi-2.4.22.patch
I don't have detailed info on OS design, but probably you'll want to take a look at the OSKit and Exokern websites, as they do go into some depth on design issues.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
Mod me off-topic if you wish, I for one welcome our new off-topic overlords.
We don't need a new kernel for now. The existing kernel has been highly stable in the types of jobs we throw at it. But that's not why it doesn't matter. Our director has finally handed down the "No more Linux installs" message. Here is the message:
As some of you may know. SCO has a lawsuit filed against IBM for breach of contract, misappropriation of trade secrets, etc. The bottom line of this disagreement is that SCO is accusing IBM of including some of SCO's trade secrets (proprietary code) in its Linux kernel and that this source code has also been included in the Linux kernel available off the Internet.
To top all of this off, the US Copyright Office awarded SCO a copyright to System IV Unix last month. SCO, through a series of mergers and acquisitions, acquired the patents, copyrights, etc to System IV Unix that was originally developed by Bell Labs in 1969. About this same time, SCO created a new division whose only purpose in life was to license Linux and Unix to end users.
Because of all of this confusion, I have asked our legal eagles to give me an opinion as to whether or not our recent installation of Linux systems in the (our department name) places (our company name) in any sort of jeopardy. Frankly, I think that SCO is simply struggling for survival as it is in severe financial trouble. I also think that any rights SCO may have think it had at one time has been abrogated since SCO was (until last month) freely distributing Linux on its web site under the GNU General Public License.
But until I receive an opinion from Legal, we will not deploy any more Linux systems.
p.s. We are a 1200 employee telecommunications company, ISP, cable TV, long distance telephone, etc.
I wonder if I can tell SCO off because of the kernel panic I am getting with this new release. Btw, I own a SCO License
Hay, don't forget to pay us the small upgrade license fee.
IP law confuses me. I am persuaded slashdot readers who read this sig now legally owe me 699$
I've been running the -mm series of the 2.6.0-testX kernel since they started coming out, and I'd recommend anyone not running a critical system (where stability is of high importance) to try them out. Some of the main improvements easily noticeable are in the scheduling / Disk I/O areas, which makes interactive (desktop) usage much smoother. For instance, problems I've had with the 2.4 series where a system under high disk usage made the desktop jerky, and sometimes slowed down to a crawl, I have yet to see with these new kernels.
... sooner it'll be stable! :)
Sure, I've stumbled upon an occasional bug in the process, and once after upgrading found the kernel unbootable, but with help from the kernel newsgroups, a quick fix could always be found. Besides that, I've found these kernels to be as stable as the 2.4-series..
And, don't forget, the more people running the soon-to-be-stable kernel, reporting bugs as they are found, the
For the first time we have cryptographic API in a stable released version of the Linux kernel. Until recently, cryptographic software could not be exported from the U.S. without a special permission. It took some time to explain to the government that the "bad guys" already have access to strong encryption. We have succeeded. Cryptographers, rejoice!
Maybe the moderator is a subscriber, and saw your post before you submitted it.
ok here is the short:
;)
Linux = good
BSD = good
NT = bad
proprietary Unix = good but expensive
BeOS = bad
Plam = wtf is plam?
here is a comparison:
Linux VS NT = linux wins
bsd vs nt = bsd wins
anything vs NT = anything wins
bsd vs linux = linux wins
proprietary unix vs linux = linux wins but it's a tight race
bsd vs proprietary unix = bsd wins again a tight race won by price and development model
plam vs anything = again wtf is plam?
There are not big core changes in this kernel, so it's believed to be very stable. Also, it includes some security fixes so you should upgrade.
Anyone know if the new kernel has been fixed for the C-Media 9738 AC97 Codec? Last time I checked Alan Cox "patched" this in 2.4.21 and my integrated sound didn't work. I know this has gotta be a pretty big problem.. my board was pretty popular (K7S6A)...
"Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
This short guide walks you through the steps used to compile and install a new 2.4 kernel.
Sorry, this is an incomplete list for the 2.6 series, while the kernel released is 2.4.22. For a almost complete list of features going into 2.6 you can see Linux Kernel 2.6 Status
No he is not, he is the boss of the 2.6 releases.
Okay, we've got a new kernel. That's cool. I've built kernels before in the past...in the past.
Now with RH9, every time I try to make a custom kernal it pooches the system mightily. I'll lose video, or I won't get power, or it'll give LOTS of errors when starting up because I didn't have a Makefile just like Redhat's magic one.
So how would a person compile 2.4.22 and still have the same support as whatever RH9 based build they're currently running?
"Draco dormiens nunquam titillandus."
Da kernel be da damn essential centa' o' some doodad opuh'atin' system, da co'
dat provides basic services 4 all otha' parts o' da damn opuh'atin' system.
Some synonym be nucleus. Some kernel kin be contrasted wit' some shell, da
outermost part o' some opuh'atin' system dat interacts wit' usa' commands.
Kernel an' shell be terms 'esploited mo' frequent-like in Unix an' some kinda'
otha' opuh'atin' systems dan in I-B-fuckin'-M mainframe systems.
Typical-like, some kernel (down low, o' no comparable centa' o' some opuh'atin'
system) includes some interrupt handla' dat handles all requests o' completed
I/O opuh'ashuns dat battle 4 da kernel's services, some schedula' dat
determines which rehabs share da damn kernel's processin' time in whut orda',
an' some supuh'visor dat actual-like gives 'esploit o' da damn doodad t'aich
process when it be scheduled. Some kernel may also include some managa' o' da
damn opuh'atin' system's address spaces in memory o' storage, sharin'
dese-he'ah among all components an' otha' usa's o' da damn kernel's services.
Some kernel's services be requested by otha' parts o' da damn opuh'atin' system
o' by applicashun through some specified set o' rehab interfaces sometimes
known as system calls.
Becuz da code dat makes down da kernel be needed continuous-like, it be
usual-like loaded into doodad storage in some arai dat be protected so's dat it
aint gonna be overlaid wit' otha' less frequent-like 'esploited parts o' da
damn opuh'atin' system.
Da kernel aint t' be confused wit' da damn Basic Input/Output System (down low,
B-I-O-fuckin'-S).
Some kinda' kernels have been developed independent-like 4 'esploit in no
opuh'atin' system dat be hankerin' t'esploit it. Right on! Some well-known
'esample be da damn Mach kernel, developed at Carnegie-Mellon University, an'
current-like 'esploited in some version o' da damn Linux opuh'atin' system 4
Apple's Powermac doodads.
Here's what you can do to use vanilla kernels in RedHat. It may not be the easiest route, but it works like a charm every time.
1) Enter your regular redhat kernel source directory. Everything should be preconfigured, unless you changed things;
2) make menuconfig, then Save Configuration to Alternate File. Pick a name you'll remember;
3) Exit menuconfig, enter vanilla kernel directory;
4) make menuconfig, Load an Alternate Configuration File. Enter the name of the previous config, with full path.
5) Profit! You might want to check any new options just for fun (such as built-in crypto for this kernel release), but it isn't necessary.
Your new kernel should now run just fine under RedHat, with a minimum of fuss. It'll be a long compile, though, because even the kitchen sink will be included. Still, it's more work for the computer and less work for you.
Someone mod this down ... it is a troll that has been posted before. These are some 2.5.X patches that will be in 2.6, nothing that is in 2.4.22. Read the real changelog that was linked from the article. Moderators ... wake up!
Do you even know anything about perl? -- AC Replying to Tom Christiansen post.
Linux kernel. 2.4.22 was released early this morning and includes a lengthy list of fixes.
all of which came from SCO's massive Pool of Intellectual Property.
Do you have ESP?
Forgiven.
... 2.6. The general idea is to backport security, stability and driver patches and leave the architectural changes alone.
The changes will need to be dupicated from one series to the other.
A change to the 2.4 series may be submitted to Linus for inclusion in 2.6, and added if he deems it worthy. The process also works the same way in the other direction. For instance, if Linus accepts a patch to the 2.6 series, then the 2.4 maintainer may choose to include a "backported" patch for the 2.4 series. Alan Cox (I believe) has been the 2.2 maintainer for a while now. (Remember the beloved stable 2.2 series?) If he feels a 2.4 series patch is essential he may backport it to 2.2.
The decision to backport is not automatic, since applying all the patches from 2.6 back to 2.4 would yield
-Jon