Slashdot Mirror
Linux 2.4.7 Released
Kazmat was one of the earlier people to write in with the news: "Linux 2.4.7 has just been released! Head on over kernel.org to download it or check the changelog." Remember to run lilo before you reboot! :)
← Back to Stories (view on slashdot.org)
for those with ieee1394 devices (in particular, DV cameras), keep in mind that due to recent "updates" to the 1394 driver things stopped working. specifically, there are issues in video1394 driver, which cause a kernel oops when using "dvconnect" program to read/send raw data to the camera. On the other hand there has been some restructuring in the 1394 code and now it at least seems to detect device insertion/removal and runs a kernel thread NodeMngr for this purpose...
anyway, hopefully 1394 stuff will be fixed by the next release (sending dv data didn't work in 2.4.6 + patches from linux1394.sourceforge.net)
(Yes, I know it gets said every time but people still don't seem to do it).
Go you big red fire engine!
Any sufficiently advanced technology is indistinguishable from a rigged demo
--Andy Finkel (J. Klass?)
(P1): arch/i386, arch/ppc, arch/sparc? These are all very confusing
(P2): gzip or bzip2 - this is a sort of browser, right? There are too many choices.
(P3): I couldn't find an icon for this "lilo" thing - it wasn't under the "foot" menu.
(P4): It said I was eaten by a grue, and I can't continue configuring it. What's a grue?
In all seriousness, great job to Sun for their Gnome Useability Report earlier today. This post is in honor of their hard work - hopefully Sun won't ask them to investigate kernel build process usability until they've rested up a little :)
Your right to not believe: Americans United for Separation of Church and
I'm not sure that it's any better than lilo, but the menu.lst does look a bit cleaner than lilo.conf.
Oh, it is. LILO stores the physical address of the first sector of the kernel image and boots off that, if you screw with the partitions even a little bit it'll cause the dreaded "LO" syndrome.
GRUB, on the other hand, reads the filesystems directly, no running it after every kernel compile, hell, you can even launch the uberleet GRUB command prompt and boot stuff you haven't defined ahead of time, it's extremely flexable and saved my ass a few times.
In conclusion kids: GRUB > LILO.
-- iCEBaLM
This post powered by Mozilla
Linux 2.4.7? I can beat that... I'm running on Linux 7.1!
So there!
(for those of you who don't know I'm joking - one of us needs help)
insignificant sig
I wonder if Linus, Alan and the whole linux-kernel crew would consider dedicating this version of the kernel to Dmitri Sklyarov. It would be a great way of bringing attention to a subject that we know hits home at least to Alan Cox.
0 /1 228200
http://www.newsforge.com/article.pl?sid=01/07/2
Using your sig line to advertise for friends is lame.
hrmm... recompile the kerknel while i'm drunjk or wailt till tomoror moringnig..? Ahh wtf, whats teh worst that coudl happen?
All I want to know is wheather or not the VM is stable. From what I understand it has been the source of instability and deadlock. I know Linus, Rik van Riel, Andrea Arcangeli, and others have been hunting for the source of the reported problems and did find some potentialially serious bugs but it's been difficult to reproduce the problem which as the programmers here know greatly complicates finding a fix. I'm getting some of this from the last paragraph of the Kernel page at lwn.net and there's an intersting thread in the lk mailing list here: Re: VM in 2.4.7-pre hurts.... Anyone have any insight into this particular problem? And I wonder if Linus will drop the issue and turn his attention to the imminent 2.5. I think that would be a mistake.
2.47 breaks the compilation of the vmware modules. If you need them, wait for an update from vmware until upgrading.
being a long time subscriber to 'if it ain't broke, don't fix it' i just thought i'd point out that i haven't upgraded to 2.4.7, and my machine still works just the same as it did yesterday... beautifully. it's been running beautifully for... 323d 10:09.45 now.
;
and even if using the newest kernel makes you 1337 TODAY, just think 10 years down the line when i pull out my crusty AMD and show the kids my 2.4.6 kernel. then they'll all be like "whoa, that guy's old school, he must be 1337 as fuck!"
"I hope I don't make a mistake and manage to remain a virgin." - Britney Spears
"I hope I don't make a mistake and manage to remain a virgin." - Britney Spears
- me: fix ptrace and
- numerous: IDE tape driver update for completion handlers
- Ben Collins: ieee1394 GUID cleanups
- Jacek Stepniewski: nasty deadlock in rename()
Whew, good thing Jacek was able to get that deadlock into this patch!
"Your superior intellect is no match for our puny weapons!"
2.4.7 is not only a dramatic improvement over 2.4.6, it is a whole new paradigm in linux computing. I urge any linux users to update with all haste. You simply must not miss out on the transition, or you will be left behind. From now on, we won't be asking "Got 2.4.6?" No, now it's "Got 2.4.7?"
The minor changes to USB will definitely rock your world, and you'll love what "initialize page->age" will do to your swap cache. I think Linus said it best, when he said "semaphores are not good swap handlers."
Remember: 2.4.7, a quantum leap forward.
Denial isn't just a river in Italy