| shouldn't be too hard though, but even then there are seriously non-trivial | differences in the tty, block/character devices, VM, networking, etc. Even | if the config interface was compatable it wouldn't ever be a 'drop in' | option, even with 'newconfig'.
In strongly system-dependent part, even if newconfig, it is required many source change. But *BSD difference is smaller than other OSes. Except for static configuration and module dependency resolvation, I feel new-bus and newconfig have the same possibility. So new-bus seems to `re-invent the wheel'. Why not improve 4.4BSD newconfig? Except for FreeBSD, almost all the drivers are newconfig. (FreeBSD's oldconfig should die) What is merit of new-bus? Identity? current newconfig code don't support dynamic configuration. but this is not newconfig potential. Furuta and I intend to code it. --- UCHIYAMA Yasushi u...@nop.or.jp To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
