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?
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?
Friends don't let friends use multiple inheritance.
http://atlantis1.prolixium.com/~prox/proserv/linux /kernel/v2.4/linux-2.4.19.tar.gz. it's 100mbit. so give kernel.org a break...
.... /boot/newkern
apt-get kernel-source-2.4.19
unbzip2, untar etc...
make menuconfig
make dep clean bzImage modules modules install
cp arch/i386/boot/bzImage
lilo
lilo -q
I've only had it fail on one machine, and it had a crappy mobo.
Looking for Book Reviews? Check out Literary Escapism.
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."
Insert standard Darn-And-I-Just-Finished-Downloading-The-Last-One- Yesterday wisecrack...
Hey Taco! Looks like you're using the "infinite monkeys and typewriters" scheme to generate Ask Slashdots again...
Actually:
/usr/src/kernel-source-2.4.19.tar.bz2 ../kernel*2.4.19*.deb
:)
apt-get install kernel-soruce-2.4.19
tar xvjf
cd kernel-source-2.4.19
make menuconfig
make-kpkg --rootcmd=fakeroot buildpackage
sudo dpkg -i
Easy
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...
Wrong bug. It compiled, but folks need to do a "make dep" after an "make oldconfig"
--
# Canmephians for a better Linux Kernel
$Stalag99{"URL"}="http://stalag99.net";
gentoo-sources-2.4.19-r7 is based on a kernel prepatch, not the kernel that was released today.
However, an updated vanilla-sources ebuild has been in the Gentoo CVS repository for 25 minutes and should make it to the mirrors shortly, if it hasn't already. Then, you can grab the new source tree by typing "emerge vanilla-sources"; or, if you're already using it, emerge -u will fetch the new copy.
I can't get 2.4 stable with my pure scsi system (hdd, cdrom, etc). Using a 2940U2W. It bombs when installing Drake 8.2. Slackware 8.1 will go on (with segfaults in the package install) but you can't compile a thing with it.
Care to give details? Do you have a console log by chance? I'm slowly taking on maintenance of this driver, so please feel free to contact me with these kinds of problems. My email is available from my URL.
Cat, the other, tastier white meat.
(02/07/17 1.642)
...
[PATCH] PATCH: personality clashes
If only they were all that easy to fix
If you are at a University, use a mirror located at another University. Chances are the traffic will travel over Internet2 at ridiculous speeds, and not strain your University's (usually) clogged commodity Internet link.
I got 1.42Mbytes/sec from U of Wisconsin to FIU, myself.
No, you've gotta wait until 2.4.19's been tested for a few years.
Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
(02/07/30 1.659)
:)
PATCH More -ac merge
Sweet, now my system will scream "FIRST BOOT!!!!" at me when I turn it on.
Everything will be taken away from you.
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.
Of those 10 points, point 10 is the only significant "Question Every Business Should Ask About the GNU General Public License (GPL)".
10. Do you have any existing obligations that might preclude your use of GPL software?
The answer is NO, there is nothing precluding anybody from using GPL software once they have access to it. The deceptive answer immediatele switches the bait to the use of "GPL code", which implys a significantly different animal. In any case, there is nothing stopping you from using the code however you se fit. The only restriction involved is in who you give the GPL code/software to, and how you go about it. Not "Every Business" is in the business of distributing computer code.
Every other Question is irrelevant with the context in which this treatise was presented.
Oh, and I didn't notice any variant of the word "terror" in this thread.
What do you expect?
/.
Slashdot isn't about Windows. If Slashdot was a Windows-centric (not UNIX centric) site, it would be \. and not
Oolite: Elite-like game. For Mac, Linux and Windows
No Linux kernel branch currently contains fixes for the issue you noted. Folks from SuSE, AMD, and Nvidia are working toward a solution that will, as another post mentioned, require major restructuring of how memory is mapped (not to mention the issue of cacheline flushes, etc.). I think you have a better chance of seeing a workaround in 2.5. (I doubt the "mem=nopentium" append fixes it, perhaps lessens the chance of an erroneous state in the cacheline. Search lkml archives for details.)
And then later...
Wow! Excellent example of misunderstanding the GPL! There are *NO RESTRICTIONS* on the use of GPL'd code. Don't believe me? Check the GPL:
What this means is that the *only* thing the GPL applies to is redistribution of code. If you simply use the code, you're free to do with it whatever you want (except redistribute it). So I'd recommend that you take your own advice and read the GPL before you start spouting off about what it's implications are.
Key to financial independence: Spend less than you earn. Save and invest the difference. Do it for a long time.
the reason is:
AMD + Nvidia = crash
unless you pass mem=nopentium to the kernel. and I couldn't figure out how to pass mem=nopentium with GRUB.
GRUB is _SO_ stupid it refuses to run if the parameter after an '=' sign is anything but a number.
What ? Me, worry ?