Jason Tackaberry wrote: > On Sun, 2006-10-15 at 18:37 +0200, Reinoud Elhorst wrote: >> The first problems were with inotify. Earlier I had recompiled glibc >> after upgrading to the 2.6.16 kernel to get rid of the message on >> inotify when installing kaa (as I understand, beacon will work without >> inotify, but I wanted inotify in). Beacon would compain however on not >> being able to find the inotify_init function. > > You shouldn't have needed to upgrade glibc. If your kernel supports > inotify but your glibc doesn't, the inotify stuff in kaa will fall back > to an internal wrapper. When you build kaa.base with a kernel that > supports inotify but a glibc that doesn't, you should see this message: > > inotify not supported in glibc; using built-in support instead. > > This isn't an error, just a notice. > > Beacon complaining about not being able to find inotify_init sounds like > a bug. Was it a python exception? Or a linker problem?
I guess it was the same bug I had. It was a newer glibc with inotify
support compiled against kernel header without. That does not work and
he needs to recompile glibc.
>
>
>> The next problem was the unpickle error discussed before. I was using
>> sqlite 3.3.5-r1 and pysqlite 2.3.1. Upgrading to sqlite 3.3.6 solved the
>> problem (which seems to contradict the conclusion reached before that it
>> was a bug in the pysqlite library). Interestingly, I just decided to
>> downgrade to 3.3.5-r1 again, and the error doesn't re-appear now (even
>> after deleting the ~/.beacon dir). Could this possibly be connected to
>> using newer linux-headers or a newer glibc too?
>
> Interesting speculation, and I think a very sensible one given what
> you've experienced. I've asked the last person to report this issue
> what glibc version they're using.
>
> Though this isn't quite consistent with what dischi experienced. He had
> the problem, updated either sqlite or pysqlite2 (but not glibc) and the
> problem went away.
Maybe my old sqlite was against an ever older glibc? I don't
know. That bug is very strange.
>> Next, it complained about connecting to the dbus. Starting the dbus
>> deamon (/etc/init.d/dbus) fixed this, however now it's complaining about
>> not being able to find org.freedesktop.Hal in any .services file.
>> Emerging hal and hal-device-manager and (re)starting the hal and dbus
>> daemons took care of this problem (I could imagine dbus and hal only
>> being used to notice a new cd/dvd being inserted, so beacon might run
>> without it, I just don't want to risk any cascading error from this).
>
> I think beacon will resort to polling to see if media has been inserted
> in the absence of hal. dischi?
Yes. Without hal beacon polls rom drives. With hal, beacon also
detects usb sticks.
>> The updated doc should, after being approved, also be merged into the wiki.
>
> Thanks. dischi, please review. :)
Will do.
Dischi
--
What happens if a big asteroid hits the Earth? Judging from realistic
simulations involving a sledge hammer and a common laboratory frog, we
can assume it will be pretty bad.
-- Dave Barry
pgpylRLsDJ4fb.pgp
Description: PGP signature
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
