Re: Deprecating smbfs(5) and removing it before FreeBSD 14
On 05/06/2024 01:05, John Hixson wrote: Thank you for the message. I'm glad someone has the courage to take the plunge. Smbfs is still very important to me. In a heterogeneous environment it is still the most common way to share data between systems. Are you planning the final version as a kernel module, or will the final version be via FUSE? I have had bad experiences with FUSE in the past with stability and performance. The final version will be a kernel module. It will also be BSD licensed. I am not an expert at the VFS layer so I want to get the stack ironed out in FUSE before moving it into kernel space. This is really good news. I can't help with the code, but once you get something I can test, let me know. I'd be happy to help with testing. Best regards Miroslav Lachman
Re: Deprecating smbfs(5) and removing it before FreeBSD 14
On Wed, Jun 5, 2024 at 12:52 AM John Hixson wrote: > > I am working on a from scratch implementation of smbfs. I do not have > any kind of time estimate since it is in my spare time. I chose this > route after spending considerable time looking at Apple and Solaris > implementations and wanting something without all of the legacy 1.0 > crap. I do have a very minimal working FUSE version at this point, but > there is much to do, and even more to abide by the various > specifications. > > I just thought I'd share in case anyone is interested. > > - John Thanks for sharing. We're building a FreeBSD based product and SMB2/3 support is very important to us. Maybe we can combine our efforts on this matter? I also contacted the FreeBSD Enterprise Working Group about this. The Greg's reply was > The verbal offer to donate an up to date fork of this still stands, but the > timing remains unclear. I continue asking. It is still unclear to me if the code is already written by some party and now the negotiation is going on about licensing it as BSD.
Re: 41dfea24eec panics during ata attach on ESXi VM
On 6/5/24 4:35 AM, Yuri Pankov wrote:
After updating to 41dfea24eec (GENERIC-NODEBUG), ESXi VM started to
panic while attaching atapci children. I was unable to grab original
boot panic data ("keyboard" dead), but was able to boot with
hint.ata.0.disabled=1, hint.ata.1.disabled=1, and `devctl enable ata0`
reproduced the issue:
ata0: at channel 0 on atapci0
This should be fixed now by commit 56b822a17cde5940909633c50623d463191a7852.
Sorry for the breakage.
--
John Baldwin
