>  > How are you partitioned? chgrp belongs in *usr*/bin. So my guess is
>>  that either the binary is in root partition's /usr directory, and
>>  then you're mounting the user partition over it, hiding it, or the
>>  binary is in the user partition and you're not mounting that.
>
>IIRC...
>150MB  /
>~2.9GB /usr
>~4.8GB /home
>950MB  /var
>196MB  swap
>
>If the system is just coming up and hasn't mounted partitions yet, 
>then that would explain why it can't find chgrp and chown, yes.  But 
>why would part of the booting or error recovery process that takes 
>place before this mounting be looking for commands on the as-yet 
>unmounted partition?

There's a few reasons that this could be. First I'd check to see 
whether or not sysinst made a valid fstab which tells the system what 
filesystems are which. Also, there's rc.conf directives for mounting 
critical filesystems first.

critical_filesystems_local="/var"
critical_filesystems_remote="/usr"

I pretty much always use just a single root&user partition, mine 
being private systems where noone but me & my family can stuff it by 
filling a partition.

>And why can't it find /dev/console?  That's the very first odd thing 
>I encounter.  I assumed the chgrp and chown were in response to 
>that, but maybe not.  In a traditional install I know there is a 
>step to create those devices.  I thought sysinst handled all that 
>without user intervention.

Because sysinst died before MAKEDEV would be my guess.

HTH
Mike
-- 
Bikers don't *DO* taglines.