On Fri, Oct 28, 2022 at 12:26:07PM -0700, Mike Larkin wrote:
> On Fri, Oct 28, 2022 at 12:30:11PM -0600, Theo de Raadt wrote:
> > Kalabic S, wrote:
> >
> > > To be more precise, I wanted to say sticking with FreeBSD means
> > > sticking with whatever behavior VMware will keep consistent and
> > >
On Fri, Oct 28, 2022 at 12:30:11PM -0600, Theo de Raadt wrote:
> Kalabic S, wrote:
>
> > To be more precise, I wanted to say sticking with FreeBSD means
> > sticking with whatever behavior VMware will keep consistent and
> > support in the future. For "Others" option I don't think they care and
>
Kalabic S, wrote:
> To be more precise, I wanted to say sticking with FreeBSD means
> sticking with whatever behavior VMware will keep consistent and
> support in the future. For "Others" option I don't think they care and
> is more probable to vary.
I cannot tell the difference. I think you
On 10/28/22 18:29, Theo de Raadt wrote:
Kalabic S. wrote:
Also, OpenBSD really is part of BSD family.
That is such a load of crap.
You have absolutely no idea what vmware is doing behind the scenes based
upon that string.
Obviously, it is doing stuff. But you want to say "oh family".
On 10/28/22 19:06, Mike Larkin wrote:
On Fri, Oct 28, 2022 at 06:25:11PM +0200, Kalabic S. wrote:
In my testing, this has no effect on the operation of the clock. Only
the guest OS selected in the VM configuration does have an effect.
We should remove any suggestion that 32bit FreeBSD is
On Fri, Oct 28, 2022 at 06:25:11PM +0200, Kalabic S. wrote:
> > In my testing, this has no effect on the operation of the clock. Only
> > the guest OS selected in the VM configuration does have an effect.
> > We should remove any suggestion that 32bit FreeBSD is the right thing
> > to select
Kalabic S. wrote:
> I have an OpenBSD VM running without issues as a guest with 'FreeBSD'
> option for years and serving as an Internet router for home
> network. IMO, it's pretty good chice.
I want to say more.
You really have no idea what you are talking about. The difference between
7.1
Kalabic S. wrote:
> Also, OpenBSD really is part of BSD family.
That is such a load of crap.
You have absolutely no idea what vmware is doing behind the scenes based
upon that string.
Obviously, it is doing stuff. But you want to say "oh family". Stop it.
> In my testing, this has no effect on the operation of the clock. Only
> the guest OS selected in the VM configuration does have an effect.
> We should remove any suggestion that 32bit FreeBSD is the right thing
> to select though, so changing the guest OS we report is still a good
> idea.
>
On Thu, Oct 27, 2022 at 11:02:06AM -0700, Mike Larkin wrote:
> On Wed, Oct 26, 2022 at 07:39:03PM +0200, Kalabic S. wrote:
> > Hello @misc,
> >
> > I do not see a reason not to update OS version that vmt (kernel level
> > implementation of VMware Tools) is advertising to VMware hypervisor from 32
On 10/27/22 20:02, Mike Larkin wrote:
On Wed, Oct 26, 2022 at 07:39:03PM +0200, Kalabic S. wrote:
Hello @misc,
I do not see a reason not to update OS version that vmt (kernel level
implementation of VMware Tools) is advertising to VMware hypervisor from 32
bit FreeBSD to 64 bit version.
If
On Wed, Oct 26, 2022 at 07:39:03PM +0200, Kalabic S. wrote:
> Hello @misc,
>
> I do not see a reason not to update OS version that vmt (kernel level
> implementation of VMware Tools) is advertising to VMware hypervisor from 32
> bit FreeBSD to 64 bit version.
>
> If for nothing else, there's clock
Hello @misc,
I do not see a reason not to update OS version that vmt (kernel level
implementation of VMware Tools) is advertising to VMware hypervisor from
32 bit FreeBSD to 64 bit version.
If for nothing else, there's clock running forward issue that appeared
in 7.2 release and that is
13 matches
Mail list logo
