kextd(8) [opendarwin man page]

KEXTD(8)						    BSD System Manager's Manual 						  KEXTD(8)

NAME

     kextd -- loads kexts on demand from kernel or client processes

SYNOPSIS

     kextd [-c] [-d] [-f] [-h] [-j] [-r directory] ...	[-v [1-6]] [-x]

DESCRIPTION

     kextd runs as a daemon process to handle requests from the kernel to load kernel extensions (kexts).  For proper operation kextd must be
     invoked as the superuser.

     kextd should not be considered a formal interface in the Darwin OS or in Mac OS X.  Neither its usage nor its presence should be relied on by
     any software or software installer.

     The options available are these:

     -c       Ignore any repository cache files and scan all kext bundles to gather information.  If this option is not given, kextd will attempt
	      to use cache files and to create them if they are out of date or don't exist.

     -d       Debug mode; run in the foreground without forking as a daemon process.

     -f       Don't fork a child task when loading kexts.  This option is present for debugging kextd and should never be used otherwise.

     -h       Print a help message describing each option flag.

     -j       Don't jettison kernel linker; load NDRVs in the kernel and exit, allowing the kernel to continue handling all load requests.  This
	      option is used in startup scripts for install CDs, along with a properly built mkext cache, in order to speed startup from the CD.

     -r directory
	      Use directory as a repository of known kexts for handling load requests.	This is not recursive; only the directory's immediate con-
	      tents are scanned.  By default kextd uses only the kexts in /System/Library/Extensions.

     -v [1-6]
	      Verbose mode; print information about the kext scanning and loading process (note that this is generally not useful when unloading).
	      See the man page for kextload(8) to see what each verbose level prints.

     -x       Run kextd in safe boot mode (indicating startup with the Shift key held down).  Kexts that don't specify a proper value for the
	      OSBundleRequired info dictionary property will not be loaded.  This option implies the use of the -c option.

DIAGNOSTICS

     kextd normally never exits.  If an error occurs it exits with a nonzero status.  If invoked with the -j option it exits with a zero status
     when no error occurs, or a nonzero status if an error does occur.

     kextd logs all error and verbose messages to the system log, or to the console if the system log facility isn't available.  When running in
     debug mode all output is printed to the standard output and error streams.

SEE ALSO

     kextcache(8), kextload(8), kextstat(8), kextunload(8), syslogd(8)

Darwin								 February 14, 2002							    Darwin

KEXTUNLOAD(8)						    BSD System Manager's Manual 					     KEXTUNLOAD(8)

NAME

     kextunload -- terminates objects and unloads code associated with a kernel extension

SYNOPSIS

     kextunload [-b bundle_id] ...  [-c class_name] ...  [-h] [-p] [ -v [0-6] | -q ] [ extension ] ...

DESCRIPTION

     The kextunload program is used to terminate and unregister I/O Kit objects associated with a kernel extension (kext) and to unload the code
     and personalities for that kext.  In order to unload a kext kextunload must be invoked as the superuser.

     If another loaded kext has a dependency on a kext being unloaded, the unload will fail.  You can determine whether a kext has dependents
     using the kextstat(8) tool.

     kextunload is a formal interface for unloading kexts in the Darwin OS and in Mac OS X.  Software and installers can rely on its presence and
     invoke it in order to unload kexts.

     The arguments and options available are these:

     extension
	      The pathname of a kext to unload.  All instances of classes associated with the kext are terminated, and personalities and code are
	      unloaded from the kernel.

     -b bundle_id
	      Unload code and personalities for the kext whose CFBundleIdentifier is bundle_id.

     -c class_name
	      Terminate all instances of class class_name if possible but do not unload code or personalities.	New load requests for devices
	      driven by these instances may result in the same class being instantiated at any time.

     -h       Print a help message describing each option flag.

     -m bundle_id
	      Same as -m (remains for backward compatibility).

     -p       Don't remove personalities when unloading (unnecessary when using the -c option).  New load requests for devices driven by the kext
	      may result in the same kext being loaded at any time.

     -q       Quiet mode; print no informational or error messages.  This option excludes -v.

     -v [0-6]
	      Verbose mode; print information about the kext scanning and loading process (note that this is generally not useful when unloading).
	      See the man page for kextload(8) to see what each verbose level prints.  This option excludes - q .

DIAGNOSTICS

     kextunload exits with a zero status upon success, or prints an error message and exits with a nonzero status upon failure.  An error when
     multiple kexts are being unloaded causes kextunload to exit immediately, so that some kexts may remain unloaded even if they could have been
     unloaded without error.

BUGS

     The results of unload requests as given by the kernel don't allow for determining the reason for a failure, such as that the kext wasn't
     loaded or that another kext has a dependency on it.  You can check these conditions using kextstat(8).

SEE ALSO

     kextcache(8), kextd(8), kextload(8), kextstat(8)

Darwin								  April 17, 2002							    Darwin