Slashdot Mirror
Linux 2.2.15 Released
Fluid Donkey was the first of many to let us know that kernel 2.2.15 has come down the wire. It's a fairly large patch (just over a meg), but it contains many updates, including support for Intelligent Input/Output (I20) devices. You can find it in the usual places. (ftp.<two-letter-country-code>.kernel.org if you forgot)
kernel upgrading is a bitch. remember this:
keep rescue disks and back everything up.
I had many problems upgrading on Redhat. I had to make many manual changes. the lib/modules directory wasn't created initially. a whole host of stuff.
As far as information. The README in the kernel source tells you how to do the kernel recompile. You just need to Cover Your Ass by throwing the existing kernel and lilo configuration on disk somewhere before you go experimenting.
I'm too tired, so I'm probably not making sense.
My fav:
Name: Douglas Stanley Jr.
Email: IT-Manager@MontgomeryAirport.org
Location:
Occupation:
This is one of main weaknesses that plagues open-source projects. This kind of software is a blessing, but it can be frustrating to wait for upgrades. Linus Torvalds may claim that his job isn't hindering further development of the 2.4 Kernel, but the fact is that it IS problem for most working people. One advantage that proprietary software has is what I call "market discipline"; if a company sets a schedule, and sets budget and manpower levels adequate to the task, they can usually finish the task in the desired amount of time
Kinda like Slashdot's "IT Consultant" troll, but apparently for real.
I'm running root RAID on one of my boxes, which is still running a copy of 2.2.11. I was going to update it to 2.2.15 tonight, but remembered the root RAID patches that I had to apply before. I checked out ftp.kernel.org's raid patches, but the last one available was 8/24/99 for 2.2.11. Is this patch ok to apply against 2.2.15, or is the latest root RAID now incoporated into 2.2.15, or what? Any help would be appreciated...
WWJD? JWRTFM!!!
I don't normally do "me too" posts, but I gotta add a bit to this one...
:) (Elvii forgets what he just said about not upgrading for upgrade's sake. :)
My router ran 2.0.37 before it died. (massive failure of 9 year old hd) The new one got a 2.2 kernel because it was a backup/test box, and wanted it up in mimimum time. But, it uses no more than is available in 2.0. 2.2 was on it, and it worked.
In short, use what works. Don't upgrade for upgrade's sake.
Thou on a more interesting note, the same box is running debian potato. Talk about a moving target there.
bash: ispell: command not found
This sig left intentionally blank.
Most of the changes in 2.2.15 were actually back-ported from the 2.3 series kernels. For example, I helped Kai with some changes to the 2.3 series tape driver, and those changes have been backported to the 2.2.x series kernels (but not in time for 2.2.15, sigh... maybe 2.2.16).
-E
Send mail here if you want to reach me.
Red Hat release a new version every 6 months...usually April and October. Every year it's been like this. So...don't grab the latest release in September either. :)
Well, there were 20 prereleases. And Alan's diary did note that he had sent a 2.2.15 to Linus. And there was already a 16pre1 out there. A bit more checking and you wouldn't have had this problem. Oh well, it's fun anyway, right? :)
I have always wondered what it is and what it does?
Well, since you don't want to take the 5 seconds on Google to search for "i2o", I did it for you.
Check out www.i2osig.org, or go straight to their Q&A section.
More importantly would it give me any speed improvements on an IDE system?
I'd guess it might, if you had an I2O IDE controller. Check out this list of products.
2. Why are additions being thrown in? Are they at least defaulted to "N"?
I would assume they default to "N" (most things do) but I can't swear to that.
As for the why - they are being thrown in because people wish them to be thrown in, and because it pleases the benevolent lord of the 2.2 kernel, Alan Cox, to grant these people their wish.
Seriously though - the additions being "thrown in" are device drivers, for devices that didn't exist when 2.2 was released. People own these devices and need to use them - you can't just tell them to use a dev kernel, or wait for 2.4. You need to implement these drivers as quickly as possible, test them hard (2.2.15 had about 20 -pre versions before this final release, you know), and then get them out there!
I suppose you could adopt a "bug fixes only" attitude towards changes in the stable major version, but you would really really need to have much more frequent major releases for that to make sense.
I2O is pretty naff from a software standpoint. The i960 that is used for the IO processor (hey they used to use Z80s for this!) runs vxWorks. Couldn't they have used an open source "alternative" like RTEMS?
When they release 2.4.x! (or 2.5.x, for that matter...)
:)
But, in the meantime... over a meg? Anything really cool I should know about?
If there's no Changelog, I guess I could just grep through the patch. Documentation is for wussies anyhow, right, guys?
---
pb Reply or e-mail; don't vaguely moderate.
pb Reply or e-mail; don't vaguely moderate.
What size limit?
Did you try typing "make bzimage" or "make bzlilo"?
---
pb Reply or e-mail; don't vaguely moderate.
pb Reply or e-mail; don't vaguely moderate.
They therefore created "water++", or I2O, to fix the problem. I2O is "virtual water", and provides all the liquid refreshment your PC requires.
Unfortunately, some motherboards don't have the necessary aqueducts to support I2O. In these cases, it is necessary to install suitable drivers who can run taxi services to and from the I2O manufacuring plants.
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)
And Leno's people wrote this question, and intercut shots from Who Wants to be a Millionaire with Ed Hall sitting in front of a fake game set. Hal Duston
(Rant) It's too bad Don Becker and team are no allowed to maintain the Ethernet drivers for Linux anymore--now we have a bunch of apparent amateurs breaking stuff. Oh well. :-(
hook, line, and sinker.
come on, could he have been more obvious?
(This comments are from my severely coffee deprived brain, so it might be wrong on a few points).
I believe DPT got stung with some of the code that was used because they got part of it from the I20 orginization and it has be be kept seperate from the kernel due to licencing issues. But, there has been quite a bit of work being done to get the I20 drivers in the kernel to run the DPT cards, and thus you wont have to use the one provided by DPT.
I haven't look into it for a while, I'll guess I'll have to revisit it now.
Actually, yes. I installed Linux from a single CD on my Sparc 4, Sparc 20 and an Ultra Enterprise 4000. The kernel has had support for the starfire for some time, too, although they wouldn't let me near ours with a Linux CD :-( Oh, and the same kernel image can be used on sun4c machines, too, which is more than can be said for Solaris. That said Solaris does currently scale better than Linux.
"The invisible and the non-existent look very much alike." -- Delos B. McKown
Same thing happened to me a few weeks ago. I was 500Mb into d/l redhat 6.1. What happens that sunday when I want to continue the d/l. Redhat 6.2. Happy d/l.
You are missing something.
Odd numbered kernels are development kernels, while even numbered ones are "stable".
There are lots of good reasons to use 2.2 series kernels, like not having weird-arsed crashes owing to obscure bugs under heavy load, being more confident that there are fewer unpublicised security holes, yadda yadda.You may not be living dangerously using a 2.3.x kernel, and if you have obscure hardware you might NEED to, and someone has to run them or they won't be properly tested, but sometimes you need the comfort of a stable series kernel.
I'm upgrading after trying out a DoS I found from (packetstorm I believe) on a friend's 2.2.14 machine, and royally pissing him off in the process. :)
the real at&t mix
I am just as American as the next umm... American, but I always download the kernel source from the Vatican mirror. I'm no Catholic, and maybe I'm nuts, but perhaps there's something... different about a kernel from the Papal State.
--Ben
--Ben
These don't seem to work with 2.2.15.
Back to 2.2.14 I go!
(BTW I get no video at all - blank screen - and can't swtich virtual consoles. Ctrl-Alt-Del fixes it though.)
:-(
I'm out of my tree just now but please feel free to leave a banana.
2.0.37? I've got one machine that's still running 1.2.13! It just keeps running, and it's not directly on the net so I don't have to worry about remote crashes... It's hit 365 days uptime twice in the 4 years it's been around, and would have gone longer if it weren't for UPS maint and server room rearranging...
Too bad I can't find a copy of SLS... I want to try running it in vmware to try to remember what it was like when I started long ago with 0.99pl5.
that you should mention stability. I just wrestled a 2.2 kernel bug to the ground that was causing my dual processor machines to crash- ok, actually, RedHat beat me to the punch, and it was their custom 2.2.14 kernel that was the problem. So they provide an updated version, also labelled 2.2.14. What gives? Why is redhat providing patched kernels of the same minor version? Why not just provide the *official* 2.2.14 kernel and send bug-fixing patches to AC? Talk about miffed- everyone's getting excited about 2.4 and we're still facing 2.2 bugs.
So long, and thanks for all the Phish
Clickitty click.
--
I think there is a world market for maybe five personal web logs.
Your too busy to compile a new kernel yet you find time to read slashdot and post comments?
;)
I'd rather use windows then linux 2.0.x
That's really cruel.
I *just* finished a wipe and reinstall on my home
desktop machine not 20 minutes ago, and now I gotta download and recompile the kernel again.
arggghhh...
I have always wondered what it is and what it does? More importantly would it give me any speed improvements on an IDE system?
You don't exist. Go away. --SysVinit Halt
Being able to read file-systems is built into the Linux kernel; being able to create them or do things like export them via NFS can be done completely in userspace--Linux's kernelspace NFS-export is purely for speed.
I've found that 2.2.x can't export things that it has mounted over NFS, but you be able to export whatever you want with a userspace daemon, until knfsd issues are resolved.
-rozzin.
As usual, everyone loves to complain that they just installed the previous kernel when a new one comes out. Here's the solution: download patch, apply patch, make config, compile, vi lilo.conf, shutdown -r now. It takes all of an hour. It's not hard. Stop your bitching.
No changelog in linux/ of the tarball
I don't understand why you expect to find a ChangeLog in these places, since none has ever existed there before.
You can grab the changes from a Linux Today search. For example, here are the 2.2.15-pre17 changes, which is pretty close to 2.2.15 proper.
And eventually the changes will also be posted by Alan Cox on the Linux.Org.UK home page along with the other 2.2.x release notes.
Jeff
For people who can't afford the random breakage that crops up with 2.3.x on their production machines, it's pretty important for bugs to continue to be fixed in the 2.2 series. Also backporting new drivers is pretty nice.
Damn straight. I tried one of the 2.3.x kernels a few weeks back (sorry forgot which one) because it had the agpgart.o module avalible directly in the kernel. It worked fine.... EXCEPT for some bizzare reason it would not umount my drives when I issued a shutdown.
Ill stick with 2.2.X and a loadable agpgart.o for now.
Try to hack my 31337 firewall!
I think it's great that it's taken half as many patches to get 2.2 rock-stable as it took for 2.0 to get nice.
Yes, 2.0 did have more time to grow, due to the long 2.1 cycle, but the frequency of 2.2 releases has been less than the 2.0 releases.
More developers, fewer bugs, world domination. Brought to you by open development, a subsidiary of free software.
>hmmm... you don't need that much fixes.... Just rename win95 to win98 and sell it.... ;-)
You also have to put the word 'internet' and the letters 'i' and 'e' all over the program
yes, this does happen to some degree. But by whinging you will still get taken down, and I hardly think that YOUR critique on "linux zeolots" is hardly constructive, in which case your post deserves to get moderated down.
I'd rather see moderation groups, so that given a group of preferences, I can see the list moderated by people like me. That way you don't get this massive wave of people moderating posts down which they "simply don't like".
my 2c.
> 1. This won't make it into potato/frozen.
Most likely not. That's a vital component of a system, and the Debian folks are not going to put a shiny new kernel release into a frozen release that they're in the final testing phases of. Besides, (and you may get differing views on this), as a standard rule of thumb, the first thing you do after installing a system should always be to compile a fresh kernel. I expect the vast majority of Debian users do this as a rule.
> (By the way, what does it take to get Slashdot to notice a story you submit? I :P
> submitted close to 9 stories as an "Anonymous Coward", 3 as Fervent (I was the first
> to make mention of the Limp Biskit-Napster support thing) but no mention of my
> name on the front page. Is Commander Taco some kind of malevolent dictator?)
Haven't you heard? Before being processed, submitted stories are uploaded to a nearby windows workstation and stored in the Windows Registry. As everyone knows, the recovery rate for information stored in the Windows Registry is 1 out of 5. Next time, to account for this try submitting the same story 68 different times under different usernames. I think there's something about this procedure in the FAQ...
i20 drivers are in FreeBSD SNAP 128 and greater. Although they are there, and seem to be pretty stable, they still lack many features; no CDROM support and some bugs.
Linux O Muerte!
Actually, in Europe if I recall correctly, it's a decimal comma, not a point.
Yup, that's right - except in the UK, where it's a decimal point...
Cheers,
Tim
It's official. Most of you are morons.
seriously, one of the reasons that linux is great is that there is a good amount of maintinance and increasing stability in the 2.0 series... (that's why this is flamebait!!!)
NT 3.5 is still used in a few places because of security probs in 4.0. I know a few ppl who wish it was maintained as well as linux 2.0. now don't make me make another microsoft comparison again!
Sounds like the same problem I had, it's because the format of /proc/mounts has changed slightly in 2.3.x, and Redhat's halt scripts use this file to work out what needs to be unmounted. It's trivial to fix :)
a better way /etc/lilo.conf look some thing lie this
/usr/src/linux ..//.conf . /sbin/lilo && reboot
first make sure you
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
linear
default=linux
image=/boot/vmlinuz
label=linux
read-only
root=/dev/hda2
image=/boot/vmlinuz.old
label=linux.old
read-only
root=/dev/hda2
yours will be a bit differant but the main thing is the linux.old entry
then cd
cp
make oldconfig
make dep && make clean && make bzImage && make modules && make modules_install && make install &&
then you can go get a coffee
What I believe you want is this, the Kernel HOW-TO.
And yes, Commander Taco is a malevolent dictator.. refused to post a submission of mine on the DMCA rally that happened 2 days ago.
Of course, since sites like Slashdot apparently don't find this worthy of the front page, many people had NO idea it happened, or if it even happened at all, including myself. Remember last time when there was a DMCA protest, Slashdot gave like 2 days notice? I sent this in -weeks- in advance, and Slashdot posts nothing. What's up with that?
Anyway, off my soapbox, and happy kernel'ing.
BilldaCat
Uh... Alan Cox (maybe you've heard of him) is the one who coordinates the 2.2 maintenance releases.
For people who can't afford the random breakage that crops up with 2.3.x on their production machines, it's pretty important for bugs to continue to be fixed in the 2.2 series. Also backporting new drivers is pretty nice.
I know you're going to say "2.3.whatever is totally stable for me" but you probably can afford the risk of downtime. Also high loads seem to uncover bugs that most desktop users don't see.
> Unfortunatly I use redhat.
Oh man, that is unfortunate!!!
SLACKWARE RULEZ!!!
( Sorry I couldn't resist! )
Johnny O
Even more clueless users can be found on Borland's Kylix newsgroups. It's quite amusing to read the baffled Windows coders asking questions like:
:)
"What do you mean Kylix won't support DDE!? How else can we make apps communicate?!" and "I've never seen a Linux DLL, what about you?"
I got a good laugh on an otherwise depressing day after reading that stuff
Every damn piece of wackyness is turned off by default in this kernel, just the way I like it. About time things stoped getting defaulted on just cause they were some developers baby.
On a lighter note, I went and bought the "Linux Core Kernel Comentary." I think this makes me a slashwhore, for running out to by it right after reading the review.
But it means that I will hopefully be adding to the kernel by the fall. Will you?
---
"Elegant, Commented, On Time; Pick any Two"
-- Crutcher --
#include <disclaimer.h>
Cheers.
GNU/Linux. The Freshmaker.
# diff -r /usr/src/linux- /usr/src/linux-
--
"The crux of the biscuit is the Apostrophe(*)" - FZ
--
"The crux of the biscuit is the Apostrophe(*)" - FZ
Oops! I forgot previewing... /usr/src/linux-new.version.number /usr/src/linux-old.version.number
# diff -r
--
"The crux of the biscuit is the Apostrophe(*)" - FZ
--
"The crux of the biscuit is the Apostrophe(*)" - FZ
-snip-
Package: kernel-image-2.2.15
Version: 2.2.15pre20-1
-snip-
The pre20 is already there. I guess we will include the real 2.2.15 there two.
signatures pending - ansa@kos.to - (dont mail there)
The regular maintainers work on this. It is commonplace for chages made in the development branch (currently 2.3.x) to be "rolled" back into the stable branch (currently 2.2.x). Generally, only those changes that have been in 2.3.x for a while, and are considered "safe" will ever see 2.2.x. Bug fixes just get merged in, since they don't shake things up too badly. New functionality (read: drivers) will probably be marked experimental.
When I say "Darling, guess what! Kernel 2.2.15 was just released hours ago and here we are still running 2.2.14!"
How many people have upgraded software on the sole basis that the new version includes Hungarian support (Besides the Hungarians out there)?
Alright! We'll slashdot them with 404s! This could be a milestone for slashdot. A momentous day indeed.
There are actually a large number of us.kernel.org's. (Do an nslookup on it, I count 25+ currently.) They are all independent mirrors that have the same directory structure, or at least /pub/linux.
You were probably unlucky and got one of the slow mirrors. Others may have gotten an updated one.
Actually, the decimal system specifies a single decimal point!
It's the morons that started the assanine idea that multiple decimal points belong in any kind of nomenclature thaqt are responsible for the confusion. "Best practices" is a zillion industries for a century or more have recognized the danger of using the decimal point as a saparator.
Dashes are the traditional separator character choice where there needs to be a division for convenience: take phone numbers, for example, or the vast majority of part numbering schemes out there.
[FLAME ON]BTW, this "cool, it's like the net" crud of using dots as separators in phone numbers is garbage. Although most people don't know it, there is a correct and standard way to write phone numbers: the IDDD standard, which specifies a leading + followed by country code ("1" for the US, Canada, and the Carribean) and phone number, separated into groups with dashes by whatever convention prevails in that country.[FLAME OFF]
"The future's good and the present is nothing to sneeze at." - Roblimo's last
"single decimal point" where? Actually, in Europe if I recall correctly, it's a decimal comma, not a point. That something has been done for plenty of time does not guarantee it's eternal existance unchanged.
Second, a version number is not a decimal number, so your "single decimal point" standard has no bearing on it; it's quite clearly documented that it's MAJOR-VERSION (dot) MINOR-VERSION (dot) REVISION, which is much more legible than using dashes. Why? Because a dot, at least for CS people, has quite a diferent connotation than a dash.
And third, why drive yourself up in a tizzy just for something as unimportant as the kernel version number separator character? Just because we/they don't think as you do? Is your consciosness so limited that it can't do context switches when it finds manifestations of new ideas? Relax, have a cup of coffee (or whatever) and get on with your life.
-elf
http://www.linux.org.uk/VERSION/ relnotes.2215.html
Yeah. Grab a Slackware either. They don't release that often. They're just "slacking". =:-)
--- If OS were buildings, then the first woodpecker to come around would erase 95 % of civilization.
What's wrong with:
/boot stuff is nonsense - I 'fix' that first thing after installing a distro...
make bzlilo; make modules; make modules_install
or getting more picky:
make bzlilo; make modules_install (since it'll make the modules first anyway)
bzlilo takes care of all of your stuff... and I still think that
"It's tough to be bilingual when you get hit in the head."
My year old celeron does it in ~3 minutes, give or take. I still remember when I got my pentium 100, and took my compiles down from ~1h15m(486/66) to ~12m. *That* was bliss.
/. posters aren't kernel developers either ;)
;-) Never got it quite stable enough to merge in, but it worked for me... as long as you waited a little bit between a network stop and start... the restart would trigger some nasty interrupts, and spew madness to the screen for a while... not anything I would feel comfortable submitting. Then I sold the card to a windows user friend. Works great 8^)
>I'd guess quite a lot of
Gee, I hope not 8^) My best effort was fixing a network driver... non-Becker, of course
"It's tough to be bilingual when you get hit in the head."
Back in the Good Olde Days, sure. Now, I'd be willing to bet that a census would show the majority of Debian users out there are running Corel Linux with its (almost) single-click installation, and most Corel users would be terrified at the idea of compiling a kernel. Well, at lease those who know what a kernel IS. :)
Note that word "most" in the last paragraph. If you're using Corel Linux on a quad 1GMHz system overclocked to 2G with liquid helium, working 24-7 to develop Gnu/Linux 3.0 and Gnome 3.0, please don't flame me for the generalization. :)
-- John Dierdorf, Austin TX
Bah. People today don't know they're born.
/. posters aren't kernel developers either ;)
My first Linux box took *8 days* to recompile the kernel (2Mb 386sx33). I ran a lot of Stuff for a fair while on a box that took about 28 hours to do a kernel build. You *really* thought about giving the right answers to 'make config' at that point.
I think the current main box takes about 2 hours. I don't do it often enough to care much, but maybe I would if I was a kernel developer. I'd guess quite a lot of
There's always room for modules.
Nautilus is the code name for the Alpha Processor Inc. (API) UP1000 motherboard, not the Gnome stuff.
The Alpha directory is for the Alpha processor, not alpha as in beta.
I work for API.
What's my Karma Mr. Burns? "Excellent"
I wish they'd use a scheme like 2.2.009 instead of 2.2.9.
When looking through FTP, and trying to find the latest release, it's REALLY annoying to have to look through the whole list to find it. The newest, 1.2.17 is actually quite a bit higher on the list than 1.2.6.
If the project was named 1.2.017 and 1.2.006, we wouldn't have this problem. We would, however run into a problem of only allowing 1000 releases per minor version number, but why REALLY wants to see more than 1000 releases before a new version comes out?
OK, so I finally decide to upgrade my 2.2.10 kernel to 2.2.14 to fix a bug with my ethernet card stalling. And what happens, not 3 hours after I reboot into 2.2.14? They release 2.2.15!
Sometimes I think I have worse timing than the Debian maintainers. (ducks)
http://www.linux.org.uk/VERSION/ relnotes.2211.html
http://www.linux.org.uk/VERSION/ relnotes.2212.html
http://www.linux.org.uk/VERSION/ relnotes.2213.html
http://www.linux.org.uk/VERSION/ relnotes.2214.html
Do you see the pattern here ? The changelog for 2.2.15 will most likely be available at:
http://www.linux.org.uk/VERSION/ relnotes.2215.html
Be patient, have fun :-)
RFC1925
It says that there are i20 drivers in there, is there any chance that the DPT SmartRAID V drivers might start shipping as a part of the kernel, or will we have to continue to hope that the supplied patches from DPT will work?
treke
That wouldn't work especially well for a distribution that keeps its kernel image in /boot/vmlinuz instead of /vmlinuz.
--
No more e-mail address game - see my user info. Time for revenge.
Win dain a lotica, en vai tu ri silota
did you try running Linux on a a PPC?
:-)
no size limit! (at least, not for practical purposes
Have access to a solaris box? Try "more /bin/clear" Shocked the hell out of me the first time I saw it.
-- Bucket
OK, so, as I thought, eth16i should still be there, it's just that menuconfig for some reason, after I applied the patch.... lost it!?
.config
ahhhh... anyway.... back to vi
Sigged!
This is a bit offtopic, as fr THIS version of kernel. I have patched kernel 2.2.13 to 2.2.14 and recompiled it. During the config, (used menuconfig) I noticed there was no etherteam16i module anymore?! When was that discontinued?
Also, where on earth can I find a list of changes between kernel versions? I mean, some changelog?
Thanks in advance!
Sigged!
can i have her instead, i really need one.
-- Ian Kirk
More generally, I'd be suprised if most serious active-active cluster solutions didn't support this in some way: planned outages are still outages after all, and they can get seriously in the way of a 24/7 service.
And loosely coupled clusters (Web farms etc) can of course do this sort of thing without problems.
--
Cheers
Cheers
Jon
I don't have the time to download a diff. In fact, I'm still using the default kernel of my distro. I have an asssumption, and then a question:
1. This won't make it into potato/frozen.
2. Why are additions being thrown in? Are they at least defaulted to "N"?
--
--
E2 IN2 IE?
Is there a changelog somewhere?
I`m only using 2.5 min to compile my kernel. I have to run to get that coffe ;) And geek`s do NOT run, umkai?
"If you loved me, you`d all kill yourselves today"
Spider Jerusalem
-Marc
P.S. Zealotry does not become you!
That's funny, last time I checked /. I got the impression that Linux out of the box had 0 downtime. Guess I misread all those posts.
-Marc
P.S. this is not a rant at you, but directed towards the misinformed zealots who seem to feel that Linux can do know wrong, and don't seem to understand that there is still work to be done.
Jesus, before you start spouting off at the mouth, maybe you better check your facts, Jack. Oh wait, you're a typical Slashdot user. No facts required.
You want to know why messing with my video card causes my machine to lock up? Because the I bought one of the first FIC SD-11 motherboards and have a Creative Labs GeForce DDR. And the two do NOT coincide nicely when trying to run at AGP 2x. So I have to run at AGP 1x. Sometimes I forget, and enable it in different ways trying to get it to work. And my computer locks up, due to the HARDWARE, fool, not the software.
So maybe it's not FUCKING DRIVER RELATED, JACKASS! Don't you look like the idiot now!
however, compiling a kernel is *still* a pain because of that size limit. I wish it would go away... do any efforts to get rid of the size limit exist?
Luckykaa wrote:
"Most people upgrade based on the assumption that any 0.0.01 improvement must be a huge difference.
I still use a 2.2.9 kernel because I can't quite stop feeling that kernel 2.2.15 should come halfway between 2.2.1 and 2.2.2"
I respond No!!!!!!!!!!!!!! Don't give into the Microsoft numbering scheme. They screwed EVERYTHING up!
They numbered updates to Dos 6.2 as 6.21 and 6.22. That is INCORRECT. The correct numbering scheme is 6.2.1 or 6.2.2. Why? Because 21 is 2 + 19, not 2+1. 2 + less than one would be 2.x, like 2.1, 2.2, etc.
That is how a decimal system works. Microsoft choose the other because it "looks right"
However, by that logic, the upgade path allows Major and Minor X.Y and upgrades off that are tricky... X.YZZZZ However, that means that you can ONLY have 10 minor upgrades per major upgrade, and only 10 patches off that.
That is CLEARLY a bad design. Especially because the correct idea:
Major.Minor.Minor-Minor.Minor-Minor-Minor etc., etc.
Allows infinite numbers of fixes. Within a single major release (Linux 2) you can have as many minor releases (2.0, 2.1, 2.2, 2.3, 2.4, 2.5, and so on, BEYOND 2.9.) Also, it means taht you can have updates on the minor ones.
Your warped numbered scheme means that you CANNOT go beyond 2.2.9. I mean, 2.2.15 is the 15th revision of the 2.2 Major/Minor combo. Each portion between the decimal points is an integer, not the decimal part.
Alex
I would moderate this guy down but I don't know what to call it. I really think there needs to be a "needs to be put to sleep" setting for moderators.
I've found this site to be helpful. It's geared towards the PowerPC Linux distros, but should be applicable for almost anyone.
John
>Actually, my MS box crashes more, because I sit >and tweak with my drivers for my SUPPORTED video >card. Sometimes it locks up, and that's hardware, >not OS.
HUH? You do realize that the drivers and operating system is what makes hardware devices run right? Hardware that locks up is dead hardware, for example: a hard disk drive whose motor is shot.
Or you mean lock up as in "I have this network card sitting on my desk and its locked up (not connected to a computer)"
You are a fucking idiot. Windows drivers and Windows architecture are 100% responsible for your lockups, not fruity hardware that runs just fine on other operating systems.
Lars -
Okay, one thing that always annoys me about kernel upgrades is that it is almost impossible for me to find a what's new file. For those of us who do not dream in Perl, have hours to pour over cryptic documents, or know Linux outside of the RedHat inspired distros (Mandrake), could someone please write a simple what's new document or something? I mean, is this really too much to ask?
generally your news stories have already been submitted about 1x times before you submit yours. Most of the time, they'll post news articles that are well written, and (of course) timely. Don't get miffed if your news piece doesn't make it. Most don't.
:)
Anyway - as far as upgrading your kernel. The best way to learn is to read the kernel HOWTO. It's a pretty good document, if not slightly antequated. It should be included in the dox on your box. If not...you can find it linked to at linux.org - Just make sure to keep a bootable backup copy of your old kernel ready to go just in case something doesn't work right. - or you just plain fuck it up
Happy kernel hacking!
FluX
After 16 years, MTV has finally completed its deevolution into the shiny things network
"It is seldom that liberty of any kind is lost all at once." -David Hume
Is this release just composed of patches sent in from people outside the regular kernel maintenance group?
:)
I can't believe that anybody from the actual kernel group would still be working on 2.2.x, it is almsot ancient after you've used 2.3.x.
Can't wait for 2.4 stable
And then: make bzImage; cp System.map /boot; cp arch/i386/boot/bzImage /vmlinuz; lilo; make modules; make modules_install; reboot
You don't keep the old kernel but always replace it with the new? I keep at least the previous kernel available (and entry for it in Lilo) just in case I've goofed something. Maybe perfect humans can survive infinitely with simple replacement of kernel, but I don't think I (or anyone else) am perfect, so... ;)
Everyone who makes generalizations should be shot.
Who the fuck cares, the show is a pile of crap anyway.
:/
It'd be a relief if the Yanks would take it back, and give Chris Tarrant US citizenship
Gosh, I just upgraded 81 million of my clients a minute ago.. A new version ALREADY!? .... Hey, when does 2.4 come out!?!?!
I'm afraid to patch my kernel!
I'm afraid that the boot messages will say "Linux is brought to you by Coca-Cola.com, Transmeta.com, GE.com, Snapple.com Doritos.com, BMW.com omahasteaks.com aol.com home.net netscape.com and Napster.com ".
(aka the Spam Patch).
Connection Closed by Foreign Car.
[Connection closed by foreign host]
Huh??? What is so difficult? just untar the source in /usr/src, do a make (menu)config.
And then: /boot; cp arch/i386/boot/bzImage /vmlinuz; lilo; make modules; make modules_install; reboot
make bzImage; cp System.map
Next drink coffe and return after 10 minutes.
Jeroen
Secure messaging: http://quickmsg.vreeken.net/
Jeroen
Secure messaging: http://quickmsg.vreeken.net/
Hmm. Seems like the agpgart module has not made it's way into this one, and the patch for 2.2.13 does not work.
All that we see or seem is but a dream within a dream.
Are you sure? Is that your final answer? Steve, you had 1 karma point........... you now have 3 (funny) karma points!!!!!!!!!!!
But then the internet wouldn't have existed had a Brit not invented the computer, monitors would not exist had a Brit not invented the CRT, and you would not be able to dial up and pretend the US did anything but throw money at other people's ideas and bully competition out of the way if a Brit hadn't invented the telephone (Alexander Graham-Bell was a Scotsman, even if he did invent his phone in the US).
So in this case 2.2.x kernels are the stable releases, and the 2.3.x kernels are the development releases.
apt-get install kernel-image-2.2.15
:-) )
(sorry, couldn't resist
There is much cruelty in the universe, John.
Yeah, we seem to have the tour map.
I remember when 2.2 came out I couldn't ever get on ftp.kernel.org, it was way overbogged, and ftp.us.kernel.org was always late in getting the latest patches and pre releases. I ended up using ftp.ca.kernel.org since it was plenty fast and synced up with the original kernel.org within an hour or so of posting patches. I'd be really great if the maintainers of all the us.kernel.org sites could speed up the sync some. Right now I just use ftp.kernel.org to get all the latest 2.3.99pre patches (and the pre-pre patches :) But I know one we get into the last week or two before 2.4.0 kernel.org will be impossible to get on. I think they may even limit kernel.org to developers only during that time. So let's speed up those us mirrors!!
Anyway, I think that anyone familiar with the Law of Fives would know that kernel 2.3 is more in tune with the hidden order of the universe.
Hopefully I didn't put any [] around my words.
I hate Regis Philbin.
Is that your final answer?
=================================
I pledge allegiance to the flag...
of the Corporate States of America...
I see, you are refering to that new spec from, what is it, -93?
When faced with a kernel patch I always check the source by hand, particularly looking for drivers that I've had problems with. A few minutes looking at the code specific to one platform determines if upgrading will be worthwhile.
I've had a look at the patch myself. Seems to be mainly I2O and ISDN updates, plus other device drivers for hardware I've never seen. A patch I submitted to allow an obscure sound card to be supported better has not appeared (although it is in 2.3). By the time it makes the stable kernel series, I won't be using this hardware any more!!
...but I found it on ca.kernel.org in both full source and patch form.
(By the way, what does it take to get Slashdot to notice a story you submit? I submitted close to 9 stories as an "Anonymous Coward", 3 as Fervent (I was the first to make mention of the Limp Biskit-Napster support thing) but no mention of my name on the front page. Is Commander Taco some kind of malevolent dictator?) :P
- I don't care if they globalize against free speech. All my best free thoughts are done in my head.