Re: install/54972: No Tmp Partition Created after Changing Size from Percentage to MB Input in 9.0 Installer

[Dan Plassche <dplassche%gmail.com@localhost>]

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

From: Dan Plassche <dplassche%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: install-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: install/54972: No Tmp Partition Created after Changing Size from
 Percentage to MB Input in 9.0 Installer
Date: Sun, 16 Feb 2020 14:39:56 -0500

 On Sun, Feb 16, 2020 at 2:25 PM Martin Husemann <martin%duskware.de@localhost> wrote:
 >
 > The following reply was made to PR install/54972; it has been noted by GNATS.
 >
 > From: Martin Husemann <martin%duskware.de@localhost>
 >
 >  Yes, that is kinda on-purpose. The next screens show the partitions on
 >  one special drive (like wd0) and /tmp will be only a mountput, but not
 >  eat space from that disk.
 >
 >  So did the install end up with tmpfs and the size you chose mounted as
 >  tmpfs on /tmp ?
 
 Yes, I did get tmpfs with the correct size in /etc/fstab and the
 installer says (tmpfs) in parentheses next to the /tmp mountpoint, so
 that behavior was logical.
 
 At first glance, I was surprised because experience differed from
 previous installers.
 
 The real issue in terms of functionality is that there's no way to add
 another user-defined partition as /tmp even if you enter a size of 0
 on the /tmp (tmpfs) line in the partitioning screen.
 
 I tend to prefer to set a separate /tmp partition to avoid sacrificing
 memory or risking the off-chance of a runaway item or process in /tmp
 filling up the root (especially in systems with limited resources).
 
 Thanks,
 
 Dan