When I move from one kernel to another (e.g. 2.2.17 to 2.2.18), can I
just copy the .config from the old directory to the new one?
I would imagine it innocuous, but I figured I'd ask just in case.
Thanks!
Jonathan
--
[EMAIL PROTECTED]
GPG public key available from http://lupavista.jamdata.net/g
What I do is, whenever I edit a configuration for my kernel, I save an additonal
copy in /root/kernelconfig. (This works at least with menuconfig and xconfig.)
Then, whenever I need to compile a new kernel, I load those settings in. Doing
it that way should put in any new settings that are added as
also sprach Jimmy Kaplowitz (on Fri, 23 Feb 2001 10:13:10PM -0500):
> What I do is, whenever I edit a configuration for my kernel, I save
> an additonal copy in /root/kernelconfig. (This works at least with
> menuconfig and xconfig.) Then, whenever I need to compile a new
> kernel, I load those set
On Fri, Feb 23, 2001 at 10:25:37PM -0500, MaD dUCK wrote:
>
> yup, that's exactly the procedure. okay, i am not really a kernel
> guru, but i have compiled *a lot* of kernels before and applied
> patches and took the make system apart...
>
> anyway, the procedure that i always follow is:
>
> (om
On Fri, 23 Feb 2001, Jonathan Lupa wrote:
>When I move from one kernel to another (e.g. 2.2.17 to 2.2.18), can I
>just copy the .config from the old directory to the new one?
Mostly. If there's an added option, you'll have to configure it somehow,
but yes, in most cases you can.
>I would imagin
On Fri, Feb 23, 2001 at 11:29:03PM -0600, Lute Mullenix wrote:
>
> Hi,
>
> I'm new to Debian, but have been using Linux in the form of SuSE 6.4
> evaluation for about six months. Under SuSE I managed to compile a custom (I
> use the word loosely) kernel that worked well enough for my needs. And
Thanks for all your answers! The listed procedures will be most
helpful.
-Jonathan
--
[EMAIL PROTECTED]
GPG public key available from http://lupavista.jamdata.net/gpg.asc
--
Lament 1750: "If I only had a radioactive decay source and
7 matches
Mail list logo
