On 3/31/20 11:46 AM, Raf Czlonka wrote:
On Tue, Mar 31, 2020 at 10:25:53AM BST, Stuart Henderson wrote:On 2020/03/31 11:05, Renaud Allard wrote:Hello, I was trying to autoinstall OpenBSD over an existing installation of linux. So I used a modified (with upobsd) bsd.rd containing an auto_install.conf. But it seems the (MBR) partitioning line is never taken into account. Using: "MBR = G" "Use (W)hole disk MBR, whole disk (G)PT or (E)dit = G" never matches, so autoinstall is always using the default ("whole").Pretty sure it is a "start of line" match rather than a substring match - try "Use (W)hole = G".Also, the whole thing hinges on whether the machine boots in (U)EFI mode and/or the latter is properly detected. If you already boot using it, then you don't need to provide the answer to that installer question at all as it is being taken care of automatically: while :; do _d=whole _q="Use (W)hole disk MBR, whole disk (G)PT" [[ $MDEFI == y ]] && _d=gpt otherwise, if you know what you're doing(!), you need to answer an additional question: [gG]*) if [[ $MDEFI != y ]]; then ask_yn "An EFI/GPT disk may not boot. Proceed?" [[ $resp == n ]] && continue fi
I used G, just to see if it was matching the line. Using W would have resulted in the default behaviour, so I wouldn't have seen the difference. But also, using W doesn't give the expected results either as the disk is not fully repartitioned for OpenBSD. So, there are actually 2 bugs, one for not matching the line and one for not repartitioning correctly when whole is used.
The funny part is that if I relaunch /autoinstall manually after the failure, it partitions everything as expected.
smime.p7s
Description: S/MIME Cryptographic Signature
