Make ALL kernel modules be visible during restore

[extace]

When restoring to a hardware setup different than the original (i.e. different RAID/SATA adapter) you can be caught in a catch22 situation wherer you can NOT load the needed kernel modules because mondo/mindi did NOT put ALL OF THEM on the bootable portion of the image. the only current solution is to KNOW the drivers needed BEFORE the mondoarchive (backup) is even done so that they can be "modprobed" into memory so that mondo/mindi makes surethey are available.

A more appropriate and correct solution would be to have the ENTIRE kernel modules tree be accessible after booting in rescue mode (i.e. on new hardware). in case hardwaredetection fails (which it does if the disk controller driver is different from the original system), one could then have access to the ENTIRE kernel modules tree to be able to load up the proper driver and continue the restore.

If it's not possible to stick it in the bootable section of the image (due to space) it SHOULD be possible to take the kernel modules tree and create that as an ISO on the C and make that loop mountable as needed.

I got hit by this bug/defect/limitation, when designing a customer solution in a virtual environment and tried to transfer it over to real physical hardware, it had NO DRIVERS avail (no complete kernel modules tree), which resulting in me having to manually load the drivers in the virtual side before mondo-archiving so that they'd be available when booting the physical machine, but this was a hack and wasted numerous hours to get around a deficiency that should never have been present IMHO.

[Bruno Cornec]

First I consider that as an enhancement request, as it's not necessarily a bug (concidering mondo is a DR solution for your machine).

Second I completely agree with you and I've began to improve things in 2.2.3 (FORCE_MODS in mindi). But it won't be handled the way you want it before 3.x.