









|
[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[NMLUG] ubuntu and me
havoc wrote:
> Kevin Rosenberg wrote:
>
>>It's rather simple to use:
>
>
> What's wrong with 'make; make install; make modules_install'?
make-kpkg creates a full debian package and registers it with grub
automatically, and keeps upgrades from taking over your custom kernel.
Using Debian's package system is usually a good idea when you can -
make-jpkg, make-kpkg, and dpkg-buildpackage in source directories with a
debian/ directory in them...
>
> Thanks, though...
>
>
>>apt_get install kernel-package
>>cd /usr/src/kernel-source-<x.x.x>
>>make-kpkg clean
>>make xconfig
>>make-kpkg kernel_image
>>make-kpkg modules_image
>
I've always had the right files installed when I just did kernel_image -
no need to use modules_image.
>
> When I get to 'make-kpkg modules_image', I get:
>
> for module in ; do \
> if test -d $module; then \
> (cd $module; \
> if ./debian/rules KVERS="2.6.11"
> KSRC="/usr/src/linux-source-2.6.11" \
> KMAINT="Unknown Kernel Package Maintainer"
> KEMAIL="unknown@unconfigured.in.etc.kernel-pkg.conf" \
>
> KPKG_DEST_DIR="/usr/src/linux-source-2.6.11/.." \
> KPKG_MAINTAINER="Unknown Kernel Package
> Maintainer" \
> KPKG_EXTRAV_ARG="" \
> ARCH="i386" \
> KDREV="10.00.Custom" kdist_image; then \
> echo "Module $module processed fine"; \
> else \
> echo "Module $module failed."; \
> if [ "X" != "X" ]; then \
> echo "Perhaps $module does not understand
> --rootcmd?"; \
> echo "If you see messages that indicate that it is
> not"; \
> echo "in fact being built as root, please file a
> bug "; \
> echo "against $module."; \
> fi; \
> echo "Hit return to Continue"; \
> read ans; \
> fi; \
> ); \
> fi; \
> done
>
> ...........
> but no modules.
>
> ideas?
>
>
>>cd ..
>>dpkg -i kernel-image-<x.x.x>*deb modules-image-<x.x.x>*deb
>
>
> jody
|
|