Hi, I just had a look at the new boot loader for octeon and got some questions.
As far as I can see, the current situation is like this: - boot.conf is always read from partion a of the booted disk (which is the root device we got from uboot via /dev/octboot) - the system root file system also is always the first partition that is found to be a “working” openbsd installation (checks for existence of various directories) Correct? If I understand the behaviour of other architectures (namely amd64( correctly, wouldn't it be desired to a) read boot.conf from the device and partition where the bootloader was found? - this would mean, from the msdos partition on octeon devices b) set the root file system from the “device" variable which is set in the boot loader - this would mean, if I “set device sd0d”, it boots the image from sd0d and sets the root file system also to that one. This is meant as question. Are those correct assumptions? If so, is this still work in progress or do you want to behave differently on octeon? Kind Regards, Christian
