Hi, I used 6.99.7 for testing. > 1) The extracted sets and devices step information was automatic but no > prompt so could easily be missed. What else did I miss reading? There's a timeout of one second when the tars finished about everything being right. Perhaps you could increase that. > 2) Some failure with pkgin install made it go to configuration menu > again. So I had to do the configuration for networking all over again. When the network is up, you won't have to configure it again. I.e. one of the ping checks (gateway or DNS server) didn't work if you didn't configure network before. Btw, that could be changed. Imho, we should change it to do_config_network instead of config_network, so the user can decide to still configure a non-working network if he wants. See attached patch configmenu.c.diff. > 3) Hung here when I tried to install pkgin: > > Status: Running > Command: /sbin/umount /targetroot/ > > (maybe hung for one minute) > > then sysinst terminated. I didn't see why. Can you reproduce that? If so, could you please suspend at that time and see which processes are still open, i.e. what could still be hanging on that filesystem? > 4) Why is "Your host name" already set but DNS domain is not second > time? The hostname can be fetched from the machine. The search domain is a resolv.conf thing or stored in a variable by sysinst resp., thus gone. > 5) Later says re0 is already configured ... use it? > So yes, then dhcp yes, then domain name (and hostname) and no IPv6 > and then again: > > I have found the following network interfaces: re0 > Which device shall I use? [re0] > > So different menu but same concepts repeated! > > So I go through it and my DNS domain is now set > but now asks for my IPv4 number.... what happened to DHCP? At what point was this? And what is the first whole message? I cannot find anything close to it (by testing variations via grep). And then, for the second, there should be the question about DHCP directly after the media question. > 6) > > IPv4 gateway [10.0.2.2 > ]: > prompt is on two lines > > Same for name server is shown on two lines. I cannot reproduce nor really track that down. You said your resolv.conf didn't work before, how did you fetch the nameserver? Or was that what you entered before? The gateway as well as the nameserver are fetched by parsing shell output which is generated line by line. I really don't know how an additional newline should have gotten in there. > 8) Then to download pkgsrc tarball had to do all the networking steps > again (this is around 6 screens). This time multiple prompts warning > about network failure due to ping but asks if I want to continue > anyways. Note that the failure prompts asking if okay to continue never > happened with the pkgin networking failure ... it just continued. This is "right" (confirming that you may do still do it), but could be fixed by the attached patch. I think, most of the errors are due to sysinst thinking your network configuration failed, as your nameserver or gateway were inaccessible via ping, or the network interface didn't come up. The multiple questioning could be changed by the patch. Warning about the attached patch: Untested. If you agree, I'd test and finally commit it. Regards, Julian
Index: configmenu.c
===================================================================
RCS file: /cvsroot/src/distrib/utils/sysinst/configmenu.c,v
retrieving revision 1.5
diff -u -r1.5 configmenu.c
--- configmenu.c 15 May 2012 15:50:58 -0000 1.5
+++ configmenu.c 28 May 2012 17:41:53 -0000
@@ -207,7 +207,7 @@
set_network(struct menudesc *menu, void *arg)
{
network_up = 0;
- if (config_network())
+ if (do_config_network())
mnt_net_config();
return 0;
}
@@ -260,7 +260,7 @@
/* binary pkg config requires network at this point, so if
it's not already configured, do it. */
if (network_up == 0) {
- if (config_network())
+ if (do_config_network())
mnt_net_config();
}
Attachment:
signature.asc
Description: PGP signature