Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 4 Nov 2017 21:53:49 +0100
From:      Farid Joubbi <djfarid@gmail.com>
To:        "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net>
Cc:        freebsd-virtualization@freebsd.org
Subject:   Re: VNC and non-US keymap in bhyve
Message-ID:  <CAEN4iuaS6m6T4hiKUYG5vYHyH2YZM1G9J2U3ACoeprWYFM2dzg@mail.gmail.com>
In-Reply-To: <201711041742.vA4HgsZP001453@pdx.rh.CN85.dnsmgr.net>
References:  <CAEN4iuYjnSc5Cym-MGSCM5=LWCgizan_qQajJhagR_LeiKUC2w@mail.gmail.com> <201711041742.vA4HgsZP001453@pdx.rh.CN85.dnsmgr.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the reply!

I'm running 11.1 Release. The fix is not there yet at least.

I read the whole bug report and understood that he was involved on both
sides.
My question was a bit more general about the changes coming from FreeNAS to
FreeBSD and the other way around.

Is there a way for me to see when this particular change, or some other
change that I might be interested about in the future will be available in
FreeBSD release, stable or current?


On Sat, Nov 4, 2017 at 6:42 PM, Rodney W. Grimes <
freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote:

> > Hello,
> >
> > I use bhyve and have a problem with non-US keymap and the VNC server.
> > This is a bug that was reported at least to FreeNAS and was fixed a few
> > weeks ago according to the bug report here:
> > https://bugs.freenas.org/issues/24450
> >
> > When will this fix come into FreeBSD?
> > How does the process work for changes into FreeNAS and then into FreeBSD?
>
> For this specific instance Marcelo, the person working the bug from the
> FreeNAS side, is also a member of the FreeBSD developers group working
> on bhyve so he tends to make sure his fixes get brought over.
>
>
> > Or is it that the change was first made into FreeBSD and then from there
> > found its way into FreeNAS?
>
> I am unclear in this case, but from reading the full text of the
> bugs.freenas.org report it is clear that he is working on both
> FreeBSD and FreeNAS to resolve the issue.
>
> > I could not find this information anywhere other than that FreeNAS is
> based
> > on FreeBSD.
>
> I think if you read the bug report carefully you should find the
> following text excerpt:
> -- begin excerpt --
>
>  Updated by Marcelo Araujo 5 months ago
>
>     Priority changed from No priority to Important
>     Status changed from Unscreened to Investigation
>     Target version set to 49
>
> Hi all,
>
> It is a know issue with bhyve, I'm working to import libvncserver to
> replace the current implementation of rfb on FreeBSD. It will take a bit of
> time as I need first commit it on FreeBSD and then merge it to FreeNAS.
>
> The process to commit on FreeBSD can take a bit of time, because we have a
> review process and a merge process as well.
>
> But I will keep you guys updated about my progress.
>
> Best,
> -- end excerpt --
> -- begin excerpt --
> Updated by Marcelo Araujo about 1 month ago
>
>     Target version changed from 11.2 to 11.1
>     Status changed from Fix In Progress to Ready For Release
>
> I added libhyve-remote and all the bits necessary to improve VNC server.
> Python bits were reviewed by williamgr and C bits by kris.
> -- begin excerpt --
>
> In this second one 11.2 and 11.1 are refering to FreeBSD releases,
> I do believe this is fixed in FreeBSD 11.1.
>
> --
> Rod Grimes
> rgrimes@freebsd.org
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEN4iuaS6m6T4hiKUYG5vYHyH2YZM1G9J2U3ACoeprWYFM2dzg>