From owner-freebsd-questions Fri Nov 26 14:15: 5 1999 Delivered-To: freebsd-questions@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 355DF151F4 for ; Fri, 26 Nov 1999 14:15:01 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id OAA32337; Fri, 26 Nov 1999 14:09:17 -0800 (PST) Date: Fri, 26 Nov 1999 14:09:17 -0800 (PST) From: Annelise Anderson To: Christopher Michaels Cc: "FreeBSD Questions (E-mail)" Subject: Re: vnconfig on bootup? In-Reply-To: <6C37EE640B78D2118D2F00A0C90FCB4401105DBD@site2s1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Nov 1999, Christopher Michaels wrote: > Ok. I'm going to add to my own message, because I've done some digging > since I sent the original message. > > vnconfig is in /usr/sbin/. Which means (I'll assume) that "vnconfig -a" > cannot be called before "mount -a" is called. > > So now my problem becomes, can anyone think of a way to easily mount my vnX > devices after vnconfig -a has been called. I can add the appropriate lines > to an rc file if I had an idea of how to go about doing this. After mount -a has been called? You can put your commands in a script to be executed on boot in /usr/local/etc/rc.d. It needs to have the characteristics of any shell script--#!/bin/sh as the first line, and permissions that make it executable. Mine seem to be owned root:wheel. Alternatively, you can put such commands in /etc/rc.conf.local, which will be read if it exists (/etc/defaults/rc.conf includes instructions to read this file if it exists). > My current problem is that I have the entries in my /etc/fstab, but I have > to leave marked "noauto". If I do not the system will fail to boot with a > "Filesystem mount failed, startup aborted" error message. I'd take them out of fstab. You don't want a boot failing for this kind of reason. > Would there be a downside to copy/moving /usr/sbin/vnconfig to > /sbin/vnconfig, and then I could add the appropriate lines to an rc file? Yes. As you would see by running ldd /usr/sbin/vnconfig, vnconfig depends on some libraries; so the file system containing the libraries needs to be loaded for it to run. You could statically compile it so it does not depend on anything, but then it will take more memory and possibly produce some other problems. Annelise > Thanks to anyone who answers this, > -Chris > > > -----Original Message----- > > From: C J Michaels [SMTP:cjm2@earthling.net] > > Sent: Thursday, November 18, 1999 7:59 PM > > To: FreeBSD Questions > > Subject: vnconfig on bootup? > > > > Hi, > > I've been looking around and I can't seem to find a way to have the system > > to run vnconfig -a before mounting all the drives. > > > > I've searching the mailing lists archives, /etc/defaults/rc.conf, and the > > like. > > > > Anyone know if there is such a setting? > > > > Thanks, > > -Chris > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message