modules and kernel elements

[Ben Ransom]

I see, looking in /usr/src/linux-<VERSION>/configs and grepping the 
appropriate file for "=m" will show the default list of modules.  It is 
still a little muddy however, as the list of "=m" from the above file does 
not match the list of "=m" from the .config file built with 'make oldconfig'

The main point tho is that I do not want to make a new kernel image and set 
of modules that is different from out of box -- at least as a starting 
point before customizing.  Is this why you suggest simply copying over 
/usr/src/linux-<VERSION>/configs/<APPROPRIATE_FILE> to 
/usr/src/linux-<VERSION>/.config?  (and then do make xconfig)
Thanks,
-Ben

At 01:38 PM 12/14/2004 -0500, you wrote:
>Ben Ransom wrote:
>>I want to add a module (ntfs read) to a system running redhat enterprise 
>>WS with kernel 2.4.21-20.
>>Going to the kernel src directory (same version as what is running) and 
>>doing a `make oldconfig`  ...will that generate a .config file that would 
>>represent the same kernel parameters and modules as a system originally 
>>installed from CD and patched using up2date?   What does "oldconfig" read 
>>to determine to define in .config?
>>Thanks,
>>-Ben
>
>
>To see the config was used to build a distributed kernel,
>install the kernel-source package for the version of the kernel you are 
>running, and then look in /usr/src/linux-<VERSION>/configs
>
>You can copy the one you are using to /usr/src/linux-<VERSION>/.config
>
>--
>redhat-list mailing list
>unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>https://www.redhat.com/mailman/listinfo/redhat-list