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.
Doesn't this realese seems like the 2.4.13? The RCs came out just one week after the other. Please God, hope to have no VM issue!
*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.
Is there such a thing? It's tiresome reading through all the changelogs (2.4.21 -> pre1 -> pre2 -> etc).
Thanks
"Would it kill you to put down the toilet seat?" -- Maya Angelou
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
I hope you're not expecting an unbiased response to this on slashdot.
Linux Trace Trollkit (LTT)
Look out trolls, now we have a way to trace you!
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)
They don't want to post a SCO story because the next story would be about an open source zealot who DoSsed SCO.
BOO! TERRO
WTF is it with this machine I bought that doesn't give me my popcorn when I give it kernels?!
...and my TAB key isn't working either...
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 run Debian, what practical difference will this make if I install it? I use the system for office type tasks.
Thanks
Is it possible that this has been a result of the slashdot effect?
The Television Wiki
Well, it's happened again. kernel.org just slowed to a crawl.
Remember to use those mirrors, folks!
Don't see anything in the changelog about removing ugly-ass Unix code claimed by SCO to be their own ... :-)
I tried to install 2.4.21 and it wouldn't read my hard drive ...
Downgraded to 2.4.20 and it worked fine. These were both "stock" (kernel.org) kernels.
Before, I had only used the Red Hat 8 kernel, a modified 2.4.18. Both the 2.4.18 and 2.4.20 seem quite stable to me.
-uso.
Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
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?
I had no problem whatsoever extracting a vanilla 2.4.20 over RH8.
What modules or services do you need? make menuconfig and make sure that they are selected. Is it THAT hard?
-uso.
n00b kernel compiler.
Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
Are you using a SCSI drive, or RAID? If so, remember to compile in support for your drive to the kernel (non-modules).
Alternately, check that support for your IDE drive hasn't been acdidentally deselected.
Plan [sic] 9 rules. Everything else is not already dead, but is starting to smell bad.
Operating System Concepts
Silberschatz & Galvin
Addison-Wesley
I reccommend both the Fourth and Fifth edition. The Fourth Edition (ISBM 0-201-50480-4) has a section on The Mach System (aka the core of MacOS X & Next) The Fifth Edition (ISBN 0-201-59113-8) has a section on Windows NT, and a section on Linux (2.0).
Well, you heard wrong. The NT kernel is not good. It's faculty for determining timeslices and aggregating CPU time is convoluted at best. It is all designed to make user level timeslice requests (ie GUI events) occur more quickly. The solution provided by NT kernel is a timeslice lookup matrix with more elements than I can currenly remember to cound (something like 3 levels with 11 sublevels for each).
When compared to the Linux or even Solaris CPU timeslice allocationg, it is horribly overcomplicated and slow and clunky.
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.
*YAWN* come on /.
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."
probably a day or so. kernel 2.4.21 took a little while, probably because of all these slashbots sucking the new kernel all at once before the mirrors have a copy :)
2.1.x -> 2.2.x you say? That's interesting, one would believe that after SCO called 2.2 a 'hobbiest' at best OS, and that they should legally have a valid license to 2.4.x->2.6.x ( :p ) that they would be using it. But, uh, yeah, whatever. :P
-If God wanted people to be better than me, he would have made them that way.
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.
Just saw that 2.6.0-test4 is out. Been using test-3 with a patch akmp patch for the APIC on the nforce2, and have loved the results. X is more responsive, sound is much less likely to skip when the disk is in use. Havent found out if they included that patch in test-4, so if anyone knows, please reply.
"My head hurts, My feet stink, and I dont love Jesus." -Jimmy Buffett
2.4.22? Could be a little while, maybe a couple weeks - Gentoo developers, at least kernel-wise, tend to apply all the best patches to the kernels all the time anyway. Basically, if you are running a new kernel that says 2.4.20-r7 or the like, chances are that all the new patches in the vanilla 2.4.22 are already built into your current kernel.
Is this some evil plot by SCO? Why have we slashdotted kernel.org?? OH THE HUMANITY!!
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.
I've always thought it strange that the kernel is in the portage tree. I understand that certain packages depend on certain kernels, but I usually just download the kernel and install like I always did.
The patch that's most useful to me is a small fix in USB support for the Sony DSC-P series of digital cameras. No more custom kernels for me. So if you have such a camera, just plug it in and mount /dev/sda1 (if that's your only SCSI device). It's a mass storage device.
What, is the above AC a 40 year old debian dev by chance?
I suggest removing the heat sink from your athlon and replacing it with a small plastic bag. In one step, you increase the amount of smokey goodness and help to keep it all contained.
To make laws that man cannot, and will not obey, serves to bring all law into contempt.
--E.C. Stanton
Holy shit, you mean you were serious? Take my advice and take the Troll label, you'll look better for it.
It's a little technical but "Understanding the Linux Kernel" is good for a reference on how linux on x86 works. It's not very technical though, if you understand C code and a little asm. For a general overview on x86, Intel's (free!) third volume in the IA-32 development set is good, though it's more about what an OS could offer, not what they do offer. I don't really know of any way to get design docs for proprietary stuff, like NT.
====
Crudely Drawn Games
I've always thought it strange that the kernel is in the portage tree. I understand that certain packages depend on certain kernels, but I usually just download the kernel and install like I always did.
You can certainly do that if you like, with no ill effects. Gentoo is highly standards compliant where it makes sense, and makes reasonable extentions/extrapolations where the standards fall short. It is certainly easier to integrate a vanilla kernel into Gentoo than it is, say, Mandrake or Red Hat (though to be fair I'm sure they'll have their own, patched versions of 2.4.22 out very soon).
However, when one is administering fifty or a hundred identical Gentoo boxes (or just 20, for that matter), it is nice to use the distribution's internal package management tool to manage software revisions for everything, including the kernel. This has advantages of, for example, being able to quickly deploy a new kernel ('sh myglobalscript.sh emerge vanilla-sources', where myglobalscript.sh does an ssh into all of the requisite boxes and runs the command I pass it), and manage it along with the rest of the software on the system in one seamless manner.
This certainly isn't the only way to do it, but when you're managing in-house software, kernel revisions, and dozens of other important packages, having one interface (portage) to manage all of it is very handy. And, unlike many packaging systems, portage simply installs the tarball and gets out of the way (meaning one doesn't have to jump through lots of non-standard hoops in actually compiling and deploying the kernel). YMMV of course, but I find having the kernel, even the vanilla kernel, in portage to be quite useful.
The Future of Human Evolution: Autonomy
ftp.sco.com has linux-2.4.13-21S.src.rpm from their OpenLinux distribution. It's free, and still available as of this morning (after the DoS ended...) Depending on your taste in distributions, you'll probably have to repackage it to use with whatever applications you need, and I don't know if there are any critical fixes after that. Sure, it's not as much fun as running 2.6.wildly.unstable, but it'll let you run a reasonably modern production environment.
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
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.
I see that nobody bothered to answer your question. Offtopic posts seem to multiplying as fast as spam these days on Slashdot.
8 59-1/boo ks/design-44bsd/
- HO WTO/index.html
BTW, have you heard of Google???
BSD:
http://freebsd.unixtech.be/doc/en_US.ISO8
Linux:
http://www.kernelhacking.org/docs/kernelhacking
http://cs.uml.edu/~cgould/
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?
yes, we very well can complain, thankyou, when we consider using these operating systems on/as servers
Actually, in this case it was to patch the Orinoco drivers to work with kismet and do a little wardriving. Ended up just booting into XP and using netstumbler.
"Draco dormiens nunquam titillandus."
I had to read that twice. What's your point? Of course the interactive processes should be given a priority. I mean why would you want to freeze the GUI?
BOO! TERRO
No actually its, Microsoft Works.
Maybe you should ask your question on a GENTOO mailing list or newsgroup?
XML causes global warming.
He would have noticed if he's trying to load the kernel.org page that shows him the mirrors...
For what it's worth, those of us in the US should probably start with this list.
Or better yet, the google cache of the top mirrors page and the
google cache of the US mirrors page.
Remember that images on those pages (little flags) are still sucking up the main kernel.org bandwidth.
That many mirrors don't have 2.4.22 yet.
Really - I'm trying to be good, but if the mirrors don't have it...
My opinions may have changed, but not the fact that I am right
I've thought about upgrading since I normally like to run the latest stuff (plus I'm hoping 2.6 will fix the broken SBP2 driver).
However, trying to get all my settings into this new kernel was not so easy (it was quite painful upgrading to 2.4 also). I'm running on a big laptop so I have a lot of special case hardware that had to be tweeked. Now, I've been a Linux user since the kernel was at 0.97 or so and I remember thinking how complicated all those kernel options were. Jump forward to today and damn, TOO MANY OPTIONS is all I can say. 99% of it I don't care about but I have to go through each one to make sure the kernel will work... agonizing. I wish the kernel could configure itself (a la Microsoft's "detecting and installing hardware").
Combine that with trying to get nVidia drivers that work (yes, yes, there are patches and all kinds of crap I can spend time screwing around with).
And then trying to get VMware to work on the new kernel...
And so on...
Well, let's just say I'm just sticking with 2.4 for now.
The ratio of people to cake is too big
The dinasour book?
Could anyone give me a hint why this book have dinosaurs on it?
I have read it but I didn't grasp the dinasour bit..
For the exact instructions above we cannot get the average user to upgrade their systems.. Kernel updates are stil crypic under a normal GUI based upgrade and gives the end user no idea of any reason to update it.
Does anyone know of a guide for how to modify a vanilla kernel for use with SuSE? I'm not just talking "make menuconfig; make bzImage; make RTFM...". I'm talking which patches to apply, standard configuration options, how to get all the niggling things like 802.11 and DRI to work. that or an rpm or tarball that can do the above.
Problem is when you spend too much time deciding if the timeslice request is from the gui or if it is from your ethernet interrupt or if it is from your game port or if it is from your disk drive, keyboard, frying pan, toilet, telephone, tea kettle, tissue paper dispenser, trackball, Bob, etc. etc.
"Only in their dreams can men truly be free 'twas always thus, and always thus will be."
--Tom Schulman
With the Sun in now so close to mercury and the earth now bieng bombarded by Kernel Penguin, Might I catch MadHatter disease if I try to make clean 2.4.22 just yet?
OH THE SHAME I fell off the wagon and use sigs again!
Is the ptrace race-condition vulnerability fixed?
.21 fixed that.
:-)
Still running 2.4.20? Because
It's certainly more important than some whitespace convention in 2.5, or
updates to JFS (which may or may not contain copyrighted code.)
Of course JFS contains copyrighted code... somebody had to write it. I think it was IBM.
Funny, I did the exact opposite (although I wasn't using Orinoco drivers, but the D-Link G650 ones). It took me 2 minutes to fetch from CVS, build and load the module, then everything worked like a charm. I feel like I'm sounding like a damn commercial, but with a little knowledge - just a little - Linux is very rewarding. Never mind the trolls bitching about different distros, window managers and all that. Chose what you like and go with that. Help each other out once in a while.
It really works, and it's definitely among the best alternatives.
Are you telling me that these people are incapable of describing in a sentence or two what their fix does?
:)
Yes
Hope somebody can implement it and release it BSDed so Microsoft can benifit from evil bit too.
For what it's worth, I verified the patch archive and the signature was good.
Belief is the currency of delusion.
Great, lets see if this new release solves my IBM R40 notebook udma harddisk issue.
Been using 2.4.21-AC-3 to enable udma a week or two,
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
ACPI? I don't know what it is, but I'm sure it works better on my Mac!
You show me one average user that can update their kernel.
:) but many see the same problem and that's why Linux will work in corporations fine with correctly trained IT staff but not for the average home users.
Can it pass the mom test? No, then point made.
Kernel updates should be seamless and not break anything that you had compiled for the kernel..
EG Nvidia drivers. I'd love to have my parents use Linux but if every time the updates are needed (although rare) I'd have to either ssh into the box or go there physically. Trust me you cant tell them how to do it over the phone (hard of hearing)
Maybe that's the whole problem. Upgrades in windows have rarely caused problems. But on the other hand a simple update to Redhat 8 on a production server completely broke it requiring a backup to a older version. The system in question was a webserver and some security update rendered RPM unusable and some subset of RPM has to work for apache to work properly so we were screwed.
I think it's time to get the devs of RPM, apt and all other major packaging programs and make them form a standard and stick with it. And whatever standard should work to where 1 package will work for all systems instead of such things like RPM where you have a rpm for every flavor and version of processor and distribution. EG Redhat RPM's and Mandrake RPM's.
As processor speeds and faster subsystems make code compling a short trip instead of the long times it can take for bigger projects maybe source packages that compile on the target system into a correct rpm for that system/distro and installs itself. But for it to be tolerable you're looking at least 6ghz with solid state HD/PCI-X/XDDR-RAM wihtout any bottlenecks.
Anyways I think I'm rambling now
Because the GUI is slow. Slow, slow slow. That is, slow compared to everything else. Do you really expect that checkmark to be repainted before anything else in the system happens? Do you really expect you can even notice it not happening in the time it takes your find to raise up from the mouse button? With a GUI you have a few milliseconds to spare, an enormous amount of time in the CPU.
A GUI should never have top priority on a system. Your video decoding, maybe, but not the damn play button!
A Government Is a Body of People, Usually Notably Ungoverned
Do you suppose they did anything with the AIC7xxx driver?
o Aic7XXX and Aic79XX drivers
o Aic79XX and Aic7xxx Drivers
o Aic7XXX and Aic79XX Drivers
o Aic7XXX and Aic79xx Drivers
[...]
o Aic7xxx Driver Update
o Aic7xxx Driver Update
o Aic79xx Driver Update
o Aic79xx Driver Update
o Aic7xxx Driver Update
o Aic7xxx and Aic79xx Driver Update
o Aic7xxx and Aic79xx driver Update
o Aic7xxx Driver Update
o Aic7xxx Driver Update
o Aic79xx Driver Update
o Aic7xxx and Aic79xx Driver Update
o Aic7xxx Driver Update
o Aic79xx Driver Update
Install RedHat 9. Start up2date - enter information. Edit up2date config (easy, within the program) and remove "kernel*" from the exclude list.
.. ) but that's it.
Now kernel-updating is done in the same way everyting else - from the web with a few clicks with the mouse. Sure, you'll have to restart the machine aftwards (it's a new kernel
it's in my head
I for my own after 10 years of open source and Linux am up to search for alternatives. A commercial OS may be better (better documentation, professional development, you can make a few bucks with your work, no pain, stable ABI and API and much more).
Many of the people who are using open source are using it just for those reasons. In real life, APIs and ABIs to commercial software change rapidly because they are driven by marketing and business interests, documentation is costly and written for morons, you can't even look at the source when you are stuck, and you end up paying so much money for the privilege of using it that you won't be making any money on it.
And commercial software has the unpleasant habit of simply disappearing from the market at the most inconvenient times or having its price skyrocket unexpectedly. Remember DEC? They're gone and a lot of their software. Remember NeXT? Absorbed by Apple, and all you can get is the OS X variant; hope you didn't bet on their PC version. Remember Taligent? NeWS? Smalltalk? Microsoft Java? OS/2? Amiga? Gone, gone, gone, gone, gone, and gone.
GNU/GPL, FSF, prayer RMS they all should go to hell they are all paralyzed.
The FSF does something about software they hold the copyright to. For the Linux kernel, the kernel copyright holders need to do something. Give it a few more months--these things take time.
People stealing open source code and embedd it in closed source programs and nothing can be done against it.
Yes, that's kind of annoying, but it isn't a threat to open source software. And sooner or later, those companies tend to get into trouble anyway.
For example, I've heard that the NT kernel is actually quite good
The NT kernel reminds me of the Ford Edsel: people rave about all the technically good things it supposedly does, but ultimately, it's not really a car most people would drive by choice.
Simplicity of design and interfaces and cheap, low-tech solutions have their own value. Linux is more like the Japanese budget cars of yore: good, reliable transportation, while NT seems more like some US car company's technical pipe dream that just isn't coming together quite right. You can figure out yourself which one is likely to be better and more affordable transportation.
..in kernel 2.4 back in 2001
e
http://sf.net/projects/kautoconfigure/
-and-
http://www.google.nl/search?q=kernel+autoconfigur
Hope somebody revives the project someday...
leh bas sab el deen ya a7' ?
Kai Makisara: o Change Kai Makisara's email address So glad that finally made it in....
Once again, it happened... Put an empty machine on LAN, install Debian, download 2.4.21. Compile and install new kernel, then install Links to read news for a few minutes before the machine goes to production.
.... then again, I wonder how long the kernel guys could possibly keep releasing new kernels while I'm in a middle of compiling the previous version.
While reading news notice that a 2.4.22 was released. That was like... 10 minutes after downloading and compiling 2.4.21.
I'm afraid to even try compiling 2.4.22 now as 2.4.23 would surely be released before the end of the day....
... just avoid RedHat. They're rapidly moving to a point of making their own proprietary version of Linux but making the distribution so reliant on extra bits they've put in themselves.
I would suggest that next time you wish to upgrade your machine go Debian, Suse or if you're a techie person then Slackware.
seebo ya 3am yeseb we yel3an zay mahoo 3ayez, lama 2.6.22 tenzel 2eb2a seb enta
The lunatic is in my head
I don't have a problem compiling a new kernel. I have done it before (back around Redhat 6.1). So I am not looking for some super-easy way to compile it. I want to know what is in it, in "plain English". I understand that there's a lot of technical stuff in there, and I don't expect it to be explained so I can completely understand every single modification. But how about two sections, one for the big features (like USB 2.0 support) and one for tweaks (optomized function blah, which you'll never see).
I know that this info is kind of out there, if you look. I just wonder why it can't be put together and released with the official announcement. The information should come from the source, which IMO is the kernel maintainer. I think it would make people more likely to adopt a new kernel, without them having to wait until the update their distro. It isn't for the end user, not even close. I can't imagine that everyone else either is clueless and just upgrades their distro, or knows and understands everything that goes on with the kernel. I am somewhere in between. I could probably research it and figure it out, but couldn't the kernel maintainers just tell everyone what is in the new kernel? I would think they would want to promote it. Not marketoid speak, just good, informative release notes.
My beliefs do not require that you agree with them.
What fix is it ? I own a DSC-P51 and it works fine using usb-mass-storage on a 2.4.18 kernel...
blah
Interesting... I really don't see how a modeling language can be compared to an operating system though?
:)
In any case, thanks for the info
Err, No. Don't do this.
Configuration files are NOT compatible accross kernel families.
Do NOT use configuration files for RedHat and then attempt to use them with plain vanilla kernel.org kernels.
you will be VER VERY sorry one of these days if you do...
If you do this, you have a ticking time bomb waiting to go off.
Always create a new configuration file with the vanilla kernel you download and do not mix configuration files across kernel releases.
-Hack
Got Geometrodynamics? Awe, too hard to figure out? Too bad.
From my [admittedly modest] knowledge on this, incompatible kernel options are discarded on different versions, and don't negatively affect anything else. So the worst thing that could happen is one kernel compile that'll miss an option or two... or at least that was what I thought until now.
There are no impacts on stability from my experience with this, so are there security implications?
to you : FUCK OFF...and die troll
/.ers reading this post : this is free speech and by no means a nazi propaganda, just because some fucktard thinks that their logo is "swastika-lookalikes" said fucktard should get his/her eyes examined.
for the remaining
thank you ladies and gents that all for tonight.
And even if we sweep this issue aside
ahh you realized that you are an asshole and that the logo on the site represents a "Z" letter not the four branches of swastika, a symbol is a symbol stupid there is nothing called "lookalike" symbol.
and it is *STILL* free speech so eat your heart out loser, Zundel is entitled to his views just like you are entitled to yours, Shame on you for prosecuting someone for their beliefs, it is ok for a man to question if God exists or not as much as it is ok for a man to question the holocaust as much as it is ok for a man to question if earth is round it is called FREEDOM of SPEECH.
Yes, there are problems.
Primarily, if you are using the "experimental" options in a kernel build.
If you attempt to add experimental options in a kernel that uses a different kernel config file, the results are undefined.
That is, the kernel isn't guaranteed to build correctly with experimental drivers, adding a diffeent config file with experimental options or built in options that need to be configured at compile time, could result in values that are compiled for modules that could cause an oops.
A good example, is the tag settings for a experimental SCSI driver. Usually you can set how many SCSI commands you can have outstanding, for your SCSI bus, before the device demands attention again from the driver.
Say the author put in a value of -1 for the experimental driver in release 2.4.x.
You makde a config for that and put it in a recent release, called 2.4.x+1.
Well, 2.4.x+1 is no longer an experimental release, and -1 when compiled, will be outside the range of the expected values. The Author, expected you to generate a new config, which WOULD have provided the module with the proper info.
So you compile it, and when the final release driver gets a -1, it oops the kernel, trashing your partition.
-Hack
Got Geometrodynamics? Awe, too hard to figure out? Too bad.