Slashdot Mirror
Linux 2.4.19 Released
Adrian Voinea writes "The latest stable Linux kernel (2.4.19) is out. The somewhat massive changelog has the details. The patch file is here and the full source is here. If possible use a mirror."
← Back to Stories (view on slashdot.org)
What do you mean, "if possible use a mirror.". Use a mirror. The only time it isn't possible is when, say, the main server gets slashdotted and there ARE no mirrors.
When will you ever learn?
If it's the latter, can any of you linux gurus tell me what is the current "accepted" solution for making backups. Not archives or images, backups.
For those of you who are going to say dump works fine on 2.4, please read this message from Linus Torvalds. I keep hoping he'll change his mind though, at least until a viable alternative arises.
When 2.4.18 came out, i thought to myself "well i'll just wait till 2.4.19 comes out to switch to 2.4, shouldn't be more than a month or so."
Since then i've had to renew my drivers license three times.
Longest . . . update . . . ever!
"The crows seemed to be calling his name, thought Caw."
Can anybody here summarize any important changes that went on between 2.4.18 and 2.4.19? This changelog is just a ton of bug fixes between prereleases. Did they do anything interesting with it?
..."
This is exactly the thing I'd like to see someone make. A simple list of notable changes for the average kernel-compiling Linux user. I've been wanting such a list for several years now, but have never seen one.
Something in the form of, "If you which to use hardware X with option Y, you may wish to upgrade, as this version adds beta support for it. If you use option Z you should definately upgrade, there are many bugfixes.
Is there any kind of ChangeLog summary available anywhere? And if not, why? I shouldn't think it would be such a big deal for someone with some knowledge of the kernel.
I doubt, therefore I may be.
for about three minutes i sat wondering: who the fuck do you buy your hardware from that actually *license* their drivers, and requires you to *renew* them? I didn't know Microsoft started manufacturing important PC components...
then it hit me.
sigh... goes to show that friday evenings are best spent away from the computer for best results.
My life in the land of the rising sun.
Anyone else notice that in the last couple of days Microsoft's ad for Visual Studio .Net keeps coming up in the rotation when ever there is Linux story.
Wonder how much that cost them to buy those keywords? Could C. Taco be enjoying a quiet vacation on an island somewhere?
You say things that offend me and I can deal with it. Can you?
Anybody notice? Whenever you *used* to untar a new kernel tarball, it created a directory 'linux'. Now it creates 'linux-2.4.19'.
'Bout time! I always hated creating a temporary directory to uncompress to...
"Ignorance more frequently begets confidence than does knowledge"
- Charles Darwin
(02/06/06 1.537.2.10)
[PATCH] Re: mislabelled label patch
No pun intended...
Don't use LILO, use Grub! There is absolutely no reason for anyone to subject themselves to LILO any more now that we have Grub. Imagine: filename tab-completion, in a bootloader! Since grub can read your filesystems, you'll never be stuck needing to use a rescue disk if there is still a valid kernel somewhere on your HD. If you mess up the upgrade, you won't hose your system as long as you didn't delete your old kernel.
main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
Assuming someone else on this list was, like me, silly enough to buy a PowerVR Kyro-based graphics accelerator, here's a fix for a compile bug that I got w/ kernel 2.4.19 and gcc 3.1:
drm/pvr_drm_vm.h, line 138, change to:
physical = (unsigned long)page_address(pte_page( pte ));
Well, I've seen a few instructions for debian, but they're either wrong or not comented, so I'll try my own also.
/usr/src/linux or whever your favorite place is.
/usr/src/linux): /boot/config-2.4.18 .config .deb's ..
/lib/modules/2.4.19-me, /boot/vmlinux-2.4.19-me, etc
First, get the sources. I don't see them in the debian tree yet, so get them from kernel.org yourself. Put it in
To compile (all in
# optional: tells debian to apply any debianized patches (eg. preempt, ReiserFS, XFS, whatever)
# very important to do *before* config, or else you'll be configuring and building different things
export PATCH_THE_KERNEL=yes
make-kpkg --append-to-version "-me" -rev test.1 --initrd debian
# configure the kernel as you chose
cp
make oldconfig # or x/menuconfig
# build the kernel image
make-kpkg --append-to-version "-me" -rev test.1 --initrd kernel_image
# optional: build debianized modules (eg. nvidia, lirc, alsa)
make-kpkg --append-to-version "-me" -rev test.1 --initrd modules_image
# install the resulting
cd
dpkg -i *2.4.19-me*.deb
Explination of make-kpkg options:
--apend-to-version: optional, but a good idea. Makes the kernel version into 2.4.19-me and avoids any conflicts by installing to
-rev: needed for the debs. good as long as it has some number in it
--initrd: tell it to build the initial ram disk (/boot/initrd.img-2.4.19-me). Not sure if it's really needed, but all debian kernels have one so I figure might as well use it.
I'm aware that not all of the options are needed on all of the commands, but I figure for safty and consistency's sake, to just leave it as is.
Hope this helps someone.
Having a trojaned SSH build script was bad enough.
You *really* don't want a compromised kernel. Use the signatures.