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...
ncftp ftp.us.kernel.org ... .config ../kernel-image-2.4.19_home.1_i386.deb ../alsa-modules-2.4.18_0.9+0beta12+3+p0+home1_i386 .deb
tar -xvzf linux-2.4.19.tar.gz
cd linux
cp ~/kernel/configs/2.4.18
make oldconfig
su
make-kpkg --revision home.1 kernel_image
make-kpkg modules_image # for alsa, nvidia-glx, plex86
dpkg -i
dpkg -i
etc.
Thanks for the good work, Manoj!
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?
Ok, I'll bite.
;0)
I didn't actually manage to get through the whole thing (about the first ten points), but basically they all seemed to deal with how the GPL could infect your software and impose certain responsibilities on you. Of course almost all of these points only affect you only if you actually develop your own inhouse programs. Horror of horrors, you can't "borrow" the code and do with it whatever you want ala BSD. I'd like to know how many companies use Windows source in their programs
Basically, this just creates FUD in the minds of business execs who don't understand software licenses to begin with. Most just pay for the software and use it as is. Very few would even think to ask if they could modify the program themselves! So this whole thing can be safely ignored by them (well, when they pirate the software by using it on home computers they'd have to remember not to copy the source, otherwise they're not breaking any laws!)
So unless we actually modify the software we run to begin with (and I assume since this is an MS doc, they're trying to get you to use MS products), how would using a GPL program be any different for the majority of users? For the minority who still write their own stuff, they should darn well be familiar with software licenses already!
Blessed are the young, for they shall inherit the national debt. --Herbert Hoover
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...
Let me know when you understand SARCASM tags...
--
# Canmephians for a better Linux Kernel
$Stalag99{"URL"}="http://stalag99.net";
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
Gentoo has been calling their kernels "2.4.19-rX" since 2.4.19-pre1 came out. Its meaningless. Other distributions have also been tracking the 2.4.19 preleases, but they have kept the version number at 2.4.18. If you download that gentoo source you'll notice it actually notice that it starts with a 2.4.18 tarball and then applies a huge patch.
"(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
(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?" `":" #");}
It may be a bore but here are some things to check:
- termination - using proper terminators for LVD? for SE? Both ends of bus terminated? only ends of
the bus terminated?
- cables - quality cables of proper impedance? correct cables for LVD, for SE?
- general - are you mixing LVD and SE? is bus length too long? all jumpers settings configured correctly on
all devices on SCSI bus? bus speed set too fast for length?
- connectors - properly and tightly seated? oxidized connectors? remove and re-seat them a couple
times to break oxidation.
- term power - are you sure that your bus is getting termination power? Check term power voltage
at each end of the bus? are term power fuses blown on controller or external devices (yes, it happens )?
You may be in denial. But it is not the kernel that is broken. Somewhere there is a fault in your SCSI hardware configuration. I tell this to you as a grizzled SCSI veteran. I've blamed software and various kernels and *always* in the end it turned out to be a problem with *my* configuration. There are a whole lot of variables. It sometimes takes a little more effort to run SCSI. . But IDE is not without its own set of problems either.Use your best debugging skills. You can do it!
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.
Because you must, must, must have the latest version? Bah.
Anyways - you might be able to get around that problem by not enabling versioning information on all modules - I've resolved a fair share of "unresolved symbols" problems by doing so in the past, most recently with my webcam.
We who were living are now dying
With a little patience
One thing I really with kernel releases had was a way to rsync/cvs/bk whatever to the release kernel. That way only the files that have been changed get sent. kernel.org's rsync is setup to let you mirror the site, but not the individual kernel. I'm thinking of the kind of access provided to the kernel sources on the penguinppc.org project. That way, I can start with any bastardized kernel source and arrive at a pristine new source dir without using up the bandwith to download the whole thing. Heck, I can even exclude the architectures I'm not using, saving even more bandwidth.
Anyone know if/where to get this kind of access to the kernels?
I am, and always will be, an idiot. Karma: Coma (mostly effected by
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.
"Meanwhile, SP3 for Windows 2000 [microsoft.com] is released, implementing the new "Set Program Access and Defaults" feature. Unsurprisingly, Slashdot is silent."
/.'ers like, I still get treated like a moron for preferring Windows 2000 over Linux. Never mind that it is reliable, gets the job done, plus I can play all my favorite games as well. No no no, you see MS is evil and doesn't do anything right.
/. blasting MS when they do something wrong, but I do wish they'd pay attention to the brighter news from MS's camp. If the Linux community acts like it's solely out for blood when dealing with MS, nobody'll take their comments seriously despite being the most informed about them. "Oh, it's those stupid Slashdotters again. What are they blithering about?"
I'm not surprised. Slashdot seems blissfully unaware that not everybody can switch to Linux. I'm a 3D artist. I use Lightwave, Photoshop, and After Effects extensively. Despite the fact that Lightwave is responsible for a fair number of pixels on Star Trek, Babylon 5, and a whole slew of other shows that
I mentioned wanting to use VNC like a KVM the other day and somebody responded with "I do stuff like that all the time. It's called the X Windowing System. Oh, you're probably running MS Windoze, never mind.". Yeah, Linux'd really solve that problem there. Too bad my rendering times would suddenly become infinity.
While I'm busy doing my job with Windows, Slashdot is posting minor updates to the Linux kernel. I think it's silly.
I'm sure I'll get modded down for this post, but it felt good to let it out. I don't mind
While I'm busy doing my job with Windows, Slashdot is posting minor updates to the Linux kernel. I think it's silly.
You don't have to read about Linux if you don't want to you know. There are a lot of Linux fans here who love to hear about new kernel releases and talk about it. This is slashdot. This site wasn't meant to cater to Windows fans. That's just how it is. If you want to read about Windows updates, you're looking in the wrong place.
"Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
But it has some serious personality problems. Luckily, I'm not the only one who noticed:
(02/07/17 1.642)
[PATCH] PATCH: personality clashes
---
"The chances of a demonic possession spreading are remote -- relax."
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
If you've got a current linux source dir, either it's called linux, or linux is a symlink to it. Thus the new tar blows away the old one.
Infuriate left and right
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.)
There is absolutely no reason for anyone to subject themselves to LILO any more
Unless, of course, you want to support an evil corporation that goes by the name of The Walt Disney Company.
The Truth About Lilo & Stitch
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.
That is, unless something else <cough>Windows Update</cough> eats your dual-boot machine's master boot record.
Will I retire or break 10K?
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.
Certainly not. A driver's response to broken hardware should never be to segfault. Sounds like both the configuration and the driver need work. Sounds also like this person is a good one to speak to regarding testing which improves the driver.
Cheers,
Ian
I noticed a huge number of apple stories hitting the front page a few weeks ago. /. central
Somthing's going on at
thank God the internet isn't a human right.
the kernel change log on fresh meat is always nice and tidy.
but you have to go through gatch rc and pre version to get a full picture.
e.g. 2.4.19-pre9 change log is....
This release should be the last pre-patch before 2.4.19. It contains USB, emu10k1, and i2o fixes, a devfs fix, several gcc 3.1 compilation error fixes, support for I845G, USB Casio EM500, and Tieman Voyager USB Braille display drivers, and several documentation updates.
thank God the internet isn't a human right.
You are correct, Maya is on Linux. Lightwave will be able to render on Linux, but you still need Win/Mac in order to create animation on it.
The problem with Maya is that the renderer is quite inferior to Lightwave's. You'd haveta get Renderman. That puppy's expensive. $5,000 last I checked.
...in its own subdirectory!
./linux directly after unpacking. Perhaps the most user-friendly change in the kernel in a long time.
;-)===)
I was geting tired of renaming
I already like it!
Most ACs are not even worth the keystrokes to insult them. Be generically insulted and ignored otherwise.
incidentally, seeing how I am privileged enough to be able to pay for all the bandwith I want, I'll download precisely what I please. (in this case it will be whatever emerge gets, but nonetheless)
sic transit gloria mundi
Doesn't it strike you as... crappy... that with a piece of software that is getting so much financial support, and tons of programmers working on it, that this happens at all?
I've used Linux and FreeBSD for some time. With Linux, I've never been able to compile a kernel where all the modules worked. With FreeBSD, I've never had a kernel where even a single kernel module didn't work. Just pointing out a fact.
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
I shouldn't have to switch to OSX just to get a little respect. Especially true when I'm actually doing cool stuff with my computer as opposed to trying to make it play catch-up with Windows.
This will modify the atime, lose file attributes, ignore ACLs, etc. It will provide an archive, not a backup.
Unmounting the drive and doing a dd is fine. assuming that the hardware I'm backing up stays permanently available, which it will not. Restoring via dd onto non-identical hardware is hit or miss at best.
I can understand the "if possible" clause.
Mirros sometimes don't have the file.
Muchas Gracias, Señor Edward Snowden !
I know that 2.4.19 took more than 5 months to complete.
I also know that Marcelo intended 2.4.19 to be a fix-bug-only release.
So, exactly how many changes are there, as compared to 2.4.18 ?
Muchas Gracias, Señor Edward Snowden !
the full 23MB of it.
At 56kb...
And I need improved wireless support in 2.4.19.
My ISP will be very pleased.
IANAL but write like a drunk one.
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 ?
Imagine!! "Backslashdot"
Don't quote me on this.
" So if your gonna come preaching to a predominately anti-microsoft crowd about how you deserve so much respect for sucking Bill Gates dick well fine, it's a free country, Micro- fuckhead!"
Those are strong words from somebody who admitted they can't do something as simple as install Windows. Heh. What a tard.
Sorry bud, you can't attribute your incompetance to Microsoft. You certainly can't troll me with it.