Re: Create linker.hints at boot

2003-03-18 Thread Doug Barton
On Mon, 17 Mar 2003, Crist J. Clark wrote: > On Mon, Mar 17, 2003 at 01:07:53PM -0800, David O'Brien wrote: > > On Mon, Mar 17, 2003 at 12:43:19PM -0800, Crist J. Clark wrote: > > > On Mon, Mar 17, 2003 at 09:11:12AM -0800, David O'Brien wrote: > > > > On Mon, Mar 17, 2003 at 12:28:34AM -0800, Cri

Re: Create linker.hints at boot

2003-03-18 Thread der_julian
On 17-Mar-2003 Crist J. Clark wrote: >> >> if (!strcmp(a,b) { >> printf("same\n"); >> } > > I don't see what that code snipit has to do with the script (but I am > in the camp that would go ahead and waste the four bytes of source > code to write that as (strcmp(a, b) == 0)). Th

Re: Create linker.hints at boot

2003-03-17 Thread Crist J. Clark
On Mon, Mar 17, 2003 at 01:07:53PM -0800, David O'Brien wrote: > On Mon, Mar 17, 2003 at 12:43:19PM -0800, Crist J. Clark wrote: > > On Mon, Mar 17, 2003 at 09:11:12AM -0800, David O'Brien wrote: > > > On Mon, Mar 17, 2003 at 12:28:34AM -0800, Crist J. Clark wrote: > > > > +kldxref_start () { > > >

Re: Create linker.hints at boot

2003-03-17 Thread David O'Brien
On Mon, Mar 17, 2003 at 12:43:19PM -0800, Crist J. Clark wrote: > On Mon, Mar 17, 2003 at 09:11:12AM -0800, David O'Brien wrote: > > On Mon, Mar 17, 2003 at 12:28:34AM -0800, Crist J. Clark wrote: > > > +kldxref_start () { > > > + if [ -z "$kldxref_module_path" ]; then > > > + MODULE_PATHS=

Re: Create linker.hints at boot

2003-03-17 Thread Crist J. Clark
On Mon, Mar 17, 2003 at 09:11:12AM -0800, David O'Brien wrote: > On Mon, Mar 17, 2003 at 12:28:34AM -0800, Crist J. Clark wrote: > > +kldxref_start () { > > + if [ -z "$kldxref_module_path" ]; then > > + MODULE_PATHS=`sysctl -n kern.module_path` > > + else > > + MODULE_PATHS

Re: Create linker.hints at boot

2003-03-17 Thread David O'Brien
On Mon, Mar 17, 2003 at 12:28:34AM -0800, Crist J. Clark wrote: > +kldxref_start () { > + if [ -z "$kldxref_module_path" ]; then > + MODULE_PATHS=`sysctl -n kern.module_path` > + else > + MODULE_PATHS="$kldxref_module_path" > + fi Please change the logic to posi

Re: Create linker.hints at boot

2003-03-17 Thread Daniel C. Sobral
Daniel C. Sobral wrote: Crist J. Clark wrote: Perhaps it would be a good idea to build a linker.hints file with kldxref(8) at boot time. At least, I can't think of any really good reasons why _not_ to do it. [...] This is my first stab at rc-ng for a long while, so please be gentle if I've not ha

Re: Create linker.hints at boot

2003-03-17 Thread Daniel C. Sobral
Crist J. Clark wrote: Perhaps it would be a good idea to build a linker.hints file with kldxref(8) at boot time. At least, I can't think of any really good reasons why _not_ to do it. [...] This is my first stab at rc-ng for a long while, so please be gentle if I've not handled that the best way. P

Re: Create linker.hints at boot

2003-03-17 Thread Daniel C. Sobral
Crist J. Clark wrote: Also, what's the best way/is there a way to figure out the boot directory rather than hardwire /boot/kernel? dirname `sysctl -n kern.bootfile` -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fon

Re: Create linker.hints at boot

2003-03-17 Thread Marcel Moolenaar
On Mon, Mar 17, 2003 at 12:28:34AM -0800, Crist J. Clark wrote: > > Index: src/etc/rc.d/kldxref > === > RCS file: src/etc/rc.d/kldxref > diff -N src/etc/rc.d/kldxref > --- /dev/null 1 Jan 1970 00:00:00 - > +++ src/etc/rc.d/kldxref

Re: Create linker.hints at boot

2003-03-17 Thread Crist J. Clark
On Fri, Mar 14, 2003 at 07:27:42PM -0800, Peter Wemm wrote: > "Crist J. Clark" wrote: > > > > --C7zPtVaVf+AK4Oqc > > Content-Type: text/plain; charset=us-ascii > > Content-Disposition: inline > > > > Perhaps it would be a good idea to build a linker.hints file with > > kldxref(8) at boot time. At

Re: Create linker.hints at boot

2003-03-14 Thread Peter Wemm
"Crist J. Clark" wrote: > > --C7zPtVaVf+AK4Oqc > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > Perhaps it would be a good idea to build a linker.hints file with > kldxref(8) at boot time. At least, I can't think of any really good > reasons why _not_ to do it. Yes,