From owner-freebsd-current Sun Oct 18 22:59:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22679 for freebsd-current-outgoing; Sun, 18 Oct 1998 22:59:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles338.castles.com [208.214.167.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22674 for ; Sun, 18 Oct 1998 22:59:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA16555; Sun, 18 Oct 1998 22:58:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810190558.WAA16555@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: Peter Wemm , Nik Clayton , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-reply-to: Your message of "Sun, 18 Oct 1998 23:30:58 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Oct 1998 22:58:13 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If I do the getvfsbyname method, I do no pattern-matching at all > (FreeBSD does that for me). When I do the lookup, the data is good at > that point, isn't it, even in the face of the vfs or KLD loads/unloads, > right? And, as long as I do no dismounting (the fs is up) that number > can't change on me. The *set* of available numbers and their mappings > can change, but not the one I'm sitting on, right? That's correct; a VFS can't be unloaded while it's referenced. > I'd stop doing that, if I trusted that the statfs f_fstypename was > reliably being set. It's too new, and I haven't found where it's > getting set, no matter how much I search for it. You can probably count on it. If you can't, that's *definitely* a bug. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message