freebsd-dev/etc/mtree/BSD.include.dist

379 lines
5.3 KiB
Plaintext
Raw Normal View History

1999-08-27 23:37:10 +00:00
# $FreeBSD$
#
# Please see the file src/etc/mtree/README before making changes to this file.
#
/set type=dir uname=root gname=wheel mode=0755
.
arpa
..
2014-12-18 18:44:22 +00:00
atf-c
..
atf-c++
..
bsm
..
bsnmp
..
c++
2007-06-01 18:53:36 +00:00
4.2
backward
..
bits
..
2004-07-28 05:27:21 +00:00
debug
..
ext
2007-06-01 18:53:36 +00:00
pb_ds
detail
basic_tree_policy
2007-06-01 18:53:36 +00:00
..
bin_search_tree_
2007-06-01 18:53:36 +00:00
..
binary_heap_
2007-06-01 18:53:36 +00:00
..
binomial_heap_
2007-06-01 18:53:36 +00:00
..
binomial_heap_base_
..
cc_hash_table_map_
..
eq_fn
2007-06-01 18:53:36 +00:00
..
gp_hash_table_map_
..
hash_fn
2007-06-01 18:53:36 +00:00
..
left_child_next_sibling_heap_
2007-06-01 18:53:36 +00:00
..
list_update_map_
2007-06-01 18:53:36 +00:00
..
list_update_policy
2007-06-01 18:53:36 +00:00
..
ov_tree_map_
2007-06-01 18:53:36 +00:00
..
pairing_heap_
2007-06-01 18:53:36 +00:00
..
pat_trie_
..
rb_tree_map_
2007-06-01 18:53:36 +00:00
..
rc_binomial_heap_
..
resize_policy
2007-06-01 18:53:36 +00:00
..
splay_tree_
2007-06-01 18:53:36 +00:00
..
thin_heap_
2007-06-01 18:53:36 +00:00
..
tree_policy
2007-06-01 18:53:36 +00:00
..
trie_policy
2007-06-01 18:53:36 +00:00
..
unordered_iterator
2007-06-01 18:53:36 +00:00
..
..
..
..
tr1
..
..
v1
experimental
..
ext
..
tr1
..
..
..
1998-09-15 10:22:37 +00:00
cam
Separate the parallel scsi knowledge out of the core of the XPT, and modularize it so that new transports can be created. Add a transport for SATA Add a periph+protocol layer for ATA Add a driver for AHCI-compliant hardware. Add a maxio field to CAM so that drivers can advertise their max I/O capability. Modify various drivers so that they are insulated from the value of MAXPHYS. The new ATA/SATA code supports AHCI-compliant hardware, and will override the classic ATA driver if it is loaded as a module at boot time or compiled into the kernel. The stack now support NCQ (tagged queueing) for increased performance on modern SATA drives. It also supports port multipliers. ATA drives are accessed via 'ada' device nodes. ATAPI drives are accessed via 'cd' device nodes. They can all be enumerated and manipulated via camcontrol, just like SCSI drives. SCSI commands are not translated to their ATA equivalents; ATA native commands are used throughout the entire stack, including camcontrol. See the camcontrol manpage for further details. Testing this code may require that you update your fstab, and possibly modify your BIOS to enable AHCI functionality, if available. This code is very experimental at the moment. The userland ABI/API has changed, so applications will need to be recompiled. It may change further in the near future. The 'ada' device name may also change as more infrastructure is completed in this project. The goal is to eventually put all CAM busses and devices until newbus, allowing for interesting topology and management options. Few functional changes will be seen with existing SCSI/SAS/FC drivers, though the userland ABI has still changed. In the future, transports specific modules for SAS and FC may appear in order to better support the topologies and capabilities of these technologies. The modularization of CAM and the addition of the ATA/SATA modules is meant to break CAM out of the mold of being specific to SCSI, letting it grow to be a framework for arbitrary transports and protocols. It also allows drivers to be written to support discrete hardware without jeopardizing the stability of non-related hardware. While only an AHCI driver is provided now, a Silicon Image driver is also in the works. Drivers for ICH1-4, ICH5-6, PIIX, classic IDE, and any other hardware is possible and encouraged. Help with new transports is also encouraged. Submitted by: scottl, mav Approved by: re
2009-07-10 08:18:08 +00:00
ata
..
mmc
..
nvme
..
1998-09-15 10:22:37 +00:00
scsi
..
..
casper
..
crypto
..
dev
acpica
..
agp
..
Fix bugs in the structure for rx_frame by making gap length one byte and a packed array so sizeof work. This broke RFMON mode and passing up 802.11 packets. The Linux emulation code was derived from the open source Linux driver to maintain compatibility. LEAP support is added, hints from Richard Johnson. I've verified this locally with PC350v42510.img firmware. More bug fixing from Marco to fix long passwords. Change DELAYs in flash part of driver to FLASH_DELAY which uses tsleep so it doesn't look like your system died during a flash update. Install header files in /usr/include/dev/an Cleanup some ifmedia bugs add "Home" key mode to ifmedia and ancontrol. This way you can manage 2 keys a little easier. Map the home mode into key 5. Enhance ifconfig to dump the various configured SSIDs. I use a bunch of different ones and roam between them. Use the syntax similar to the WEP keys to deal with setting difference SSIDs. Bump up up the Card capabilities RID since they added 2 bytes to it in the latest firmware. Thankfully we changed it from a terminal failure so the card still worked but the driver whined. Some cleanup patches from Marco Molteni. Submitted by: Richard Johnson <raj@cisco.com> Marco Molteni <molter@tin.it> and myself Various checks: David Wolfskill <david@catwhisker.org> Reviewed by: Brooks Davis <brooks@freebsd.org> Warner Losh <imp@freebsd.org> Approved by: Brooks Davis <brooks@freebsd.org> Warner Losh <imp@freebsd.org> Obtained from: Linux emulation API's from Aironet driver.
2001-12-31 22:01:44 +00:00
an
..
bktr
..
ciss
..
evdev
..
filemon
..
firewire
..
hwpmc
..
2016-11-15 02:36:12 +00:00
hyperv
..
2001-06-05 07:07:52 +00:00
ic
..
iicbus
..
io
..
mfi
..
mlx5
..
- Add support for eMMC "partitions". Besides the user data area, i. e. the default partition, eMMC v4.41 and later devices can additionally provide up to: 1 enhanced user data area partition 2 boot partitions 1 RPMB (Replay Protected Memory Block) partition 4 general purpose partitions (optionally with a enhanced or extended attribute) Of these "partitions", only the enhanced user data area one actually slices the user data area partition and, thus, gets handled with the help of geom_flashmap(4). The other types of partitions have address space independent from the default partition and need to be switched to via CMD6 (SWITCH), i. e. constitute a set of additional "disks". The second kind of these "partitions" doesn't fit that well into the design of mmc(4) and mmcsd(4). I've decided to let mmcsd(4) hook all of these "partitions" up as disk(9)'s (except for the RPMB partition as it didn't seem to make much sense to be able to put a file-system there and may require authentication; therefore, RPMB partitions are solely accessible via the newly added IOCTL interface currently; see also below). This approach for one resulted in cleaner code. Second, it retains the notion of mmcsd(4) children corresponding to a single physical device each. With the addition of some layering violations, it also would have been possible for mmc(4) to add separate mmcsd(4) instances with one disk each for all of these "partitions", however. Still, both mmc(4) and mmcsd(4) share some common code now e. g. for issuing CMD6, which has been factored out into mmc_subr.c. Besides simply subdividing eMMC devices, some Intel NUCs having UEFI code in the boot partitions etc., another use case for the partition support is the activation of pseudo-SLC mode, which manufacturers of eMMC chips typically associate with the enhanced user data area and/ or the enhanced attribute of general purpose partitions. CAVEAT EMPTOR: Partitioning eMMC devices is a one-time operation. - Now that properly issuing CMD6 is crucial (so data isn't written to the wrong partition for example), make a step into the direction of correctly handling the timeout for these commands in the MMC layer. Also, do a SEND_STATUS when CMD6 is invoked with an R1B response as recommended by relevant specifications. However, quite some work is left to be done in this regard; all other R1B-type commands done by the MMC layer also should be followed by a SEND_STATUS (CMD13), the erase timeout calculations/handling as documented in specifications are entirely ignored so far, the MMC layer doesn't provide timeouts applicable up to the bridge drivers and at least sdhci(4) currently is hardcoding 1 s as timeout for all command types unconditionally. Let alone already available return codes often not being checked in the MMC layer ... - Add an IOCTL interface to mmcsd(4); this is sufficiently compatible with Linux so that the GNU mmc-utils can be ported to and used with FreeBSD (note that due to the remaining deficiencies outlined above SANITIZE operations issued by/with `mmc` currently most likely will fail). These latter will be added to ports as sysutils/mmc-utils in a bit. Among others, the `mmc` tool of the GNU mmc-utils allows for partitioning eMMC devices (tested working). - For devices following the eMMC specification v4.41 or later, year 0 is 2013 rather than 1997; so correct this for assembling the device ID string properly. - Let mmcsd.ko depend on mmc.ko. Additionally, bump MMC_VERSION as at least for some of the above a matching pair is required. - In the ACPI front-end of sdhci(4) describe the Intel eMMC and SDXC controllers as such in order to match the PCI one. Additionally, in the entry for the 80860F14 SDXC controller remove the eMMC-only SDHCI_QUIRK_INTEL_POWER_UP_RESET. OKed by: imp Submitted by: ian (mmc_switch_status() implementation)
2017-03-16 22:23:04 +00:00
mmc
..
mpt
mpilib
..
..
nvme
..
ofw
..
pbio
..
pci
..
powermac_nvram
..
ppbus
..
pwm
..
smbus
..
2005-11-11 17:38:10 +00:00
speaker
..
Add the "TCP Blackbox Recorder" which we discussed at the developer summits at BSDCan and BSDCam in 2017. The TCP Blackbox Recorder allows you to capture events on a TCP connection in a ring buffer. It stores metadata with the event. It optionally stores the TCP header associated with an event (if the event is associated with a packet) and also optionally stores information on the sockets. It supports setting a log ID on a TCP connection and using this to correlate multiple connections that share a common log ID. You can log connections in different modes. If you are doing a coordinated test with a particular connection, you may tell the system to put it in mode 4 (continuous dump). Or, if you just want to monitor for errors, you can put it in mode 1 (ring buffer) and dump all the ring buffers associated with the connection ID when we receive an error signal for that connection ID. You can set a default mode that will be applied to a particular ratio of incoming connections. You can also manually set a mode using a socket option. This commit includes only basic probes. rrs@ has added quite an abundance of probes in his TCP development work. He plans to commit those soon. There are user-space programs which we plan to commit as ports. These read the data from the log device and output pcapng files, and then let you analyze the data (and metadata) in the pcapng files. Reviewed by: gnn (previous version) Obtained from: Netflix, Inc. Relnotes: yes Differential Revision: https://reviews.freebsd.org/D11085
2018-03-22 09:40:08 +00:00
tcp_log
..
usb
..
veriexec
..
vkbd
..
wi
..
..
zfsd(8), the ZFS fault management daemon Add zfsd, which deals with hard drive faults in ZFS pools. It manages hotspares and replements in drive slots that publish physical paths. cddl/usr.sbin/zfsd Add zfsd(8) and its unit tests cddl/usr.sbin/Makefile Add zfsd to the build lib/libdevdctl A C++ library that helps devd clients process events lib/Makefile share/mk/bsd.libnames.mk share/mk/src.libnames.mk Add libdevdctl to the build. It's a private library, unusable by out-of-tree software. etc/defaults/rc.conf By default, set zfsd_enable to NO etc/mtree/BSD.include.dist Add a directory for libdevdctl's include files etc/mtree/BSD.tests.dist Add a directory for zfsd's unit tests etc/mtree/BSD.var.dist Add /var/db/zfsd/cases, where zfsd stores case files while it's shut down. etc/rc.d/Makefile etc/rc.d/zfsd Add zfsd's rc script sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c Fix the resource.fs.zfs.statechange message. It had a number of problems: It was only being emitted on a transition to the HEALTHY state. That made it impossible for zfsd to take actions based on drives getting sicker. It compared the new state to vdev_prevstate, which is the state that the vdev had the last time it was opened. That doesn't make sense, because a vdev can change state multiple times without being reopened. vdev_set_state contains logic that will change the device's new state based on various conditions. However, the statechange event was being posted _before_ that logic took effect. Now it's being posted after. Submitted by: gibbs, asomers, mav, allanjude Reviewed by: mav, delphij Relnotes: yes Sponsored by: Spectra Logic Corp, iX Systems Differential Revision: https://reviews.freebsd.org/D6564
2016-05-28 17:43:40 +00:00
devdctl
..
edit
readline
..
..
fs
2014-05-24 20:31:55 +00:00
cuse
..
2001-12-17 13:38:58 +00:00
devfs
..
fdescfs
..
msdosfs
..
nfs
..
nullfs
..
procfs
..
smbfs
..
udf
..
unionfs
..
..
gcc
4.2
..
..
2003-02-08 13:25:48 +00:00
geom
cache
..
concat
..
eli
..
gate
..
journal
..
label
..
mirror
..
mountver
..
multipath
..
nop
..
raid
..
2004-08-16 06:36:21 +00:00
raid3
..
2005-01-11 18:18:40 +00:00
shsec
..
stripe
..
virstor
..
2003-02-08 13:25:48 +00:00
..
2004-02-16 22:23:34 +00:00
gnu
2004-02-25 02:51:37 +00:00
posix
..
2004-02-16 22:23:34 +00:00
..
gssapi
..
infiniband
complib
..
iba
..
opensm
..
vendor
..
..
isofs
cd9660
..
..
kadm5
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
..
krb5
..
lib80211
..
libipt
..
libmilter
..
libxo
..
lzma
..
machine
pc
..
..
net
altq
..
..
2003-06-25 14:59:17 +00:00
net80211
..
netgraph
atm
..
bluetooth
include
..
..
netflow
..
..
netinet
cc
..
netdump
..
..
netinet6
..
2002-10-18 04:21:29 +00:00
netipsec
..
2000-10-15 00:43:06 +00:00
netnatm
api
..
msg
..
saal
..
sig
..
2000-10-15 00:43:06 +00:00
..
netpfil
pf
..
..
netsmb
..
nfs
..
nfsclient
..
nfsserver
..
opencsd
c_api
..
etmv3
..
etmv4
..
ptm
..
stm
..
..
openssl
..
pcap
..
protocols
..
rdma
..
rpc
..
rpcsvc
..
security
audit
..
mac_biba
..
mac_bsdextended
..
mac_lomac
..
mac_mls
..
mac_partition
..
mac_veriexec
..
..
ssp
..
sys
disk
..
..
teken
..
ufs
ffs
..
ufs
..
..
vm
..
xlocale
..
..