Re: mmap bug

1999-08-11 Thread Juha Nurmela
If the latter mmap.c is allowed to fill up filesystem, -current hangs in /kernel: pid 2 (pagedaemon), uid 0 on /: file system full /kernel: vnode_pager_putpages: I/O error 28 /kernel: vnode_pager_putpages: residual I/O 16384 at 880 ...repeating the last two lines, gradually increasing pindex, re

Re: mmap bug

1999-08-11 Thread Juha Nurmela
If the latter mmap.c is allowed to fill up filesystem, -current hangs in /kernel: pid 2 (pagedaemon), uid 0 on /: file system full /kernel: vnode_pager_putpages: I/O error 28 /kernel: vnode_pager_putpages: residual I/O 16384 at 880 ...repeating the last two lines, gradually increasing pindex, r

Re: Proposing argv for klds and preloaded modules

1999-08-03 Thread Juha Nurmela
On Tue, 3 Aug 1999, Peter Wemm wrote: > Don't forget, there are zero or more modules per file. Which one gets the > arguments? Coda (for example) is structured so that it has two modules, one > device (codadev) and one vfs (coda). Yes, the naming 'module_get_file_argstr()' had the _file_ for

Re: Proposing argv for klds and preloaded modules

1999-08-03 Thread Juha Nurmela
On Tue, 3 Aug 1999, Peter Wemm wrote: > Don't forget, there are zero or more modules per file. Which one gets the > arguments? Coda (for example) is structured so that it has two modules, one > device (codadev) and one vfs (coda). Yes, the naming 'module_get_file_argstr()' had the _file_ for

Re: Proposing argv for klds and preloaded modules

1999-08-03 Thread Juha Nurmela
On Tue, 3 Aug 1999, Daniel C. Sobral wrote: > Actually... Loader passes a string. It seems the kldcode is passing > argv[]. Juha, you sure you have they both working the same way (from > a module's perspective)? It's splatted together, by just putting ' ' between words, somewhere in there. Sea

Re: Proposing argv for klds and preloaded modules

1999-08-03 Thread Juha Nurmela
On Tue, 3 Aug 1999, Daniel C. Sobral wrote: > Actually... Loader passes a string. It seems the kldcode is passing > argv[]. Juha, you sure you have they both working the same way (from > a module's perspective)? It's splatted together, by just putting ' ' between words, somewhere in there. Sear

Re: Proposing argv for klds and preloaded modules

1999-08-01 Thread Juha Nurmela
On Sun, 1 Aug 1999, Chris Costello wrote: > On Sun, Aug 01, 1999, Juha Nurmela wrote: > > Sometimes it would be handy to pass a commandline > > to a kld, preloaded modules already support > > arguments. kldload(2) unfortunately has only > > the pathname.ko argumen

Re: Proposing argv for klds and preloaded modules

1999-08-01 Thread Juha Nurmela
On Sun, 1 Aug 1999, Chris Costello wrote: > On Sun, Aug 01, 1999, Juha Nurmela wrote: > > Sometimes it would be handy to pass a commandline > > to a kld, preloaded modules already support > > arguments. kldload(2) unfortunately has only > > the pathname.ko argumen

Proposing argv for klds and preloaded modules

1999-08-01 Thread Juha Nurmela
Hello. Sometimes it would be handy to pass a commandline to a kld, preloaded modules already support arguments. kldload(2) unfortunately has only the pathname.ko argument. Following url proposes patches to make a new syscall kldload(char *pathname, char **argv, struct kldload *) and keep old way

Proposing argv for klds and preloaded modules

1999-08-01 Thread Juha Nurmela
Hello. Sometimes it would be handy to pass a commandline to a kld, preloaded modules already support arguments. kldload(2) unfortunately has only the pathname.ko argument. Following url proposes patches to make a new syscall kldload(char *pathname, char **argv, struct kldload *) and keep old wa