From owner-freebsd-current  Thu May  2 15:12:36 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA00479
          for current-outgoing; Thu, 2 May 1996 15:12:36 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA00472
          for <freebsd-current@FreeBSD.org>; Thu, 2 May 1996 15:12:32 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id IAA00812; Fri, 3 May 1996 08:10:14 +1000
Date: Fri, 3 May 1996 08:10:14 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199605022210.IAA00812@godzilla.zeta.org.au>
To: bde@zeta.org.au, julian@ref.tfs.com
Subject: Re: execve
Cc: chuckr@Glue.umd.edu, freebsd-current@FreeBSD.org,
        joerg_wunsch@uriah.heep.sax.de, terry@lambert.org
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> struct.  There would have to be declarations in files[.machine] to tell
>> config what to emit.  E.g.,
>> 
>> kern_imgact.c	standard	TEXT_SET(execsw_set, aout_execsw)
>> ...
>what about files that need to have multiple linker sets..
>(there are a few)

foo.c	standard	TEXT_SET(bar_set, func_1)
...
foo.c	standard	DATA_SET(baz_set, obj_1)
...

This leads to my next topic :-).  There shouldn't be any such files because
they don't work as lkm's.  For lkm's there should be a single entry point
that registers all the necessary objects and functions:

void foo_init(void *arg)
{
	register_bar_func(func_1);
	...
	register_baz_obj(obj_1);
	...
}

Bruce