From owner-freebsd-current Wed Jan 12 6:46: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 6A74214D8D for ; Wed, 12 Jan 2000 06:46:07 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id JAA77998; Wed, 12 Jan 2000 09:45:56 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001121445.JAA77998@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: Martin Blapp , "Rodney W. Grimes" , current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: move portmap(8) from /usr/sbin to /sbin References: <200001120846.AAA68588@apollo.backplane.com> In-reply-to: Your message of "Wed, 12 Jan 2000 00:46:15 PST." <200001120846.AAA68588@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 09:45:56 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's all this about loopback mounts in fstab about? What does > that have to do with diskless startup? I've got a loopback mount in /var/db/mounttab that looks like this: 946789037 localhost /null which is there because I run cfs (a crypto file system; see /usr/ports/security/cfs). Part of the cfs startup script does this: /usr/local/sbin/cfsd && mount -o port=3049,intr localhost:/null /crypt The problem is that when you boot, the invocation of 'rpc.umntall -k' hangs for a while trying to contact the mountd or portmapper on localhost. If it was smart enough to recognize an ICMP port unreachable error and move on, we wouldn't have this problem. It's not that I think moving mountd and portmap is necessarily a good idea; this is just one scenario which perhaps has prompted this line of thought. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message