Date: Thu, 31 Dec 2020 16:42:04 +0100 From: CerebrosuS <CerebrosuS@gmx.net> To: freebsd-hackers@freebsd.org Subject: Re: Project information - SMBv2+ Message-ID: <8edb2ee8-0643-f3f4-ef5a-bdd9bd8a1b9a@gmx.net> In-Reply-To: <8758d2d0-12e9-77bb-e417-4bac430b4e9a@gmx.net> References: <16e5725b-ec2f-3222-d20d-fd15e597c12c@gmx.net> <dea01842-79e7-33ed-4302-28f2df51d710@quip.cz> <075f31cb-dd13-778d-ed50-3ec7d6f30731@gmx.net> <20201230203416.xr42tsdo2m7txex7@nerd-thinkpad.local> <8758d2d0-12e9-77bb-e417-4bac430b4e9a@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
So I am found the main protocol spec existing in freebsd-src/sys/netsmb and got the corresponding implementation from apple. As I've never developed on FreeBSD, I am searching for a good workflow to test builds. Right now I've build freebsd-src from git. As far as I understand netsmb in sys is not a module build into the kernel? Therefore I have to update kernel and install it in a test environment for debugging. I don't want to polute my main system and read about using bhyve as a vm system for testing. Is this the only way or is there a smarter way getting debugging done to test my implementation. I've never developed things on kernel-level so I got a prog-debug cycle with high frequency for now. (As you can see, I am starting from the beginning related to FreeBSD development. Sry for that.) Am 30.12.20 um 21:44 schrieb CerebrosuS: > Yes, the video is part of the wiki.freebsd.org entry I've written down. > > The information in the video is a little bit unmotivated and I am aware > that it is not that simple. That video leads me to the question here, if > anyone is working on it. Cause Mr. Gibbs talks about it like he already > started something in this direction and is already into it (or he just > knows). :-) > > Yet, I will start by looking into the FreeBSD mount_smbfs code and the > one from apple. > > Am 30.12.20 um 21:34 schrieb Daniel Ebdrup Jensen: >> On Wed, Dec 30, 2020 at 08:24:31PM +0100, 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/AccessingSmbSharesWithSam= baClient) >>>>> >>>>> >>>>> >>>>> >>>>> This is what I am asking: >>>>> - Is there a project existing for solving this problem (with whateve= r >>>>> 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 fr= om >>>> 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 FreeBS= D >>>> 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 s= ee >>>> how they evolve to v2 / v3. >>> >>> They are both using exactly the same source code as a starting point a= nd >>> extend it (or rewrite it) to SMBv2? >>> >>>> But it is out of my skill. I am not >>>> developer. I am just an extensive user of SMB mounted shares from >>>> Windows servers. >>> That might also be my problem, cause I've never written an application >>> for network nor anything related to FreeBSD on os-level. But if no one >>> starts, nothing might change at all. >>> >>>> >>>> Kind regards >>>> 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, >> >> Justin T Gibbs, during one of the Office Hours meetings that have been >> happening throughout the year, spoke at some length on the subject of >> SMBv3 as it relates to integraetion in the base system [1] - and suffic= e >> it to say, it's not nearly as simple as some people seem to asume that >> it is. >> >> I hope that's somewhat helpful, and it's at least a little newer than >> what's referenced elsewhere. >> >> [1]: https://www.youtube.com/watch?v=3DJi4ux4FWpRU&t=3D970 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.or= g"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8edb2ee8-0643-f3f4-ef5a-bdd9bd8a1b9a>