anaconda-devel-list-bounces@xxxxxxxxxx wrote on 05/26/2004 11:31:12 AM: > On Wed, 2004-05-26 at 10:20 -0400, James_Martin@xxxxxxxxxxxxxxx wrote: > There are significant space considerations that make this difficult (you > have to have sshd which then requires a whole pile of stuff like SSL, > glibc, PAM, kerberos) and that seriously bloats the memory requirements > since those have to be in the initrd. The telnet implementation is dirt > simple and completely contained within the loader and thus doesn't have > any of those problems. Hmm... I thought this sort of thing could be stuffed into the stage2.img, not the initrd. But still I can see how memory would be a problem. > > Also, could you please give another look at : > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119328 > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119329 > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119331 > > > > They have to do with re-probing hardware after %pre (as to set up some > > hardware raid devices in %pre) and > > Drives shouldn't get probed until after %pre, otherwise you wouldn't be > able to partition in %pre and use those partitions in the ks.cfg. Are > you sure you're not just hitting the dialog from the loader about the > lack of hard drives? If you're hitting that, then I just committed > something so that it won't pop up in kickstart. > I'll have to check that new code out... > > having anaconda prompt for network > > information during kickstart even if you are doing a CD install. > > This exists, put network --query in your ks.cfg Could've sworn I've tried that before.. I take it that didn't make it in RHEL3QU2? > > Cheers, > > Jeremy > > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list
