On 15 April 2010 17:41, Nathan Whitehorn wrote:
> On 04/15/10 08:13, John Baldwin wrote:
>>
>> On Thursday 15 April 2010 6:06:24 am pluknet wrote:
>>
>>>
>>> On 7 April 2010 23:49, John Baldwin wrote:
>>>
On Tuesday 06 April 2010 11:24:21 am Nathan Whitehorn wrote:
>
> pluk
On 04/15/10 08:13, John Baldwin wrote:
On Thursday 15 April 2010 6:06:24 am pluknet wrote:
On 7 April 2010 23:49, John Baldwin wrote:
On Tuesday 06 April 2010 11:24:21 am Nathan Whitehorn wrote:
pluknet wrote:
Hi,
the interesting part for me is how to properly as
On Thursday 15 April 2010 6:06:24 am pluknet wrote:
> On 7 April 2010 23:49, John Baldwin wrote:
> > On Tuesday 06 April 2010 11:24:21 am Nathan Whitehorn wrote:
> >> pluknet wrote:
> >> > Hi,
> >> >
> >> > the interesting part for me is how to properly assert now a value of
e.g.
> >> > KINFO_PRO
On 7 April 2010 23:49, John Baldwin wrote:
> On Tuesday 06 April 2010 11:24:21 am Nathan Whitehorn wrote:
>> pluknet wrote:
>> > Hi,
>> >
>> > the interesting part for me is how to properly assert now a value of e.g.
>> > KINFO_PROC_SIZE varying on err.. different COMPAT_FREEBSD32 arches
>> > (say
On Tuesday 06 April 2010 11:24:21 am Nathan Whitehorn wrote:
> pluknet wrote:
> > Hi,
> >
> > the interesting part for me is how to properly assert now a value of e.g.
> > KINFO_PROC_SIZE varying on err.. different COMPAT_FREEBSD32 arches
> > (say, FreeBSD would have _kern_proc FreeBSD32 compat lay
pluknet wrote:
Hi,
the interesting part for me is how to properly assert now a value of e.g.
KINFO_PROC_SIZE varying on err.. different COMPAT_FREEBSD32 arches
(say, FreeBSD would have _kern_proc FreeBSD32 compat layer for top/ps/).
Probably the cleanest thing would be to set KINFO_PROC_SIZE
Hi,
the interesting part for me is how to properly assert now a value of e.g.
KINFO_PROC_SIZE varying on err.. different COMPAT_FREEBSD32 arches
(say, FreeBSD would have _kern_proc FreeBSD32 compat layer for top/ps/).
--
wbr,
pluknet
___
freebsd-curren
On Tue, 23 Mar 2010 20:49, Carlos A. M. dos Santos wrote:
In Message-Id:
On Tue, Mar 23, 2010 at 8:39 PM, jhell wrote:
On Mon, 22 Mar 2010 15:42, deischen@ wrote:
[ Some CC's stripped ]
On Mon, 22 Mar 2010, M. Warner Losh wrote:
P.S. I think that there's much traction to the idea of m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24.03.2010 01:49, Carlos A. M. dos Santos wrote:
> On Tue, Mar 23, 2010 at 8:39 PM, jhell wrote:
>>
>> On Mon, 22 Mar 2010 15:42, deischen@ wrote:
>>>
>>> [ Some CC's stripped ]
>>>
>>> On Mon, 22 Mar 2010, M. Warner Losh wrote:
>>>
P.S. I th
On Tue, Mar 23, 2010 at 8:39 PM, jhell wrote:
>
> On Mon, 22 Mar 2010 15:42, deischen@ wrote:
>>
>> [ Some CC's stripped ]
>>
>> On Mon, 22 Mar 2010, M. Warner Losh wrote:
>>
>>> P.S. I think that there's much traction to the idea of moving from
>>> COMPAT_FREEBSDx to some other variable called,
On Mon, 22 Mar 2010 15:42, deischen@ wrote:
[ Some CC's stripped ]
On Mon, 22 Mar 2010, M. Warner Losh wrote:
P.S. I think that there's much traction to the idea of moving from
COMPAT_FREEBSDx to some other variable called, for example,
COMPAT_FREEBSD_BACK_TO=x, which will give compatibility
[ Some CC's stripped ]
On Mon, 22 Mar 2010, M. Warner Losh wrote:
P.S. I think that there's much traction to the idea of moving from
COMPAT_FREEBSDx to some other variable called, for example,
COMPAT_FREEBSD_BACK_TO=x, which will give compatibility for binaries
as old as FreeBSD x.0, and have
P.S. I think that there's much traction to the idea of moving from
COMPAT_FREEBSDx to some other variable called, for example,
COMPAT_FREEBSD_BACK_TO=x, which will give compatibility for binaries
as old as FreeBSD x.0, and have all the other magic handled behind the
scenes. This would render the
In message: <20100322185331.ga88...@dragon.nuxi.org>
"David O'Brien" writes:
: On Fri, Mar 12, 2010 at 12:50:32PM -0700, M. Warner Losh wrote:
: > : On Thu, Mar 11, 2010 at 07:24:23PM -0700, M. Warner Losh wrote:
: > So the issue isn't as cut and dried as you might think. There's
: >
On Fri, Mar 12, 2010 at 12:50:32PM -0700, M. Warner Losh wrote:
> : On Thu, Mar 11, 2010 at 07:24:23PM -0700, M. Warner Losh wrote:
> So the issue isn't as cut and dried as you might think. There's
> multiple different conventions used here in addition to your simple
> example.
I guess we'd have
On Mon, 15 Mar 2010 14:02, Garance A Drosehn wrote:
In Message:
At 12:59 PM -0600 3/12/10, Mark Linimon wrote:
On Fri, Mar 12, 2010 at 09:22:55AM -0800, David O'Brien wrote:
> Yes it is. Where was it discussed first? I do not see anything
> in my freebsd-arch or freebsd-current archive; o
At 12:59 PM -0600 3/12/10, Mark Linimon wrote:
On Fri, Mar 12, 2010 at 09:22:55AM -0800, David O'Brien wrote:
> Yes it is. Where was it discussed first? I do not see anything
> in my freebsd-arch or freebsd-current archive; or any other
> FreeBSD list.
http://docs.freebsd.org/cgi/mid.cgi?4B
Svein Skogen (Listmail Account) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15.03.2010 13:49, Ian FREISLICH wrote:
Hi
I originally wasn't going to weigh in on this, but:
options COMPAT_FREEBSD4 #Compatible with FreeBSD4
options COMPAT_FREEBSD5 #Comp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15.03.2010 13:49, Ian FREISLICH wrote:
> Hi
>
> I originally wasn't going to weigh in on this, but:
>
> options COMPAT_FREEBSD4 #Compatible with FreeBSD4
> options COMPAT_FREEBSD5 #Compatible with FreeBSD5
> options
On Mon, 15 Mar 2010 14:49:11 +0200, Ian FREISLICH wrote:
Hi
I originally wasn't going to weigh in on this, but:
options COMPAT_FREEBSD4 #Compatible with FreeBSD4
options COMPAT_FREEBSD5 #Compatible with FreeBSD5
options COMPAT_FREEBSD6 #Compatib
On Mon, Mar 15, 2010 at 8:49 AM, Ian FREISLICH wrote:
> Hi
>
> I originally wasn't going to weigh in on this, but:
>
> options COMPAT_FREEBSD4 #Compatible with FreeBSD4
> options COMPAT_FREEBSD5 #Compatible with FreeBSD5
> options COMPAT_FREEBSD6 #C
Hi
I originally wasn't going to weigh in on this, but:
options COMPAT_FREEBSD4 #Compatible with FreeBSD4
options COMPAT_FREEBSD5 #Compatible with FreeBSD5
options COMPAT_FREEBSD6 #Compatible with FreeBSD6
options COMPAT_FREEBSD7 #Com
In message: <20100312171758.gb31...@dragon.nuxi.org>
"David O'Brien" writes:
: On Thu, Mar 11, 2010 at 07:24:23PM -0700, M. Warner Losh wrote:
: > In message: <7d6fde3d1003111720g7dccf93w1f51db88758a5...@mail.gmail.com>
: > Garrett Cooper writes:
: > : On Thu, Mar 11, 2010
Ulrich Spörlein wrote:
On Fri, 12.03.2010 at 11:36:25 +0100, Gary Jennejohn wrote:
On Thu, 11 Mar 2010 20:24:57 -0800
Garrett Cooper wrote:
I can haz PR review then? Here's an easy one :)...
http://www.freebsd.org/cgi/query-pr.cgi?pr=144644
Looks OK to me except I don't like the
On Fri, Mar 12, 2010 at 09:22:55AM -0800, David O'Brien wrote:
> Yes it is. Where was it discussed first? I do not see anything in my
> freebsd-arch or freebsd-current archive; or any other FreeBSD list.
http://docs.freebsd.org/cgi/mid.cgi?4B971CA3.9090301
crossposted on amd64@, ia64@, emulat..
David O'Brien wrote:
Yes names matter. Otherwise we would have made it "DEF8931". #define
names are chosen to be self-documenting.
$ grep COMPAT_FREEBSD conf/*
conf/NOTES:# Note that as a general rule, COMPAT_FREEBSD depends on
conf/NOTES:# COMPAT_FREEBSD, COMPAT_FREEBSD, etc.
conf/NO
On Thu, Mar 11, 2010 at 08:54:32PM -0700, Scott Long wrote:
> On Mar 11, 2010, at 6:14 PM, Scot Hetzel wrote:
> > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> > wrote:
> >> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
> >>>
> >>> As a result of importing 32-bit compatibility support for non-
On Thu, Mar 11, 2010 at 07:24:23PM -0700, M. Warner Losh wrote:
> In message: <7d6fde3d1003111720g7dccf93w1f51db88758a5...@mail.gmail.com>
> Garrett Cooper writes:
> : On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel wrote:
> : > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> : > wrote
On Fri, 12.03.2010 at 11:36:25 +0100, Gary Jennejohn wrote:
> On Thu, 11 Mar 2010 20:24:57 -0800
> Garrett Cooper wrote:
>
> > I can haz PR review then? Here's an easy one :)...
> >
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=144644
> >
>
> Looks OK to me except I don't like the
>
On Thu, 11 Mar 2010 20:24:57 -0800
Garrett Cooper wrote:
> I can haz PR review then? Here's an easy one :)...
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=144644
>
Looks OK to me except I don't like the
if (something) {
one-line-of-code();
}
constructs, bu
On Thu, Mar 11, 2010 at 6:24 PM, M. Warner Losh wrote:
> In message: <7d6fde3d1003111720g7dccf93w1f51db88758a5...@mail.gmail.com>
> Garrett Cooper writes:
> : On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel wrote:
> : > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> : > wrote:
> : >>
On Mar 11, 2010, at 6:14 PM, Scot Hetzel wrote:
> On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> wrote:
>> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
>>>
>>> As a result of importing 32-bit compatibility support for non-x86 64-bit
>>> platforms, the kernel options COMPAT_IA32 has been rename
On Thu, Mar 11, 2010 at 9:24 PM, M. Warner Losh wrote:
> In message: <7d6fde3d1003111720g7dccf93w1f51db88758a5...@mail.gmail.com>
>Garrett Cooper writes:
> : On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel wrote:
> : > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> : > wrote:
> : >>
In message: <7d6fde3d1003111720g7dccf93w1f51db88758a5...@mail.gmail.com>
Garrett Cooper writes:
: On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel wrote:
: > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
: > wrote:
: >> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
: >>>
: >>> As a resu
On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel wrote:
> On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> wrote:
>> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
>>>
>>> As a result of importing 32-bit compatibility support for non-x86 64-bit
>>> platforms, the kernel options COMPAT_IA32 has been re
On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
wrote:
> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
>>
>> As a result of importing 32-bit compatibility support for non-x86 64-bit
>> platforms, the kernel options COMPAT_IA32 has been renamed COMPAT_FREEBSD32
>> in revision 205014, so all kernel c
On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
As a result of importing 32-bit compatibility support for non-x86
64-bit platforms, the kernel options COMPAT_IA32 has been renamed
COMPAT_FREEBSD32 in revision 205014, so all kernel configurations
including this option must be modified accordingly.
On Fri, 12 Mar 2010, Hajimu UMEMOTO wrote:
Hi,
On Thu, 11 Mar 2010 08:50:05 -0600
Nathan Whitehorn said:
nwhitehorn> As a result of importing 32-bit compatibility support for non-x86
64-bit
nwhitehorn> platforms, the kernel options COMPAT_IA32 has been renamed
nwhitehorn> COMPAT_FREEBSD32
Hi,
> On Thu, 11 Mar 2010 08:50:05 -0600
> Nathan Whitehorn said:
nwhitehorn> As a result of importing 32-bit compatibility support for non-x86
64-bit
nwhitehorn> platforms, the kernel options COMPAT_IA32 has been renamed
nwhitehorn> COMPAT_FREEBSD32 in revision 205014, so all kernel
39 matches
Mail list logo
