> >>>>> On Wed, 12 May 1999 15:09:05 -0700, Mike Smith <m...@smith.net.au> said:
> 
> > It would appear that you don't understand the problem, as no 
> > configuration technique can telepathically determine in advance which 
> > new drivers you are going to load.
> 
> Apparently you misunderstand newconfig. :-)
> There is compiled format of "files" file which path is known by
> kernel.

Aha.  And the kernel has to read this file?  How does it read it if 
it's loading eg. the disk driver that it will be using to read the disk?

Why does the information have to be in this file?  Why not put it in 
the drivers themselves?

> >> The way on new-bus will cause compatibility problem when
> >> OS is upgraded, because the implementation (filename) may
> >> be changed between versions and versions.
> 
> > This is a transient implementation issue, the obsolecesnce of which is 
> > already manifest in the plans that have been laid for a device 
> > identifier to module to file lookup with the translation data _outside_ 
> > the kernel.
> 
> In other words, that is not compatible with the BSD way where FreeBSD
> and BSDI and NetBSD and OpenBSD already probed.

There is no "BSD way" anymore.  The "BSD way" was developed to support Unibus 
on the early Vax systems.

It's not clear to you that newbus does draw on ideas from newconfig.  
But newbus is a lot more than _just_ a new set of names for the probe/
configuration functions; it's a complete driver interface architecture. 
Newconfig is a good semi-static semi-dynamic configuration framework, 
but that's all it is.

> It is actually true that FreeBSD becomes Linux.

This is a childish troll, especially coming from you.  If for no other 
reason, this is an excellent reason _not_ to be working with your team.

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




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

Reply via email to