From owner-freebsd-questions Mon Aug 7 23:20:48 2000 Delivered-To: freebsd-questions@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id B406D37BA2F; Mon, 7 Aug 2000 23:20:43 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id XAA01130; Mon, 07 Aug 2000 23:20:41 -0700 Message-ID: <398FA6B9.45E9D1C2@urx.com> Date: Mon, 07 Aug 2000 23:20:41 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: marcel@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: what is the correct invocation of config so that module dependencies.. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > I have /tstsys as a real directory. > > It turns out that /usr/src/sys is indeed a symlink to /space/sys, > > But /tstsys is still referring to things from /usr/src/sys (realpath, > /space/sys). Broken. I have a tendancy to stay with defaults because if anything like that is going to happen, they try it on me first. I hadn't seen anything like that. Looks like they have a hard link somewhere and Murphy got you instead :). The only thing I tried was linking src/ and obj/ to different HD's to see if concurrent I/O made any difference. The time it saved was just about the time it took to set up the links and produced a net zero savings. Kent > > On Mon, 7 Aug 2000, Kent Stewart wrote: > > > > > > > Matthew Jacob wrote: > > > > > > This is -current, everything up to date... > > > > > > ..come out of the sys that is being built- not /usr/src/sys? > > > > > > I have a sys module, /tstsys. I configure kernels in it, and the modules > > > *always* have depencies out of /usr/src/sys (which gets out of date). > > > > > > This is really broken, isn't it? > > > > Not from what I see. You had some shortcuts in and now you are seeing > > the real path. There are some "you cannot's", i.e., build a kernel > > after a source update without building your world at the same time. > > > > I have some short cuts and what I have is > > > > ruby# pwd > > /usr/src/sys/i386/conf > > ruby# ruby > > ruby# pwd > > /usr/src/sys/compile/RUBY > > > > For example, if you did the following, you can see where you ended up. > > > > ruby# cd /sys > > ruby# pwd > > /usr/src/sys > > > > This has been true since I started using FreeBSD 2.2.8. > > > > Kent > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > > > -- > > Kent Stewart > > Richland, WA > > > > mailto:kbstew99@hotmail.com > > http://kstewart.urx.com/kstewart/index.html > > FreeBSD News http://daily.daemonnews.org/ > > > > Bomber dropping fire retardant in front of Hanford Wild fire. > > http://kstewart.urx.com/kstewart/bomber.jpg > > -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message