From owner-freebsd-stable  Tue Mar 20 23:55:11 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80])
	by hub.freebsd.org (Postfix) with ESMTP id CE39137B71E
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Mar 2001 23:55:03 -0800 (PST)
	(envelope-from eugen@svzserv.kemerovo.su)
Received: from svzserv.kemerovo.su (kost.svzserv.kemerovo.su [213.184.65.82])
	by www.svzserv.kemerovo.su (8.9.3/8.9.3) with ESMTP id OAA55007
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Mar 2001 14:55:01 +0700 (KRAT)
	(envelope-from eugen@svzserv.kemerovo.su)
Message-ID: <3AB85E53.CE88E841@svzserv.kemerovo.su>
Date: Wed, 21 Mar 2001 14:54:59 +0700
From: Eugene Grosbein <eugen@svzserv.kemerovo.su>
Organization: SVZServ
X-Mailer: Mozilla 4.76 [en] (Win95; U)
X-Accept-Language: ru,en
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.ORG
Subject: 'make release' breaks vn0
References: <3AB813C3.82638C88@svzserv.kemerovo.su>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi!

I keep vn0 used for mounting an ISO image (it's contents is mounted
on /var/ftp/pub/... for downloads) and had experience with
PicoBSD which detects next free vn? number so did not bother to check
'make release'. And it finished it's work. After that I found that it
destroyed my vn0 configuration. I'm forced to use 'umount -f' to free
mount point than do vnconfig and mount to restore running system.
Finally I found that this can be avoided using 
make release VNDEVICE=vn1 ...

This should be documented (f.e. in the FAQ when 'make release is explained)
or, better, changed to detect free vn node.

Now, is built release correct?

Eugene Grosbein

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message