Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 May 1999 01:32:56 +0900 (JST)
From:      Noriyuki Soda <soda@sra.co.jp>
To:        Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc:        Tomoaki NISHIYAMA <tomoaki@biol.s.u-tokyo.ac.jp>, rwhitesel@nbase-xyplex.com, soda@sra.co.jp, current@FreeBSD.ORG
Subject:   Re: cvs commit: src/sys/pci pcisupport.c 
Message-ID:  <199905121632.BAA23027@srapc342.sra.co.jp>
In-Reply-To: <5756.926523945@critter.freebsd.dk>
References:  <19990513003825D.tomoaki@moss.nibb.ac.jp> <5756.926523945@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Wed, 12 May 1999 17:45:45 +0200,
	Poul-Henning Kamp <phk@critter.freebsd.dk> said:

>> What is the definition of "config"?

> 	config(8)

>> Why do you want to remove it?

> Why should we, as a 3rd millenium OS need a static config tool ?

For example,

- To specify the drivers which is linked statically to kernel.
  As I said earlier, you cannot link console driver dynamically,
  If you do this, you cannot get error message when dynamic
  linking of the console driver failed.

- There should be a way to inform kernel about inter module dependency
  dynamically. config(8) converts this information to a file which is
  kernel readable format.

- There should be a way to inform kernel about mapping from device
  name to driver filename dynamically. config(8) converts this
  information to a file which is kernel readable format.

- To achieve better performance in both UP and SMP cases.
  Proper SMP implementation requires fine grained locking, though this
  increases performance penalty in UP case.  (e.g. Solaris shows this
  problem.)  Thus, the way to specify "options SMP" is needed to use
  (static) source level and compiler level optimization.
  This option should automatically select the appropriate sources
  which is compiled into kernel, according to the source is needed
  only in UP case, or only in SMP case, or both. This is what
  oldconfig and newconfig does.

The new-bus doesn't have these features.

> We are working on FreeBSD as a OS for the future, not for the past.

Of course!
We never should go back to the age of 1979 (i.e. before 4.0BSD).
--
soda


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905121632.BAA23027>