[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: No network selection during Kickstarted FC3RC3 build



Here is a thought!

keyboard us
firewall --enabled --port=22:tcp
selinux --enforcing
authconfig --enableshadow --enablemd5


I have this in my ks file. I wonder if the firewall and selinux entries
aren't forcing the script past the network section since I think they
are in the same section (on the same page). I will work this theory out
tomorrow.


On Fri, 2004-10-29 at 10:42, Nick wrote:
> On Fri, 2004-10-29 at 09:53, James_Martin ao uscourts gov wrote:
> > This has been an issue for awhile... I opened a bug on this awhile ago 
> > (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119331), because 
> > it's seems like it should prompt someone for network information during a 
> > CD install, especially since it prompts you for so many other things if 
> > you leave them blank. 
> 
> I saw something on a web page about "consistent" behavior. This would be
> nice.
> 
> I think this problem though, is more involved. Since I don't even
> pretend to understand Python, I wont swear to this, but I was able to
> make this work in Core 1 by commenting out the skipStep line. I compared
> the code in the Core1 release with the Core3 release and they are
> functionally the same. So it seems to me that the problem lies somewhere
> outside of kickstart.py.
> 
> Has anyone else hacked into this in the Core 3 release??
> 
> 
> > The bug was "be considered for a future release".
> > 
> > Jeremy, did this make it into FC3's anaconda?
> > 
> > 
> > James S. Martin, RHCE
> > Contractor
> > Administrative Office of the United States Courts
> > Washington, DC
> > (202) 502-2394
> > 
> > anaconda-devel-list-bounces redhat com wrote on 10/29/2004 07:18:52 AM:
> > 
> > > This is what I did in Core1 to get the network section to come up during
> > > a kickstart when there was no entry in the ks.cfg file. It doesn't work
> > > anymore. any Ideas??
> > > 
> > > 
> > > Copy stage2.img in the Core3/Fedora/base/stage2.img to /tmp mkdir
> > > /mnt/img
> > > 
> > > mount -o loop /tmp/stage2.img /mnt/img
> > > 
> > > cd /mnt/img
> > > 
> > > tar cvf /tmp/stage2.tar .
> > > 
> > > cd /tmp
> > > 
> > > mkdir stage2
> > > 
> > > cd stage2
> > > 
> > > tar xvf /tmp/stage2.tar
> > > 
> > > in the  /tmp/stage2/usr/lib/anaconda/kickstart.py
> > > 
> > > comment out the line:
> > > 
> > > dispatch.skipStep("network")
> > > 
> > > cd /tmp and umount /mnt/img
> > > 
> > > remove the stage2.tar and the current stage2.img file
> > > 
> > > 'mkcramfs stage2/ stage2.img' to generate the new stage2.img
> > > 
> > > copy the stage2.img back into the source tree
> > > CD.
> > > 
> > > 
> > > _______________________________________________
> > > Anaconda-devel-list mailing list
> > > Anaconda-devel-list redhat com
> > > https://www.redhat.com/mailman/listinfo/anaconda-devel-list
> > 
> > _______________________________________________
> > Anaconda-devel-list mailing list
> > Anaconda-devel-list redhat com
> > https://www.redhat.com/mailman/listinfo/anaconda-devel-list
> 
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list redhat com
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]