On 11/15/10 7:35 PM, Garrett Cooper wrote:
On Mon, Nov 15, 2010 at 6:24 PM, wrote:
So, I have Core 2 Duo, runing as i386.
I decided to go for amd64 (it's name, is so deceiving, that I've just
recently, accidentaly figured out, that it can be used, with intel CPUs,
too) :P
8.1 cross build i386
On Mon, Nov 15, 2010 at 9:37 PM, Garrett Cooper wrote:
> On Mon, Nov 15, 2010 at 7:09 PM, Brandon Gooch
> wrote:
>> On Mon, Nov 15, 2010 at 7:17 PM, Benjamin Lee wrote:
>>> On 11/15/2010 02:08 PM, Joerg Pulz wrote:
Hi,
after the security/heimdal port was updated to the current hei
On Mon, Nov 15, 2010 at 7:09 PM, Brandon Gooch
wrote:
> On Mon, Nov 15, 2010 at 7:17 PM, Benjamin Lee wrote:
>> On 11/15/2010 02:08 PM, Joerg Pulz wrote:
>>> Hi,
>>>
>>> after the security/heimdal port was updated to the current heimdal
>>> release and i added one missing function from base it is
On Mon, Nov 15, 2010 at 7:35 PM, Garrett Cooper wrote:
> On Mon, Nov 15, 2010 at 6:24 PM, wrote:
>> So, I have Core 2 Duo, runing as i386.
>> I decided to go for amd64 (it's name, is so deceiving, that I've just
>> recently, accidentaly figured out, that it can be used, with intel CPUs,
>> too)
On Mon, Nov 15, 2010 at 6:24 PM, wrote:
> So, I have Core 2 Duo, runing as i386.
> I decided to go for amd64 (it's name, is so deceiving, that I've just
> recently, accidentaly figured out, that it can be used, with intel CPUs,
> too) :P
>
> 8.1 cross build i386 -> amd64 has failed
> World comple
On Mon, Nov 15, 2010 at 7:17 PM, Benjamin Lee wrote:
> On 11/15/2010 02:08 PM, Joerg Pulz wrote:
>> Hi,
>>
>> after the security/heimdal port was updated to the current heimdal
>> release and i added one missing function from base it is now possible to
>> completely buildworld src/ using the port
So, I have Core 2 Duo, runing as i386.
I decided to go for amd64 (it's name, is so deceiving, that I've just
recently, accidentaly figured out, that it can be used, with intel CPUs,
too) :P
8.1 cross build i386 -> amd64 has failed
World completes successfully, but kernel fails:
mkdep -f .de
On 11/15/2010 02:08 PM, Joerg Pulz wrote:
> Hi,
>
> after the security/heimdal port was updated to the current heimdal
> release and i added one missing function from base it is now possible to
> completely buildworld src/ using the port for all Kerberos5/GSSAPI
> enabled parts.
Hi Joerg,
I don'
On Mon, Nov 15, 2010 at 12:51:57PM -0800, Julian Elischer wrote:
> "keep more information associated with each kevent and use the user
> cookie to
> match them" this is what it was for.
> it's a tool, not an answer. Given this tool you should be able to
> get what you want.
> how you do it is your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
after the security/heimdal port was updated to the current heimdal release
and i added one missing function from base it is now possible to
completely buildworld src/ using the port for all Kerberos5/GSSAPI enabled
parts.
The patches for sr
On Mon Nov 15 10, Alexander Best wrote:
> On Mon Nov 15 10, Xin LI wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Hi,
> >
> > On 11/15/10 10:24, Alexander Best wrote:
> > > hi there,
> > >
> > > any thoughts on this patch? it changes the semantics of gzip so that it is
>
On Mon Nov 15 10, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> On 11/15/10 10:24, Alexander Best wrote:
> > hi there,
> >
> > any thoughts on this patch? it changes the semantics of gzip so that it is
> > consistent with the semantics of bzip2, xz and for more im
On Mon Nov 15 10, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> On 11/15/10 10:24, Alexander Best wrote:
> > hi there,
> >
> > any thoughts on this patch? it changes the semantics of gzip so that it is
> > consistent with the semantics of bzip2, xz and for more im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 11/15/10 10:24, Alexander Best wrote:
> hi there,
>
> any thoughts on this patch? it changes the semantics of gzip so that it is
> consistent with the semantics of bzip2, xz and for more important GNU gzip.
Could you please elaborate more a
On 11/15/10 12:14 PM, Paul LeoNerd Evans wrote:
On Mon, Nov 15, 2010 at 11:37:23AM -0800, Julian Elischer wrote:
I don't think it was thought of in the context of reference counted items.
This problem has nothing to do with reference counting, and all to do
with resource ownership.
Consider in
On Mon, Nov 15, 2010 at 11:37:23AM -0800, Julian Elischer wrote:
> I don't think it was thought of in the context of reference counted items.
This problem has nothing to do with reference counting, and all to do
with resource ownership.
Consider in the totally C-based world, no refcounts, just ma
On Mon, Nov 15, 2010 at 9:53 AM, Garrett Cooper wrote:
> According to SYSCTL_INT(9):
>
> The SYSCTL kernel interfaces allow code to statically declare sysctl(8)
> MIB entries, which will be initialized when the kernel module containing
> the declaration is initialized. When the mod
On 11/15/10 10:38 AM, Paul LeoNerd Evans wrote:
On Mon, Nov 15, 2010 at 10:33:25AM -0800, Julian Elischer wrote:
it was provided for pretty much what you are using it for, so that
the userland caller could
easily associate the returning event with some private information
about the event.
This
On Mon, Nov 15, 2010 at 02:10:45PM -0500, John Baldwin wrote:
> On Monday, November 15, 2010 1:12:11 pm Paul LeoNerd Evans wrote:
> > On Mon, Nov 15, 2010 at 11:25:42AM -0500, John Baldwin wrote:
> > > I think the assumption is that userland actually maintains a reference on
> > > the
> > > speci
On Monday, November 15, 2010 1:12:11 pm Paul LeoNerd Evans wrote:
> On Mon, Nov 15, 2010 at 11:25:42AM -0500, John Baldwin wrote:
> > I think the assumption is that userland actually maintains a reference on
> > the
> > specified object (e.g. a file descriptor) and will know to drop the
> > asso
On Mon, Nov 15, 2010 at 10:33:25AM -0800, Julian Elischer wrote:
> it was provided for pretty much what you are using it for, so that
> the userland caller could
> easily associate the returning event with some private information
> about the event.
This was indeed the impression I got. With refer
On 11/15/10 10:12 AM, Paul LeoNerd Evans wrote:
On Mon, Nov 15, 2010 at 11:25:42AM -0500, John Baldwin wrote:
I think the assumption is that userland actually maintains a reference on the
specified object (e.g. a file descriptor) and will know to drop the associated
data when the file descriptor
hi there,
any thoughts on this patch? it changes the semantics of gzip so that it is
consistent with the semantics of bzip2, xz and for more important GNU gzip.
cheers.
alex
--
a13x
diff --git a/usr.bin/gzip/gzip.1 b/usr.bin/gzip/gzip.1
index 848a4b3..8eab82c 100644
--- a/usr.bin/gzip/gzip.1
++
On Mon, Nov 15, 2010 at 11:25:42AM -0500, John Baldwin wrote:
> I think the assumption is that userland actually maintains a reference on the
> specified object (e.g. a file descriptor) and will know to drop the
> associated
> data when the file descriptor is closed. That is, think of the keven
On Monday, November 15, 2010 12:53:57 pm Garrett Cooper wrote:
> According to SYSCTL_INT(9):
>
> The SYSCTL kernel interfaces allow code to statically declare sysctl(8)
> MIB entries, which will be initialized when the kernel module containing
> the declaration is initialized.
According to SYSCTL_INT(9):
The SYSCTL kernel interfaces allow code to statically declare sysctl(8)
MIB entries, which will be initialized when the kernel module containing
the declaration is initialized. When the module is unloaded, the sysctl
will be automatically destro
On Friday, November 12, 2010 1:40:00 pm Paul LeoNerd Evans wrote:
> I'm trying to build a high-level language wrapper around kqueue/kevent,
> specifically, a Perl wrapper.
>
> (In fact I am trying to fix this bug:
> http://rt.cpan.org/Public/Bug/Display.html?id=61481
> )
>
> My plan is to use t
On 14 Nov 2010, at 03:40, Adrian Chadd wrote:
> I've committed the below changes to -HEAD. You can now create and build your
> own busybox style binary system, completely cross-compiled within the
> existing Make framework. It isn't as impressive as it sounds though - a lot
> of the framework is
On Mon, 15 Nov 2010 12:56:29 +0100, Erik Cederstrand
wrote:
>Den 15/11/2010 kl. 12.40 skrev Tom Evans:
>> The important things for us are that given a binary, you should be
>> able to easily reproduce the source environment that the binary was
>> produced from, and any two binaries produced from
On Sun Nov 14 10, Alexander Best wrote:
> On Sun Nov 14 10, Kostik Belousov wrote:
> > On Sun, Nov 14, 2010 at 01:55:59PM +, Alexander Best wrote:
> > > hi there,
> > >
> > > could we please have the following manual pages
> > >
> > > lib/libc/i386/sys/i386_get_ioperm.2
> > > lib/libc/i386/sy
On Sun, Nov 14, 2010 at 9:13 PM, Spörlein wrote:
> On Sun, 14.11.2010 at 21:57:25 +0100, Erik Cederstrand wrote:
>>
>> Den 14/11/2010 kl. 21.32 skrev Dimitry Andric:
>>
>> > On 2010-11-14 21:22, Erik Cederstrand wrote:
>> >> I'm curious as to why this might be useful? Would the mtime of the
>> >>
Den 15/11/2010 kl. 12.40 skrev Tom Evans:
> The important things for us are that given a binary, you should be
> able to easily reproduce the source environment that the binary was
> produced from, and any two binaries produced from the same sources
> should be identical.
I'm leaning towards not
32 matches
Mail list logo
