On Tue, Jun 03, 2003 at 01:37:26PM -0500, Brian Elliott Finley wrote: > Thus spake David N. Lombard ([EMAIL PROTECTED]): > > Brian, > > > > I think your best bet is to ask for the kernel's .config and validate > > that. If none is provided, you could first look for /proc/config.gz > > before crabbing. > > > > Regardless, you should document the config items that you require and > > allow a user to force their kernel and modules.
i'm assuming this is the generate-boot-flavor-from-working-machine thread? there are a few standard places to look for the config, as well as giving the user an option to specify their own config. in most cases, we can do runtime tests too - create a cramfs fs & see if we can mount it - if not, try ext2. is devfs in /proc/filesystems, or should we copy over the system's /dev into the ramdisk? both have the problem of insuring that the kernel you are installing matches the information you have (except for kernels w/ config.gz or the dotconfig patch), but i don't think we'll solve that. -- --------------------------- dann frazier Hewlett-Packard Linux and Open Source Lab [EMAIL PROTECTED] (970) 898-0800 ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
