> > is it possible that it reordered your changes? changing boot order is > supposed to be done by editing the scripts in question -- there is a > comment at the top which a program called chkconfig or something reads. > There should be a skel file lying around with the meanings of each of > the numbers. After you edit it you need to run chkconfig again to tell > it about the changes (you need to specify some flags).
I was following the advice given in some Redhat documentation on the order in which things get started: http://www.redhat.com/support/resources/tips/Boot-Process-Tips > Don't know if that's the problem or not, but it is the "right" way to do > it so probably worth chasing up. > > was there anything listed in the logs about failed pcmcia startup or > something? Just the failed eth0 initialisation, saying that it would come back to it later. The annoying (and difficult) problem is that usually it does seem to get started, but about 20% of the time it doesn't happen. I haven't been able to find anything in the logs that distinguishes between a good start and a bad one. > > If you want a cheap, quick hack, you could put the appropriate lines to > get your pcmcia stuff running in the network startup script. Try > everything else first though - that's gotta break something else :) Worst hack of all seems to work. In rc.local I put in ifconfig eth0 down ifconfig eth0 up dhclient & Awful, I guess, but it does seem to work. Thanks to everyone on this, and please keep me in mind if you run across any answers. Cheers, Alan > -- ------------------------------------------------------ Alan L Tyree [EMAIL PROTECTED] http://www.law.usyd.edu.au/~alant Tel: +61 2 4782 2670 Mobile: +61 405 084 990 Fax: +61 2 4782 7092 -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
