I've been doing some work on a hierarchical jail setup, but I've got
this nagging feeling it's been done before. Does anyone know of such
an existing project? If not, I'll put forward my own code.
- James Gritton
[EMAIL PROTECTED]
___
Pawel Jakub Dawidek wrote:
Something like this:
http://garage.freebsd.pl/mljail.README
I did it some time ago, and this is one of the feature for new jail
implementation with is beeing designed
Yes, that's just the thing I'm talking about, so it looks like I have
indeed be reinventing
please please please familiarise yourself with the Vimage code that
Marko Zec is working on.
This is the stuff at http://imunes.tel.fer.hr/virtnet/, right? I take
it that's the definitive place to go. I recall having looked at that
before, and I guess I was thrown off by the "net work virtua
John Baldwin wrote:
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a
specific (although mundane) hardware configuration, and each of several
servers runnin
John Baldwin wrote:
On Thursday 19 June 2008 11:57:51 am James Gritton wrote:
John Baldwin wrote:
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The dea
ing a
page? I see some things in the VM code that look like recerence counts
(such as act_count in struct vm_page), but they don't seem to really be
such, or at least they don't count what I'm expecting them to.
This is on 4.7. I haven't really looked at 5, so I don't know
Julian Elischer <[EMAIL PROTECTED]> writes:
> check out /proc//map for a really detailed map of the process.
That looks good for a single process, suffers from the problem I'm
having. For example, if I run a program that simply mallocs a chumk of
memory and reads through it (to map it all in)
Matthew Dillon <[EMAIL PROTECTED]> writes:
> You can also theoretically push into shadow VM objects to locate
> pages from the parent process that have not yet been COW'd into the
> child (in the case of a fork()), noting also that these shadow objects
> might be shared with other
Matthew Dillon <[EMAIL PROTECTED]> writes:
> Then you simply group all the processes which share VM
> objects together and report statistics on a group-by-group basis
> rather then on a process-by-process basis. You won't know what an
> individual process uses but you know exactly
After playing with a few encrypted filesystems, and giving up on them (after
a kernel crash or two), I went looking for something else to encrypt. The
logical choice is the device.
Well, the virtual device. Like a cryptfs that's based on a loopback mount,
I'm encrypting a virtual device based o
"Daniel O'Connor" <[EMAIL PROTECTED]> writes:
> Have you seen ports/security/vncrypt?
Oops :-). I never was very good at looking to see what's out there. It
looks good - it apparently supports different crypto algorithms and isn't
broken WRT labels. Oh well, I can still call mine the poor
11 matches
Mail list logo
