Re: NFS /usr/src and /usr/obj?
On Wed, Jan 26, 2000 at 06:45:59PM -0600, [EMAIL PROTECTED] wrote:
Hi,
On Wed, 26 Jan 2000, Poul-Henning Kamp wrote:
I've done it in the past, but not recently.
Consider the alternative of mounting the destination on the compilehost
and make install DESTDIR=/mnt
Thanks to everyone for the replies. It works fine for me now. I was
automounting all of the directories from the server using AMD, and then
I had /usr/src and /usr/obj as symlinks to their respective automount
locations. This apparently was what was causing me problems. With
/usr/src and /usr/obj directly mounted themselves, the installworld is
proceeding as I type this.
I've run into this myself, but exacerbated by the fact that on my
"master" machine, /usr/{obj,src} are symlinks to /export/FreeBSD/{obj,src}
which are exported to the "slave" systems. Unfortunately, the "slaves"
need _write_ access to the /usr/obj image. I havn't tracked down the
exact details why, but there are a few things that don't seem to
be done /usr/obj untill "install" time. Shouldn't /usr/obj ideally
be read-only during install?
(This all may become moot, as I'm considering going to a master-push
or just a rsync scheme.)
____________
William R. Somsky [EMAIL PROTECTED]
Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: $FreeBSD tag confusion
On Sun, Aug 29, 1999 at 09:37:51PM -0700, John Polstra wrote: Expansion of RCS keywords occurs on check_out_, not on checkin. In other words, your cvs is responsible for expanding them. Hmm... but what about if you're cvsup-ing the sources? I'm cvsup-ing stable, not current, (cvsup file included below) and $FreeBSD appears all over the place unexpanded. Is this the way it's supposed to be? Isn't cvsup supposed to be (effectively) doing a "check-out"? Or am I just confused? = cvsupfile = *defaulthost=cvsup2.FreeBSD.org *defaultbase=/usr *defaultprefix=/usr *defaultrelease=cvs use-rel-suffix *defaultdelete compress *defaulttag=RELENG_3 src-all src-crypto src-secure ports-all tag=. = cvsup -v = CVSup client, GUI version Software version: REL_16_0 Protocol version: 16.0 http://www.polstra.com/projects/freeware/CVSup/ Report problems to [EMAIL PROTECTED] = behavior = #] cd /usr/src #] rm bin/echo/echo.c #] date bin/echo/echo.1 #] make update -- Running /usr/local/bin/cvsup -- Parsing supfile "/etc/cvsupfile" Looking up address of cvsup2.FreeBSD.org Connecting to cvsup2.FreeBSD.org Connected to cvsup2.FreeBSD.org Server software version: REL_16_0 Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection src-all/cvs Checkout src/bin/echo/echo.1 Checkout src/bin/echo/echo.c ^CCleaning up ... #] grep src/bin/echo bin/echo/echo.[1c] bin/echo/echo.1:.\" $FreeBSD: src/bin/echo/echo.1,v 1.6.2.2 1999/08/29 14:12:19 peter Exp $ bin/echo/echo.c: "$FreeBSD: src/bin/echo/echo.c,v 1.7.2.1 1999/08/29 14:12:20 peter Exp $"; = = So... no expansion of $FreeBSD that I can see here... Am I just confused? ____________ William R. Somsky [EMAIL PROTECTED] Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /var/db/pkg/.mkversion
On Thu, Apr 01, 1999 at 02:22:57PM -0500, Bill Fumerola wrote: On Wed, 31 Mar 1999, Jordan K. Hubbard wrote: I think this entire thing is a massive botch and needs to be removed as a bad idea ASAP. I think that's jumping to conclusions a little too quickly. Jordan, we are eliminating a LOT more future PRs and FAQs by using this method. A few permission and installation oversights (no software can ever be tested on every possible instance.) should not constitute removal of the whole idea. At minimum, the implementation is off... What /var/db/pkg/.mkversion is tracking w/ the current implementation it the date of the last _installation_ of the make files... Wouldn't just a MKPKG_VERSION=xxyyzz inside of the relevant make file work easier? What's _really_ trying to be accomplished w/ .mkversion? Tracking the version/date of the make binary, of the full set of share/mk files, of just the ports related makefiles? William R. Somsky wrsom...@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
On Wed, Mar 31, 1999 at 09:56:07AM +0100, Dom Mitchell wrote: On 30 March 1999, Satoshi Asami proclaimed: Just a side note; this new file breaks pkg_info. I've appended a simple patch below; somebody ought to do something better for the version in the src tree. Yep, this definitely suggests that /var/db/pkg isn't the appropriate place for the make version file. I think /usr/share/mk would be better. After all, that's where the make files that it's saying what the date of are anyway. And potentially, things other than ports might want to refer to it as well. -- William R. Somsky wrsom...@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
On Tue, Feb 09, 1999 at 02:21:09PM -0800, Jordan K. Hubbard wrote: Rather that listen to people wail over the next few months, it was decided instead to go to a slight variation on the previous theme in hopes that more people will be happy with the compromise. In essence, what used to be everything in /etc/rc.conf has moved to /etc/defaults/rc.conf and this file takes care of including (optionally) /etc/rc.conf and /etc/rc.conf.local. This means that you can go back to editing /etc/rc.conf again and the expected things will happen, though those interested in the full set of tunables will still need to look at /etc/defaults/rc.conf (which, like all defaults to eventually live in that directory, will be freely upgradable by the system). Since that made rc.conf.site obsolete, it was taken out of the configuration. Please move it to rc.conf on your system, should you be one of those folks who installed from an earlier snapshot and are now updating your /etc from -current or -stable sources (not likely to be all that many people). This change will also be in 3.1. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Any chance of something similar being done for make.conf? I've gotten in the habit of only adding stuff at the end, but it's still a pain copying file chunks back and forth. (Well, just forth I guess, no back) William R. Somsky wrsom...@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: man reads /etc/rc.conf?
On Wed, Nov 10, 1999 at 01:47:46PM +0100, [EMAIL PROTECTED] wrote: /usr/bin/apropos contains: ---snip--- # If possible check global system configuration file for additional # man locales installed if [ -r /etc/defaults/rc.conf ] ; then . /etc/defaults/rc.conf elif [ -r /etc/rc.conf ] ; then . /etc/rc.conf fi ---snip--- Hmm... aside from whether or not apropos should be reading in rc.conf, isn't this code fragment doing the wrong thing in regards to the way we have /etc/defaults/rc.conf and /etc/rc.conf setup nowadays? Shouldn't it read _both_ if present? Ie: if [ -r /etc/defaults/rc.conf ] ; then . /etc/defaults/rc.conf fi if [ -r /etc/rc.conf ] ; then . /etc/rc.conf fi William R. Somsky [EMAIL PROTECTED] Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: man reads /etc/rc.conf?
On Fri, Nov 19, 1999 at 08:41:30AM +0100, Alexander Leidinger wrote: On 18 Nov, William R. Somsky wrote: Hmm... aside from whether or not apropos should be reading in rc.conf, isn't this code fragment doing the wrong thing in regards to the way we have /etc/defaults/rc.conf and /etc/rc.conf setup nowadays? No, look at the last lines of /etc/defaults/rc.conf and also search for rc_conf_files in it. Um... yeah... I knew that... at one time anyway... nevermind... William R. Somsky [EMAIL PROTECTED] Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
