cvs commit: src/usr.sbin/eeprom Makefile eeprom.8 eeprom.c ofw_options.c ofw_options.h

[Marius Strobl]

On Sun, May 23, 2004 at 08:43:45PM +0200, Dag-Erling Smørgrav wrote:
> Marius Strobl <marius at FreeBSD.org> writes:
> >   The idea of eeprom(8) is that handlers can be written to add support
> >   for any firmware that stores such configuration in EEPROM or NVRAM;
> >   sort of e.g. eeprom(1M) on Solaris/x86 is used to turn PAE-support
> >   on and off (stored in a file then, not hardware). In FreeBSD, a
> >   candidate for this would be a handler for the EFI boot environment
> >   for FreeBSD/ia64.
> 
> Would it make sense to teach eeprom(8) how to handle /boot/loader.conf?
> 

My idea (which doesn't necessarily mean it has to come true) was
a single utility with the same MI frontend for displaying and
modifying MD configurations stored in hardware somewhere. The
mention of eeprom(1M) on Solaris/x86 was meant as an example of
precedence that a utility named "eeprom" already is in multi-
platform use (the NetBSD one, too, btw., but only for their
sun3* and sun4* ports).
IMO teaching it about loader.conf would overload it at some point
("Hey, it already handles loader.conf, can we make it handle
rc.conf, too?") and a separate utility for handling loader.conf
or FreeBSD config files in general would be more appropriate.
However, I don't feel like being the maintainer of the FreeBSD
eeprom(8) so if others think it makes sense to teach it about
e.g. loader.conf, why not.