Re: install/56303: On a fresh installation, /tmp on sparc64 is not sticky

[Andreas Gustafsson <gson%gson.org@localhost>]

The following reply was made to PR install/56303; it has been noted by GNATS.

From: Andreas Gustafsson <gson%gson.org@localhost>
To: Martin Husemann <martin%duskware.de@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: install/56303: On a fresh installation, /tmp on sparc64 is not
 sticky
Date: Mon, 12 Jul 2021 22:03:33 +0300

 Martin Husemann wrote:
 > Also I did only look at the state of the disk after sysinst terminated (and
 > unmounted the target device) - it also coud be some rc.d script going wild
 > due to something else missing at first boot.
 
 I did a manual qemu install on lyta and escaped to a shell by typing
 control-z at the "The installation of NetBSD-9.99.86 is now complete"
 screen, and /targetroot/tmp had the incorrect 0755 mode at that point.
 
 My current theory is that one of gzip -dc, progress, or tar fails
 during the base.tar.xz extraction, specifically after the the
 directory /targetroot/tmp has been created but before it has been
 chmod'ed to its final mode, and that for some reason, sysinst doesn't
 notice the error.
 
 For example, if I escape to a shell during set extraction by typing
 control-z, manually kill the gzip -dc process, and exit the shell,
 sysinst appears to continue like nothing happened and says all sets
 extracted successfully.  Can you reproduce this?
 -- 
 Andreas Gustafsson, gson%gson.org@localhost