On Mon, 2008-12-01 at 12:03 -1000, David Cantrell wrote: > Load the SCSI modules earlier for CD/DVD installs on s390. Also, > always set up the network interface because you still need that > to ssh in and run loader. There's nothing that seems out of place here in a quick look given the surrounding aspect of linuxrc.s390. Has it been tested in the context of something more rawhide-ish? Things like insmod instead of modprobe jump out at me as potentially problematic. I'm going to have to say I have no clue where the Fedora on s390 efforts stand these days. But taking a step back to some more general thoughts on linuxrc.s390, is there an effort to actually get it using the same things we use everywhere else? There's a lot of manual module probing instead of letting things be done by udev and then manual network configuration instead of using NetworkManager. As we've moved more of these bits to be common, we really probably need to sit down and rework the entire way that the script works. The goal of it is that it takes the place of loader/init.c with a few notable and important differences * Prompting for information on things like network setup if you don't set it in the parm file. This pretty much has to be "custom" for s390 and doing it with shell is as easy as anything else * Getting modules loaded. We don't do this until in the loader on other arches, but we need to do it to get the network up. But we really probably want to let udev do it as much as we can * Starting the network. Which we do with spawning NetworkManager in the "normal" case Jeremy _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
