Randy McMurchy wrote: > Hi all, > > I've committed the first pass at getting D-BUS into BLFS. I would > sure appreciate it if you folks that have experience using D-BUS > would look over the instructions for mistakes. I do not claim to > be an expert on D-BUS. > > These issues are specifically where I may have made mistakes: > > 1. I say that you must have the System V IPC parameter in the General > Setup section of the kernel configuration enabled. > > 2. I'm not sure if I need both X and GTK+-2 as dependencies. The > configuration looks for X independently from GTK so I'm not sure. > > 3. There are quite a few dependencies listed that are strictly > for building the bindings to the various packages listed. Should > perhaps these be moved to a separate dependency section named > "Optional (for building API bindings)"? > > 4. I don't list any configuration tasks. The only thing mentioned > is that you shouldn't touch the installed files, and instead create > 'local' files if you need to modify the default configuration. > > 5. D-BUS operates as such: A system daemon is started at boot-time. > I've got the bootscript for this. Then, the documentation says that > users should start their session daemon through login scripts. But > I'm not sure this is necessary as it may be that GNOME (or whatever > application) will do this. So, I'm asking if the book should > provide instructions to start the session daemon in user login > scripts. > > 6. The bootscript is started in run-levels 2, 3, 4 and 5. Because > D-BUS is mainly designed for same-machine event messaging, I feel > that it is not dependent on networking. Does this sound right? > > Thanks in advance to anyone who can provide information about the > stuff mentioned above. > Looks good to me. I've just installed it. I was more or less waiting for this app to be added to BLFS.
First at 6. : the links in the runlevel 2,3,4 and 5 the name of the link is not right. It's cyrus-sasl, which is wrong obvious. The comment at the introduction is good, but maybe some more things can be said about the reason why dbus is needed. I do not understand it enough to know why. Can you compare this library and daemon with fam? If something in the hardware changes this is communicated to all other applications, and udev and hotplug do not do this. Futher, the dbus-viewer does not work. It exits with the message: "Could not open bus connection: Unable to determine the address of the message bus". I start the dbus-viewer as an ordinary user. Stef Bon -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
