Re: mmap bug
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, residual changing to 64kB. Juha To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: mmap bug
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, residual changing to 64kB. Juha To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposing argv for klds and preloaded modules
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 just this reason, filewide argument string. I didn't know any plans were already made on these circles, had only buggered Mr. Rabson once about arguments. Well, no harm done, I hope. Juha To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposing argv for klds and preloaded modules
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 just this reason, filewide argument string. I didn't know any plans were already made on these circles, had only buggered Mr. Rabson once about arguments. Well, no harm done, I hope. Juha To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposing argv for klds and preloaded modules
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. Search for strbuf Juha To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposing argv for klds and preloaded modules
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. Search for strbuf Juha To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposing argv for klds and preloaded modules
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 argument. > >Is this really a problem? Can the administrator not use > sysctl instead? Yes, but (this might be a trademark ;) commonly the arguments would be used during the sysinit->attach, and at that time sysctl has not yet been able to change anything. Use of sysctl would require a sidestep from attach and later continuation with a sysctl_proc. Not a problem, but inconvenient, IMHO. And it's analogous to executing, they too can get arguments. Juha To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposing argv for klds and preloaded modules
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 argument. > >Is this really a problem? Can the administrator not use > sysctl instead? Yes, but (this might be a trademark ;) commonly the arguments would be used during the sysinit->attach, and at that time sysctl has not yet been able to change anything. Use of sysctl would require a sidestep from attach and later continuation with a sysctl_proc. Not a problem, but inconvenient, IMHO. And it's analogous to executing, they too can get arguments. Juha To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Proposing argv for klds and preloaded modules
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 in okldload(pathname). Modules can call module_get_file_argstr(mod) to get these arguments if they so prefer, this is the same with preloaded/kldloaded cases. The third argument, struct kldload, is unused. Arguments are catted together, blank separated, this was the existing way preloading did it (subject to change ?). Patches are against a recent (week ?) -CURRENT, original and modified files are also available. Juha http://qn-lpr2-165.quicknet.inet.fi:22/kldargs/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Proposing argv for klds and preloaded modules
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 in okldload(pathname). Modules can call module_get_file_argstr(mod) to get these arguments if they so prefer, this is the same with preloaded/kldloaded cases. The third argument, struct kldload, is unused. Arguments are catted together, blank separated, this was the existing way preloading did it (subject to change ?). Patches are against a recent (week ?) -CURRENT, original and modified files are also available. Juha http://qn-lpr2-165.quicknet.inet.fi:22/kldargs/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
