Date: Fri, 29 Nov 2002 09:20:52 +0300 From: Fred Souza <cseg@storming.org> To: Yury Tarasievich <grog@grsu.by> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vnconfig Message-ID: <20021129062052.GA20364@torment.storming.org> In-Reply-To: <20021129094708.GC408@deptty.in.grsu.by> References: <200211282309.SAA95904@corp.e-scape.net> <20021129094708.GC408@deptty.in.grsu.by>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi, Hello > Regarding vn subsystem: since about 4.6-RELEASE vnconfig -d no longer disables /dev/vn entry. > That means that... > > vnconfig -e /dev/vn<something> <file> > vnconfig -d /dev/vn<something> > vnconfig -e /dev/vn<something> <anotherfile> > > ....gives vnconfig: VNIOCATTACH: Devise busy... > and only kldunload vn helps. Actually, it does disable it (or at least, using the same words from the manpage, if it's possible). Your problem most likely is that -d only disables the device, but does not "unconfigure" it. Try using the -u flag instead of -d, it'll do both things for you. Fred -- "Beware of friends who are false and deceitful." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021129062052.GA20364>