> As a side point, is it worth implementing a much more complex
> configuration manager as a user-side daemon, and have a very simple
> configuration manager in the kernel itself?
This seems the best approach.
As for the rest of the issues, they _are_ quite tricky. For example with
my NodeRunner, it _can_ be reconfigured, but probably not without
rebooting, and as it's an EEPROM, it probably doesn't have that many
available write cycles. So it would be wonderful to be able to plug in a
module that lets the configuration manager _know_ it can be reconfigured,
and do so it if I explicitly authorize it. But doing it without permission
would be a no-no, and ideally there should be a weighting to suggest that
changing that device is less favorable then changing other devices.
I'm wondering if a Prolog engine (or something along those lines) would be
needed for the full-scale configuration manager.
-- Kenneth Albanowski (kjahds@kjahds.com, CIS: 70705,126)