Very Computer

by **asbar..** » Thu, 29 Jun 2000 04:00:00

I have a quick question about rebuilding my kernel to the latest stable
(currently 2.2.16).

I noticed quite a few changes in the menu options. I also noticed that
many common options are not even defaulted as modules. such as network
devices like PPP, generic sound support, etc. All of these are modules
that came with my redhat 6.2 distro.

Is this normal, and should I go through every option to decide if the
device I want should be a module or built-in? I'm a bit new at the
kernel-building :-).

And I noticed that when I pass vga=ask to the kernel via lilo, it
ignores that option unlike the 2.2.14 kernel that comes with RH 6.2. Is
there any way to get the smaller text mode?

Aaron

Sent via Deja.com http://www.deja.com/
Before you buy.

by **Vincent F** » Thu, 29 Jun 2000 04:00:00

>I have a quick question about rebuilding my kernel to the latest stable
>(currently 2.2.16).
>I noticed quite a few changes in the menu options. I also noticed that
>many common options are not even defaulted as modules. such as network
>devices like PPP, generic sound support, etc. All of these are modules
>that came with my redhat 6.2 distro.
>Is this normal, and should I go through every option to decide if the
>device I want should be a module or built-in? I'm a bit new at the
>kernel-building :-).

What I would do, go into your old kernel, make menuconfig.
From there, go to the bottom, save out your kernel config as
a file somewhere accessible to all kernels like /usr/src/
Now go into the new kernel tree, make menuconfig, and read
in this kernel config file. Done. I'm sure someone else will
have a better simpler faster way.

--
"Who needs horror movies when we have Microsoft"?
-- Christine Comaford, PC Week, 27/9/95

by **Eggert.Eh..** » Fri, 30 Jun 2000 04:00:00

>What I would do, go into your old kernel, make menuconfig.
>From there, go to the bottom, save out your kernel config as
>a file somewhere accessible to all kernels like /usr/src/
>Now go into the new kernel tree, make menuconfig, and read
>in this kernel config file. Done. I'm sure someone else will
>have a better simpler faster way.

I always copy the .config file from the old kernel tree to the new one, cd into
the new tree and run
make oldconfig
this asks you every new kernel option to be set. Then I run
make menuconfig
or
make xconfig
to check the configuration.
this works fine for me. I just upgraded to 2.2.16, no probs.

--
Eggert Ehmke

by **Horst Simo** » Tue, 11 Jul 2000 04:00:00

I have RAID 0 and after upgrading to kernel 2.2.16 it will no more
recognize the the raid drives it fail with VFS eerrors. I tried to
recreate the raid 0 array, but when i did mke2fs it hung on
creating the inodes. After reverting back to kernel 2.2.15 all was
ok. Anyoneexperience the same problems and is there a fix/patch
available?

regards,
Horst Simon

>>would do, go into your old kernel, make menuconfig. From there, go to
>>the bottom, save out your kernel config as a file somewhere accessible
>>to all kernels like /usr/src/ Now go into the new kernel tree, make
>>menuconfig, and read in this kernel config file. Done. I'm sure someone
>>else will have a better simpler faster way.

> I always copy the .config file from the old kernel tree to the new one,
> cd into the new tree and run make oldconfig this asks you every new
> kernel option to be set. Then I run make menuconfig or make xconfig to
> check the configuration. this works fine for me. I just upgraded to
> 2.2.16, no probs.

> --

Very Computer

kernel 2.2.16 questions

kernel 2.2.16 questions

kernel 2.2.16 questions

kernel 2.2.16 questions

kernel 2.2.16 questions