February 6th, 2004, 01:58 PM
Linux Kernel 2.6.2 is out
February 6th, 2004, 04:02 PM
Way ahead of you SDK, downloaded and compiled it yesterday . No problems so far, everything works perfectly.
February 6th, 2004, 05:09 PM
::Shudders when he realizes he hasn't updated Slackware yet:: Speaking of which...is there an auto-update program for Slack? One that looks for newer versions of existing packages/programs installed on the box? For SuSE, RH, and Fedora I know there is, but I haven't found any indication of whether or not there is one with Slack 9.1
February 6th, 2004, 05:34 PM
I use swaret (thanks the_JinX!) to keep my Slackware system up to date. Check it out at http://www.swaret.org/ .
February 9th, 2004, 10:35 AM
guyszz ...... recommend a good how-to on linux kernel installation....I'm using linux 2+ yrs never came across reinstalling the kernel......(new challenge)
February 9th, 2004, 10:55 AM
I have a realy short version of a kernel installation howto for you..
since the server is offline, here's the google cache version
Say you've got your linux system nice and running..
And all of a sudden you surf a site like this and you seen oh.no!!! A new linux kernel...
you download the thirty fourty odd megs.. and are stuck with a file..
the x's are version numbers and filetypes, wich I'll discuss in a while..
now what to do:
Move (or copy) the file to /usr/src
there unzip it.. two options.. linux-2.x.x.tar.bz2 or linux-2.x.x.tar.gz
if you have the bz2 edition and a fairly new linux distro..
type: tar xjvf linux-2.x.x.tar.bz2
else type: tar xcvf linux-2.x.x.tar.gz
now that the file is unpackt, you'll need to link it to the /usr/src/linux..
if there is a link present from a former kernel (the one you are running now) remove it..
now that does sound scary !!
now we'll link a new one.. (symbolic link)
ln -s linux-2.x.x linux
now we'll step into that new linux folder
we'd like to have the kernel more or less act the way the old (current) one did..
cp ../linux-2.x.x/.config .
note !! this time the .x.x points to the old one (propably 2.4.22 or something)
now we want the kernel to be able to do something with it..
this asks a couple of questions about the NEW features and automaticaly takes over the setting your old kernel had for the other things..
to check out the kernel configuration.
makes the new dependencies..
make modules modules_install install
this last line makes the modules, installs them and installs the kernel..
that is, if you are using lilo and have your /etc/lilo.conf configured the right way..
if you are using some other bootmanager, then make bzImage might be a better idea then make install
well that's all for this quick and dirty kernel update tutorial..
ASCII stupid question, get a stupid ANSI.
When in Russia, pet a PETSCII.
Get your ass over to SLAYRadio
the best station for C64 Remixes !
February 9th, 2004, 11:24 AM
Glad to see that slackware has a great following on antionline.com
Thanx jinx might have to give it a try now
February 9th, 2004, 11:51 AM
Actually it's changed with the 2.6.x kernels. cgkanchi I believe referenced this article in another kernel thread. There are some items you need to ensure you can in fact compile.
Basically the steps are:
1. Download the source
2. Unzip it in the /usr/src directory
3. Optional Step: Remove the previous softlink (rm -f linux) and add a new softlink (ln -s linux-2.6.x linux)
4. Certainly you could use make oldconfig but given the changes I'd almost say not to. Use make xconfig or make menuconfig according to your current screen options for the root user
5. Pick what you need and remove what you don't
6. (here's the change): make bzImage && make modules && make modules_install. Make dep is deprecated. And they've turned it into a "silent mode" so to speak. You don't see screens upon screens of compiler info plus it's quicker (IMHO).
7. rm /boot/System.map : remove the existing System.map
8. mv arch/i386/boot/bzImage /boot/bzImage-2.6.2 : move the new kernel over. You may find it a bit larger than previous kernels.
9. mv System.map /boot/System.map-2.6.2 : move the system map over. Don't forget the soft link ln -s System.map-2.6.2 System.map
10. Alter lilo or grub accordingly. I use lilo so I put a line in the lilo.conf (see below) and re-ran lilo command. Don't remove references to the existing kernel. It helps as a backup.
11. Reboot. If it doesn't work reboot back to the old kernel. Go back to step 4 and start again. If you've created one kernel build and it didn't work, you don't have to use make oldconfig. You can go straight to make menuconfig or make xconfig. This will have the settings you last used.
February 9th, 2004, 01:22 PM
February 10th, 2004, 09:46 PM