Hi All,

I am running:
kern.version=OpenBSD 6.8-beta (GENERIC.MP) #69: Tue Sep 15 12:34:41 MDT 2020
    dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

I just tried to use sysupgrade and I notice that its behaviour has
changed a bit since my last upgrade. Previously (last six months or so)
after the download of the new sets and the reboot, I would have been
prompted as to what to do i.e. Install, Upgrade, or Shell.  Then for a
keyboard layout (e.g. de) and for the name of the disk containing OpenBSD
(i.e. the system root partition) or "/").
 
 1. Now on the console I see (post reboot):
    "Performing non-interactive upgrade..."
    It automatically selects a "root" disk, and in my case it correctly
    selects sd1. which is great.

 2. The upgrade then proceeds, however it fails to identify the location
    of the newly downloaded sets. The error is:
    "The directory '/home/_sysupgrade/' does not exist."

 3. It then seems to abort the upgrade and reboot the system. Thus
    leaving me back where I started.

 4. I get an excellent log via email of sysupgrades actions (see below).

The sets are (or at least they were) present on disk, located in
/space/home/_sysupgrade. There is also a symlink from /home/_sysupgrade
to this directory.

Sysupgrade has this partition mounted as "/mnt/space".

How can I best tell sysupgrade where to find the sets?

According to the man page for autoinstall it seems as if I should be able
control it with an upgrade response file e.g. previous sysupgrade runs
sent this sample/example via email:
> Which disk is the root disk = sd1
> Force checking of clean non-root filesystems = no
> Location of sets = disk
> Is the disk partition already mounted = yes
> Pathname to the sets = /mnt/space/home/_sysupgrade
> Set name(s) = done
> Directory does not contain SHA256.sig. Continue without verification = yes
> Location of sets = done

But what I am missing is how to supply the response file to sysupgrade.
In the above man page it states "... If either /auto_install.conf or
/auto_upgrade.conf is found on bsd.rd's built-in RAM disk,"

But how do I get the file into the .rd RAM disk? Or should I put it
somewhere else entirely? This is a (snapshot) upgrade, not an complete
install.

The man page also mentions serving it up via the network, using http and
dhcp, but that would require another running system.

Or, can I somehow tell sysupgrade _not_ to automatically run, but rather
interrupt it so as to manually provide the right answers (path)?

Cheers,
Robb.


Email content:
...
Subject: mjoelnir.domain.tld upgrade log

Choose your keyboard layout ('?' or 'L' for list) [default] default
Available disks are: sd0 sd1.
Which disk is the root disk? ('?' for details) [sd0] sd1
Checking root filesystem (fsck -fp /dev/sd1a)... OK.
Mounting root filesystem (mount -o ro /dev/sd1a /mnt)... OK.
Force checking of clean non-root filesystems? [no] no
fsck -p 281ef747da03afe7.e... OK.
fsck -p 281ef747da03afe7.f... OK.
fsck -p 281ef747da03afe7.g... OK.
fsck -p 281ef747da03afe7.h... OK.
fsck -p 281ef747da03afe7.k... OK.
fsck -p 281ef747da03afe7.j... OK.
fsck -p 281ef747da03afe7.l... OK.
fsck -p 7a1775fef773535e.h... OK.
/dev/sd1a (281ef747da03afe7.a) on /mnt type ffs (rw, local)
/dev/sd1e (281ef747da03afe7.e) on /mnt/var type ffs (rw, local, nodev, nosuid)
/dev/sd1f (281ef747da03afe7.f) on /mnt/usr type ffs (rw, local, nodev)
/dev/sd1g (281ef747da03afe7.g) on /mnt/usr/X11R6 type ffs (rw, local, nodev)
/dev/sd1h (281ef747da03afe7.h) on /mnt/usr/local type ffs (rw, local, nodev, 
wxallowed)
/dev/sd1k (281ef747da03afe7.k) on /mnt/usr/obj type ffs (rw, local, nodev, 
nosuid)
/dev/sd1j (281ef747da03afe7.j) on /mnt/usr/src type ffs (rw, local, nodev, 
nosuid)
/dev/sd1l (281ef747da03afe7.l) on /mnt/fast type ffs (rw, local, nodev, nosuid)
/dev/sd0h (7a1775fef773535e.h) on /mnt/space type ffs (rw, local)

Let's upgrade the sets!
Location of sets? (disk http nfs or 'done') [http] disk
Is the disk partition already mounted? [yes] yes
Pathname to the sets? (or 'done') [6.8/amd64] /home/_sysupgrade/
The directory '/home/_sysupgrade/' does not exist.

Reply via email to