Bug#109455: dhcp non-functional 3.0.11
Stephen Waters <swaters@amicus.com> writes:
> On 24 Aug 2001 11:01:01 -0400, Adam Di Carlo wrote:
> > > That is true. In fact, I suspect that a lot of folks using the
> > > DHCP/network install option just might be cable and DSL installers...
> > > perhaps a note like this would be useful:
> >
> > No, that's too hard to do, and it's more likely that our silly test
> > will fail than anything else.
> >
> > I really think this is a dhcp-client bug ? Or did any people really
> > identify that it's something about the root disk which causes this?
>
> I'm not familiar enough with either codebase to say whether dhclient
> returns an error or not or that b-f incorrectly detects success when
> dhclient actually reported failure.
You'd have to run it on the cmdline and look at return values. You
don't need to look at the source to do that.
I need help with this bug because I've never experienced it. DHCP has
always worked great for me.
> As far as difficulty of implementing the message, I just figured you'd
> wrap the error with the help text instead of just returning "Operation
> failed" which is definitely unhelpful. :-) I wouldn't worry about
> testing for the condition.
>
> Flow:
> fork(dhclient)
> dhclient returns failure (doesn't matter what the failure is)
> printf("Suggestion helptext yadda. ERROR %s",ERRTEXT)
> printf("Would you like to manually configure?")
That's reasonable, although minor. So it's dhclient which is saying
"operation failed", and that is getting put up on the window? I must
have misread you -- I thought you were saying dhclient was returning
success, but no IP... ?
--
...Adam Di Carlo..<adam@onshore-devel.com>...<URL:http://www.onshored.com/>
Reply to: