From owner-freebsd-arch@FreeBSD.ORG  Sat Jul  5 06:57:31 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D73DE37B401
	for <freebsd-arch@freebsd.org>; Sat,  5 Jul 2003 06:57:31 -0700 (PDT)
Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0F31243FE9
	for <freebsd-arch@freebsd.org>; Sat,  5 Jul 2003 06:57:31 -0700 (PDT)
	(envelope-from vova@vbook.fbsd.ru)
Received: from vova by vbook.fbsd.ru with local (Exim 4.20)
	id 19YnXz-0000Mf-Iz; Sat, 05 Jul 2003 17:57:51 +0400
From: "Vladimir B. Grebenschikov" <vova@fbsd.ru>
To: Ian Dowse <iedowse@maths.tcd.ie>
In-Reply-To: <200306282254.aa83607@salmon.maths.tcd.ie>
References: <200306282254.aa83607@salmon.maths.tcd.ie>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: quoted-printable
Organization: SWsoft Inc.
Message-Id: <1057413470.716.3.camel@localhost>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.0 
Date: 05 Jul 2003 17:57:51 +0400
Sender: Vladimir Grebenschikov <vova@vbook.fbsd.ru>
cc: freebsd-arch@freebsd.org
Subject: Re: Unmounting by filesystem ID
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jul 2003 13:57:32 -0000

=F7 Sun, 29.06.2003, =D7 01:54, Ian Dowse =D0=C9=DB=C5=D4:
> The patch below adds a new mount flag MNT_BYFSID that can be used
> to unmount a filesystem by specifying its filesystem ID instead of
> a path. The umount utility is changed to use this mechanism by
> default. This approach has a number of advantages:

Cool!

May be you fix issue of umounting by known vnode ?
problem is in mounting different devices under chroot.
in list of mounts they differ only by device id, and it is rather=20
difficult to umount filesystem if I known absolute path but do not enter
to chroot.


--=20
Vladimir B. Grebenschikov <vova@fbsd.ru>
SWsoft Inc.