ink ripping
the band-aid off is fine, especially since the replacement API has been
ready for such a long time (and goes back to 7.0).
--
John Baldwin
___
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"
700013, so you can use that version. OTOH, I would be
surprised if VirtualBox worked on FreeBSD 6.x.
--
John Baldwin
___
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"
gt; >
> > Michael
> >
>
>
> +1
Then the port needs to be patched? It's been using an API deprecated
for the last 15 years. A simple s/taskqueue_enqueue_fast/taskqueue_enqueue/
will fix it.
--
John Baldwin
___
freeb
The following reply was made to PR kern/186051; it has been noted by GNATS.
From: John Baldwin
To: Steven Spence
Cc: bug-follo...@freebsd.org
Subject: Re: kern/186051: [vmware] [panic] FreeBSD 8.4+, 9.x+, 10.0 guest panic
with VMWare Server on boot
Date: Wed, 30 Apr 2014 17:34:28 -0400
On
The following reply was made to PR kern/186051; it has been noted by GNATS.
From: John Baldwin
To: Steven Spence
Cc: bug-follo...@freebsd.org
Subject: Re: kern/186051: [vmware] [panic] FreeBSD 8.4+, 9.x+, 10.0 guest panic
with VMWare Server on boot
Date: Wed, 30 Apr 2014 13:17:18 -0400
On
The following reply was made to PR kern/186051; it has been noted by GNATS.
From: John Baldwin
To: Steven Spence
Cc: bug-follo...@freebsd.org
Subject: Re: kern/186051: [vmware] [panic] FreeBSD 8.4+, 9.x+, 10.0 guest panic
with VMWare Server on boot
Date: Wed, 30 Apr 2014 12:09:44 -0400
On
The following reply was made to PR kern/186051; it has been noted by GNATS.
From: John Baldwin
To: Steven Spence
Cc: bug-follo...@freebsd.org
Subject: Re: kern/186051: [vmware] [panic] FreeBSD 8.4+, 9.x+, 10.0 guest panic
with VMWare Server on boot
Date: Tue, 29 Apr 2014 15:43:16 -0400
On
The following reply was made to PR kern/186051; it has been noted by GNATS.
From: John Baldwin
To: Steven Spence
Cc: bug-follo...@freebsd.org
Subject: Re: kern/186051: [vmware] [panic] FreeBSD 8.4+, 9.x+, 10.0 guest panic
with VMWare Server on boot
Date: Mon, 28 Apr 2014 10:32:23 -0400
This
The following reply was made to PR kern/186051; it has been noted by GNATS.
From: John Baldwin
To: bug-follo...@freebsd.org,
free...@stratum16.com
Cc:
Subject: Re: kern/186051: [vmware] [panic] FreeBSD 8.4+, 9.x+, 10.0 guest panic
with VMWare Server on boot
Date: Mon, 21 Apr 2014 14:37:41
On Monday, January 28, 2013 12:49:44 pm Chagin Dmitry wrote:
> On Mon, Jan 28, 2013 at 09:47:39AM -0500, John Baldwin wrote:
> > This patch attempts to reduce duplication between i386/linux/linux.h and
> > amd64/linux32/linux.h by moving bits that are MI out into headers in
>
reduction could be possible if we wanted to make a linux-i386.h that these two
headers could share, but that would be a separate project.
http://www.FreeBSD.org/~jhb/patches/linux_mi.patch
--
John Baldwin
___
freebsd-emulation@freebsd.org mailing list
On Monday, January 21, 2013 2:55:22 pm Alexander Leidinger wrote:
> On Sat, 19 Jan 2013 11:26:13 -0500 John Baldwin wrote:
>
> > The current setsockopt() wrapper for the Linux ABI claims that Linux
> > and FreeBSD use the same values for TCP socket options. This is true
>
MAXSEG2
+#defineLINUX_TCP_KEEPIDLE 4
+#defineLINUX_TCP_KEEPINTVL 5
+#defineLINUX_TCP_KEEPCNT 6
+#defineLINUX_TCP_MD5SIG14
+
struct l_sockaddr {
l_ushortsa_family;
char sa_data
icy. I do think the installer can set a
good initial policy for this just as it can for /home. Now, using the default
layout the installer could just leave /compat as a dir on /. Many folks
still customize their layout to make /usr or /home separa
This patch teaches the Linux ABIs to use the new posix_fadvise(2) system calls
instead of using stubs. I've no good way to test this so would appreciate
some extra review or testing.
Patch is at http://www.freebsd.org/~jhb/patches/fadvise_linux.patch
--
John Ba
Fixing this problem generically is very hard. Instead, we have patched
individual sysctls and ioctls on a case-by-case basis.
I do think newer interfaces often opt to use fixed-size types so that
the structure is the same for both 32-bit and 64-bit, but that will not
work for existing interfaces
On Wednesday 10 March 2010 10:55:40 am Nathan Whitehorn wrote:
> John Baldwin wrote:
> > On Wednesday 10 March 2010 9:39:15 am Nathan Whitehorn wrote:
> >
> >> John Baldwin wrote:
> >>
> >>> On Tuesday 09 March 2010 11:14:27 pm Nathan Whitehorn
On Wednesday 10 March 2010 9:39:15 am Nathan Whitehorn wrote:
> John Baldwin wrote:
> > On Tuesday 09 March 2010 11:14:27 pm Nathan Whitehorn wrote:
> >
> >> The patch at http://people.freebsd.org/~nwhitehorn/compat_freebsd32.diff
> >> (pre-generated freebsd32
s are for, but fixing ia32_reg.h would be a good first
step. It would make your diffs smaller I think.
The rest of the diff looks fine to me.
--
John Baldwin
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
19 matches
Mail list logo
