Re: Working on Zoom port
Eric McCorkle <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.x11,gmane.os.freebsd.devel.hackers |
|---|---|
| Message-ID | <[email protected]> |
On 5/3/20 8:27 PM, Austin Shafer wrote: > Eric McCorkle <[email protected]> writes: > >> On 5/3/20 8:07 PM, Austin Shafer wrote: >>>> linux: pid 3906 (QDBusConnection): syscall inotify_init1 not implemented >>>> linux: pid 3906 (QDBusConnection): syscall inotify_init not implemented >>>> linux: pid 3919 (QDBusConnection): syscall inotify_init1 not implemented >>>> linux: pid 3919 (QDBusConnection): syscall inotify_init not implemented >>>> linux: pid 3906 (vcdn_thread): syscall inotify_init not implemented >>> >>> A while back I tried to map linux's inotify to kqueue in the linuxlator >>> to solve this problem for steam. It was not very successful. Although it >>> could handle monitoring single files, it could not do directories which >>> is how most people seem to use inotify. I wonder why zoom needs this? >>> >>> Unfortunately I can't seem to find the patches. If I do I'll let >>> you know. >>> >> >> Those are syslog messages. The corresponding application log messages >> look like it's trying to talk through a socket, probably to DBus > > Either way, something is trying to use inotify which the linuxlator does not > support. > Guess I'm dead in the water, then. Oh well, it was worth a shot.
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQ9+4mhuzHQx7ikjAs846Nm3BBWrAUCXq9jXgAKCRA846Nm3BBW rJkpAQCGiEjLUMlJ2F2Rigsii33Cc4ZUJtkOD8iWy1gVZKPengEA0kEc5UaEEzPk KlabuWmszt8QmUsWTdB8hi0EY98RAgU= =AdbV -----END PGP SIGNATURE-----