of the compiled in _PATH_REMSH, which is now ssh.
This allows some users to still specify /usr/bin/rsh and (if they run as root)
have the program use rcmd(), while solving the problems like that in the
PR: 79093
Submitted by: Alex Deiter
Bump PORTREVISION.
FWIW, checkout of these things took 5+hrs, staying on the local
.freebsd.org net w/o hitting the 'net at all.
As promised,
$ time cvs ci
real 67m51.701s
user 0m1.250s
sys 0m5.345s
something already there (PORTOBJFORMAT, OSVERSION) or move stuff from after
.include <bsd.port.mk> to before.
(This is not by any means the complete list but just the ones I've noticed
recently.)
cc -O -pipe -DOS_H=\"os-freebsd2.h\" -I. -I../include -I../config -c filesys-os.c
filesys-os.c: In function `getmountent':
filesys-os.c:183: `MOUNT_NFS' undeclared (first use this function)
filesys-os.c:183: (Each undeclared identifier is reported only once
filesys-os.c:183: for each function it appears in.)
filesys-os.c:188: warning: unreachable code at beginning of switch statement
*** Error code 1
PLISTs.
Note: I know that this is going to break some symlinks and/or .so
includes, I will back some of these out as I run into these during
package building.
buffer overflow problems, which shouldn't be an issue since it's
not setuid.
While here, do not hardcode /usr/local, use $(PREFIX). Do not patch
the install target so that 'make install' does the man pages, add
install.man to the ${INSTALL_TARGET} variable so that both "install"
and "install.man" are done. This reduces the diff to the base source a
little, but has the same overall effect.
Among other things, it has pretty much got native FreeBSD support, does not
core dump on ^C, some sync problems, uid/gid caching fixes, symlink detection
problems, portability to new platforms..
The server executable is still rdistd, because there is no conflict with
the standard rdist, and because it's hardcoded in the other non-freebsd
clients that exec it via rsh.
