Editing Kernel

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1,111: Line 1,111:
 
|/boot/kernel/[https://www.freebsd.org/doc/handbook/network-nfs.html nfslockd].ko||Network File System (NFS)
 
|/boot/kernel/[https://www.freebsd.org/doc/handbook/network-nfs.html nfslockd].ko||Network File System (NFS)
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nfsmb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nfsmb].ko||The nfsmb driver provides access to NVIDIA nForce2/3/4 SMBus 2.0 controllers.
+
|/boot/kernel/nfsmb.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nfssvc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nfssvc].ko||The nfssvc() system call is used by the NFS daemons to pass information into and out of the kernel and also to enter the kernel as a server daemon.
+
|/boot/kernel/nfssvc.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_async&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_async].ko||The async node type performs conversion between synchronous frames and  asynchronous frames, as defined for the PPP protocol in RFC 1662.
+
|/boot/kernel/ng_async.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_atmllc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_atmllc].ko||The atmllc node type translates frames in to and out of ATM LLC encapsulation, as specified by RFC 1483.
+
|/boot/kernel/ng_atmllc.ko||
 
|-
 
|-
−
|/boot/kernel/ng_bluetooth.ko||The ng_bluetooth module is a placeholder for global Bluetooth variables. All Bluetooth variables can be examined and changed via [[sysctl]].
+
|/boot/kernel/ng_bluetooth.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_bpf&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_bpf].ko||The bpf node type allows Berkeley Packet Filter (see bpf(4)) filters to be applied to data travelling through a Netgraph network. Each node allows an arbitrary number of connections to arbitrarily named hooks.
+
|/boot/kernel/ng_bpf.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_bridge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_bridge].ko||The bridge node type performs Ethernet bridging over one or more links.    Each link (represented by a connected hook) is used to transmit and receive raw Ethernet frames.
+
|/boot/kernel/ng_bridge.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_bt3c&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_bt3c].ko||Netgraph node type that is also a 3Com Bluetooth PC card
+
|/boot/kernel/ng_bt3c.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_btsocket&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_btsocket].ko||Bluetooth sockets layer
+
|/boot/kernel/ng_btsocket.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_car&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_car].ko||Committed Access Rate netgraph node type
+
|/boot/kernel/ng_car.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ccatm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ccatm].ko||The ng_ccatm node implements the API specified by the ATM Forum for access to ATM services (see ATM-Forum document af-saa-0108).
+
|/boot/kernel/ng_ccatm.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_cisco&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_cisco].ko||The cisco node type performs encapsulation and de-encapsulation of packets using the Cisco HDLC protocol. This is a fairly simple protocol for  the transmission of packets across high speed synchronous lines.
+
|/boot/kernel/ng_cisco.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_deflate&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_deflate].ko||The deflate node type implements the Deflate sub-protocols of the Compression Control Protocol (CCP).
+
|/boot/kernel/ng_deflate.ko||
−
 
+
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_device&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_device].ko||A device node is both a netgraph node and a system device interface.    When a device node is created, a new device entry appears which is accessible via the regular file operators such as open(2), close(2), read(2),  write(2), etc.
+
|/boot/kernel/ng_device.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_echo&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_echo].ko||The echo node type reflects all data and control messages back to the    sender.  This node type is used for testing and debugging.
+
|/boot/kernel/ng_echo.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_eiface&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_eiface].ko||The eiface netgraph node implements the generic Ethernet interface.
+
|/boot/kernel/ng_eiface.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_etf&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_etf].ko||The etf node type multiplexes and filters data between hooks on the basis  of the ethertype found in an Ethernet header, presumed to be in the first  14 bytes of the data.  Incoming Ethernet frames are accepted on the    downstream hook and if the ethertype matches a value which the node has  been configured to filter, the packet is forwarded out the hook which was    identified at the time that value was configured.
+
|/boot/kernel/ng_etf.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ether&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ether].ko||The ether netgraph node type allows Ethernet interfaces to interact with    the netgraph(4) networking subsystem.
+
|/boot/kernel/ng_ether.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ether_echo&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ether_echo].ko||The ether_echo node type reflects all data and control messages back to  the sender.  It assumes (and does not check) that the packet is an ethernet frame, and swaps the source and destination addresses before echoing  it.  This node type is used for testing and debugging.
+
|/boot/kernel/ng_ether_echo.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_frame_relay&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_frame_relay].ko||The frame_relay node type performs encapsulation, de-encapsulation, and    multiplexing of packets using the frame relay protocol.  It supports up  to 1024 DLCI's.  The LMI protocol is handled by a separate node type (see  ng_lmi(4)).
+
|/boot/kernel/ng_frame_relay.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_gif&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_gif].ko||The ng_gif netgraph node type allows gif(4) interfaces to interact with the netgraph(4) networking subsystem.  Once the ng_gif module is loaded  in the kernel, a node is automatically created for each gif(4) interface  in the system.
+
|/boot/kernel/ng_gif.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_gif_demux&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_gif_demux].ko||The ng_gif_demux netgraph node type demultiplexes the output from ng_gif(4) nodes in the netgraph(4) networking subsystem.
+
|/boot/kernel/ng_gif_demux.ko||
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_hci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_hci].ko||The hci node type is a Netgraph node type that implements Bluetooth Host  Controller Interface (HCI) layer as per chapter H1 of the Bluetooth Specification Book v1.1.
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_hci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_hci].ko||The hci node type is a Netgraph node type that implements Bluetooth Host  Controller Interface (HCI) layer as per chapter H1 of the Bluetooth Specification Book v1.1.

Please note that all contributions to GhostBSD Wiki are considered to be released under the Creative Commons Attribution (see GhostBSD Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "http://wiki.ghostbsd.org/index.php/Kernel"