Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Dec 2015 05:47:23 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 205263] Fix for netwait boot order issues and other bugs
Message-ID:  <bug-205263-8-9SiCtRPYiO@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205263-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-205263-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205263

--- Comment #4 from Brendan Molloy <brendan+freebsd@bbqsrc.net> ---
(In reply to Ian Lepore from comment #1)

Further to your point about /boot/loader.conf being the correct way to solve
this, that may well be the case. It certainly feels a lot better. However,
while this patch might provide a less ideal solution, it doesn't require extra
configuration to make the interface work, while not adding the patch has the
consequence that my bootup is delayed by an extra 30 seconds while NFS cannot
mount and stalls temporarily, which only serves to confuse the user further.

Also, I know that changing $netwait_ip to be optional is potentially a
controversial move, and I am quite happy to remove that from the patch if it is
seen as entirely disagreeable, but I saw no use for it as if it weren't for the
fact I am waiting for a late interface to arrive, I wouldn't be pinging during
the boot sequence anyway, so it is not useful in my use case of netwait.

I hope my explanation has been helpful!

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205263-8-9SiCtRPYiO>