config(8) should check if a scheduler is selected

[Scott Long]

Wes Peters wrote:
> On Saturday 19 April 2003 01:05, Scott Long wrote:
> 
>>Bruce Evans wrote:
>>
>>>It is the only mandatory option (sic).  Kernels with no options
>>>(although they might not be useful) can be built except for this bug.
>>> Example of a minimal config file (before misconfiguration of the
>>>configuration of scheduling).
>>>
>>>%%%
>>>machine		i386
>>>cpu		I686_CPU
>>>ident		MIN
>>>%%%
>>
>>The scheduler is (one of) the first core subsystems to be made
>>modular.  If by chance the VM system became modular (VM_MACH, VM_UVM
>>=-) you'd have a similar situation there also.
> 
> 
> Doesn't this argue for a keyword rather than an option?  If you have to 
> have one or the other for the kernel to function, wouldn't a 'scheduler' 
> keyword (and likewise a 'vm' or 'vm_model' keyword) save us from the 
> lunacy of non-optional options?
>
> 
>>I'm afraid that the lack of seatbelts in config(8) for SCHED_xxx will
>>generate a lot of user complaints when 5.1 is released.  Since code to
>>implement it has not magically appeared yet, we might have to make due
>>with adding extra eye-catching comments to things like NOTES and
>>GENERIC.
> 
> 
> Or maybe we could fix it?
> 

I'll repeat again:

 >> Since code to implement it has not magically appeared yet...

=-)

I'd be happy if someone took this up.  If Terry can do it with
magical linker sets and virtual tables or whatever, that would be
great too.  Until patches appear, I'm not too concerned on how
it's done.

Scott