From owner-FreeBSD-tech-jp@jp.freebsd.org  Wed Jun 10 05:43:40 1998
Received: (from daemon@localhost)
	by jaz.jp.freebsd.org (8.8.8+3.0Wbeta13/8.7.3) id FAA09362;
	Wed, 10 Jun 1998 05:43:40 +0900 (JST)
	(envelope-from owner-FreeBSD-tech-jp@jp.FreeBSD.org)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
	by jaz.jp.freebsd.org (8.8.8+3.0Wbeta13/8.7.3) with ESMTP id FAA09356
	for <tech-jp@jp.freebsd.org>; Wed, 10 Jun 1998 05:43:34 +0900 (JST)
	(envelope-from mike@antipodes.cdrom.com)
Received: from antipodes.cdrom.com (localhost [127.0.0.1])
	by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id FAA02437;
	Tue, 9 Jun 1998 05:39:32 -0700 (PDT)
Message-Id: <199806091239.FAA02437@antipodes.cdrom.com>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Atsushi Furuta <furuta@sra.co.jp>
cc: mike@smith.net.au, itojun@itojun.org, core@FreeBSD.org,
        hackers@FreeBSD.org, tech-jp@jp.freebsd.org
In-reply-to: Your message of "Tue, 09 Jun 1998 15:57:46 +0900."
             <199806090657.PAA27116@sras63.sra.co.jp> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 09 Jun 1998 05:39:32 -0700
From: Mike Smith <mike@smith.net.au>
Reply-To: FreeBSD-tech-jp@jp.freebsd.org
Precedence: bulk
X-Distribute: distribute [version 2.1 (Alpha) patchlevel=24]
X-Sequence: FreeBSD-tech-jp 1511
Subject: [FreeBSD-tech-jp 1511] Re: new config 
Errors-To: owner-FreeBSD-tech-jp@jp.freebsd.org
Sender: owner-FreeBSD-tech-jp@jp.freebsd.org

> >> In article <199806090414.VAA00467@antipodes.cdrom.com>,
> 	Mike Smith <mike@smith.net.au> writes:
> 
> > Newconfig imposes very strict hierarchical structure on the system, and 
> > whilst well-geared towards a static configuration, is much less well 
> > suited to dynamic operation (my evaluation only).  Bearing in mind that 
> > it has been at least a year since I had anything to do with newconfig, 
> > I'd be interested in more clarification.
> 
>   Please tell me your definition of "static/dynamic configuration" in
> this context.
> 
> My understanding:
> 
> 	static configuration -> to give parameters in compile time
> 	dynamic configuration -> to give parameters in boot time
> 
> Is this correct?

Close.

Static configuration bases everything on resources incorporated at 
compile time, yes.

Dynamic configuration uses resources available at run time; not just 
user input before/during the boot process.  In the context above, the 
key features of a "dynamic" approach include:

 - The ability to create/delete new instances of a driver.
 - The ability to create/delete new instances of a bus.
 - The ability to retain parametric hints for unknown driver
   instances.
 - The ability to obtain and manage resource information.
 - The ability to load/unload code supporting new devices/busses.

-- 
\\  Sometimes you're ahead,       \\  Mike Smith
\\  sometimes you're behind.      \\  mike@smith.net.au
\\  The race is long, and in the  \\  msmith@freebsd.org
\\  end it's only with yourself.  \\  msmith@cdrom.com


