Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 3 May 2021 14:37:07 -0700
From:      Pete Wright <pete@nomadlogic.org>
To:        Chargen <chargen@gmail.com>, freebsd-current@freebsd.org
Subject:   Re: WSLg update on 1-5-2021 - BSD / WSL
Message-ID:  <0b3d6049-f6eb-f9d4-5f20-f09ac666e949@nomadlogic.org>
In-Reply-To: <CAA-K0n%2BsJ%2BKmc3LitPiX_RLxcKv8aUcY9=cRiM7mx58NY5xs-A@mail.gmail.com>
References:  <CAA-K0n%2BsJ%2BKmc3LitPiX_RLxcKv8aUcY9=cRiM7mx58NY5xs-A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On 5/1/21 12:42 PM, Chargen wrote:
> Dear all
>
> please note that I hope this message will be discussed to get this on the
> roadmap for FreeBSD. Perhaps there is already talk about &&  work done on
> that.
> I would like to suggest having a BSD side for Microsoft FOSS ambitions and
> get to know the BSD license. I hope the tech people here, know which nuts
> and bolts would be ready to boot a *BSD subsystem kernel and make that
> available on Windows 10 installations.

I believe most of the effort make this happen lies with Microsoft - it 
is their product after all.

WSL under the covers is Hyper-V which supports FreeBSD pretty well. I 
believe most of the work would be on the Windows side to get the 
plumbing in place to spin up a FreeBSD VM.  There are open discussions 
on the WSL github system where people have asked for this but it has not 
gained much traction by Microsoft.

-p

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0b3d6049-f6eb-f9d4-5f20-f09ac666e949>