On Tue, 1 Feb 2005 00:43:06 -0500
"George Georgalis" <george@galis.org> wrote:
> On Mon, Jan 31, 2005 at 08:57:08PM -0800, Chris Pressey wrote:
> >On Mon, 31 Jan 2005 19:08:55 -0500
> >"George Georgalis" <george@galis.org> wrote:
> >
> >> Is it intentional that the installer (20040913) refuses to
> >configure a > network interface for a network that is not immediately
> >available? I > found it a bit awkward to setup an interface with
> >dhcp, only to change > it back when the box left my bench and went to
> >the internet.
> >
> >Not "intentional" so much as it's the typical use case we've been
> >assuming - the network configuration you set up during install is
> >likely the same network configuration you want to use when you boot
> >the box, at least for the first time. As with several situations
> >with the current installer, exceptions must be handled manually
> >(mount the target system yourself, edit /mnt/etc/rc.conf, etc)
> >Version 2 will handle network configuration in a more sophisticated
> >manner, we hope. That's still a fair ways off, though.
>
> If you can tell me the file to patch, I'll try to come up with a
> temporary fix, ie "that network unavailable, are you sure (y/N)" It
> would be convenient for people who haven't memorized rc.conf syntax
> (me). But if that option is tricky, I can live without it.
You can look at function fn_assign_ip() in fn_configure.c:
http://www.bsdinstaller.org/cgi-bin/cvsweb.cgi/installer/src/backend/installer/fn_configure.c
But, by the looks of the code, it actually does write your selected
network settings to rc.conf, even if they failed to connect. Possibly
all that is needed is a more informative error message.
-Chris