On some wireless hardware I have experienced that Avahi running FC12, by default, sometimes blocks the boot, following dmesg, apparently because the wireless driver is slow on wake up. Is possible Avahi starting on a non-block mode and try later to check the connections again?
The problem was on a Atheros wireless card, ath5k.
Thank you, best regards.
2010/4/15 "Jóhann B. Guðmundsson" johannbg@hi.is:
On 04/14/2010 12:43 PM, Bastien Nocera wrote:
On Wed, 2010-04-14 at 06:24 +0000, "Jóhann B. Guðmundsson" wrote:
I personally dont think that avahi should be run by default until bug 534076 gets fixed
Just my 2 cents..
How does it stop avahi from working apart from your particular use?
I personally don't use avahi and the first thing I do is turn of the avahi-daemon after each installation however we have implemented dns-sd wide-area here at the university and students running Fedora wont be able to take advantage of it ( while os-x users can ) and that is what I consider bad desktop experience since the end user needs open up a terminals and start editing files if he wants to get it to work.
I don't see it as a blocker for adding Avahi to the default installation.
It certainly is not a blocker if avahi ( or any other application ) works "out of the box" for the end user.
If it does not then the end uses might just as well install the application himself ( As opposed for it being installed by default for him ) then turn the knobs to get it to work.
JBG