Date: Wed, 30 Dec 2020 23:56:24 +0100 From: Daniel Ebdrup Jensen <debdrup@FreeBSD.org> To: freebsd-hackers@freebsd.org Subject: Re: Project information - SMBv2+ Message-ID: <20201230225624.atsnf6u5mmtcu5sw@nerd-thinkpad.local> In-Reply-To: <704a700c-32ff-66eb-6711-5d75099abcd4@quip.cz> References: <16e5725b-ec2f-3222-d20d-fd15e597c12c@gmx.net> <dea01842-79e7-33ed-4302-28f2df51d710@quip.cz> <075f31cb-dd13-778d-ed50-3ec7d6f30731@gmx.net> <704a700c-32ff-66eb-6711-5d75099abcd4@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
--x6ccdfbtybphjisq Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 30, 2020 at 10:16:44PM +0100, Miroslav Lachman wrote: >On 30/12/2020 20:24, CerebrosuS wrote: >> >> >>Am 30.12.20 um 20:05 schrieb Miroslav Lachman: >>>On 30/12/2020 18:57, CerebrosuS wrote: >>>>Hello at all, >>>> >>>>the community and developer at FreeBSD seem to know, that SMBv1 for >>>>clients is nearly over and that the included mount_smbfs doesn't support >>>>newer versions. So good, so far... >>>> >>>>So I can find multiple information about the situation, but no clear >>>>path on how FreeBSD community and developer will go on to solve this >>>>missing function. (Just got the information on: >>>>https://wiki.freebsd.org/MateuszPiotrowski/AccessingSmbSharesWithSambaC= lient) >>>> >>>> >>>> >>>>This is what I am asking: >>>>- Is there a project existing for solving this problem (with whatever >>>>target)? >>>>- What is the way to go in future? Extend mount_smbfs or support the >>>>fuse-smbnetfs part to be stable and fast like mount_smbfs (buggy and >>>>laggy here)? >>>>- Who is mainly working on it, if a project already exist? >>>> >>>>I'am just interested, cause of not finding such information clearly. Is >>>>there maybe a general project management list / team to see what >>>>projects are going on in whatever state? >>>> >>>>I am a hobby developer mainly coming from chemical engineering side, >>>>having some time to help. I've already written some cross platform >>>>software but never related to network or on os-level. So I am motivated >>>>to invest some time in getting stuff into FreeBSD, but for me, there is >>>>a lack on information (see above). >>>> >>>>Thank you in advance for information and help. >>> >>>I was involved in the thread linked by Gleb. AFAIK nothing changed from >>>that time. I tried something from ports but it has more problems (shares >>>cannot be mounted on boot like mount_smbfs does). >>>If somebody has time and skills to try to bring SMBv2 or v3 to FreeBSD >>>then Apple or Solaris sources is good start. The both were using the >>>same mount_smbfs (v1) as FreeBSD so one can check their sources and see >>>how they evolve to v2 / v3. >> >>They are both using exactly the same source code as a starting point and >>extend it (or rewrite it) to SMBv2? > >They are based on the ported code. Apple Mac OS X and Solaris have=20 >different kernel so they needed modified port of the same code as was=20 >in FreeBSD back in the days (there is the same copyright header).=20 >Apple sources or Solaris sources cannot be used directly on FreeBSD=20 >but some skilled developer can look in to those sources to see their=20 >evolution. But as was already noted v2 and v3 are very different from=20 >v1. It will be hard to port but not impossible. >Current solutions in ports (fusefs) are almost useless in server=20 >environment. > >Miroslav Lachman > >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" Hi folks, Assuming that the reasons for not using fuse in a server environment are re= lated=20 primarily to performance and that the implementation that was in base used = to be=20 quite out-of-date, has this at all been reevalulated since a new version wa= s=20 merged? [1] Yours, Daniel Ebdrup Jensen [1]: https://svnweb.freebsd.org/changeset/base/350665 --x6ccdfbtybphjisq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAABCgB9FiEEDonNJPbg/JLIMoS6Ps5hSHzN87oFAl/tBZhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDBF ODlDRDI0RjZFMEZDOTJDODMyODRCQTNFQ0U2MTQ4N0NDREYzQkEACgkQPs5hSHzN 87oJLgf+PmTDrmRy0kGZLj3BQ8Kvg3QjSt7GY4FetyPW4t00u4KZ4G910lVC2Wnr L4/7VrLh1UwoHYPjeIDRZbR6A9uqBhhL2Fljjh0XzJGrt6WkQMgRZXyBXWa0XvyJ RsUSCaax33oZGGE/NjBm9yuXqCYNyK6hpVSH/bbjMlykaiNmqvSOeqOkLH/YmzxR 6jNhz6PcnkkvPPdwJ50mTw3pfBDdD4gyU2Dgk2/cHwG/fv8lPaGJQd5xSsjYiOvh p6P6a1nBnRSOfnkgMLIHjElo77Y66Ua6Zfd1WBVEyY+6EXDPmbI2cj7QyVt0YFJO erfpt7OIpjHG89Ty4wI8nmoHfOGpUw== =UrDw -----END PGP SIGNATURE----- --x6ccdfbtybphjisq--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201230225624.atsnf6u5mmtcu5sw>