Re: Sharing the same VM address space between Kernel and UserSpace

2005-11-15 Thread Peter Jeremy
On Mon, 2005-Nov-14 13:39:19 -0700, John Giacomoni wrote: >I am in need of a way to share memory between kernel space and possibly >multiple different user-space processes for an extended period of time. >This memory would need to be a single unpageable region. Does the region have to have the sam

Re: Sharing the same VM address space between Kernel and UserSpace

2005-11-15 Thread Robert Watson
On Tue, 15 Nov 2005, Peter Jeremy wrote: Avoiding other mappings isn't that difficult, though it's not totally trivial. You need to avoid KVA, stack, text, heap, shared libraries, SysV SHM and other random mmap()'s. If this is a fairly custom application, you can get a fairly good idea of w

Re: Sierra Wireless / AC775 / Loading an external cisfile as a 'quirck'

2005-11-15 Thread Dirk-Willem van Gulik
After a hint from Warner - with the quirck from OpenBSD, see below; I am getting the AC775 nicely detected and showing sensible values; but the attaching of the expected sio(4) driver failes with a: pccard0: check_cis_quirks pccard0: using CIS quirks for Sierra Wireless, AC775, ED

Re: SSH From within a Jail

2005-11-15 Thread d c
Koen Martens <[EMAIL PROTECTED]> wrote: Koen Martens wrote: > d c wrote: > >>Greetings: >> >>I currently am running Freebsd 6.0 Release. >> >>I am experimenting with jails and have run into a >>problem. I need to ssh from within my jail to another >>server. Actually I need to use scp. WHen I t

Config options

2005-11-15 Thread Maslan
hi hackers, i would appreciate if any one told me how to : 1- add a new option for config. 2- disable an option without removing it. 3- re-enable a disabled option. thanks alot -- I'm Searching For Perfection, So Even If U Need Portability U've To Use Assembly ;-) http://libosdk.berlios.de http://

Works: Sierra Wireless / AC775 / Loading an external cisfile as a 'quick'

2005-11-15 Thread Dirk-Willem van Gulik
For reasons unclear to me; the standard sio0 address 0x3f8 gets in the way even if there is absolutely nothing on that address. It is almost as if the BIOS wispers it in the ear of the kernel even when disabled. Not sure where the kernel gets this from. But in any case; moving it up to the COM3 a