Yeah sure why not.

Klemens Nanni <k...@openbsd.org> wrote:

> Upgrades are noiser on macppc (and loongson and octeon) than on other
> architectures because boot firmware changes and/or tips to complete an
> OpenBSD installation are always printed, even though they are not needed
> after an upgrade:
> 
>       INSTALL.macppc describes how to configure Open Firmware to boot 
> OpenBSD. The
>       command to boot OpenBSD will be something like 'boot hd:,ofwboot /bsd'.
> 
> Shall we limit those one-shot bits relevant to new installations to
> actual installations?
> 
> I don't see how those are useful after an upgrade of a working OpenBSD
> install.
> 
> Index: miniroot/install.sub
> ===================================================================
> RCS file: /cvs/src/distrib/miniroot/install.sub,v
> retrieving revision 1.1213
> diff -u -p -r1.1213 install.sub
> --- miniroot/install.sub      19 Oct 2022 08:24:14 -0000      1.1213
> +++ miniroot/install.sub      5 Nov 2022 21:49:38 -0000
> @@ -2951,13 +2951,16 @@ __EOT
>  CONGRATULATIONS! Your OpenBSD $MODE has been successfully completed!
>  
>  __EOT
> -     [[ $MODE == install ]] && cat <<__EOT
> +     if [[ $MODE == install ]]; then
> +             cat <<'__EOT'
>  When you login to your new system the first time, please read your mail
>  using the 'mail' command.
>  
>  __EOT
>  
> -     md_congrats
> +             md_congrats
> +     fi
> +
>       $AI && >/tmp/ai/ai.done
>  }
>  
> 

Reply via email to