From owner-freebsd-fs@freebsd.org Sun Jan 3 21:47:33 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D20B4A60FCE for ; Sun, 3 Jan 2016 21:47:33 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA8851A1B for ; Sun, 3 Jan 2016 21:47:33 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 47E8220400 for ; Sun, 3 Jan 2016 16:47:32 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Sun, 03 Jan 2016 16:47:32 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=OVNlGRiFSbzvsHI qDVbTXkmn1V0=; b=ayInsFH8bsN1ZU0zqs+LS1LzUoipXbwaVCeg1mu46bQHHoj xhRL5tqsyZwlyOmAs9VuQWnwwbCufcC/q2tXs8A+81xV8pXOUhcIZ0zKfxzslDcw WUlUB1Thks99TUS953v4szOabrCRg3ZVKAjQfHgfdzf52tG3qiMrh/LOEcL4= Received: by web3.nyi.internal (Postfix, from userid 99) id 1C4C2105F46; Sun, 3 Jan 2016 16:47:32 -0500 (EST) Message-Id: <1451857652.3746528.481792578.0312DB48@webmail.messagingengine.com> X-Sasl-Enc: CnYoSefStSy0gwfY6mN9ySVQSAE5dEbPJRml0WfihlDR 1451857652 From: Mark Felder To: Jordan Hubbard Cc: Chris Stankevitz , FreeBSD Filesystems MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-42cc5299 Subject: Re: Monitoring FS changes Date: Sun, 03 Jan 2016 15:47:32 -0600 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> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 21:47:33 -0000 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