On Wed, Oct 03, 2012 at 07:22:18PM +, Alexander Nasonov wrote:
> Module Name: src
> Committed By: alnsn
> Date: Wed Oct 3 19:22:18 UTC 2012
>
> Removed Files:
> src/external/bsd/sljit: README.import
> src/external/bsd/sljit/dist: Makefile README
> src/external/bsd/s
David Laight wrote:
> How long was it there? and was it ever in a build?
> If not built it can be deleted from the repository.
Not for long and it was never hooked to the build.
It can be removed but I don't know how.
Alex
On Thu, Oct 04, 2012 at 08:25:00PM +0100, Alexander Nasonov wrote:
> Not for long and it was never hooked to the build.
> It can be removed but I don't know how.
Send mail to admins requesting it.
Thomas
On Mon, Oct 01, 2012 at 09:16:47PM +, Alexander Nasonov wrote:
> Module Name: src
> Committed By: alnsn
> Date: Mon Oct 1 21:16:46 UTC 2012
>
> Update of /cvsroot/src/external/bsd/sljit/dist
> In directory ivanova.netbsd.org:/tmp/cvs-serv13245
>
> Log Message:
> Initial import of sl
Joerg Sonnenberger wrote:
> If this is intended for kernel use, why is it in src/external?
There is an interest to use it as userspace library as well.
Alex
On Mon, Oct 01, 2012 at 11:20:33PM +0100, Alexander Nasonov wrote:
> Joerg Sonnenberger wrote:
> > If this is intended for kernel use, why is it in src/external?
>
> There is an interest to use it as userspace library as well.
The kernel should not depend on anything outside src/common and src/sy
Joerg Sonnenberger wrote:
> The kernel should not depend on anything outside src/common and src/sys.
> It is acceptable for userland to access code from either place.
Is it done properly for solaris/zfs? I used as an example.
Alex
On Mon, Oct 01, 2012 at 11:52:00PM +0100, Alexander Nasonov wrote:
> Joerg Sonnenberger wrote:
> > The kernel should not depend on anything outside src/common and src/sys.
> > It is acceptable for userland to access code from either place.
>
> Is it done properly for solaris/zfs? I used as an exam
Joerg Sonnenberger wrote:
> AFAIK, zfs is module-only, e.g. it can't be compiled into the kernel.
sljit and bpfjit are modules too. But this may change later, e.g. if we
want to use bpfjit in a packet filter. I'll reimport sljit properly.
> It's a pretty bad example to start from. acpica is saner
On Tue, Oct 02, 2012 at 07:53:08AM +0100, Alexander Nasonov wrote:
> Joerg Sonnenberger wrote:
> > AFAIK, zfs is module-only, e.g. it can't be compiled into the kernel.
>
> sljit and bpfjit are modules too. But this may change later, e.g. if we
> want to use bpfjit in a packet filter. I'll reimpor
02.10.12, 11:13, "David Laight" ":
>
> It is plausibly possible to have the packet filter code call into
> a loadable jit module (module registers a function pointer vector).
This is what I do already.
>
> Doing that will make testing easier.
In general, yes, but it's not possible to unload the
On Tue, Oct 02, 2012 at 12:32:22AM +0200, Joerg Sonnenberger wrote:
> The kernel should not depend on anything outside src/common and src/sys.
> It is acceptable for userland to access code from either place.
The basic idea of src/external was good - however, the split into
various "externals" (li
On Tue, Oct 02, 2012 at 09:43:39AM +0200, Martin Husemann wrote:
> On Tue, Oct 02, 2012 at 12:32:22AM +0200, Joerg Sonnenberger wrote:
> > The kernel should not depend on anything outside src/common and src/sys.
> > It is acceptable for userland to access code from either place.
>
> The basic idea
Date: Tue, 2 Oct 2012 09:43:39 +0200
From: Martin Husemann
The basic idea of src/external was good - however, the split into
various "externals" (like src/external, src/crypto/external,
src/sys/external) makes it a pain. One very painfull example is ipf, it
is split into src/ext
On Tue, Oct 02, 2012 at 09:43:39AM +0200, Martin Husemann wrote:
> Either we want standalone kernel source (then common should die or at least
> move below src/sys), or we do not care, in which case src/external for
> everything should be fine.
src/common should be moved to src/sys/common; how
In article <20121002170622.ga13...@netbsd.org>,
David Holland wrote:
>On Tue, Oct 02, 2012 at 09:43:39AM +0200, Martin Husemann wrote:
> > Either we want standalone kernel source (then common should die or at least
> > move below src/sys), or we do not care, in which case src/external for
> > ev
In article ,
Christos Zoulas wrote:
>In article <20121002170622.ga13...@netbsd.org>,
>David Holland wrote:
>>On Tue, Oct 02, 2012 at 09:43:39AM +0200, Martin Husemann wrote:
>> > Either we want standalone kernel source (then common should die or at least
>> > move below src/sys), or we do not ca
> Joerg Sonnenberger wrote:
> > AFAIK, zfs is module-only, e.g. it can't be compiled into the kernel.
>
> sljit and bpfjit are modules too. But this may change later, e.g. if we
> want to use bpfjit in a packet filter. I'll reimport sljit properly.
unless there is a legal matter, please make sur
On Feb 22, 4:19am, Martin Husemann wrote:
} On Tue, Oct 02, 2012 at 12:32:22AM +0200, Joerg Sonnenberger wrote:
} > The kernel should not depend on anything outside src/common and src/sys.
} > It is acceptable for userland to access code from either place.
}
} The basic idea of src/external was g
19 matches
Mail list logo
