PCMCIA services start too late on laptops. This breaks a number of
networking services, including ypbind (which is what my specific complaint
is about) and others.
I've seen the other bug reports which you guys marked as not a bug or won't
fix, but that's just preposterous. Surely with the number of complaints
you've received about this, you must realize that this is a real bug that
requires real attention.
In the case where you are pointing ypbind at a specific server (i.e.
because that's all you have and it's not on the same subnet), ypbind fails
to bind. Period.
After the system is finished booting, you can restart ypbind manually, and
things will begin to work properly, but this is clearly not an acceptable
solution, as it requires manual intervention from a user, and because it
lengthens the boot process exponentially as yp lookups fail.
From a purely philisophical standpoint, does it make sense to ANYONE that
you start a bunch of network services while you KNOW that the network cards
aren't all configured? It doesn't make any sense to me.
Assigning to kernel (that's where the pcmcia-cs package is.)
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/