| /freebsd/share/man/man4/ |
| H A D | kld.4 | 21 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
39 predecessor, allows the system administrator to dynamically add and remove
40 functionality from a running system.
45 Various types of modules can be loaded into the system.
46 There are several defined module types, listed below, which can
47 be added to the system in a predefined way.
49 is a generic type, for which the module itself handles loading and
54 system makes extensive use of loadable kernel modules, and provides loadable
57 client and server, all the screen-savers, and the
81 program unloads any given loaded module, i
[all...] |
| H A D | hwpmc.4 | 1 .\" Copyright (c) 2003-2008 Joseph Koshy
26 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
39 .Bd -ragged -offset indent
44 .Bd -ragged -offset indent
48 To load the driver as a module at boot time:
49 .Bd -literal -offset indent
54 .Bd -ragged -offset indent
62 .Bd -ragged -offset indent
75 The driver supports multi-processor systems.
83 Subsequent operations on the allocated PMC use this handle to denote
[all …]
|
| H A D | splash.4 | 3 .\" Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
22 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
44 on the screen when the system is about to start.
45 This image will remain on the screen
47 until the login prompt appears on the screen
62 matching splash image decoder module must be loaded by the boot loader.
65 .Bl -tag -width splash_decoder -compact
73 This decoder currently only supports version 5 8-bpp single-plane
77 Displays a text-mode 80x25 ASCII drawing, such as that produced by
92 either by statically linking the VESA module or by loading the VESA module
[all …]
|
| H A D | siftr.4 | 25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
39 as a module at run-time, run the following command as root:
40 .Bd -literal -offset indent
46 as a module at boot time, add the following line into the
49 .Bd -literal -offset indent
62 kernel module logs a range of statistics on active TCP connections to
65 state, aimed at system administrators, developers and researchers.
66 .Ss Compile-time Configuration
72 .Bd -literal -offset indent
73 CFLAGS+=-DSIFTR_IPV6
[all …]
|
| H A D | mac_bsdextended.4 | 7 .\" DARPA/SPAWAR contract N66001-01-C-8035 ("CBOSS"), as part of the
26 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
36 .Nd "file system firewall policy"
38 To compile the file system firewall policy into your kernel,
40 .Bd -ragged -offset indent
45 Alternately, to load the file system firewall policy module at boot time,
47 .Bd -ragged -offset indent
53 .Bd -literal -offset indent
59 security policy module provides an interface for the system administrator
60 to impose mandatory rules regarding users and some system objects.
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | firmware.9 | 19 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
39 .Bd -literal
41 const char *name; /* system-wide name */
93 manually at runtime, or on demand by the firmware subsystem.
113 mechanisms specified below (typically, a kernel module
132 The function returns NULL on error (e.g. because an
141 from the system.
154 to indicate that errors on firmware load or registration should
157 If the image is not yet registered with the system,
191 In certain cases, such as on driver detach, this cannot be allowed.
[all …]
|
| H A D | mac.9 | 1 .\"-
2 .\" Copyright (c) 1999-2002 Robert N. M. Watson
3 .\" Copyright (c) 2002-2004 Networks Associates Technology, Inc.
10 .\" Associates, Inc. under DARPA/SPAWAR contract N66001-01-C-8035
29 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
52 introduced system security modules to modify system security functionality.
64 The MAC framework manages labels on a variety of types of in-kernel
68 Label data on kernel objects, represented by
70 is policy-unaware, and may be used in the manner seen fit by policy modules.
75 MAC-relevant operations, accept one or more subjects (credentials)
[all …]
|
| H A D | DECLARE_MODULE.9 | 1 .\" -*- nroff -*-
24 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
34 .Nd kernel module declaration macro
44 macro declares a generic kernel module.
45 It is used to register the module with the system, using the
57 A module declared with
62 is identical to that on which it was built.
63 This declaration should be used by modules which depend on interfaces beyond
64 the stable kernel KBI (such as ABI emulators or hypervisors that rely on
74 .Bl -tag -width indent
[all …]
|
| H A D | tcp_functions.9 | 21 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
53 on a single system.
55 A system administrator can set a system default stack.
56 By default, all TCP connections will use the system default stack.
57 Additionally, users can specify a particular stack to use on a per-connection
61 for details on setting the system default stack, or selecting a specific stack
74 functions request that the system add a specified function block
80 the name) after it has been registered, unless the module first successfully
81 de-registers the function block.
85 function requests that the system register the function block with the name
[all …]
|
| /freebsd/stand/defaults/ |
| H A D | loader.conf.5 | 20 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
29 .Nd "system bootstrap configuration information"
33 contains descriptive information on bootstrapping the system.
49 the prefix identifies which module the setting controls.
52 .Bl -bullet
58 Only one setting can be present on each line.
74 may have any prefix; the prefix identifies a module.
76 prefix refer to the same module.
77 .Bl -ta
[all...] |
| /freebsd/contrib/bsnmp/snmp_mibII/ |
| H A D | snmp_mibII.3 | 2 .\" Copyright (c) 2004-2005
5 .\" Copyright (c) 2001-2003
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
62 .Nd "mib-2 module for bsnmpd."
118 module implements parts of the internet standard MIB-2.
120 Some of the tables are restricted to be read-only instead of read-write.
123 The module also exports a number of functions and global variables for use
129 module opens a socket that is used to execute all network related
137 module handles a list of all currently existing network interfaces.
143 .Bd -literal -offset indent
[all …]
|
| /freebsd/share/doc/smm/18.net/ |
| H A D | 7.t | 23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
38 module are possible:
52 #define PRU_CONTROL 11 /* control operations on protocol */
65 A call on the user request routine is of the form,
73 The address \fIaddr\fP is supplied for address-oriented requests
76 chain containing user-specified capabilities (see the \fIsendmsg\fP
77 and \fIrecvmsg\fP system calls). The protocol is responsible for
78 disposal of the data mbuf chains on output operations.
79 A non-zero return value gives a
86 system call) the protocol module is called with this
[all …]
|
| /freebsd/share/man/man5/ |
| H A D | mqueuefs.5 | |
| /freebsd/sys/contrib/device-tree/Bindings/phy/ |
| H A D | ti-phy.txt | 6 - compatible: Should be one of
7 "ti,control-phy-otghs" - if it has otghs_control mailbox register as on OMAP4.
8 "ti,control-phy-usb2" - if it has Power down bit in control_dev_conf register
9 e.g. USB2_PHY on OMAP5.
10 "ti,control-ph
[all...] |
| /freebsd/usr.sbin/bsnmpd/modules/snmp_wlan/ |
| H A D | snmp_wlan.3 | 1 .\"-
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
33 .Nd "wireless networking module for"
40 module implements a private BEGEMOT-WIRELESS-MIB, which allows
47 module on systems where security is crucial.
50 .Bl -tag -width "XXXXXXXXX"
53 To add a new interface, a SET should be executed on the
67 To finally create the interface in the system, a SET with value of active(1) to
79 Depending on the operating mode of the interface and the hardware capabilities
86 Information about the active channels for the wireless interfaces in the system.
[all …]
|
| /freebsd/usr.sbin/bsnmpd/modules/snmp_bridge/ |
| H A D | snmp_bridge.3 | 1 .\"-
21 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .Nd "bridge module for snmpd"
37 module implements the BRIDGE-MIB as standardized in RFC 4188, the RSTP-MIB
38 standardized in RFC4318 and a private BEGEMOT-BRIDGE-MIB, which allows
40 Most of the objects defined in the private BEGEMOT-BRIDGE-MIB are duplicates
41 of the original objects defined by the standard BRIDGE-MIB, but the private
49 module on systems where security is crucial.
52 .Bl -tag -width "XXXXXXXXX"
56 .Bl -tag -width ".It Va createAndWait"
[all …]
|
| /freebsd/cddl/contrib/opensolaris/cmd/dtrace/ |
| H A D | dtrace.1 | 33 .Op Fl -libxo
46 .Op Fl m Oo Ar provider : Oc Ar module Oo Oo Ar predicate Oc Ar action Oc
47 .Op Fl f Oo Oo Ar provider : Oc Ar module : Oc Ar function Oo Oo Ar predicate \
49 .Op Fl n Oo Oo Oo Ar provider : Oc Ar module : Oc Ar function : Oc Ar name \
51 .Op Fl i Ar probe-id Oo Oo Ar predicate Oc Ar action Oc
56 the behavior of the operating system and user programs.
62 .Bl -bullet -offset indent
67 specifiers (provider, module, function, name)
70 programs written directly on the command line
103 D program code specified on the command line must be appropriately quoted to
[all …]
|
| /freebsd/contrib/openpam/doc/man/ |
| H A D | pam.conf.5 | 1 .\"-
2 .\" Copyright (c) 2005-2017 Dag-Erling Smørgrav
24 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
38 .Bl -enum
40 .Pa /etc/pam.d/ Ns Ar service-name
44 .Pa /usr/local/etc/pam.d/ Ns Ar service-name
54 Entries in per-service policy files must be of one of the two forms
56 .Bd -unfilled -offset indent
57 .Ar facility control-flag module-path Op Ar arguments ...
58 .Ar facility Cm include Ar other-service-name
[all …]
|
| /freebsd/share/examples/kld/cdev/ |
| H A D | README | 26 # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
56 # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
65 This is the README file for the sample kld module
68 A kld module may be used to load any data or
71 the kernel that the module should be used instead of the
74 Generally, it is assumed that a loadable module is one of
75 a set of similar modules (such as a file system or console
79 This is not enforced, so you may use the kld module
82 As with the loadable system calls, it may be desirable to
83 allow the module loader to replace an *existing* entry to
[all …]
|
| /freebsd/share/doc/papers/bufbio/ |
| H A D | bio.ms | 1 .\" ----------------------------------------------------------------------------
2 .\" "THE BEER-WARE LICENSE" (Revision 42):
5 .\" this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp
6 .\" ----------------------------------------------------------------------------
13 - or -
17 Poul-Henning Kamp <phk@FreeBSD.org>
21 Historically, the only translation performed on I/O requests after
22 they they left the file-system layer were logical sub disk implementation
25 and operating system have done it their own way. As FreeBSD migrates to
27 able to co-exist with other operating systems on the same disk.
[all …]
|
| /freebsd/contrib/llvm-project/clang/include/clang/Basic/ |
| H A D | DiagnosticSerializationKinds.td | 1 //==--- DiagnosticSerializationKinds.td - serialization diagnostics -------===//
5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 //===----------------------------------------------------------------------===//
22 "%select{precompiled header|module file|AST file}1 '%2' was built"
30 "after modifying system headers, please delete the module cache at '%0'">;
45 def err_pch_modulecache_mismatch : Error<"PCH was compiled with module cache "
49 InGroup<DiagGroup<"pch-vfs-diff">>;
63 "module '%0' is defined in both '%1' and '%2'">, DefaultFatal;
65 "%select{PCH|module|AST}0 file '%1' not found%select{|: %3}2">, DefaultFatal;
67 "%select{PCH|module|AST}0 file '%1' is out of date and "
[all …]
|
| /freebsd/contrib/llvm-project/clang/include/clang/Lex/ |
| H A D | HeaderSearch.h | 1 //===- HeaderSearch.h - Resolve Header File Locations -----------*- C++ -*-===//
5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 //===----------------------------------------------------------------------===//
11 //===----------------------------------------------------------------------===//
53 class Module; variable
76 /// Keep track of whether this is a system header, and if so,
88 /// Whether this header is part of and built with a module. i.e. it is listed
89 /// in a module map, and is not `excluded` or `textual`. (same meaning as
94 /// Whether this header is a `textual header` in a module. If a header is
95 /// textual in one module and normal in another module, this bit will not be
[all …]
|
| /freebsd/share/doc/smm/02.config/ |
| H A D | 6.t | 23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 ADDING NEW SYSTEM SOFTWARE
35 well as the pertinent parts of the system autoconfiguration process.
38 other system facilities sufficient information to do so in the
43 general guidelines to be followed in modifying system code,
45 how to add non-standard system facilities to 4.4BSD,
49 Modifying system code
51 If you wish to make site-specific modifications to the system
60 to use a source code control system (e.g. SCCS, RCS), and
69 We try to isolate our site-dependent code in individual files
[all …]
|
| /freebsd/contrib/llvm-project/lldb/bindings/interface/ |
| H A D | SBModuleSpecDocstrings.i | 2 Get const accessor for the module file.
4 This function returns the file for the module on the host system
5 that is running LLDB. This can differ from the path on the
13 Get accessor for the module platform file.
15 Platform file refers to the path of the module as it is known on
16 the remote system on which it is being debugged. For local
17 debugging this is always the same as Module::GetFileSpec(). But
21 '/tmp/lldb/platform-cache/remote.host.computer/usr/lib/liba.dylib'
|
| /freebsd/sys/i386/conf/ |
| H A D | NOTES | 2 # NOTES -- Lines that can be cut/pasted into kernel and hints configs.
32 # IPI_PREEMPTION instructs the kernel to preempt threads running on other
33 # CPUS if needed. Relies on the PREEMPTION option
47 # You must specify at least one CPU (the one you intend to run on);
49 # parts of the system run faster.
61 # CPU_BLUELIGHTNING_3X enables triple-clock mode on IBM Blue Lightning
62 # CPU if CPU supports it. The default is double-clock mode on
[all...] |