Red Hat Bugzilla – Bug 84266
dns boot command line info not used fully (and a fix?)
Last modified: 2008-01-17 12:49:42 EST
If one specifies "dns" on the command line, this makes it into the second-stage installer, but isn't shown in the *first* stage (in the loader) if one is doing a network install. The culprit seems to be at the beginning of setupNetworkDeviceConfig in net.c -- if loaderData->ipinfo_set is 0, the function returns right away. This check seems unnecessary, as the individual bits of data each get their own if statement later -- and removing it makes everything work perfectly, as far as I can tell.
Are you specifying your ip on the command line? Essentially, to get any of the network information to take effect, you need to specify the ip as well otherwise we throw it out as invalid.
No, I'm not. And I don't want to. :) In fact, perhaps this bug should be changed to: "Don't throw out dns information from the command line just because ip isn't set". :) Most people setting up machines here don't know the campus DNS servers off the top of their heads, so it's extremely useful to have the information pre-filled. With earlier versions, I patched anaconda to have them hardcoded, but that's both a pain and ugly. So I want to specify them on the command line in isolinux.cfg -- a much more trivial change to make since all it requires is a text editor and mkisofs. Ideally, I'd like to be able to specify three different dns servers this way, but I figure one thing at a time. :)
(I created bug #84409 for the "specify multiple servers" thing, by the way.)
Okay, I guess that's good enough reasoning to convince me. Committed something similar to CVS
ipinfo_set now seems to be set in multiple places but never actually read (except in printLoaderDataIPINFO). Given your comment in loader.h about how you don't like the _set attribs, should it be completely removed?
I'm going through Bugzilla closing some bugs that have been marked as Modified for some period of time. I believe that most of these issues have been fixed, so I'm resolving these bugs as Rawhide. If the bug you are seeing still exists, please reopen this report and mark it as Reopened.