On 18/01/2006 9:56 a.m., Rahul Sundaram wrote:
Hi
Daniel, thanks for the explanation. I was not trying to lay the blame
the selinux team (or anyone else). Like you wrote, the responsibility
for the current situation is collective. I was only pointing out that
with all the Fedora component roadmap interactions the current devel
is pretty instable. Which is a bit frightening given we already have
two test releases behind us and the next one is scheduled soonish.
Thats a understandable concern. One way to mitigate this problem is
getting all those bug reports filed and if the responses are not
forthcoming post a list of the bug reports to the list to get them more
attention if they are considered as major blockers.
I think this bug is worthy of some discussion:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=104058
and
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176522
(which are arguably duplicates anyway)
It relates to dbus being started late on in the bootup cycle, which causes
problems because bluetooth needs dbus yet bluetooth is started very early on in
the boot.
Without it being fixed we are going into FC5 with a situation where bluetooth
mice and keyboards will not work out of the box... :(
Reuben
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
