Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 3 May 2020 20:35:42 -0400
From:      Eric McCorkle <eric@metricspace.net>
To:        Austin Shafer <amshafe2@ncsu.edu>, freebsd-hackers@freebsd.org, multimedia@FreeBSD.org, "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org>
Subject:   Re: Working on Zoom port
Message-ID:  <66ed62a7-7417-a6ca-ff01-045dc837d41d@metricspace.net>
In-Reply-To: <m2d07kilx7.fsf@triplebuff.com>
References:  <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> <cfd68f02-c84c-0af6-2d8e-a9f4661de04a@nomadlogic.org> <a1353679c97b39acdd8d32d79efb6d79@waitman.net> <76793d13-c7df-c607-6751-19bf02fde4b8@metricspace.net> <df007ac7-5e81-1589-71fd-65c110faed40@metricspace.net> <5d92730b-dad0-974d-f99e-894dcc17af40@metricspace.net> <m2ftcgimuh.fsf@triplebuff.com> <59438393-6608-1afb-7fcd-dbce5a7503f7@metricspace.net> <m2d07kilx7.fsf@triplebuff.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--dEQUCOMvssHU89fHhmQjp3UMrmtwAI5x6
Content-Type: multipart/mixed; boundary="36XMZy87cA0aOKi5GI76P1EJKL1a8tzRF";
 protected-headers="v1"
From: Eric McCorkle <eric@metricspace.net>
To: Austin Shafer <amshafe2@ncsu.edu>, freebsd-hackers@freebsd.org,
 multimedia@FreeBSD.org, "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org>
Message-ID: <66ed62a7-7417-a6ca-ff01-045dc837d41d@metricspace.net>
Subject: Re: Working on Zoom port
References: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net>
 <cfd68f02-c84c-0af6-2d8e-a9f4661de04a@nomadlogic.org>
 <a1353679c97b39acdd8d32d79efb6d79@waitman.net>
 <76793d13-c7df-c607-6751-19bf02fde4b8@metricspace.net>
 <df007ac7-5e81-1589-71fd-65c110faed40@metricspace.net>
 <5d92730b-dad0-974d-f99e-894dcc17af40@metricspace.net>
 <m2ftcgimuh.fsf@triplebuff.com>
 <59438393-6608-1afb-7fcd-dbce5a7503f7@metricspace.net>
 <m2d07kilx7.fsf@triplebuff.com>
In-Reply-To: <m2d07kilx7.fsf@triplebuff.com>

--36XMZy87cA0aOKi5GI76P1EJKL1a8tzRF
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 5/3/20 8:27 PM, Austin Shafer wrote:
> Eric McCorkle <eric@metricspace.net> writes:
>=20
>> On 5/3/20 8:07 PM, Austin Shafer wrote:
>>>> linux: pid 3906 (QDBusConnection): syscall inotify_init1 not impleme=
nted
>>>> linux: pid 3906 (QDBusConnection): syscall inotify_init not implemen=
ted
>>>> linux: pid 3919 (QDBusConnection): syscall inotify_init1 not impleme=
nted
>>>> linux: pid 3919 (QDBusConnection): syscall inotify_init not implemen=
ted
>>>> linux: pid 3906 (vcdn_thread): syscall inotify_init not implemented
>>>
>>> A while back I tried to map linux's inotify to kqueue in the linuxlat=
or
>>> to solve this problem for steam. It was not very successful. Although=
 it
>>> could handle monitoring single files, it could not do directories whi=
ch
>>> 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
>=20
> Either way, something is trying to use inotify which the linuxlator doe=
s not
> support.
>=20

Guess I'm dead in the water, then.  Oh well, it was worth a shot.


--36XMZy87cA0aOKi5GI76P1EJKL1a8tzRF--

--dEQUCOMvssHU89fHhmQjp3UMrmtwAI5x6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQ9+4mhuzHQx7ikjAs846Nm3BBWrAUCXq9jXgAKCRA846Nm3BBW
rJkpAQCGiEjLUMlJ2F2Rigsii33Cc4ZUJtkOD8iWy1gVZKPengEA0kEc5UaEEzPk
KlabuWmszt8QmUsWTdB8hi0EY98RAgU=
=AdbV
-----END PGP SIGNATURE-----

--dEQUCOMvssHU89fHhmQjp3UMrmtwAI5x6--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?66ed62a7-7417-a6ca-ff01-045dc837d41d>