> From: Kevin Oberman
> Sent: Sun Nov 28 02:19:53 CET 2021
> To: Sysadmin Lists
> Cc: Derek Schrock ,
> freebsd-emulation@freebsd.org
> Subject: Re: VirtualBox Remote Instance
> I find an easier way to do this without the aliases, grep, or awk is:
> ptavv> pkg info
On 11/3/21 11:13, Konstantin Belousov wrote:
On Wed, Nov 03, 2021 at 11:05:11AM -0400, Michael Butler via freebsd-emulation
wrote:
On 11/3/21 10:36, Ed Maste wrote:
The kgdb back-trace isn't any more enlightening to me :-(
__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:
On 11/3/21 11:13, Konstantin Belousov wrote:
On Wed, Nov 03, 2021 at 11:05:11AM -0400, Michael Butler via freebsd-emulation
wrote:
On 11/3/21 10:36, Ed Maste wrote:
The kgdb back-trace isn't any more enlightening to me :-(
__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:
On 11/3/21 10:36, Ed Maste wrote:
On Tue, 2 Nov 2021 at 18:32, Michael Butler via freebsd-emulation
wrote:
Before reporting this, I rebuilt world including kernel, all kmods and
virtualbox itself to no avail :-(
Thanks for confirming.
Now that the WARN_ON noise is disabled by default would
On 11/3/21 10:36, Ed Maste wrote:
On Tue, 2 Nov 2021 at 18:32, Michael Butler via freebsd-emulation
wrote:
Before reporting this, I rebuilt world including kernel, all kmods and
virtualbox itself to no avail :-(
Thanks for confirming.
Now that the WARN_ON noise is disabled by default would
On 11/2/21 17:48, Cy Schubert wrote:
In message <36923A7F-23DE-490D-B1FA-A8B064740BD6@unrelenting.technology>,
Greg
V via freebsd-current writes:
On November 2, 2021 5:16:35 PM GMT+03:00, Michael Butler via freebsd-current
wrote:
On current as of this morning (I haven't tried to bisect yet)
On 11/2/21 17:48, Cy Schubert wrote:
In message <36923A7F-23DE-490D-B1FA-A8B064740BD6@unrelenting.technology>,
Greg
V via freebsd-current writes:
On November 2, 2021 5:16:35 PM GMT+03:00, Michael Butler via freebsd-current
wrote:
On current as of this morning (I haven't tried to bisect yet)
On 25/10/21 09:35, Guido Falsi via emulation wrote:
On 25/10/21 08:23, Kevin Oberman wrote:
Since the update to virtualbox-ose-kmod-6.1.28, I have been seeing a very
large number of the error:
vboxdrv: Bad CPU context error at line 373 in SUPDrv-freebsd.c:
ulCmd=0x2000568a: 0x282->0x
On 25/10/21 08:23, Kevin Oberman wrote:
Since the update to virtualbox-ose-kmod-6.1.28, I have been seeing a very
large number of the error:
vboxdrv: Bad CPU context error at line 373 in SUPDrv-freebsd.c:
ulCmd=0x2000568a: 0x282->0x287!
hundreds of times a day.
I have seen no actual issues with
On 02/08/21 15:25, Mario Lobo wrote:
On Sun, Aug 1, 2021 at 1:38 PM Guido Falsi wrote:
On 01/08/21 14:49, Mario Lobo wrote:
On Wed, Jul 21, 2021, 17:11 Guido Falsi via freebsd-emulation
mailto:freebsd-emulation@freebsd.org>>
wrote:
Hi,
I've tested updating to latest
Hi,
I've tested updating to latest virtualbox. It mostly works. But the
audio subsystem has been overhauled. Our patches don't apply anymore,
but they may not be necessary. Looks like the new code does the right
thing for OSS and ALSA.
Unluckily I'm unable to start any VM using pulseaudio. I
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addr
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addre
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-legacy] Failed for
virtualbox-ose-legacy-5.2.44_6 in build" was unable to be delivered to the
list because the list address was not found in either the T
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-nox11-legacy] Failed for
virtualbox-ose-nox11-legacy-5.2.44_6 in build" was unable to be delivered
to the list because the list address was not found in
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not f
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addr
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addre
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-legacy] Failed for
virtualbox-ose-legacy-5.2.44_6 in build" was unable to be delivered to the
list because the list address was not found in either the T
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-nox11-legacy] Failed for
virtualbox-ose-nox11-legacy-5.2.44_6 in build" was unable to be delivered
to the list because the list address was not found in
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not f
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addr
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addre
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-legacy] Failed for
virtualbox-ose-legacy-5.2.44_5 in build" was unable to be delivered to the
list because the list address was not found in either the T
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-nox11-legacy] Failed for
virtualbox-ose-nox11-legacy-5.2.44_5 in build" was unable to be delivered
to the list because the list address was not found in
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not f
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addr
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addre
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-legacy] Failed for
virtualbox-ose-legacy-5.2.44_5 in build" was unable to be delivered to the
list because the list address was not found in either the T
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-nox11-legacy] Failed for
virtualbox-ose-nox11-legacy-5.2.44_5 in build" was unable to be delivered
to the list because the list address was not found in
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not f
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addr
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addre
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-legacy] Failed for
virtualbox-ose-legacy-5.2.44_5 in build" was unable to be delivered to the
list because the list address was not found in either the T
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-nox11-legacy] Failed for
virtualbox-ose-nox11-legacy-5.2.44_5 in build" was unable to be delivered
to the list because the list address was not found in
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not f
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addr
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addre
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not f
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addr
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addre
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not f
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addr
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addre
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not f
Hi,
As the subject states, with a very recent head (main-n247147-8682abbf7bf
from today) I'm seeing "kldload vboxnetflt" hang in the rc script
vboxnet. The module is although correctly loaded; interrupting that
process and launching it again proceeds to load everything correctly.
Looks like
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addr
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions] Failed for
virtualbox-ose-additions-6.1.22 in build" was unable to be delivered to the
list because the list address was not found in either
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-nox11-legacy] Failed
for virtualbox-ose-additions-nox11-legacy-5.2.44_3 in build" was unable to
be delivered to the list because the list addre
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-nox11] Failed for
virtualbox-ose-additions-nox11-6.1.22 in build" was unable to be delivered
to the list because the list address was not foun
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-amd64-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not
Hi, this is the Mlmmj program managing the
mailing list.
The message from with subject "[package -
main-i386-default][emulators/virtualbox-ose-additions-legacy] Failed for
virtualbox-ose-additions-legacy-5.2.44_3 in build" was unable to be
delivered to the list because the list address was not f
On 01/05/21 01:17, Dutchman01 via freebsd-emulation wrote:
bugfix release 6.1.22 is released!
There is need to upgrade from 6.1.20 to 6.1.22
This is known, automatic notifications already reached the mailing list
yesterday at 8:55 UTC
The notification actually contained an error and I
bugfix release 6.1.22 is released!
There is need to upgrade from 6.1.20 to 6.1.22
Regards,
Dutchman
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to
ic testing.
--
Guido Falsi
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
oup.
The tentative work can be viewed here:
https://github.com/freebsd/freebsd-quarterly/pull/325
Thanks in advance.
--
Guido Falsi
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
stab,
> manually, or another script):
>
> sysrc linux_mounts_enable=YES
>
> > I had not yet actually attempted to run my small Linuxes in FreeBSD or
> > NetBSD, not ready yet.
> > I still would need such things as init scripts, proc fs, /etc/fstab and
> > other con
iles.
The target directory can be empty (in the case of the default emulation path,
'/compat/linux') when starting the service. It doesn't actually "start" your
guest OS. I don't know what your plans are, but running Linux inside a jail is
different than using the co
‐‐‐ Original Message ‐‐‐
On Monday, February 8th, 2021 at 4:00 AM,
wrote:
> Message: 4
>
> Date: Mon, 08 Feb 2021 02:51:55 +
>
> From: "Thomas Mueller" mueller6...@twc.com
>
> To: freebsd-emulation@freebsd.org
>
> Subject: Linuxulator: run
Quoting Thomas Mueller (from Mon, 08 Feb 2021
02:51:55 +):
Is it possible to run one's own little Linux in FreeBSD by
null-mounting directory or partition on /compat/linux?
Short answer: most probably yes.
[...]
Would the Linux C library have to be glibc, or could it be uClibc-ng
o
icate of this. In the duplicate
I posted a patch including the __FreeBSD_version check.
Since you just gave approval for that I'll go ahead and commit, it
should also be merged to 2021Q1, since it affects 13.
--
Guido Falsi
___
freebsd
>
> Message: 4
> Date: Sun, 25 Oct 2020 22:05:42 +
> From: Edward Tomasz Napiera?a tr...@freebsd.org
> To: JB via freebsd-emulation freebsd-emulation@freebsd.org
> Subject: Re: /compat/linux Web Browser
> Message-ID: 20201025220542.GA2593@brick
> Content-Type: text
ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxREM.so]
Error 1
kmk: *** Waiting for unfinished jobs
imb
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
in
a FreeBSD guest.
Thanks for the work you are puting into this.
There's a bug on bugzilla:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234878
I don't have any more information.
--
Guido Falsi
___
freebsd-emulation@freebsd.org mai
ed "virtualbox-ose-additions patch"
Direct link to patch:
https://bz-attachments.freebsd.org/attachment.cgi?id=219058
--
Guido Falsi
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsu
implementation is quite old. I'm inclined to guess that it simply cannot
fully interface with the newer mesa we now have in the ports tree.
--
Guido Falsi
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
-devel-kmod or not? With
and without it gives the same error.
Don't think it's related.
--
Guido Falsi
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send
rw--- 1 user1 user1 236M Oct 22 15:17 palemoon.core
-rw--- 1 user1 user115G Oct 25 10:52 thread_shutdown.core
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
* Waiting for unfinished jobs
imb
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Quoting Edward Tomasz Napierała (from Tue, 30 Jun
2020 12:45:12 +0100):
On 30 Jun 2020, at 09:29, Alexander Leidinger
wrote:
Quoting bugzilla-nore...@freebsd.org (from Thu, 25 Jun 2020
20:31:29 +):
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230160
--- Comment #12 from co
Quoting bugzilla-nore...@freebsd.org (from Thu, 25 Jun 2020 20:31:29 +):
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230160
--- Comment #12 from commit-h...@freebsd.org ---
A commit references this bug:
Author: markj
Date: Thu Jun 25 20:30:31 UTC 2020
New revision: 362631
URL: https:
Quoting "Mikhail T." (from Fri, 19 Jun 2020
14:59:35 -0400):
On 19.06.20 04:52, Tijl Coosemans wrote:
You should not use USE_LINUX_RPM. It's meant for infrastructure ports.
Yes, this is the current stance, but it seems like an unnecessary
limitation... :( Software distributed by vendors i
lease report this to the FreeBSD
port maintainers". This user's version of VirtualBox was v5.2.22
Any help will be appreciated.
With thanks,
Marek
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freeb
(01:24:38 / 01:25:43)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Quoting Alexandr Krivulya (from Fri, 27 Mar
2020 20:27:21 +0200):
27.03.20 19:29, Alexander Leidinger пишет:
Quoting Alexandr Krivulya (from Fri, 27
Mar 2020 15:21:49 +0200):
Hi, emulation@ !
I'm trying to start Linux version of Zoom client [1] on my FreeBSD
(latest head)
Quoting Alexandr Krivulya (from Fri, 27 Mar
2020 15:21:49 +0200):
Hi, emulation@ !
I'm trying to start Linux version of Zoom client [1] on my FreeBSD
(latest head) and I have two questions:
1. Why I need to copy all libraries from Zoom binary folder to
/compat/linux/lib64 be
On 20-03-22 17:47:43, Kyle Evans wrote:
On Sun, Mar 22, 2020 at 5:40 PM Gerald Pfeifer wrote:
On Thu, 12 Mar 2020, Kyle Evans wrote:
> Log:
> emulators/virtualbox-ose: use contemporary GCC instead of old llvm
This patch does not exactly do that. =:o
> +# machine/atomic.h may use features t
Please upgrade vbox asap, important bugfixes in upstream release😊
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
: relaxed VRM / VRA (variable rate audio) bit checks to
provide more compatibility for guests running ALSA setups with the AC'97
emulation
* Audio: Fixed "double buffering" size of a stream's internal ring
buffer, adjusted logging).
* USB: made device capturing
Your mail to 'freebsd-emulation' with the subject
[package - head-i386-default][emulators/virtualbox-ose-nox11]
Failed for virtualbox-ose-nox11-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post by non-m
Your mail to 'freebsd-emulation' with the subject
[package - head-amd64-default][emulators/virtualbox-ose-nox11]
Failed for virtualbox-ose-nox11-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post by non-m
Your mail to 'freebsd-emulation' with the subject
[package - head-i386-default][emulators/virtualbox-ose] Failed for
virtualbox-ose-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post by non-member to a me
Your mail to 'freebsd-emulation' with the subject
[package - head-amd64-default][emulators/virtualbox-ose] Failed
for virtualbox-ose-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post by non-member to a me
Your mail to 'freebsd-emulation' with the subject
[package - head-amd64-default][emulators/virtualbox-ose-nox11]
Failed for virtualbox-ose-nox11-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message ha
Your mail to 'freebsd-emulation' with the subject
[package - head-i386-default][emulators/virtualbox-ose] Failed for
virtualbox-ose-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message has implicit destinati
Your mail to 'freebsd-emulation' with the subject
[package - head-i386-default][emulators/virtualbox-ose-nox11]
Failed for virtualbox-ose-nox11-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message ha
Your mail to 'freebsd-emulation' with the subject
[package - head-amd64-default][emulators/virtualbox-ose] Failed
for virtualbox-ose-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message has implicit d
Your mail to 'freebsd-emulation' with the subject
[package - head-i386-default][emulators/virtualbox-ose-nox11]
Failed for virtualbox-ose-nox11-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message ha
Your mail to 'freebsd-emulation' with the subject
[package - head-amd64-default][emulators/virtualbox-ose] Failed
for virtualbox-ose-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message has implicit d
Your mail to 'freebsd-emulation' with the subject
[package - head-i386-default][emulators/virtualbox-ose] Failed for
virtualbox-ose-5.2.32_1 in build
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message has implicit destinati
1 - 100 of 451 matches
Mail list logo
