From owner-freebsd-hackers Tue Jun 9 13:45:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01625 for freebsd-hackers-outgoing; Tue, 9 Jun 1998 13:45:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01028; Tue, 9 Jun 1998 13:42:53 -0700 (PDT) (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 cc: mike@smith.net.au, itojun@itojun.org, core@FreeBSD.ORG, hackers@FreeBSD.ORG, tech-jp@jp.freebsd.org Subject: Re: new config 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 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> In article <199806090414.VAA00467@antipodes.cdrom.com>, > Mike Smith 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message