In message <pine.bsf.3.95.990514121818.24898a-100...@current1.whistle.com>, Julian Elischer writes: > >On Fri, 14 May 1999, Luoqi Chen wrote: > >> > > This was due to a kludge in mfs implementation. Try change NUMCDEV in >> > > kern_conf.c to 255. >> > >> > Are you saying that there is a bug in the mfs implementation and a fix >> > will be commited soon? (and change NUMCDEV until then) >> > >> > Or are you saying, the mfs implementation is now considered correct (but >> > there are some kludges in there) and that changing NUMCDEV in kern_conf.c >> > to 255 is the perminate fix? >> > >> > -- >> > -- David (obr...@nuxi.com -or- obr...@freebsd.org) >> > >> This is a fundamental problem with mfs' design, mfs steals bdev major 255 for >> its private use. One thing we could do is to have mfs legally acquire this >> major number, i.e., setup a devsw structure and register with device conf >> system. This problem probably would go away after we have a fully functional >> DEVFS. > >Actually this problem is the one that makes DEVFS explode.. >It does an alias lookup on it's 'dummy' vnode and since teh sytem has been >switched to use devfs routines for everything, some of it's >assumptions are not longer true..
I don't expect the current DEVFS prototype to be indicative of how our real DEVFS will work. -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
