Re: Making kernel using make install
At 12:08 AM 1/19/97 +0100, Thomas Baetzler wrote: Victor Torrico wrote: When making a kernel 2.0.27 I do the following: [clumsy procedure deleted] Actually, on Debian it´s so much nicer to install the kernel-package package. Then you cd to the linux source, make mrproper and make config just once, and then you can always rebuild your kernel by running make-kpkg binary. This´ll give you a new kernel package that contains all you need. dpkg --install it, and so even your Debian system knows which kernel you´re using. ### Okay, I did this and waited a little over an hour for it to get all through and am ready for the dpkg --install part, but I don't have a package called kernel-package.anything anymore, so what package am I installing Regards, Kendrick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Modules (was Re: Making kernel using make install)
On Fri, 17 Jan 1997, David Wright wrote: Am I right in thinking that a module is a module is a module? In other words, is the sound.o module always the same even though different base addresses/IRQs etc. were configured? Nope. Each time you compile it, differences do occur. You can USE some modules between different kernel versions/compiles, but sometimes you cant. Functionality though, is the same. Symbols usually don't get matched up properly, causing it not to work. -- Daniel Stringfield mailto:[EMAIL PROTECTED] http://users.southeast.net/~servo Send email for more information on the Jacksonville Linux Users Group! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Making kernel using make install
kooij == J P D Kooij [EMAIL PROTECTED] writes: kooij Regarding compiling and installing new kernels, kooij I would like to know more about details of installing new kooij (and older) kernels and have an overview of the process as kooij well. IMHO this is something that is not quite exhausively kooij covered in the documentation. The definitive manual for configuring and installing a new kernel is /usr/src/linux/README. By following the directions contained here, and reading the help entries for the individual configurable items when running 'make config', you can make any kind of kernel you want. What more can you ask for? If you want to hack the kernel, see the Kernel Hacker's Guide, by Michael K. Johnson, at the following URL: http://www.redhat.com:8080/HyperNews/get/khg.html kooij But when compiling kernels is kooij addressed, they only tell you to do make this, make kooij that. There's hardly any documentation of what the makefile kooij does, is supposed to do and can do for you. kooij Of course, there's the kernel-HOWTO and it is very good kooij where it makes configuring a new kernel very easy, explains kooij a lot about what the kernel does, how it handles devices, kooij what modules are, where to get the source, how to patch it, kooij etc.. But when it comes down to the final part: installing kooij the kernel, there's not much more than a reference to the kooij lilo manual. I would really like to see some additions made kooij about how the kernel is (or kernels are) embedded in the kooij filesystem. kooij IMHO installkernel(8) and mkboot(8) and are not good enough kooij as the only reference to the install option of the kernel kooij make. The process of installing a new kernal is much to kooij fundamental to linux to be documented only in the huge lilo kooij documentation or the kernel hacking guide. Mere complaining about lack of documentation is not going help anybody, least of all you. If you want something to be improved, ask yourself: how can I help improve this? Remember, nobody's getting paid for the work they do here. -- Nathan L. Cutler Linux Enthusiast http://www.cise.ufl.edu/~nlc -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Making kernel using make install
Victor Torrico wrote: When making a kernel 2.0.27 I do the following: [clumsy procedure deleted] Actually, on Debian it´s so much nicer to install the kernel-package package. Then you cd to the linux source, make mrproper and make config just once, and then you can always rebuild your kernel by running make-kpkg binary. This´ll give you a new kernel package that contains all you need. dpkg --install it, and so even your Debian system knows which kernel you´re using. By the way, if you´ve been looking at the docs, ever tried make menuconfig or make xconfig? Those make it much easier to configure your custom kernel - no more mistyping! The make install is not documented in the /usr/src/linux directory as far as I know but when it is used it seems to put everything from the new kernel where it belongs properly in the /boot directory and lets you update lilo as well. I just tried doing this for the hell of it and it seems to work very well. Is this a new feature? What exactly does make install do? Read the fine Makefile :-) As far as I´ve been able to follow it, it uses a user-supplied script to install the kernel. Guess what, it´s part of the Debian distribution. Still, kernel-package is the way to go. Ciao, -- Thomas Baetzler, [EMAIL PROTECTED], [EMAIL PROTECTED] A HREF=http://home.pages.de/~thb/;thb's Homepage/A -- This message was delayed because the list mail delivery agent was down.
Re: Making kernel using make install
Pete Templin wrote: Ah-hah! Finally, what seems to be a simple sequence of commands for building a new kernel. But what must I do to ensure that my old kernel will continue to work (with its modules), especially if lilo wants to complain that the new kernel is too large? I assume that certain files and directories ought to be backed up or renamed or something, but some pointers to safe kernel testing would be very helpful! If you have problems with Lilo and large Kernels, you can always use make bzlilo instead of make zlilo. By default, the kernel installation will move your old kernel and System.map to *.old. All you need to do to be able to boot into the previous kernel would be to add a boot entry in /etc/lilo.conf. Or you could just cp your stable kernel and the accompanying map to *.stable, and then add an entry for that. Ciao, -- Thomas Baetzler, [EMAIL PROTECTED], [EMAIL PROTECTED] A HREF=http://home.pages.de/~thb/;thb's Homepage/A -- This message was delayed because the list mail delivery agent was down.
Making kernel using make install
When making a kernel 2.0.27 I do the following: make mrproper make config make dep make clean make zImage make modules make modules_install make install The make install is not documented in the /usr/src/linux directory as far as I know but when it is used it seems to put everything from the new kernel where it belongs properly in the /boot directory and lets you update lilo as well. I just tried doing this for the hell of it and it seems to work very well. Is this a new feature? Is it OK to do this or are there possible problems? What exactly does make install do? Victor Torrico -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Making kernel using make install
On Fri, 17 Jan 1997, Victor Torrico wrote: When making a kernel 2.0.27 I do the following: make mrproper make config make dep make clean make zImage make modules make modules_install make install The make install is not documented in the /usr/src/linux directory as far as I know but when it is used it seems to put everything from the new kernel where it belongs properly in the /boot directory and lets you update lilo as well. I just tried doing this for the hell of it and it seems to work very well. Ah-hah! Finally, what seems to be a simple sequence of commands for building a new kernel. But what must I do to ensure that my old kernel will continue to work (with its modules), especially if lilo wants to complain that the new kernel is too large? I assume that certain files and directories ought to be backed up or renamed or something, but some pointers to safe kernel testing would be very helpful! --Pete ___ Peter J. Templin, Jr. Client Services Analyst Computer Communication Services tel: (717) 524-1590 Bucknell University [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Making kernel using make install
Victor Torrico [EMAIL PROTECTED] writes: What exactly does make install do? See installkernel(8) and mkboot(8). Guy -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Making kernel using make install
On Fri, 17 Jan 1997, Pete Templin wrote: Hi there, Ah-hah! Finally, what seems to be a simple sequence of commands for building a new kernel. But what must I do to ensure that my old kernel will continue to work (with its modules), especially if lilo wants to complain that the new kernel is too large? I assume that certain files and directories ought to be backed up or renamed or something, but some pointers to safe kernel testing would be very helpful! Every kernel release gets its own direcory in /etc/modules/ So no need to backup the modules. The new directory gets created with make modules_install Yours, -- martin +++ the KDE project mailing lists +++ kde-announce (Announcements)kde (general discussion) kde-devel (Development issues) kde-look (look and feel issues) To subscribe (unsubscribe), send mail to [EMAIL PROTECTED] with empty subject line and subscribe (unsubscribe) [your-email-address] in the message body -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Making kernel using make install
Regarding compiling and installing new kernels, On 17 Jan 1997, Guy Maor wrote: Victor Torrico [EMAIL PROTECTED] writes: What exactly does make install do? See installkernel(8) and mkboot(8). Hey, this is not a very elaborate answer. I would like to know more about details of installing new (and older) kernels and have an overview of the process as well. IMHO this is something that is not quite exhausively covered in the documentation. And yes, I did read the lot in the source tree, which is great literature when your kernel won't boot because your XYZ scsi-tape won't bargain with the interface on your DEF souncard because it has the kind of obsolete 456PQ123 chip, so you'll have to hack the source a bit. I also read Running Linux and Raven and I think they're great for everyone who wants to get an overview of linux, especially newbies. But when compiling kernels is addressed, they only tell you to do make this, make that. There's hardly any documentation of what the makefile does, is supposed to do and can do for you. Of course, there's the kernel-HOWTO and it is very good where it makes configuring a new kernel very easy, explains a lot about what the kernel does, how it handles devices, what modules are, where to get the source, how to patch it, etc.. But when it comes down to the final part: installing the kernel, there's not much more than a reference to the lilo manual. I would really like to see some additions made about how the kernel is (or kernels are) embedded in the filesystem. IMHO installkernel(8) and mkboot(8) and are not good enough as the only reference to the install option of the kernel make. The process of installing a new kernal is much to fundamental to linux to be documented only in the huge lilo documentation or the kernel hacking guide. Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Modules (was Re: Making kernel using make install)
On Fri, 17 Jan 1997, Martin Konold wrote: Every kernel release gets its own direcory in /etc/modules/ So no need to backup the modules. The new directory gets created with make modules_install Am I right in thinking that a module is a module is a module? In other words, is the sound.o module always the same even though different base addresses/IRQs etc. were configured? David. -- David Wright, Open University, Earth Science Department, Milton Keynes MK7 6AA U.K. email: [EMAIL PROTECTED] tel: +44 1908 653 739 fax: +44 1908 655 151 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Making kernel using make install
On Fri, 17 Jan 1997, Victor Torrico wrote: When making a kernel 2.0.27 I do the following: make mrproper make config make dep make clean make zImage make modules make modules_install make install The make install is not documented in the /usr/src/linux directory as far as I know but when it is used it seems to put everything from the new kernel where it belongs properly in the /boot directory and lets you update lilo as well. I just tried doing this for the hell of it and it seems to work very well. Ah-hah! Finally, what seems to be a simple sequence of commands for building a new kernel. But what must I do to ensure that my old kernel will continue to work (with its modules), especially if lilo wants to complain that the new kernel is too large? I assume that certain files and directories ought to be backed up or renamed or something, but some pointers to safe kernel testing would be very helpful! What I do when I want to upgrade my kernel (which I will be doing later today... 2.0.28 is out) is something like this (assuming that linux-2.0.28.tar.gz is already in /var/tmp, but it could be anywhere, really): tar xzvf linux-2.0.28.tar.gz cd linux cp /usr/src/linux/.config . make-kpkg -revision custom.1.0 kernel_image kernel_source cd .. # rm -rf linux linux-2.0.28.tar.gz dpkg --install kernel-image-2.0.28_custom.1.0_i386.deb dpkg --install kernel-source-2.0.28_custom.1.0_i386.deb dpkg --remove kernel-source-2.0.27_custom.1.0_i386.deb dpkg --remove kernel-image-2.0.26_custom.1.0_i386.deb and that's it. My /etc/lilo.conf has entries for /vmlinux and /vmlinux.old, which are symbolic links that the post-install script for the kernel-image package maintain properly (and reruns lilo as well). I keep one set of installed kernel sources and two installed kernel images. All you need for this is to install the kernel-package package, and it should work. Read the docs in /usr/doc/kernel-package for more information. --Pete ___ Peter J. Templin, Jr. Client Services Analyst Computer Communication Services tel: (717) 524-1590 Bucknell University [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] -- Buddha Buck [EMAIL PROTECTED] Just as the strength of the Internet is chaos, so the strength of our liberty depends upon the chaos and cacaphony of the unfettered speech the First Amendment protects. -- A.L.A. v. U.S. Dept. of Justice -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
