Date: Fri, 20 Sep 1996 15:25:42 -0700 From: Jason Thorpe <thorpej@nas.nasa.gov> To: Bruce Evans <bde@zeta.org.au> Cc: asami@freebsd.org, freebsd-bugs@freefall.freebsd.org Subject: Re: bin/1643: Support for NetBSD in bsd.port.mk Message-ID: <199609202225.PAA25341@lestat.nas.nasa.gov>
next in thread | raw e-mail | index | archive | help
On Fri, 20 Sep 1996 22:47:46 +1000 Bruce Evans <bde@zeta.org.au> wrote: > Not so OK. We originally used plain `md5', but changed it because people > might not have /sbin in $PATH. md5 is in /sbin because it might be useful > for checking security before mounting /usr. I don't like having absolute > paths anywhere in the build. This is, of course, an architecural decision you'll have to make. I'm basically concerned with making one "ports" makefile work on FreeBSD and NetBSD. IMO, placing md5 in /sbin is of dubious value (that's a discussion for somewhere else :-), thus is belongs in /usr/bin (with other checksumming utilities). I don't mind just calling it "md5", since NetBSD users will basically always have /usr/bin in their patch. I was merely following the convention which appeared to be used in the file. (BTW, IMO the user should have /sbin in their path, since the 4.4BSD security model allows non-priveliged users to use mount(8), etc. So, making it "md5" and having it crap out if a user doesn't have /sbin in their PATH is just ducky with me :-) -- save the ancient forests - http://www.bayarea.net/~thorpej/forest/ -- Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609202225.PAA25341>