From owner-freebsd-current Thu May 18 14:45:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 927EA37BAF2 for ; Thu, 18 May 2000 14:45:16 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA02688; Thu, 18 May 2000 23:11:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Edwards Cc: Nick Hibma , FreeBSD CURRENT Mailing List , wc.bulte@chello.nl, Maxim Sobolev Subject: Re: vn.ko load/unload/mount = panic In-reply-to: Your message of "Mon, 15 May 2000 13:06:14 BST." <391FE836.7DB49846@openet-telecom.com> Date: Thu, 18 May 2000 23:11:59 +0200 Message-ID: <2686.958684319@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <391FE836.7DB49846@openet-telecom.com>, Peter Edwards writes: >After reading the rest of the discussion on this thread, and moving out >of my depth a little, I assume vn should probably be using >disk_create()/disk_destroy(), and attaching its softc to the disk object >rather than the device object. (However, I suppose given the special >nature of vn, there might be reasons for not using this interface). > >I'll gladly "disk"ify vn as a mini- junior-kernel-hacker task if someone >indicates that it is needed, and if no one more qualified wants to do >it. Please go ahead, I'll review and test your patches. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message