Hmm, let me ask this another way.
What part of the code reads the kickstart file and parses it? I am digging thru the source now, but I am not finding it.
I basically want to see how the code parses the kickstart file and find out why it is only processing a single device line.
On Fri, 29 Apr 2005, Ronald Reed wrote:
Hmm, let me ask this another way.
What part of the code reads the kickstart file and parses it? I am digging thru the source now, but I am not finding it.
I basically want to see how the code parses the kickstart file and find out why it is only processing a single device line.
See kickstart.py at the toplevel directory of anaconda sources :)
- Panu -
Ok. I now see where the kickstart file is read and parsed, but if I am reading this code correctly, the device parameter does not have a handler. I have never programmed in python before, so I may be missing something. I am looking for how the device line in a kickstart file is handled. Because right now, only the very first one is parsed, and I need it to parse more than that.
Ron
On Sat, 2005-04-30 at 06:55, Panu Matilainen wrote:
On Fri, 29 Apr 2005, Ronald Reed wrote:
Hmm, let me ask this another way.
What part of the code reads the kickstart file and parses it? I am digging thru the source now, but I am not finding it.
I basically want to see how the code parses the kickstart file and find out why it is only processing a single device line.
See kickstart.py at the toplevel directory of anaconda sources :)
- Panu -
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
Is the dispatch.py code the main section? I assume that the program follows the installSteps in order?
I still have not found which part of the code uses the device parameter. Thanks to Panu Matilainen, I found the part that reads the kickstart file, but the kickstart.py file does nothing with the device parameter.
Ron
On Mon, 2005-05-02 at 09:02, Ronald Reed wrote:
Ok. I now see where the kickstart file is read and parsed, but if I am reading this code correctly, the device parameter does not have a handler. I have never programmed in python before, so I may be missing something. I am looking for how the device line in a kickstart file is handled. Because right now, only the very first one is parsed, and I need it to parse more than that.
Ron
On Sat, 2005-04-30 at 06:55, Panu Matilainen wrote:
On Fri, 29 Apr 2005, Ronald Reed wrote:
Hmm, let me ask this another way.
What part of the code reads the kickstart file and parses it? I am digging thru the source now, but I am not finding it.
I basically want to see how the code parses the kickstart file and find out why it is only processing a single device line.
See kickstart.py at the toplevel directory of anaconda sources :)
- Panu -
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
On Tue, 2005-05-03 at 09:08 -0500, Ronald Reed wrote:
Is the dispatch.py code the main section? I assume that the program follows the installSteps in order?
Yup, installSteps is the order in which the dispatcher follows things once anaconda really starts. However...
I still have not found which part of the code uses the device parameter. Thanks to Panu Matilainen, I found the part that reads the kickstart file, but the kickstart.py file does nothing with the device parameter.
... part of the kickstart file is handled by the loader - it has to, in order to find the rest of anaconda :) So what really handles the device parameter is loader2/kickstart.c and thereabouts.
- Panu -
I am getting a handle on this slowly, thanks Panu. What I am trying to figure out is why anaconda only reads the first device line in a kickstart file and ignores the rest.
Should multiple device lines work? Or should all the needed modules be put on a single line?
Ron
On Tue, 2005-05-03 at 10:50, Panu Matilainen wrote:
On Tue, 2005-05-03 at 09:08 -0500, Ronald Reed wrote:
Is the dispatch.py code the main section? I assume that the program follows the installSteps in order?
Yup, installSteps is the order in which the dispatcher follows things once anaconda really starts. However...
I still have not found which part of the code uses the device parameter. Thanks to Panu Matilainen, I found the part that reads the kickstart file, but the kickstart.py file does nothing with the device parameter.
... part of the kickstart file is handled by the loader - it has to, in order to find the rest of anaconda :) So what really handles the device parameter is loader2/kickstart.c and thereabouts.
- Panu -
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
anaconda-devel@lists.stg.fedoraproject.org