Date: Sat, 9 May 2020 23:17:59 +0200 From: Mateusz Guzik <mjguzik@gmail.com> To: John-Mark Gurney <jmg@funkthat.com> Cc: vbox@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: patch to make vboxvfs work again Message-ID: <CAGudoHFef7JPDhtSs1750_FXbX4baHN3%2BoO=jxnfRADFfMmk2g@mail.gmail.com> In-Reply-To: <20200509203336.GN4213@funkthat.com> References: <20200509203336.GN4213@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
That will do the trick indeed. I don't know about that bcmp thingy, ideally it would be needed. I presume there is a sufficient header mess which makes this to be the easiest hack. On 5/9/20, John-Mark Gurney <jmg@funkthat.com> wrote: > Hello virtualbox maintainer(s), > > Attached is a patch to make VirtualBox vboxvfs work again. I've only > tested under -current. > > mjg, what is the correct way to make this patch work on past versions > of FreeBSD? would a simple #ifdef VFS_VOP_VECTOR_REGISTER wrapper > around the call work? > > Thanks. > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > -- Mateusz Guzik <mjguzik gmail.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGudoHFef7JPDhtSs1750_FXbX4baHN3%2BoO=jxnfRADFfMmk2g>