svn commit: r239598 - head/etc/rc.d

[Ian Lepore]

On Thu, 2012-09-06 at 12:02 -0700, David O'Brien wrote:
> On Thu, Sep 06, 2012 at 11:19:21AM -0600, Ian Lepore wrote:
> > The kenv application may be available, but on any platform that
> > lacks /boot/loader it's likely to produce empty output.  Because the
> > kernel environment is typically empty, an embedded system may not even
> > have the kenv binary installed.  
> 
> The FreeBSD kernel expects to be loaded by /boot/loader and for it to
> provided a suitable environment.
> 

>From 'man 8 boot' ...

        However, it is possible to dispense with the third stage
        altogether, either by specifying a kernel name in the boot block
        parameter file, /boot.config, or, unless option -n is set, by
        hitting a key during a brief pause (while one of the characters
        -, \, |, or / is displayed) before loader(8) is invoked.
        Booting will also be attempted at stage two, if the third stage
        cannot be loaded.  
        
Dispensing with loader(8) still seems to be sanctioned.

> If one has chosen to not use /boot/loader (or include 'kenv' on their
> embedded boot media), they're already gone so far down the path of
> customization that hacking 'initrandom' should be expected.

It's not a choice thing.  /boot/loader just isn't an option on any of
the non-x86 systems I work with.  That's not just embedded systems -- my
ARM-based DreamPlug, a small off the shelf general purpose computer, can
only load a kernel.bin file.  It'd be nice to have /boot/loader working
some day, but it's just not even possible right now.

-- Ian