Trouble with Debian kernel build
I am trying to build a kernel the Debian way and am stuck. According to the FAQ, the first thing a need to do (from memory) is: make-kpkg --install kernel-package_2.0.36_all.deb However, there is no kernel-package_2.0.36.deb package. I am in the /usr/src directory, and there are files here called, (again, from memory) kernel_headers.2.0.36.tar.gz and kernel_sources.2.0.36.tar.gz . I have the following packages installed: kernel_headers.2.0.36-3, kernel_source.2.0.36-3, kernel-package. So what gives? Do I have to untar/zip the files? Why didn't the installation do this? I'm afraid to do anything to screw-up the kernel packages, and I have never built a kernel under Debian. Thanks, Bryan
RE: Trouble with Debian kernel build
On 17-May-99 Bryan Scaringe wrote: I am trying to build a kernel the Debian way and am stuck. According to the FAQ, the first thing a need to do (from memory) is: make-kpkg --install kernel-package_2.0.36_all.deb I am going back to the old way of doing it because I am still uncertain if I have done it correctly. Read the stuff in /usr/doc/kernel-package -- Andrew
RE: Trouble with Debian kernel build
On 17-May-99 George Bonser wrote: On Mon, 17 May 1999, Pollywog wrote: On 17-May-99 Bryan Scaringe wrote: I am trying to build a kernel the Debian way and am stuck. According to the FAQ, the first thing a need to do (from memory) is: make-kpkg --install kernel-package_2.0.36_all.deb I am going back to the old way of doing it because I am still uncertain if I have done it correctly. Read the stuff in /usr/doc/kernel-package The way I do it is: 1. make menuconfig 2. make-kpkg --bzimage --revision L1 kernel-image (the revision is L for Local and then whatever number I want) If simply upgrading from an older kernel and you want to use your old config file, make oldconfig instead of make menuconfig usually works. Once it is done, you will have a kernel .deb package in the parent directory of your kernel tree. I just install it with dpkg -i I followed the instructions in /usr/doc/kernel-package but I had doubtts about whether I had put the kernel source in the correct place, mostly because of the errors about modules, which I kept seeing in my logs. I did it the old way today, and if I don't see the same errors, I probably did something wrong *after* installing the kernel image debs. -- Andrew
Re: Trouble with Debian kernel build
On Sun, May 16, 1999 at 10:55:31PM -0400, Bryan Scaringe wrote: I am trying to build a kernel the Debian way and am stuck. According to the FAQ, the first thing a need to do (from memory) is: make-kpkg --install kernel-package_2.0.36_all.deb However, there is no kernel-package_2.0.36.deb package. I am in the /usr/src directory, and there are files here called, (again, from memory) kernel_headers.2.0.36.tar.gz and kernel_sources.2.0.36.tar.gz . I have the following packages installed: kernel_headers.2.0.36-3, kernel_source.2.0.36-3, kernel-package. You should read /usr/doc/kernel-package/README.gz before proceeding. Short version of what it says: Untar/unzip the kernel source, run 'make menuconfig' (or make config or make xconfig), then run 'make-kpkg clean' and 'make-kpkg --revision=custom.1.0 kernel_image'. This will compile the source and create a debian kernel-image package which you can then install. So what gives? Do I have to untar/zip the files? Why didn't the installation do this? I'm afraid to do anything to screw-up the kernel packages, and I have never built a kernel under Debian. Hmmm, I thought that the installation did that, but I haven't an installed kernel-source package to check. If you have kernel-source, you don't need the kernel-headers (with hamm you did). Bob -- Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
Re: Trouble with Debian kernel build
On 17-May-99 Bob Nielsen wrote: Hmmm, I thought that the installation did that, but I haven't an installed kernel-source package to check. If you have kernel-source, you don't need the kernel-headers (with hamm you did). That is what I was confused about, the headers. thanks -- Andrew
