Re: Kernel configuration
Jens,
"make-kpkg" actually runs "make oldconfig". It may be redundant unless
you really want to run it twice. I tend to run following sequence after
creating initial .config:
$ make menuconfig # customize as one wish, optional
$ make-kpkg clean
$ fakeroot make-kpkg --flavour=special --revision=local.1.0 kernel_image
Osamu
On Sun, Apr 15, 2001 at 05:03:02PM -0400, Jens Gecius wrote:
> Osamu Aoki <debian@aokiconsulting.com> writes:
>
> > I would copy .config from your previous build tree or /boot/config-2.4.2
> > to your new build tree.
>
> And I would run "make oldconfig" once after it is copied, just to
> update the new config-options and to see, what's going on in
> kernel-development.
>
> I know Stan didn't ask for that, but it is easy and gives a short
> glimpse on what's new. Pressing enter is also easy, 'cause the
> standard-answer is No.
>
> > On Sun, Apr 15, 2001 at 11:24:25AM -0400, Stan Brown wrote:
> > > Givne that I am building kernels with kernel-package (which works
....
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~
+ Osamu Aoki <debian@aokiconsulting.com>, GnuPG-key: 1024D/D5DE453D +
+ For more debian survival information, peek into: +
+ http://www.aokiconsulting.com/debian-survival/ +
Reply to: