According to Rich Winkel:
> According to Charles Owens:
> > Rich Winkel wrote:
> > > I just cvsupped fresh sources this weekend with the same result.
> > > Does anyone else use nfs to "installworld"?
> > > Or am I the only one having this problem?
> > From 3.0R to at least 3.1-stable I've seen this problem. The
> > (annoying) workaround has been to do RW mounts of /usr/src and
> > /usr/obj. I've seen some discussion of this problem on the -hackers
> > list of late, with some mention of fixes. I updated my sources to the
> > latest 3.2-stable on August 4th and happily found that running
> > installworld over read-only NFS mounts worked again!
> Actually this error arises with a r/w mount. I get a different
> error (while trying to make a symbolic link) when it's r/o.
I just cvsupped RELENG_3 again today (8/13/99) and I'm still having the
same problem. If anyone out there has this working properly over a
r/o OR r/w nfs mount I'd like to know about it.
Or should I just set NOPERL=true in /etc/make.conf and forget about it?
===> gnu/usr.bin/ld
install -c -s -o root -g wheel -m 555 ld /usr/libexec/aout
install -c -o root -g wheel -m 444 ld.1aout.gz /usr/share/man/man1aout
===> gnu/usr.bin/perl
===> gnu/usr.bin/perl/libperl
ln -sf /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/config_h.SH
config_h.sh
ln: config_h.sh: Read-only file system
Incurably optimistically,
Rich
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
