that "your hard disk" is about to get nuked, and you are no longer sure
which of your ten disks you told sysinst to wipe?
Change this to tell you:
``Ok, we are now ready to install NetBSD on your hard disk (wd0). Nothing ...''
'rc_configured' is still changed via sed's s///, wscons=yes is appended
via "echo >>".
* make target-routines (target_expand(), and whatnot) work if no root
disk was selected. With this, sysinst can now be used on a "normal"
system to adjust the system's timezone. Use the entry in the "Utilities"
menu for that.
Both changes were tested by a full i386 installation.
before extracting sets, and move it back afterwards, to save the information
which X server to use.
Adresses PR 10935 by Dan McMahill <dmcmahill@netbsd.org>
* If etc/localtime can't be readlink(3)'d, assume the default time zone is
UTC
* if errors occur (malloc, fts_open, fts_read, menu generation fails),
skip timezone setting instead of terminating sysinst.
(/mnt)/usr/share/zoneinfo in a listbox, and setting (/mnt)/etc/localtime
accordingly.
* Adjust for the needed menuc change un run.c's log_flip() and script_flip()
functions.
Related PRs:
5777 sysinst does not offer to tweak /etc/localtime
8099 changing the default time zone is non-obvious
9910 sysinst doesn't ask about setting timezone
to prevent menuc(?) from putting all things in one line
(I don't know since when we got this "auto-wrapping" stuff,
and it may be nice for text paragraphs, but it's a PITA for
tables etc.)
do not save address/netmask/default router, if we got them from dhcp.
(we shouldn't do that). if we keep any of dhcp config into /etc, we shoul
update rc.conf to run dhcp again.
- on a IPv6/v4 dual stack network, it makes more sense to configure both.
- also, many of IPv4/v6 dual stack network requires us to contacd DNS
over IPv4 transport.
discussed with cyber@netbsd.org.
that can be specified with CHS, truncate it to the maximum values that
the BIOS provided, not 1023*255*63. Some BIOSs get awfully cranky when
you do that.
