[S.u.S.E. Linux] updating the kernel
What is the easiest way for me to update my 2.0.33 kernel to the 2.03.35 kernel? Also, where are some good sites that cover kernel updating (preferably dealing with suse)? -- Aaron Seelye <A HREF="http://revolution.3-cities.com/~roberto"><A HREF="http://revolution.3-cities.com/~roberto</A">http://revolution.3-cities.com/~roberto</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
What is the easiest way for me to update my 2.0.33 kernel to the 2.03.35 kernel? Also, where are some good sites that cover kernel updating (preferably dealing with suse)?
The easiest way to update the Kernel is to go to the following Website: <A HREF="http://www.linuxhq.com/kpatch20.html"><A HREF="http://www.linuxhq.com/kpatch20.html</A">http://www.linuxhq.com/kpatch20.html</A</A>> You will then see a link towards the patch upgrade to 2.0.35! So, download this patch, copy it to the /usr/src/ directory. This site also contains information on how to apply the patch as well. At this point in time, I am assuming that you have a current copy of your linux source code in /usr/src/linux/ Since you are dealing with SuSE, I believe that there may a symbolic link to /usr/src/linux-2.0.33.SuSE/. If so, type the following: rm linux (IF IT IS A SYMBOLIC LINK) cp -r /usr/src/linux-2.0.33.SuSE/ /usr/src/linux (this copies the SuSE linux source code to the expected directory. With the patch in the /usr/src directory, type the following command: gzip -cd patch-2.0.35.gz | patch -p0 This will update all the files, and proceed with the following commands in the /usr/src/linux/ directory: make mrproper (cleans up stale files) make menuconfig (menu system where you can specify which options you want the kernel to load) make dep -- these three commands are done after saving the new kernel. make clean make zImage Then the tricky part is knowing where to place the new Kernel Image. The new kernel image is located in the following directory: /usr/src/linux/arch/i386/boot/ with the filename: zImage If you are booting using loadin through WIN95 Boot Loader menu, copy the zImage file to the c:\loadlin\ directory. If you are using lilo, then copy it to the root directory (if using SuSE). Preferably, make a backup copy of the current kernel. In order to boot properly, regardless of which way you are booting, the file needs to be named: vmlinuz After this, hopefully your kernel is updated and everything should run smoothly If you are in need of anymore assistance, please let me know. Paul Brun --- Email: pbrun@geocities.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Which kernel will be in 5.3? - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Kernel 2.0.35 will be suppled with SuSE 5.3 according to their Website. Paul P.S. It is better practice have the entire source code in the /usr/src/linux directory instead of creating a symbolic link. It is easier to patch the kernel when all is in the real Linux directory. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Not even close Paul. You have obviously never untarred kernel sources before. All linux kernel sources untar to "linux", so if you untar that new 2.0.35 source you just downloaded and you have 2.0.34 in /usr/src/linux, well, now you have both in /usr/src/linux. Also, some people like to have multiple kernel sources on hand, in which case your advice is also impractical. A symlink to your active source directory is the best way to handle either situation, and your advice was just plain bad. Paul Brun wrote:
Kernel 2.0.35 will be suppled with SuSE 5.3 according to their Website. Paul
P.S. It is better practice have the entire source code in the /usr/src/linux directory instead of creating a symbolic link. It is easier to patch the kernel when all is in the real Linux directory.
-- ==================================================================== Michael Lankton <A HREF="http://tasteslikechicken.ml.org"><A HREF="http://tasteslikechicken.ml.org</A">http://tasteslikechicken.ml.org</A</A>> ==================================================================== - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
First of all, I have untarred many kernel sources, both at work and at home so your statement is incorrect to start with. Secondly, when I untarred my source files, I copy the current linux directly to let's say: "/usr/src/linux-2.0.34/ and then I just remove the current linux source by "rm -rf /usr/src/linux/". I copy the new kernel tar file into /usr/src and then I use the typical tar xvpzf ...... command to untar the new kernel and then I go into make menuconfig to configure my kernel. It works like a charm and from my knowledge the most popular distributor "Redhat" uses this method. Secondly, if you want multiple kernel's, then go to that kernel directory and make a new kernel through there. Keeping the default kernel source code in /usr/src/linux makes more sense. Hope this clarifies any misconceptions on your part. Paul --- Email: pbrun@geocities.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
At 09:00 AM 07/23/98 -0400, you wrote:
What is the easiest way for me to update my 2.0.33 kernel to the 2.03.35 kernel? Also, where are some good sites that cover kernel updating (preferably dealing with suse)?
The easiest way to update the Kernel is to go to the following Website:
<A HREF="http://www.linuxhq.com/kpatch20.html"><A HREF="http://www.linuxhq.com/kpatch20.html</A">http://www.linuxhq.com/kpatch20.html</A</A>>
You will then see a link towards the patch upgrade to 2.0.35! So, download this patch, copy it to the /usr/src/ directory. This site also contains information on how to apply the patch as well.
A while back, there was some discussion that the SuSE kernel RPM is already patched with additional stuff on top of the official kernel and that application of kernel update patch may not work. Is this not true any more? -- Arun Khan - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Don't take this as a lecture, but if you haven't compiled a kernel, you need to learn. Get the sources for 2.0.35 from your favorite kernel.org mirror, or off my news page if you have bzip2 installed, then mv it to /usr/src and follow these steps: 1. rm linux 2. tar -zxvf linux-2.0.35.tar.gz OR bunzip2 linux-2.0.35.tar.bz2 tar -xvf linux-2.0.35.tar 3. mv linux linux-2.0.35 4. ln -s linux-2.0.35 linux 5. cd linux-2.0.35 6. make mrproper 7. make config (or make menuconfig or make xconfig) 8. make dep 9. make clean 10. make zImage 11. make modules 12. make modules_install 13. cp arch/i386/boot/zImage /vmlinuz 14. /sbin/lilo 15. reboot bam! you've upgraded your kernel. It's not rocket science, and it's something you need to be comfortable doing. Hope this helps. Aaron Seelye wrote:
What is the easiest way for me to update my 2.0.33 kernel to the 2.03.35 kernel? Also, where are some good sites that cover kernel updating (preferably dealing with suse)?
-- ==================================================================== Michael Lankton <A HREF="http://tasteslikechicken.ml.org"><A HREF="http://tasteslikechicken.ml.org</A">http://tasteslikechicken.ml.org</A</A>> ==================================================================== - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Not to be contrary but a wanted to mention a few things. Firstly, if this is your first kernel build make CERTAIN you have a back up and setup lilo so you can use it to boot the old kernel should something go wrong. Do THIS before deleting your old sources and before installing the new image. I only mention this cause I think it's dangerous to be fooling around with kernel installations for the first time without taking precautions and no one mentioned backing up the old image before installing the new one. *OR* you could use make bzlilo instead of make zImage and this will copy the old kernel (and System.map) to vmlinuz.old, and you can set lilo up to give that as a lilo prompt option at boot time. If zImage does this as well, I apologize. I always use 'make bzlilo'. All Michael's instructions are right..but I think you should just use YaST to upgrade your kernel off SuSE's ftp site. ( You can do this right, they have an RPM for 2.0.35 up there, I believe. Also you asked for the EASIEST WAY and to me this *is* the easiest). I haven't been to the site in a while so if I'm mistaken here, please ignore. I thought someone said it was up there. And THEN after all this play with building a kernel once you already are out of the water. This will give you trial runs and put you in a position where you aren't prey to any mistakes should -heaven forbid- something go wrong. Note: you can make a disk to test the new kernel rather than installing it as well with the make bzdisk command. P.S. it's also a good idea to install the documentation so you have the HOW-TOs on board. There's a nice Kernel howto in there that can give you safe reference material in the future as most of all that's been said is right there in easy to grasp form. If all this sounds totally idiotic, just ignore me. I am prone to err. :-) Michael On Thu, 23 Jul 1998, Michael Lankton wrote:
Don't take this as a lecture, but if you haven't compiled a kernel, you need to learn. Get the sources for 2.0.35 from your favorite kernel.org mirror, or off my news page if you have bzip2 installed, then mv it to /usr/src and follow these steps: 1. rm linux 2. tar -zxvf linux-2.0.35.tar.gz OR bunzip2 linux-2.0.35.tar.bz2 tar -xvf linux-2.0.35.tar 3. mv linux linux-2.0.35 4. ln -s linux-2.0.35 linux 5. cd linux-2.0.35 6. make mrproper 7. make config (or make menuconfig or make xconfig) 8. make dep 9. make clean 10. make zImage 11. make modules 12. make modules_install 13. cp arch/i386/boot/zImage /vmlinuz 14. /sbin/lilo 15. reboot
bam! you've upgraded your kernel. It's not rocket science, and it's something you need to be comfortable doing. Hope this helps.
Aaron Seelye wrote:
What is the easiest way for me to update my 2.0.33 kernel to the 2.03.35 kernel? Also, where are some good sites that cover kernel updating (preferably dealing with suse)?
-- ==================================================================== Michael Lankton <A HREF="http://tasteslikechicken.ml.org"><A HREF="http://tasteslikechicken.ml.org</A">http://tasteslikechicken.ml.org</A</A>> ==================================================================== - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-M One is most dishonest towards one's God; he is not _permitted_ to sin. mail: mjohnson@pop3.aebc.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I mentioned in some other post that I thought that maybe SuSE had an rpm 2.0.35 kernel on their site. I believe I was wrong about this. I think the point I was trying to make was on the easiest way, EASY being the effective word here. Note, yast will let you remove and install different kernels ( example are the standard and development kernels that come with SuSE). This way is easier and faster than building a whole new kernel. I expect 2.0.35 will be in 5.3, yes? So to me the easiest way is through the SuSE administration tools, if one wanted to wait or was super nervous about kernel compilation. Sorry for my mistake. Been one of those days. Michael. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Just a thought, We need to put this type of information out on our local web site for reference to all. We don't need to duplicate the LDP but just a few of the more common things for all of us to have at hand. -ted Michael Lankton wrote:
Don't take this as a lecture, but if you haven't compiled a kernel, you need to learn. Get the sources for 2.0.35 from your favorite kernel.org mirror, or off my news page if you have bzip2 installed, then mv it to /usr/src and follow these steps: 1. rm linux
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Ted Maciag wrote:
Just a thought,
We need to put this type of information out on our local web site for reference to all. We don't need to duplicate the LDP but just a few of the more common things for all of us to have at hand.
I will be planning on creating a Website geared towards Linux with various a simplified section of HOWTO's, links, links to downloads, etc. It is not ready yet, but if you would like, here is the URL for this site: <A HREF="http://www.geocities.com/SiliconValley/Foothills/4495/"><A HREF="http://www.geocities.com/SiliconValley/Foothills/4495/</A">http://www.geocities.com/SiliconValley/Foothills/4495/</A</A>> Hope you link it! Paul Brun -- Email: pbrun@geocities.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Michael Lankton wrote:
Don't take this as a lecture, but if you haven't compiled a kernel, you need to learn. Get the sources for 2.0.35 from your favorite kernel.org mirror, or off my news page if you have bzip2 installed, then mv it to /usr/src and follow these steps:
compiling wasn't an issue, I just needed to know if I take the kernel source to /usr/src/ and point the sym link to the new kernel or not. if not, then what, but it sounds like that's all there is. -- Aaron Seelye <A HREF="http://revolution.3-cities.com/~roberto"><A HREF="http://revolution.3-cities.com/~roberto</A">http://revolution.3-cities.com/~roberto</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Thu, 23 Jul 1998, Aaron Seelye wrote:
Don't take this as a lecture, but if you haven't compiled a kernel, you need to learn. Get the sources for 2.0.35 from your favorite kernel.org mirror, or off my news page if you have bzip2 installed, then mv it to /usr/src and follow these steps:
compiling wasn't an issue, I just needed to know if I take the kernel source to /usr/src/ and point the sym link to the new kernel or not. if not, then what, but it sounds like that's all there is.
man, it would save bandwidth to be specific wouldn't it? Just kidding. -M One is most dishonest towards one's God; he is not _permitted_ to sin. mail: mjohnson@pop3.aebc.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Thu, 23 Jul 1998, Michael Lankton wrote:
/usr/src and follow these steps: 1. rm linux 2. tar -zxvf linux-2.0.35.tar.gz OR bunzip2 linux-2.0.35.tar.bz2 tar -xvf linux-2.0.35.tar 3. mv linux linux-2.0.35 4. ln -s linux-2.0.35 linux 5. cd linux-2.0.35 6. make mrproper 7. make config (or make menuconfig or make xconfig) 8. make dep 9. make clean 10. make zImage 11. make modules 12. make modules_install
Personally, I would be careful doing this next step. I would either do a 'make zlilo', which copies /vmlinuz to /vmlinuz.old and makes an additional entry in your /etc/lilo.conf file which gives you the option of booting the old kernel in case the new one doesn't work, or I would 'cp /vmlinuz /vmlinuz.old' and make the entry manually in /etc/lilo.conf. If you don't and the new kernel won't boot for some reason, you're screwed.
13. cp arch/i386/boot/zImage /vmlinuz > 14. /sbin/lilo 15. reboot
bam! you've upgraded your kernel. It's not rocket science, and it's something you need to be comfortable doing. Hope this helps.
-------------------------------------------- Brad Shelton bshelton@ole.net On Line Exchange <A HREF="http://ole.net"><A HREF="http://ole.net</A">http://ole.net</A</A>> Detroit News <A HREF="http://detnews.com"><A HREF="http://detnews.com</A">http://detnews.com</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Brad Shelton wrote:
Personally, I would be careful doing this next step. I would either do a 'make zlilo', which copies /vmlinuz to /vmlinuz.old and makes an additional entry in your /etc/lilo.conf file which gives you the option of booting the old kernel in case the new one doesn't work, or I would 'cp /vmlinuz /vmlinuz.old' and make the entry manually in /etc/lilo.conf. If you don't and the new kernel won't boot for some reason, you're screwed.
Brad has a point. I have a vfat partition "/dos" which I use to share files between linux and windows, and I always: "cp /vmlinuz /dos/vmlinuz", that way if there is a problem with the new kernel I can boot my old kernel with loadlin and bail myself out. You are UNLIKELY to ever have problems with a non-development kernel, but it's always wise to be cautious. -- ==================================================================== Michael Lankton <A HREF="http://tasteslikechicken.ml.org"><A HREF="http://tasteslikechicken.ml.org</A">http://tasteslikechicken.ml.org</A</A>> ==================================================================== - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Another answer is to keep a boot disk handy. YaST can make boot and rescue disks for you. Michael Lankton wrote:
Brad has a point. I have a vfat partition "/dos" which I use to share files between linux and windows, and I always: "cp /vmlinuz /dos/vmlinuz", that way if there is a problem with the new kernel I can boot my old kernel with loadlin and bail myself out. You are UNLIKELY to ever have problems with a non-development kernel, but it's always wise to be cautious. -- ==================================================================== Michael Lankton <A HREF="http://tasteslikechicken.ml.org"><A HREF="http://tasteslikechicken.ml.org</A">http://tasteslikechicken.ml.org</A</A>> ==================================================================== - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- ==================================================================== Michael Lankton <A HREF="http://tasteslikechicken.ml.org"><A HREF="http://tasteslikechicken.ml.org</A">http://tasteslikechicken.ml.org</A</A>> ==================================================================== - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Fri, 24 Jul 1998, Michael Lankton wrote:
Another answer is to keep a boot disk handy. YaST can make boot and rescue disks for you.
And you can always boot your already installed system using the installation boot disk ;-)
Michael Lankton
-o) Hubert /\\ _\_v - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hubert Mantel wrote:
Hi,
On Fri, 24 Jul 1998, Michael Lankton wrote:
Another answer is to keep a boot disk handy. YaST can make boot and rescue disks for you.
And you can always boot your already installed system using the installation boot disk ;-)
Michael Lankton
-o) Hubert /\\ _\_v
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Yup. Helped me out a few times when fsck said my filesystems were corrupted. :) Ken -- Ken Schuller Network Systems Specialist NovaNET Learning, Inc. <hint> Take out the spam foil to reply via e-mail. </hint> Incidentally, I speak for me. That's all. No one else. Linux- the best things in life are free! (Or at least GPL'ed...) - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
In looking at a list of permissions in a directory listing (ls -l) i've encountered c,s, and b in the first column for entries in the /dev directory. I understand that - means a file, l is a link and d is a directory, what do these other letters indicate? Also, if I try to copy one of these (with a "c" prefix) it does not copy. What's going on? gv. ____________________________________________________ | | | Gary Vinyard | | Department of Biology /314 | | University of Nevada | | Reno, Nevada 89557-0015 | | | | gvinyard@med.unr.edu | | <A HREF="http://www.brrc.unr.edu"><A HREF="http://www.brrc.unr.edu</A">http://www.brrc.unr.edu</A</A>> | |____________________________________________________| - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi Gary, On Tue, 28 Jul 1998, Gary L. Vinyard wrote:
In looking at a list of permissions in a directory listing (ls -l) i've encountered c,s, and b in the first column for entries in the /dev directory. I understand that - means a file, l is a link and d is a directory, what do these other letters indicate? Also, if I try to copy one of these (with a "c" prefix) it does not copy. What's going on?
IIRC, c stands for "character device", b for "block device" and s is a "socket" LenZ ------------------------------------------------------------------ Lenz Grimmer S.u.S.E. GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Gebhardtstrasse 2 <A HREF="http://www.suse.de"><A HREF="http://www.suse.de</A">http://www.suse.de</A</A>> 90762 Fuerth, Germany - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (11)
-
arunkhan＠xnet.com -
bshelton＠ole.net -
grimmer＠suse.de -
gvinyard＠med.unr.edu -
hekate＠intergate.bc.ca -
mantel＠suse.de -
pbrun＠geocities.com -
roberto＠cbvcp.com -
satan3＠home.com -
schullersite＠NOSPAMworldnet.att.net -
tsm＠wwnet.net