Date: Fri, 26 Nov 1999 17:31:22 -0500 From: Christopher Michaels <ChrisMic@clientlogic.com> To: 'Annelise Anderson' <andrsn@andrsn.stanford.edu> Cc: "FreeBSD Questions (E-mail)" <questions@FreeBSD.ORG> Subject: RE: vnconfig on bootup? Message-ID: <6C37EE640B78D2118D2F00A0C90FCB4401105DBE@site2s1>
next in thread | raw e-mail | index | archive | help
In other words, w/o making a script that explicitly mounts each mount point, it can't be done. This much I already know how to do, I was hoping for some level of automation. Just incase I feel like playing with this. Can you (or someone else) give me some pointers as to how to statically compile vnconfig (or any program for that matter). Thank you, -Chris > -----Original Message----- > From: Annelise Anderson [SMTP:andrsn@andrsn.stanford.edu] > Sent: Friday, November 26, 1999 5:09 PM > To: Christopher Michaels > Cc: FreeBSD Questions (E-mail) > Subject: Re: vnconfig on bootup? > > > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6C37EE640B78D2118D2F00A0C90FCB4401105DBE>