Hi,

I just did a fresh install of 2.0_RC4 using the RAMDISK kernel,
which uses sysinst as the install tool.  I found the following
problems:

1) sysinst does a "cp /usr/mdec/boot /targetroot/boot".  This
   fails because /usr/mdec/boot doesn't exist, which is the way
   it's supposed to be, because the hp300 port doesn't use a
   two-stage boot loader.  This step seems to be superfluous.

2) sysinst does "/usr/mdec/installboot /usr/mdec/uboot.lif
   /dev/rsd0a".  This leads to an error message from disklabel
   saying "no disklabel".  There are two problems here:
    - In the disk label sysinst makes, the 'a' partition does not
      cover the sector where the disklabel is located
    - The type of the 'c' partition is "unused" not "boot", which
      is required if you want to install uboot.lif there.

   I worked around this by doing
    # disklabel sd0 | sed -e 's/unused/  boot/' > /tmp/label.sd0
    # disklabel -R -r sd0 /tmp/label.sd0
    # /usr/mdec/installboot /usr/mdec/uboot.lif /dev/rsd0c
   I could not use "disklabel -e" because neither 'ed' or 'vi' are
   part of the ramdisk image.

3) sysinst, while doing "MAKEDEV all" in /targetroot/dev emits an
   error message "df: not found".  Not sure what device that made
   a problem for, but it appears not to be critical.

4) sysinst, even though told that the networking details manually
   entered during installation are to be used for the system
   leaves /etc/rc.conf with rc_configured=3DNO, requiring manual
   intervention on the first boot.

Modulo these minor glitches the install appears to have gone OK.

Regards,

- H=E5vard