Re: Kernel build with kpkg (was Install of VMware)
On Sat, 23 Sep 2000, Tom Hoover wrote: > Is there any advantage to building the kernel outside of fakeroot? The fakeroot man page says quite clearly that "Thou shall never configure a anything under fakeroot", so I try to only do the install targets under fakeroot to avoid hard-to-track problems. BTW, kernel-package 7.17 (woody) is broken. If you have problems with it, that's why :-) I'm filling bugs right now. > > I dislike compiling the modules under fakeroot (and the fakeroot docs do > > warn not to do this), but ALSA seems not to mind it. Anyway, I dislike the > > I'm learning here...why do you dislike compiling modules under fakeroot? Try to compile ALSA (alsa-source package, I think) under fakeroot. It'll run GNU configure. Now read the fakeroot manpage. I've never had problems with fakeroot configure (I did not notice that big warning right away ;^) ), but since I do NOT presume to know better than the fakeroot author, I'm not about to go around doing stuff he went out of his way to warn one not to. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh pgp8bFK6lGDTb.pgp Description: PGP signature
Re: Kernel build with kpkg (was Install of VMware)
On Sat, Sep 23, 2000 at 06:57:48PM -0300, Henrique M Holschuh wrote: > > I don't know. What I could suggest you to do is this: > > make-kpkg --revision... build > fakeroot make -f debian/rules kernel-image-deb > fakeroot make-kpkg modules_image > > The above sequence has never failed me. It builds the kernel without a > fakeroot jail, and does the install-and-create-a-deb pass inside a single > fakeroot jail. Is there any advantage to building the kernel outside of fakeroot? > I dislike compiling the modules under fakeroot (and the fakeroot docs do > warn not to do this), but ALSA seems not to mind it. Anyway, I dislike the I'm learning here...why do you dislike compiling modules under fakeroot? Thanks for the help! -- Tom Hoover N5NTM <[EMAIL PROTECTED]> - http://www.hisword.net/tom - checkout HisWord(tm) Palmtop Bible at the above URL - --- finger [EMAIL PROTECTED] for PGP key
Re: Kernel build with kpkg (was Install of VMware)
On Sat, Sep 23, 2000 at 07:11:23PM -0300, Henrique M Holschuh wrote: > On Sat, 23 Sep 2000, Henrique M Holschuh wrote: > > > Am I misreading the docs? > > I don't know. What I could suggest you to do is this: > > Well, now I know. The make-kpkg man page makes it very clear that the only > target which knows how to deal with rootcmd is buildpackage. I never use it, > though. I don't need to build the rather big kernel-doc package, as I keep > the kernel source tree around. Thanks for the clarification. The following (from the kernel-package README) led me to believe (especially the part that I begin with ">>>" ) that it would work with kernel_image: Phase ONE: Getting and configuring the kernel 1 % cd 2 % make config # or make menuconfig or make xconfig and configure Phase TWO: Create a portable kernel image .deb file 3 % make-kpkg clean 4 % $Get_Root make-kpkg --revision=custom.1.0 kernel_image (Get_Root is whatever you need to become root -- fakeroot or sudo are examples that come to mind). Phase THREE: Install the kernel image on one or more machines 5 # dpkg -i ../kernel-image-X.XXX_1.0_.deb 6 # shutdown -r now >>> With the addition of fakeroot ( a really nice program, I recommend >>> it). To use fake root, try setting ROOT_CMD to 'fakeroot --'. Steps >>> 1 to 4 can be carried out as a non root user. Step 5 does require >>> root privileges. -- Tom Hoover N5NTM <[EMAIL PROTECTED]> - http://www.hisword.net/tom - checkout HisWord(tm) Palmtop Bible at the above URL - --- finger [EMAIL PROTECTED] for PGP key
Re: Kernel build with kpkg (was Install of VMware)
On Sat, 23 Sep 2000, Henrique M Holschuh wrote: > > Am I misreading the docs? > I don't know. What I could suggest you to do is this: Well, now I know. The make-kpkg man page makes it very clear that the only target which knows how to deal with rootcmd is buildpackage. I never use it, though. I don't need to build the rather big kernel-doc package, as I keep the kernel source tree around. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh pgpESjPbG9o7E.pgp Description: PGP signature
Re: Kernel build with kpkg (was Install of VMware)
On Sat, 23 Sep 2000, Tom Hoover wrote: > I've successfully built a new kernel package with make-kpkg, but only if I > use: > > fakeroot -- make-kpkg --revision=custom.X.XX. kernel_image I'll usually run fakeroot make-kpkg ... I've never needed that -- > Am I misreading the docs? I don't know. What I could suggest you to do is this: make-kpkg --revision... build fakeroot make -f debian/rules kernel-image-deb fakeroot make-kpkg modules_image The above sequence has never failed me. It builds the kernel without a fakeroot jail, and does the install-and-create-a-deb pass inside a single fakeroot jail. I dislike compiling the modules under fakeroot (and the fakeroot docs do warn not to do this), but ALSA seems not to mind it. Anyway, I dislike the horrible idea of compiling something as true root much more, so... (and I've not checked for another way to do it yet. Might as well go read the source of kernel-package and file a bug if there isn't one...) > Here's the last few lines of messages when the build fails: [...] > install -p -d -o root -g root -m 755 debian/tmp-image/DEBIAN > install: debian/tmp-image: Operation not permitted > make: *** [kernel-image-deb] Error 1 This suggests a bug in kernel-package. It's not wrapping the *whole* install-and-create-the-deb pass with the root wrapper, apparently. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh pgpuX3UvrQUm2.pgp Description: PGP signature
Kernel build with kpkg (was Install of VMware)
On Sat, Sep 23, 2000 at 07:30:19AM -0700, Nuhn Yobiznez wrote: > > Debian is great for newbie kernel building > because it has a wonderful package called kpkg. This > package does ALMOST everything for you! I highly > recommend doing an apt-get for it! It simplifies the > process to the point that after xconfig all you have > to do is: > make-kpkg clean > make-kpkg --revision=custom.X.XX. kernel_image I've successfully built a new kernel package with make-kpkg, but only if I use: fakeroot -- make-kpkg --revision=custom.X.XX. kernel_image I've attempted to set the environment variable "ROOT_CMD='fakeroot --'" as called out in the docs, but the package build always fails unless I include the "fakeroot --" at the beginning of the command. echo $ROOT_CMD correctly returns "fakeroot --", so I know that the variable is set correctly. Am I misreading the docs? Here's the last few lines of messages when the build fails: make[1]: Leaving directory `/usr/src/kernel-source-2.2.15' touch stamp-build rm -f -r ./debian/tmp-image ./debian/tmp-image.deb test -f stamp-configure || make -f /usr/share/kernel-package/rules configure test -f stamp-build || make -f /usr/share/kernel-package/rules build install -p -d -o root -g root -m 755 debian/tmp-image/DEBIAN install: debian/tmp-image: Operation not permitted make: *** [kernel-image-deb] Error 1 "DEBIAN" never gets created. I'm running as thoover, and the permissions of the directories are as follows (debian and tmp-image are created during the make-kpkg process): drwxr-sr-x3 thoover src 4096 Sep 23 13:24 debian/ drwxr-sr-x2 thoover src 4096 Sep 23 13:24 tmp-image/ -- Tom Hoover N5NTM <[EMAIL PROTECTED]> - http://www.hisword.net/tom - checkout HisWord(tm) Palmtop Bible at the above URL - --- finger [EMAIL PROTECTED] for PGP key
