secure-supfile ?
--START # cd /usr/src # make update [.. snip stable-supfile stuff ..] Edit src/usr.sbin/zic/zic/Makefile Add delta 1.5.2.1 2001.04.25.12.11.16 ru Shutting down connection to server Finished successfully Parsing supfile /usr/share/examples/cvsup/secure-supfile Cannot open /usr/share/examples/cvsup/secure-supfile: No such file or directory *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # ls -l /usr/src/Makefile -rw-r--r-- 1 root wheel 7486 Apr 27 12:13 /usr/src/Makefile # --END anybody have a clue what's going on here? am i using a dodgy Makefile? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: secure-supfile ?
* Vincent D Murphy [EMAIL PROTECTED] [010427 12:31]: Parsing supfile /usr/share/examples/cvsup/secure-supfile Cannot open /usr/share/examples/cvsup/secure-supfile: No such file or directory anybody have a clue what's going on here? am i using a dodgy Makefile? Does this file exist? It's a bit odd that it reads it twice. cvsup -g -L 2 /path/to/supfile will work. -- There is no reason for any individual to have a computer in their home. -- Ken Olson, President of DEC, World Future Society Convention, 1977 Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: secure-supfile ?
On Fri, Apr 27, 2001 at 12:28:34PM +0100, Vincent D Murphy wrote: --START # cd /usr/src # make update [.. snip stable-supfile stuff ..] Edit src/usr.sbin/zic/zic/Makefile Add delta 1.5.2.1 2001.04.25.12.11.16 ru Shutting down connection to server Finished successfully Parsing supfile /usr/share/examples/cvsup/secure-supfile Cannot open /usr/share/examples/cvsup/secure-supfile: No such file or directory *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # ls -l /usr/src/Makefile -rw-r--r-- 1 root wheel 7486 Apr 27 12:13 /usr/src/Makefile # --END anybody have a clue what's going on here? am i using a dodgy Makefile? Uhh, secure-supfile is gone over almost a year ago. Remove the SUPFILE1= line from your /etc/make.conf. I will fix src/etc/defaults/make.conf. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: secure-supfile ?
= Ruslan Ermilov [EMAIL PROTECTED] [20010427 1254]: Uhh, secure-supfile is gone over almost a year ago. Remove the SUPFILE1= line from your /etc/make.conf. I will fix src/etc/defaults/make.conf. just to confirm: i did cp /etc/defaults/make.conf /etc/make.conf a while back. i can't remember why, but i think there is no file there by default and i needed one for some reason. thank you (and everybody else) for your help. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: secure-supfile ?
Date: Fri, 27 Apr 2001 13:12:50 +0100 From: Vincent D Murphy [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] = Ruslan Ermilov [EMAIL PROTECTED] [20010427 1254]: Uhh, secure-supfile is gone over almost a year ago. Remove the SUPFILE1= line from your /etc/make.conf. I will fix src/etc/defaults/make.conf. just to confirm: i did cp /etc/defaults/make.conf /etc/make.conf a while back. i can't remember why, but i think there is no file there by default and i needed one for some reason. This is normal. The idea is NOT to copy the /etc/defaults files to /etc. The idea is to place specific changes from defaults into a file in /etc. The /etc/defaults files contain the normal defaults for a great many things and should not be modified. That way, should OS changes require it, defaults can be changed easily (POLA). Rules for files in /etc/defaults: 1. Don't ever modify these files! 2. Don't ever copy them into /etc 3. Should defaults need to be changed, create or edit the /etc file of the same name to contain just the items requiring non-default behavior. If you do this, the odds of things failing after a system software upgrade are substantially reduced. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
