<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> First of all, thanks for responding, I was pretty sure that the issue had fallen into the void. It doesn't *really* matter to me, as I've fixed it in my source code, but I know that it's bitten other people, as it was originally brought to my attention in the centos IRC channel. That's what I thought at first, because my test platform uses kickstart and updates over http, so I figured that it was just as you suspected, but I tried it with both the kickstart burned onto CD, and the ks=floppy boot method, and both times, it failed to configure the network. There's one scenario left that I haven't tested, which is to boot up on a network without a DHCP server (I haven't tested it for a couple of reasons[1]), and see if it asks for a network configuration. However based on my reading of the anaconda code; the fact that kickstart.py *always* calls dispatch.skipStep("network"), and the commit message from a commit that was subsequently retracted in the anaconda git repo[2], I'm sure that, no matter what I do, if kickstart is invoked, it will not ask me to configure the network. I guess I have to open up an enhancement request on Fedora to get this fixed to behave as I think it should... 1. I'd have to set up a virtual network on a private LAN, which would take too much time for a test that I know would fail, and it's kinda beside the point, just because the use case I'm envisioning separates install-time network configuration from permanent network config 2. <tt><a class="moz-txt-link-freetext" href="http://preview.tinyurl.com/dyv7y9">http://preview.tinyurl.com/dyv7y9</a> and the commit message states: </tt> <blockquote><tt>This patch adds support for a new network bootproto. The point of this is</tt> <tt>to work around our basic assumption that no network line in the kickstart</tt> <tt>file means you get dhcp. Some environments may want the assumption that</tt> <tt>no network line means you get prompted for network configuration. That's</tt> <tt>what this patch adds.</tt> </blockquote> <tt>and the commit is reverted two weeks later. After reading the bug referenced the commit msg, I kinda understand what happened. (It's a confusing bug). </tt> Jeroen van Meeuwen wrote: <blockquote cite="mid:49D0B42E.9080005@kanarip.com" type="cite"> <pre wrap="">On 03/25/2009 08:37 PM, Matt Rose wrote: </pre> <blockquote type="cite"> <pre wrap="">Mind you, I'm not sure whether my expectations are correct. The patch I attached "fixes" this behaviour so that the network configuration dialog is brought up, if there is no "network" option in the ks.cfg </pre> </blockquote> <pre wrap=""> Has your network been preconfigured in any way? I'm thinking ksdevice=, ip= (and friends) on the cmdline or something. In those cases, a kickstart that does not have a "network" line should not bring up the network configuration dialog. Kind regards, Jeroen van Meeuwen -kanarip _______________________________________________ Kickstart-list mailing list <a class="moz-txt-link-abbreviated" href="mailto:Kickstart-list@redhat.com">Kickstart-list@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/kickstart-list">https://www.redhat.com/mailman/listinfo/kickstart-list</a> </pre> </blockquote> </body> </html>