Date: Fri, 23 Jun 2017 12:10:05 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Stefan Esser <se@freebsd.org>, "theunusualmatt@gmail.com" <theunusualmatt@gmail.com> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: SMBv1 Deprecation Message-ID: <YTXPR01MB0189251BCE0A17B8D0C51514DDD80@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <45b0864b-680c-8fe0-f5a5-353b6373d069@freebsd.org> References: <CALJ5sFkKMGvhgRYzegikDTiTTyV1xtA_WYJW_gLkHFN9Oh0OqA@mail.gmail.com> <YTXPR01MB01893E3AAB21A03677998D2FDDDB0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> <CALJ5sFnMWGAGS8oyUvzXfq_Z4ZeRzgs==EDZf%2BqO-4O269qdiw@mail.gmail.com> <9b556cbe-f9f3-ab15-6fcd-71397d18c126@freebsd.org> <20170623104654.07e5a3e0@ernst.home>, <45b0864b-680c-8fe0-f5a5-353b6373d069@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Stefan Esser <se@freebsd.org> wrote: [lots of stuff snipped] > You may want to have a look at FuseSMB, which might be easier to port to > FreeBSD than teaching smbfs newer SMB protocols. Yes, if there is a fuse module, that shouldn't be too hard to get working. If there is something missing in the FreeBSD fuse interface it needs, I mig= ht be able to help with that, since I have done a few fuse patches (for the ke= rnel interface that uses the module, not the module itself). > Windows servers (at least 2012 and 2016) support NFS upto version 4.1, > and if you can configure the servers to provide NFS access to the > relevant data, that might be the easiest route for you. I've never tested the FreeBSD NFSv4.1 client against a Windows server (to be honest, I didn't know they supported one until now;-), but I might be able to help if go this route and have problems with the mounts. Good luck with it, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTXPR01MB0189251BCE0A17B8D0C51514DDD80>