From owner-freebsd-questions@FreeBSD.ORG Thu Jul 10 13:11:50 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CAB937B401 for ; Thu, 10 Jul 2003 13:11:50 -0700 (PDT) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 791CE43F93 for ; Thu, 10 Jul 2003 13:11:49 -0700 (PDT) (envelope-from stanb@panix.com) Received: from panix.com (brillig.panix.com [166.84.1.76]) by mail1.panix.com (Postfix) with ESMTP id ED5D1487C0 for ; Thu, 10 Jul 2003 16:11:48 -0400 (EDT) Received: from teddy.fas.com (pcp01010374pcs.mplsnt01.sc.comcast.net [68.58.176.69]) by panix.com (Postfix) with ESMTP id B7BC52AA38 for ; Thu, 10 Jul 2003 16:11:48 -0400 (EDT) Received: from stan by teddy.fas.com with local (Exim 3.36 #1 (Debian)) id 19ahlc-0006sd-00 for ; Thu, 10 Jul 2003 16:11:48 -0400 Date: Thu, 10 Jul 2003 16:11:48 -0400 From: stan To: Free BSD Questions list Message-ID: <20030710201148.GB26310@teddy.fas.com> Mail-Followup-To: Free BSD Questions list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.21 X-Uptime: 16:05:00 up 24 days, 3:07, 2 users, load average: 0.00, 0.01, 0.00 User-Agent: Mutt/1.5.4i Sender: Stan Brown Subject: Mounting a Samab share at boot time X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2003 20:11:50 -0000 I've got a boot up timing race issue. Here is what I'm trying to do. I want to mount a Samba share from a remote machine on boot up. Presently I have the appropriate entry in /etc/fsatb, such that I can mount the share _once I am in multiuser_. I have figured out how to get the smbfs kernel module loaded at boot time, using /boot/loader.conf. However, it appears that the remaining problem is that the NIC is not yet configured when the startup scripts try to mount the file systems. Therefore the system drops to a shell prompt since it can't mount _all_ the file systems. Seems like this issue would exist for NFS file systems that were staticly mount (as opposed to automonted). How can I get around this? -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin