On Sat, Aug 21, 1999 at 04:30:57PM +1000, Bruce Evans wrote:
> >Hmmm, I know this is your code, but are you sure? 8-). My understanding of
> >dkmodslice() and friends is that they manipulate dev_t entries, but don't
> >actually initialise them. Since the subr_diskslice code takes a dev_t
>
> dkmodslice() once just manipulated bits in dev_t scalars. Now that dev_t
> is a pointer, dkmodslice() has to create something for the pointer to
> point to. That something needs to be fully initialised and not created
> more than once. The initialisation is apparently incomplete. Multiple
> creation is avoided by searching the list of previously created entries.
I agree that something has to create something for the dev_t pointer to
point to, but I thought that it would be the device code that would
do that. I've only looked at this from the perspective of vn, since
that is what is biting me 8-).
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
