SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
where did you get this kernel ?
I never ever I mean NEVER EVER !! up grade my kernel with out configuring it EVER .
you just don't do that
unless
you want something broken on your system
Wed Sep 22 03:03:58 UTC 2010
a/kernel-firmware-2.6.33.4-noarch-2.txz: Rebuilt.
a/kernel-generic-2.6.33.4-x86_64-2.txz: Rebuilt.
This kernel has been patched to fix security problems on x86_64:
64-bit Compatibility Mode Stack Pointer Underflow (CVE-2010-3081).
IA32 System Call Entry Point Vulnerability (CVE-2010-3301).
These vulnerabilities allow local users to gain root privileges.
For more information, see: http://cve.mitre.org/cgi-bin/cvename...=CVE-2010-3081 http://cve.mitre.org/cgi-bin/cvename...=CVE-2010-3301
(* Security fix *)
a/kernel-huge-2.6.33.4-x86_64-2.txz: Rebuilt.
Patched for CVE-2010-3081 and CVE-2010-3301.
(* Security fix *)
a/kernel-modules-2.6.33.4-x86_64-2.txz: Rebuilt.
d/kernel-headers-2.6.33.4-x86-2.txz: Rebuilt.
k/kernel-source-2.6.33.4-noarch-2.txz: Rebuilt.
Patched for CVE-2010-3081 and CVE-2010-3301.
(* Security fix *)
kernels/*: Rebuilt.
Patched for CVE-2010-3081 and CVE-2010-3301.
(* Security fix *)
usb-and-pxe-installers/usbboot.img: Rebuilt.
Patched for CVE-2010-3081 and CVE-2010-3301.
(* Security fix *)
I'll be interested in finding out if others have the same problems (of if I do once I get around to installing the patched kernels). This should be a drop-in fix, even for multi-lib systems, right?
One needs to rerun LILO after upgrading to the patched kernel, but I don't think it's necessary to recreate the initrd (although that might be a good idea anyway).
Problems with audio and video, I think, point to module problems. But perhaps I'm off-base.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Quote:
Originally Posted by Lufbery
...Problems with audio and video, I think, point to module problems. But perhaps I'm off-base.
I think you are correct. However, I've re-installed the previous packages and the "problems" have gone away.
I'll wait awhile before trying the new packages again.
One needs to rerun LILO after upgrading to the patched kernel, but I don't think it's necessary to recreate the initrd (although that might be a good idea anyway).
If you are loading modules in your initrd, you should. I don't know why you would think otherwise.
I just updated with slackpkg HDA Intel sound drivers still work, couldn't remember modules to load in mkinitrd so took a gamble on old initrd.gz and it worked.
I just updated with slackpkg HDA Intel sound drivers still work, couldn't remember modules to load in mkinitrd so took a gamble on old initrd.gz and it worked.
You should rebuild your initrd.gz to include the rebuilt kernel modules.
It is easy.
1. cd /boot
2. /usr/share/mkinitrd/mkinitrd_command_generator.sh (this is Alien_Bob's very useful tool)
3. Copy the output from the above into the command line and run it.
4. Rerun lilo.
Is a initrd rebuild really necessary? The modules will still be the same. It's the same kernel version after all, and the patches don't look like they impact any modules to me. Obviously, it's safest to rebuild just to be on the safe side, but in this case I'm not convinced it's necessary.
Last edited by GazL; 09-23-2010 at 03:45 AM.
Reason: typo
Is a initrd rebuild really necessary? The modules will still be the same. It's the same kernel version after all, and the patches don't look like they impact any modules to me.
I agree. I'm no expert, but I didn't rebuild the initrd, and everything is working. I booted into the huge kernel, ran mkinitrd_command_generator.sh, and it was exactly the same as with the pre-update kernel. So nothing's changed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.