On Sat, May 09, 2020 at 10:51:49PM +, Mikolaj Kucharski wrote:
>
> A bit of explanation with `cat -n install.sub | expand -t 2`
>
>
> 1599
> 1600 # Fetch and verify the set files.
> 1601 for _f in BUILDINFO $_get_sets; do
> 1602$UU && reset_watchdog
> 1603
>
On Sat, May 09, 2020 at 10:51:49PM +, Mikolaj Kucharski wrote:
> @@ -1678,6 +1678,11 @@ install_files() {
> file:///mnt/var/sysmerge/${_f%%base*}etc.tgz |
> tar -zxphf - -C /mnt
> fi
> + ;;
>
Hi Stuart,
On Thu, Apr 16, 2020 at 11:53:19AM +0100, Stuart Henderson wrote:
> Rather than downloading it and deleting it again, it would be more
> useful if BUILDINFO was kept around after installing. Then sysupgrade
> could check to make sure it isn't going backwards with a future update.
>
On 2020/04/13 08:44, Mikolaj Kucharski wrote:
> Hi,
>
> Would below be okay?
>
> On Tue, Apr 07, 2020 at 04:46:38AM +, Mikolaj Kucharski wrote:
> > Hi,
> >
> > When I'm upgrading my machines, I find it useful to have BUILDINFO
> > file around. Tested on RPi3.
> >
> > Please carbon-copy me
Hi,
Would below be okay?
On Tue, Apr 07, 2020 at 04:46:38AM +, Mikolaj Kucharski wrote:
> Hi,
>
> When I'm upgrading my machines, I find it useful to have BUILDINFO
> file around. Tested on RPi3.
>
> Please carbon-copy me in any replies. Thank you.
>
> openbsd-rpi# sysupgrade -s -n
>
Hi,
When I'm upgrading my machines, I find it useful to have BUILDINFO
file around. Tested on RPi3.
Please carbon-copy me in any replies. Thank you.
openbsd-rpi# sysupgrade -s -n
Fetching from https://cdn.openbsd.org/pub/OpenBSD/snapshots/arm64/
SHA256.sig 100%
