Re: Fixed modular kernel path and different kernels

[christos%astron.com@localhost (Christos Zoulas)]

In article <Pine.NEB.4.64.1701181346340.24490%speedy.whooppee.com@localhost>,
Paul Goyette  <paul%whooppee.com@localhost> wrote:
>-=-=-=-=-=-
>
>On Wed, 18 Jan 2017, Paul Goyette wrote:
>
>>> One obvious and trivial way to allow for testing like this is to have
>>> boot -a also ask for an override of the module path.
>>
>> This should not be too difficult, although it would (continue to) have the 
>> restriction that modules "pushed" from the boot loader (those which are 
>> loaded via /boot.conf as well as those automatically pushed for non-ffs 
>> boot-device file systems) would continue to be loaded from the boot device.
>>
>>> Once that is there, also provide the override via userconf or
>>> /boot.cfg.
>>
>> Would this really be necessary?  Do we have the ability to set the root file 
>> system via userconf or /boot.cfg?  (Neither the boot.cfg(5) nor userconf(4) 
>> man pages hint that this is available?)
>>
>>
>> With a goal of improving the useability of kernel modularity, I'd be happy to 
>> implement this capability (WRT boot -a), if there's some sort of consensus.
>
>I've gone ahead and implemented this - see attached patches.
>
>Code review appreciated, as well as comments on whether or not this 
>should be committed.

I think this should happen at boot loader time, otherwise it is too load for
preloaded modules?


christos