Date: Sun, 03 Jan 2016 15:47:32 -0600 From: Mark Felder <feld@FreeBSD.org> To: Jordan Hubbard <jordanhubbard@icloud.com> Cc: Chris Stankevitz <chris@stankevitz.com>, FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: Re: Monitoring FS changes Message-ID: <1451857652.3746528.481792578.0312DB48@webmail.messagingengine.com> In-Reply-To: <046580B0-BF8E-4A83-B1BB-28C632B1B9B5@icloud.com> References: <5684D810.6070700@stankevitz.com> <1451855317.3739776.481776018.64F6C4D9@webmail.messagingengine.com> <046580B0-BF8E-4A83-B1BB-28C632B1B9B5@icloud.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 3, 2016, at 15:36, Jordan Hubbard wrote: >=20 > I think we can probably all agree that Linux inotify wouldn=E2=80=99t be = worth > the trouble. From the wikipedia page: Just talk to Bryan Cantrill if you want to know why we should avoid inotify at all costs. He had to work on mapping it to FEN on SmartOS and he discovered a world of hurt in the process. They're allegedly stuck with the broken implementation of inotify now because Linus doesn't want KBI breakage. Not to say we couldn't provide a compatibility shim so inotify things can compile on FreeBSD, but it might be wise to have something else that works better. Not sure if we really should reinvent the wheel, but I have zero clue how FSEvents or FEN scale. >=20 > Assuming there=E2=80=99s interest, I could potentially see throwing some > engineering effort into this. >=20 > - Jordan >=20 I would love to see this happen in the near future. It is *the* reason Dropbox hasn't released a FreeBSD-native client last I checked. I know that Plex would use it if it was available. There's a lot of cool things ripe for porting if we only had a mechanism... --=20 Mark Felder ports-secteam member feld@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1451857652.3746528.481792578.0312DB48>