David-
Actually, I'm not sure how they've got it setup, but if you run 'make
oldconfig' on a fresh RH7 system (with the .config NOT in the source tree), it
creates a .config file for you. This .config file seems to my novice eye to
reflect the kernel built on install, to which you could then make your minor
modifications.
I don't know if this will help with Ted's question or not. I guess it depends
on where and when the kernel he's running was built. Was it the most recent
kernel built on his system? If so, then he should have an existing .config
file, or be able to create it with a 'make oldconfig'. I would definately look
for an existing .config before running 'make <ANYTHING>'!!
-Jacob
On Tue, 20 Mar 2001, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>
> Chuck Mead wrote:
>
> >On Mon, 19 Mar 2001, Ted Hilts blurted out:
> >
> >TH>I arranged for a custom built computer for a data base server.
> >TH>Apparently the kernel was recompiled to provide for special options. If
> >TH>I were to upgrade the software installation including the kernel I might
> >TH>lose those options. So my question is this: How do I look into the
> >TH>system to discover how it was actually compiled (assuming the kernel was
> >TH>not compiled elsewhere and simply dropped into the system). What
> >TH>directories, files, and command line queries are necessary for me to
> >TH>develop this information.
> >
> >If memory serves:
> >
> >cd /usr/src/linux
> >make oldconfig
> >
> >will recreate the last config file. For that matter it may also already
> >exist in /usr/src/linux.
>
> 'make oldconfig' uses an old .config file to rebuild deps, I think ...
> so you'd need that. Oddly, it doesn't appear that Red Hat distributes
> a .config with their tree, so I can't just make a minor modification
> to their stock kernel; I have to start from scratch. (Which I
> normally do anyway, but it'd be nice to have the option.)
>
> - -d
>
> - --
> David Talkington
> http://www.spotnet.org
>
> PGP key: http://www.prairienet.org/~dtalk/dt000823.asc
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 6.5.8
> Comment: Made with pgp4pine 1.75-6
>
> iQEVAwUBOrgG9L1ZYOtSwT+tAQE0aQf9GmWAB2EDX/wsHrjM9Ux7rHXNA/FmanvM
> 6XiMVQF1+oYzijeQSGtP5hwF9+SF32cIyKU+DNNK7lXCCngTbkwnsPvxIISDeG+F
> 94HcdCKIZoX6F2i7i3G6B3jW3njiWrwzxRKbHUFku/RTDnioroy6+d4t6knt5LsB
> HiLxR5VA4AjcEU4fYX2xQC0gGDIu/IwVPYy22sVb4D5/Vt6qFIWc7g+ep9ZjXzEu
> TALLjxKBGI0Z+Q4gZ7hbLMxVNPPu1mDEa3caD0R32JlnxMqRigGgOtULEPjhqRl7
> RzkZ9DgUZbfUrFlV2RfLujLasqciVehUqCerdTvYHUFUBGybwskUkw==
> =YnJ3
> -----END PGP SIGNATURE-----
>
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
--
Jacob Killian
PGTC System Administrator
<mailto: [EMAIL PROTECTED]>
<http://www.pgtc.net>
501-846-7245
"Long may we walk" --my mom
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
