Christian Gut <cycl...@is-root.org> wrote: > 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)
I t should be read from /etc in the root filesystem. Are you saying it is read from somewhere else? > - 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) There is a strong default to consider it the 'a' partition on 'some device', decided MD, and hopefully not too much trouble. > 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 It is supposed to be read from /etc, which is in the root filesystem. Why are you proposing it be read from some strange location??? You really aren't explaining your usage case. > 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. There's probably some magic to choose it. You are proposing that people have to set more uboot variables?? That isn't fun maybe we give up on the platform.. > If so, is this still work in progress or do you want to behave differently on > octeon? You start by describing it working just like amd64. Then you embark on wanting it to work different from amd64. And now you ask why it is different? Confused.
