Hi,
>>"bill" == <[EMAIL PROTECTED]> writes:
bill> I think that there are several issues here but wonder if I see
bill> the right ones. Is isn't one of the problems with not using make
bill> kpkg that you may accidently "upgrade" a kernel using dselect?
Yes, but if you can build and inst
I think that there are several issues here but wonder if I see the right ones.
Is isn't one of the problems with not using make kpkg that you may accidently
"upgrade" a kernel using dselect?
I don't know (yet) how the preinst scripts handle kernel dependencies but if
they use the files in var t
"Cullen" <[EMAIL PROTECTED]> writes:
> Well rather than read the docs, I decided to re-compile my kernel
> using the steps I normally take and all seems well.
>
> First. The steps I took were
> "make mrproper"
> "make config"
> "make dep; make clean"
> "make zImage"
> "make modules"
>
> I then m
Hi,
make-kpkg takes all the steps that you took, and,
additionally, tells dselect/dpkg and friends that you have the kernel
installed, and it installs documentation in /usr/doc. It also adds an
easy method to remove it all cleanly, and warns you if you try to
remove a running kernel or
Well rather than read the docs, I decided to re-compile my kernel
using the steps I normally take and all seems well.
First. The steps I took were
"make mrproper"
"make config"
"make dep; make clean"
"make zImage"
"make modules"
I then moved my current modules with,
"mv /lib/modules/2.0.30 /lib/
5 matches
Mail list logo
