History log of /openbsd/usr.sbin/installboot/loongson_installboot.c (Results 1 – 10 of 10)
Revision Date Author Comments
# 6c99b301 06-Nov-2022 krw <krw@openbsd.org>

Nuke some 'set but not used' pathlen variables.

ok beck@


# a08d2734 19-Oct-2022 kn <kn@openbsd.org>

Replace "newfs/fsck_ext2fs" with "newfs/msdos -t ext2fs", constify

OK miod


# dea985b6 27-Sep-2022 kn <kn@openbsd.org>

fix passing explicit stage files

This fixes installboot regress on octeon; same diff as
macppc_installboot.c r1.6, powerpc64_installboot r1.7 and
octeon_installboot r1.8.

loongson was the last arch

fix passing explicit stage files

This fixes installboot regress on octeon; same diff as
macppc_installboot.c r1.6, powerpc64_installboot r1.7 and
octeon_installboot r1.8.

loongson was the last architecture requiring this fix. I don't have a
machine to test it myself (loongson isn't built anymore, anyway) but given
the same diff works on four other architectures, this should just work.

show more ...


# 14cbb8d0 14-Sep-2022 kn <kn@openbsd.org>

Backout "Reflect script failure in exit code"

amd64 install using (G)PT seems busted as reported by tb


# 35c2a5e8 11-Sep-2022 miod <miod@openbsd.org>

Fix build after previous


# 20f1db54 09-Sep-2022 kn <kn@openbsd.org>

Reflect script failure in exit code

installboot(8) runs newfs(8) and fsck(8) via system(3) but only checks
failures of the function itself, always returning zero no matter what the
programs/shell re

Reflect script failure in exit code

installboot(8) runs newfs(8) and fsck(8) via system(3) but only checks
failures of the function itself, always returning zero no matter what the
programs/shell returned.

This is bad for regress tests relying on correct return codes.

create_filesystem() itself must not exit as write_filesystem() calls it and
cleans up temporary files upon failure.

Make it return -1 if the script returned non-zero so write_filesystem()
handles it as error, cleans up and makes installboot exit 1.

Stop ignoring create_filesystem()'s return code in md_prepareboot() and
exit the same way.

Here's the change in behaviour on arm64 (newfs fails because of the
vnd/disklabel race, see "Race in disk_attach_callback?" on tech@):

# installboot -vp vnd0 ; echo $?
newfsing 6694ae5b0d7596ed.i
newfs_msdos: /dev/r6694ae5b0d7596ed.i: No such file or directory
0
# ./obj/installboot -vp vnd0 ; echo $?
newfsing 6694ae5b0d7596ed.i
newfs_msdos: /dev/r6694ae5b0d7596ed.i: No such file or directory
1

Tested on amd64 arm64 macppc octeon powerpc64 sparc64
OK millert

show more ...


# c3e1bf61 20-Jul-2021 kettenis <kettenis@openbsd.org>

Add -p option to "prepare" (newfs) a filesystem that will be used for
the bootloader. This is a no-op on architectures where such a filesystem
isn't needed.

ok krw@, deraadt@


# 86850af8 19-Jul-2020 visa <visa@openbsd.org>

Should use ufs_args here after all.

While here, make messages more correct.


# a1ee4d86 18-Jul-2020 deraadt <deraadt@openbsd.org>

use correct structure for mounting, duh
ok visa kettenis


# a284d5af 27-Jun-2020 deraadt <deraadt@openbsd.org>

convert macppc, octeon, and loongson to use MI installboot, removing
special case scripting in install.md.
(macppc still requires manual steps for HFS bootmode)
tested by krw, visa, gkoehler