From: "Michael Altizer" <[EMAIL PROTECTED]> > Thomas Backlund wrote: > > >From: "Michael Altizer" <[EMAIL PROTECTED]> > > > > > >>Where can I find the config files used to generate the kernel images of > >>the installation floppies and/or more information on using the blank.img? > >>Thanks > >> > >> > >> > >BOOT kernel > >/usr/src/linux/arch/i386/defconfig-BOOT > > > >as for blank.img... > >read the readme and install files on the CD or in the root of the cooker > >tree, > >or to put it short... build a kernel with ewerything you need compiled in, > >_no_ modules, and copy it to blank.img.... and boot/install... > > > >Thomas > > > Thank you for the quick response, but a couple items are still confusing me: > First, the default configuration for the BOOT kernel seems to contain a > large number of modules which would be in opposition of the second part > of your reply.
Yes, they are.... but we use the BOOT kernel on the CD, and the other floppy images, since the modules are on precompiled on the CD... but that's only usable if you have built them all at the same time.... > Second, I attempted what the readme says (yes, I had read it previously, > my mail was actually looking for a bit more detail) and I receive 'Could > not open ramdisk device file.' when attempting to load anything onto the > ramdisk (duh) even though I have compiled in support for RAM disks > (under Block devices). Also, I am unable to switch between virtual > consoles (with alt+F3, alt+F4) during the attempted installation, which > has me somewhat baffled. > Any further aid would be greatly appreciated. > -Michael > but when you use the blank.img you can't easily support any modules, or initrd, so you have to build a custom kernel, where you can use the above mentioned config as a start, but you have to remove is's module and initrd support...(chosing 'N' in the xconfig/menuconfig/config) and every h/w and fs you need to support during installation, has to be compiled in... (chosing 'Y' in the xconfig/menuconfig/config) Now, the next question is of course... why do you need to do all this? Doesn't the installerkernel support your system? Regards Thomas
