freebsd-nq/usr.sbin/Makefile

342 lines
4.6 KiB
Makefile
Raw Normal View History

# From: @(#)Makefile 5.20 (Berkeley) 6/12/93
1999-08-28 01:35:59 +00:00
# $FreeBSD$
1994-05-26 05:23:31 +00:00
.include <bsd.own.mk>
SUBDIR= adduser \
1998-08-30 20:58:16 +00:00
arp \
bootparamd \
bsdconfig \
bsdinstall \
1998-08-30 20:58:16 +00:00
cdcontrol \
chkgrp \
chown \
chroot \
ckdist \
Add the new kernel-mode NFS Lock Manager. To use it instead of the user-mode lock manager, build a kernel with the NFSLOCKD option and add '-k' to 'rpc_lockd_flags' in rc.conf. Highlights include: * Thread-safe kernel RPC client - many threads can use the same RPC client handle safely with replies being de-multiplexed at the socket upcall (typically driven directly by the NIC interrupt) and handed off to whichever thread matches the reply. For UDP sockets, many RPC clients can share the same socket. This allows the use of a single privileged UDP port number to talk to an arbitrary number of remote hosts. * Single-threaded kernel RPC server. Adding support for multi-threaded server would be relatively straightforward and would follow approximately the Solaris KPI. A single thread should be sufficient for the NLM since it should rarely block in normal operation. * Kernel mode NLM server supporting cancel requests and granted callbacks. I've tested the NLM server reasonably extensively - it passes both my own tests and the NFS Connectathon locking tests running on Solaris, Mac OS X and Ubuntu Linux. * Userland NLM client supported. While the NLM server doesn't have support for the local NFS client's locking needs, it does have to field async replies and granted callbacks from remote NLMs that the local client has contacted. We relay these replies to the userland rpc.lockd over a local domain RPC socket. * Robust deadlock detection for the local lock manager. In particular it will detect deadlocks caused by a lock request that covers more than one blocking request. As required by the NLM protocol, all deadlock detection happens synchronously - a user is guaranteed that if a lock request isn't rejected immediately, the lock will eventually be granted. The old system allowed for a 'deferred deadlock' condition where a blocked lock request could wake up and find that some other deadlock-causing lock owner had beaten them to the lock. * Since both local and remote locks are managed by the same kernel locking code, local and remote processes can safely use file locks for mutual exclusion. Local processes have no fairness advantage compared to remote processes when contending to lock a region that has just been unlocked - the local lock manager enforces a strict first-come first-served model for both local and remote lockers. Sponsored by: Isilon Systems PR: 95247 107555 115524 116679 MFC after: 2 weeks
2008-03-26 15:23:12 +00:00
clear_locks \
crashinfo \
1998-08-30 20:58:16 +00:00
cron \
Add the CAM Target Layer (CTL). CTL is a disk and processor device emulation subsystem originally written for Copan Systems under Linux starting in 2003. It has been shipping in Copan (now SGI) products since 2005. It was ported to FreeBSD in 2008, and thanks to an agreement between SGI (who acquired Copan's assets in 2010) and Spectra Logic in 2010, CTL is available under a BSD-style license. The intent behind the agreement was that Spectra would work to get CTL into the FreeBSD tree. Some CTL features: - Disk and processor device emulation. - Tagged queueing - SCSI task attribute support (ordered, head of queue, simple tags) - SCSI implicit command ordering support. (e.g. if a read follows a mode select, the read will be blocked until the mode select completes.) - Full task management support (abort, LUN reset, target reset, etc.) - Support for multiple ports - Support for multiple simultaneous initiators - Support for multiple simultaneous backing stores - Persistent reservation support - Mode sense/select support - Error injection support - High Availability support (1) - All I/O handled in-kernel, no userland context switch overhead. (1) HA Support is just an API stub, and needs much more to be fully functional. ctl.c: The core of CTL. Command handlers and processing, character driver, and HA support are here. ctl.h: Basic function declarations and data structures. ctl_backend.c, ctl_backend.h: The basic CTL backend API. ctl_backend_block.c, ctl_backend_block.h: The block and file backend. This allows for using a disk or a file as the backing store for a LUN. Multiple threads are started to do I/O to the backing device, primarily because the VFS API requires that to get any concurrency. ctl_backend_ramdisk.c: A "fake" ramdisk backend. It only allocates a small amount of memory to act as a source and sink for reads and writes from an initiator. Therefore it cannot be used for any real data, but it can be used to test for throughput. It can also be used to test initiators' support for extremely large LUNs. ctl_cmd_table.c: This is a table with all 256 possible SCSI opcodes, and command handler functions defined for supported opcodes. ctl_debug.h: Debugging support. ctl_error.c, ctl_error.h: CTL-specific wrappers around the CAM sense building functions. ctl_frontend.c, ctl_frontend.h: These files define the basic CTL frontend port API. ctl_frontend_cam_sim.c: This is a CTL frontend port that is also a CAM SIM. This frontend allows for using CTL without any target-capable hardware. So any LUNs you create in CTL are visible in CAM via this port. ctl_frontend_internal.c, ctl_frontend_internal.h: This is a frontend port written for Copan to do some system-specific tasks that required sending commands into CTL from inside the kernel. This isn't entirely relevant to FreeBSD in general, but can perhaps be repurposed. ctl_ha.h: This is a stubbed-out High Availability API. Much more is needed for full HA support. See the comments in the header and the description of what is needed in the README.ctl.txt file for more details. ctl_io.h: This defines most of the core CTL I/O structures. union ctl_io is conceptually very similar to CAM's union ccb. ctl_ioctl.h: This defines all ioctls available through the CTL character device, and the data structures needed for those ioctls. ctl_mem_pool.c, ctl_mem_pool.h: Generic memory pool implementation used by the internal frontend. ctl_private.h: Private data structres (e.g. CTL softc) and function prototypes. This also includes the SCSI vendor and product names used by CTL. ctl_scsi_all.c, ctl_scsi_all.h: CTL wrappers around CAM sense printing functions. ctl_ser_table.c: Command serialization table. This defines what happens when one type of command is followed by another type of command. ctl_util.c, ctl_util.h: CTL utility functions, primarily designed to be used from userland. See ctladm for the primary consumer of these functions. These include CDB building functions. scsi_ctl.c: CAM target peripheral driver and CTL frontend port. This is the path into CTL for commands from target-capable hardware/SIMs. README.ctl.txt: CTL code features, roadmap, to-do list. usr.sbin/Makefile: Add ctladm. ctladm/Makefile, ctladm/ctladm.8, ctladm/ctladm.c, ctladm/ctladm.h, ctladm/util.c: ctladm(8) is the CTL management utility. It fills a role similar to camcontrol(8). It allow configuring LUNs, issuing commands, injecting errors and various other control functions. usr.bin/Makefile: Add ctlstat. ctlstat/Makefile ctlstat/ctlstat.8, ctlstat/ctlstat.c: ctlstat(8) fills a role similar to iostat(8). It reports I/O statistics for CTL. sys/conf/files: Add CTL files. sys/conf/NOTES: Add device ctl. sys/cam/scsi_all.h: To conform to more recent specs, the inquiry CDB length field is now 2 bytes long. Add several mode page definitions for CTL. sys/cam/scsi_all.c: Handle the new 2 byte inquiry length. sys/dev/ciss/ciss.c, sys/dev/ata/atapi-cam.c, sys/cam/scsi/scsi_targ_bh.c, scsi_target/scsi_cmds.c, mlxcontrol/interface.c: Update for 2 byte inquiry length field. scsi_da.h: Add versions of the format and rigid disk pages that are in a more reasonable format for CTL. amd64/conf/GENERIC, i386/conf/GENERIC, ia64/conf/GENERIC, sparc64/conf/GENERIC: Add device ctl. i386/conf/PAE: The CTL frontend SIM at least does not compile cleanly on PAE. Sponsored by: Copan Systems, SGI and Spectra Logic MFC after: 1 month
2012-01-12 00:34:33 +00:00
ctladm \
daemon \
dconschat \
2001-04-21 00:13:57 +00:00
devinfo \
digictl \
diskinfo \
dumpcis \
etcupdate \
extattr \
extattrctl \
fifolog \
2002-12-30 10:13:16 +00:00
fwcontrol \
getfmac \
getpmac \
gstat \
i2c \
ifmcstat \
1998-08-30 20:58:16 +00:00
inetd \
1998-11-09 23:39:02 +00:00
iostat \
isfctl \
kldxref \
mailwrapper \
makefs \
1999-04-07 04:12:02 +00:00
memcontrol \
1999-10-20 07:33:09 +00:00
mergemaster \
mfiutil \
1999-11-13 18:34:22 +00:00
mixer \
2000-04-11 03:02:37 +00:00
mlxcontrol \
mountd \
mptutil \
1998-08-30 20:58:16 +00:00
mtest \
mtree \
newsyslog \
nfscbd \
nfsd \
nfsdumpstate \
nfsrevoke \
nfsuserd \
nmtree \
nologin \
${_pc_sysinstall} \
1998-08-30 20:58:16 +00:00
pciconf \
periodic \
2005-02-26 21:18:20 +00:00
powerd \
1998-08-30 20:58:16 +00:00
procctl \
pstat \
pw \
pwd_mkdb \
quot \
rarpd \
rmt \
Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) and associated changes that had to happen to make this possible as well as bugs fixed along the way. Bring in required TLI library routines to support this. Since we don't support TLI we've essentially copied what NetBSD has done, adding a thin layer to emulate direct the TLI calls into BSD socket calls. This is mostly from Sun's tirpc release that was made in 1994, however some fixes were backported from the 1999 release (supposedly only made available after this porting effort was underway). The submitter has agreed to continue on and bring us up to the 1999 release. Several key features are introduced with this update: Client calls are thread safe. (1999 code has server side thread safe) Updated, a more modern interface. Many userland updates were done to bring the code up to par with the recent RPC API. There is an update to the pthreads library, a function pthread_main_np() was added to emulate a function of Sun's threads library. While we're at it, bring in NetBSD's lockd, it's been far too long of a wait. New rpcbind(8) replaces portmap(8) (supporting communication over an authenticated Unix-domain socket, and by default only allowing set and unset requests over that channel). It's much more secure than the old portmapper. Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded to support TI-RPC and to support IPV6. Umount(8) is also fixed to unmount pathnames longer than 80 chars, which are currently truncated by the Kernel statfs structure. Submitted by: Martin Blapp <mb@imp.ch> Manpage review: ru Secure RPC implemented by: wpaul
2001-03-19 12:50:13 +00:00
rpcbind \
1998-08-30 20:58:16 +00:00
rpc.lockd \
rpc.statd \
rpc.umntall \
1998-11-09 23:39:02 +00:00
rtprio \
service \
services_mkdb \
2008-05-10 00:43:13 +00:00
setfib \
setfmac \
setpmac \
2004-05-17 10:57:03 +00:00
smbmsg \
2005-07-20 22:53:57 +00:00
snapinfo \
1998-08-30 20:58:16 +00:00
spray \
syslogd \
sysrc \
tcpdchk \
tcpdmatch \
tcpdrop \
tcpdump \
1998-08-30 20:58:16 +00:00
timed \
traceroute \
trpt \
tzsetup \
ugidfw \
1998-08-30 20:58:16 +00:00
vipw \
wake \
1998-08-30 20:58:16 +00:00
watch \
watchdogd \
zic
# NB: keep these sorted by MK_* knobs
.if ${MK_ACCT} != "no"
SUBDIR+= accton
SUBDIR+= sa
.endif
.if ${MK_AMD} != "no"
SUBDIR+= amd
.endif
.if ${MK_AUDIT} != "no"
SUBDIR+= audit
SUBDIR+= auditd
.if ${MK_OPENSSL} != "no"
SUBDIR+= auditdistd
.endif
SUBDIR+= auditreduce
SUBDIR+= praudit
.endif
.if ${MK_AUTHPF} != "no"
SUBDIR+= authpf
.endif
.if ${MK_BIND_DNSSEC} != "no" && ${MK_OPENSSL} != "no"
SUBDIR+= dnssec-dsfromkey
SUBDIR+= dnssec-keyfromlabel
SUBDIR+= dnssec-keygen
SUBDIR+= dnssec-revoke
SUBDIR+= dnssec-settime
SUBDIR+= dnssec-signzone
SUBDIR+= dnssec-verify
.endif
.if ${MK_BIND_NAMED} != "no"
SUBDIR+= arpaname
SUBDIR+= ddns-confgen
SUBDIR+= genrandom
SUBDIR+= isc-hmac-fixup
SUBDIR+= named
SUBDIR+= named-checkconf
SUBDIR+= named-checkzone
SUBDIR+= named-journalprint
SUBDIR+= nsec3hash
SUBDIR+= rndc
SUBDIR+= rndc-confgen
.endif
.if ${MK_BLUETOOTH} != "no"
SUBDIR+= bluetooth
.endif
.if ${MK_BSNMP} != "no"
SUBDIR+= bsnmpd
.endif
.if ${MK_CTM} != "no"
SUBDIR+= ctm
.endif
.if ${MK_FLOPPY} != "no"
SUBDIR+= fdcontrol
SUBDIR+= fdformat
SUBDIR+= fdread
SUBDIR+= fdwrite
.endif
.if ${MK_FREEBSD_UPDATE} != "no"
SUBDIR+= freebsd-update
.endif
.if ${MK_GSSAPI} != "no"
SUBDIR+= gssd
Implement support for RPCSEC_GSS authentication to both the NFS client and server. This replaces the RPC implementation of the NFS client and server with the newer RPC implementation originally developed (actually ported from the userland sunrpc code) to support the NFS Lock Manager. I have tested this code extensively and I believe it is stable and that performance is at least equal to the legacy RPC implementation. The NFS code currently contains support for both the new RPC implementation and the older legacy implementation inherited from the original NFS codebase. The default is to use the new implementation - add the NFS_LEGACYRPC option to fall back to the old code. When I merge this support back to RELENG_7, I will probably change this so that users have to 'opt in' to get the new code. To use RPCSEC_GSS on either client or server, you must build a kernel which includes the KGSSAPI option and the crypto device. On the userland side, you must build at least a new libc, mountd, mount_nfs and gssd. You must install new versions of /etc/rc.d/gssd and /etc/rc.d/nfsd and add 'gssd_enable=YES' to /etc/rc.conf. As long as gssd is running, you should be able to mount an NFS filesystem from a server that requires RPCSEC_GSS authentication. The mount itself can happen without any kerberos credentials but all access to the filesystem will be denied unless the accessing user has a valid ticket file in the standard place (/tmp/krb5cc_<uid>). There is currently no support for situations where the ticket file is in a different place, such as when the user logged in via SSH and has delegated credentials from that login. This restriction is also present in Solaris and Linux. In theory, we could improve this in future, possibly using Brooks Davis' implementation of variant symlinks. Supporting RPCSEC_GSS on a server is nearly as simple. You must create service creds for the server in the form 'nfs/<fqdn>@<REALM>' and install them in /etc/krb5.keytab. The standard heimdal utility ktutil makes this fairly easy. After the service creds have been created, you can add a '-sec=krb5' option to /etc/exports and restart both mountd and nfsd. The only other difference an administrator should notice is that nfsd doesn't fork to create service threads any more. In normal operation, there will be two nfsd processes, one in userland waiting for TCP connections and one in the kernel handling requests. The latter process will create as many kthreads as required - these should be visible via 'top -H'. The code has some support for varying the number of service threads according to load but initially at least, nfsd uses a fixed number of threads according to the value supplied to its '-n' option. Sponsored by: Isilon Systems MFC after: 1 month
2008-11-03 10:38:00 +00:00
.endif
.if ${MK_GPIO} != "no"
SUBDIR+= gpioctl
.endif
Implement support for RPCSEC_GSS authentication to both the NFS client and server. This replaces the RPC implementation of the NFS client and server with the newer RPC implementation originally developed (actually ported from the userland sunrpc code) to support the NFS Lock Manager. I have tested this code extensively and I believe it is stable and that performance is at least equal to the legacy RPC implementation. The NFS code currently contains support for both the new RPC implementation and the older legacy implementation inherited from the original NFS codebase. The default is to use the new implementation - add the NFS_LEGACYRPC option to fall back to the old code. When I merge this support back to RELENG_7, I will probably change this so that users have to 'opt in' to get the new code. To use RPCSEC_GSS on either client or server, you must build a kernel which includes the KGSSAPI option and the crypto device. On the userland side, you must build at least a new libc, mountd, mount_nfs and gssd. You must install new versions of /etc/rc.d/gssd and /etc/rc.d/nfsd and add 'gssd_enable=YES' to /etc/rc.conf. As long as gssd is running, you should be able to mount an NFS filesystem from a server that requires RPCSEC_GSS authentication. The mount itself can happen without any kerberos credentials but all access to the filesystem will be denied unless the accessing user has a valid ticket file in the standard place (/tmp/krb5cc_<uid>). There is currently no support for situations where the ticket file is in a different place, such as when the user logged in via SSH and has delegated credentials from that login. This restriction is also present in Solaris and Linux. In theory, we could improve this in future, possibly using Brooks Davis' implementation of variant symlinks. Supporting RPCSEC_GSS on a server is nearly as simple. You must create service creds for the server in the form 'nfs/<fqdn>@<REALM>' and install them in /etc/krb5.keytab. The standard heimdal utility ktutil makes this fairly easy. After the service creds have been created, you can add a '-sec=krb5' option to /etc/exports and restart both mountd and nfsd. The only other difference an administrator should notice is that nfsd doesn't fork to create service threads any more. In normal operation, there will be two nfsd processes, one in userland waiting for TCP connections and one in the kernel handling requests. The latter process will create as many kthreads as required - these should be visible via 'top -H'. The code has some support for varying the number of service threads according to load but initially at least, nfsd uses a fixed number of threads according to the value supplied to its '-n' option. Sponsored by: Isilon Systems MFC after: 1 month
2008-11-03 10:38:00 +00:00
.if ${MK_INET6} != "no"
SUBDIR+= faithd
SUBDIR+= ip6addrctl
SUBDIR+= mld6query
SUBDIR+= ndp
SUBDIR+= rip6query
SUBDIR+= route6d
SUBDIR+= rrenumd
SUBDIR+= rtadvctl
SUBDIR+= rtadvd
SUBDIR+= rtsold
SUBDIR+= traceroute6
.endif
.if ${MK_IPFW} != "no"
SUBDIR+= ipfwpcap
.endif
.if ${MK_IPX} != "no"
SUBDIR+= IPXrouted
.endif
.if ${MK_JAIL} != "no"
SUBDIR+= jail
SUBDIR+= jexec
SUBDIR+= jls
.endif
# XXX MK_SYSCONS
.if ${MK_LEGACY_CONSOLE} != "no"
SUBDIR+= kbdcontrol
SUBDIR+= kbdmap
SUBDIR+= moused
SUBDIR+= vidcontrol
.endif
.if ${MK_LIBTHR} != "no" || ${MK_LIBPTHREAD} != "no"
.if ${MK_PPP} != "no"
SUBDIR+= pppctl
.endif
.if ${MK_NS_CACHING} != "no"
SUBDIR+= nscd
.endif
.endif
.if ${MK_LPR} != "no"
SUBDIR+= lpr
.endif
.if ${MK_MAN_UTILS} != "no"
SUBDIR+= manctl
.endif
.if ${MK_NAND} != "no"
SUBDIR+= nandsim
SUBDIR+= nandtool
.endif
.if ${MK_NETGRAPH} != "no"
SUBDIR+= flowctl
SUBDIR+= lmcconfig
SUBDIR+= ngctl
SUBDIR+= nghook
.endif
.if ${MK_NIS} != "no"
SUBDIR+= rpc.yppasswdd
SUBDIR+= rpc.ypupdated
SUBDIR+= rpc.ypxfrd
SUBDIR+= ypbind
SUBDIR+= yp_mkdb
SUBDIR+= yppoll
SUBDIR+= yppush
SUBDIR+= ypserv
SUBDIR+= ypset
.endif
.if ${MK_NTP} != "no"
SUBDIR+= ntp
.endif
.if ${MK_OPENSSL} != "no"
SUBDIR+= keyserv
.endif
.if ${MK_PC_SYSINSTALL} != "no"
_pc_sysinstall= pc-sysinstall
.endif
.if ${MK_PF} != "no"
SUBDIR+= ftp-proxy
.endif
2012-07-02 18:04:31 +00:00
.if ${MK_PKGBOOTSTRAP} != "no"
SUBDIR+= pkg
.endif
.if ${MK_PKGTOOLS} != "no"
SUBDIR+= pkg_install
.endif
# XXX MK_TOOLCHAIN?
.if ${MK_PMC} != "no"
SUBDIR+= pmcannotate
SUBDIR+= pmccontrol
SUBDIR+= pmcstat
.endif
.if ${MK_PORTSNAP} != "no"
SUBDIR+= portsnap
.endif
.if ${MK_PPP} != "no"
SUBDIR+= ppp
.endif
.if ${MK_QUOTAS} != "no"
SUBDIR+= edquota
SUBDIR+= quotaon
SUBDIR+= repquota
.endif
.if ${MK_RCMDS} != "no"
SUBDIR+= rwhod
.endif
.if ${MK_SENDMAIL} != "no"
SUBDIR+= editmap
SUBDIR+= mailstats
SUBDIR+= makemap
SUBDIR+= praliases
SUBDIR+= sendmail
.endif
.if ${MK_TOOLCHAIN} != "no"
SUBDIR+= config
SUBDIR+= crunch
.endif
.if ${MK_USB} != "no"
2010-10-03 20:09:19 +00:00
SUBDIR+= uathload
SUBDIR+= uhsoctl
SUBDIR+= usbconfig
SUBDIR+= usbdump
.endif
.if ${MK_UTMPX} != "no"
SUBDIR+= ac
SUBDIR+= lastlogin
SUBDIR+= utx
.endif
.if ${MK_WIRELESS} != "no"
SUBDIR+= ancontrol
SUBDIR+= wlandebug
SUBDIR+= wpa
.endif
.include <bsd.arch.inc.mk>
2002-10-18 15:38:39 +00:00
SUBDIR:= ${SUBDIR:O}
1994-05-26 05:23:31 +00:00
.include <bsd.subdir.mk>