NAKAGAWA Yoshihisa wrote: > > > Then explain to us why newbus is wrong and why the 4.4BSD scheme is > > right. > > Because, you are misunderstanding 4.4BSD scheme (and newconfig).
The *GOAL* here is the following: You bought a computer with the super-ultra-new Microsoft (tm) Microsoft Bus (tm), for which you bought the latest and greatest device X. Now, you want device X to work. Your FreeBSD 4.5 doesn't know about Microsoft Bus, much less about device X. As it happens, this Microsoft Bus is actually mounted through USB, which happens to be available through an CardBus device, which is actually mounted on a PCI card providing the bus. What you *must* achieve is the following: cd /modules fetch http://www.microsoft.com/FreeBSD/drivers/yeah.sure./msbus.ko fetch http://www.company.x.com/drivers/deviceX/x.ko kldload x results in the msbus being loaded on demand, located and mounted across the assorted bridges, and device X driver then getting loaded, having it's resources automatically set up, and becoming available for use. No kernel recompiling of file editing can be added to above sequence, and other files should be kept to the minimum possible (strictly -- if it can be done with less, it should be done with less). The newconfig opponents fear that one must edit some file to add the information that x must be mounted over msbus, or even worse (such as kernel recompiling). If you can show that the four lines above would suffice in newconfig, you got a winner. Feel free to change the kldload x to dconfig x if you like, but 'dconfig x "at msbus"' will not be well received. -- Daniel C. Sobral (8-DCS) d...@newsguy.com d...@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
