On 7/13/22 1:11 PM, Vincent Legoll wrote:
Hello,
I was trying to autoinstall OpenBSD 7.1 on a VM when I stumbled upon
something unexpected (to my uneducated eyes) in the installer.
What I'm trying to do may very well fall in the "unsupported" basket,
just tell me. But still, I think I can at least ask if this is
actually intended behavior.
When I used the following answers:
[...]
Location of sets = disk
Is the disk partition already mounted = yes
Pathname to the sets = /
[...]
I expected the setup to look at the / (from the ramdisk), but it
searched in /mnt2 instead.
As a user, I'd expect the response there to be "As would be seen
on the running system."
As a user, I expect it to go something like this:
I put the install sets someplace on the running systemm, say
/home/upgrade or /usr/rel. I rebooted into bsd.rd, chose
"install" or "upgrade", I expect to answer exactly where I put
the files. How the upgrader or installer does the upgrade or
install, I really don't care."
The installer happens to mount the system hanging off /mnt2,
but I shouldn't have to know that. I definitely shouldn't have to
include that in my answer (in my opinion)
...
Is this in need for a modification, or is it good as-is ?
I can submit a patch if you think it is useful.
Speaking only for myself, I think it is working exactly as I'd
hope right now.
I would spend some time thinking about why you are stuffing the
install files into the ramdisk rather than from an existing
file system or other more supported option. I think the "proper"
answers will work better for you all around.
Nick.
