/freebsd/contrib/llvm-project/libcxx/include/ |
H A D | module.modulemap | 2 module std_algorithm [system] { 6 module std_any [system] { 10 module std_array [system] { 14 module std_atomic [system] { 18 module std_barrier [system] { 22 module std_bit [system] { 26 module std_bitset [system] { 30 module std_charconv [system] { 34 module std_chrono [system] { 38 module std_codecvt [system] { [all …]
|
/freebsd/share/doc/smm/02.config/ |
H A D | 3.t | 28 .\".ds RH "System Building Process 31 SYSTEM BUILDING PROCESS 33 In this section we consider the steps necessary to build a bootable system 34 image. We assume the system source is located in the ``/sys'' directory 35 and that, initially, the system is being configured from source code. 37 Under normal circumstances there are 5 steps in building a system. 39 Create a configuration file for the system. 41 Make a directory for the system to be constructed in. 46 to compile and load the system image. 49 configured system with [all …]
|
H A D | 2.t | 33 A system configuration must include at least the following 40 system identification 46 location of the root file system 51 allows multiple system images to be generated from a single 52 configuration description. Each system image is configured 54 file system and, possibly, other system devices. 60 indicates if the system is going to operate on a DEC VAX-11\(dg computer, 74 indicates which, of possibly many, cpu's the system is to operate on. 75 For example, if the system is being configured for a VAX-11, it could 80 more than one cpu type implies that the system should be configured to run [all …]
|
H A D | d.t | 38 Certain system data structures are sized at compile time 49 is copied into the directory of each configured system to allow 58 for use by other modules; they may generally be patched in the system 78 The maximum number of files in the file system which may be 80 well as directory files being read or written by the system 99 structure is used per internal system event handled with 124 are present only when disc quotas are configured in the system. One 132 are present only when disc quotas are configured in the system. 133 One dquot structure is required per user, per active file system quota. 134 That is, when a user manipulates a file on a file system on which [all …]
|
/freebsd/lib/libsys/ |
H A D | mount.2 | 35 .Nd mount or dismount a file system 51 system call grafts 52 a file system object onto the system file tree 57 describes the file system object to be mounted. 65 The contents of the file system 72 are unavailable until the file system is unmounted. 76 system call behaves similarly to 78 except that the mount options (file system type name, device to mount, 88 .Li fstype Ta file system type name (e.g., Dq Li procfs ) 93 Depending on the file system type, other options may be [all …]
|
H A D | statfs.2 | 33 .Nd get file system statistics 46 system call 47 returns information about a mounted file system. 51 is the path name of any file within the mounted file system. 59 typedef struct fsid { int32_t val[2]; } fsid_t; /* file system id type */ 98 The file system is mounted read-only; 101 Files may not be executed from the file system. 105 All I/O to the file system is done synchronously. 107 No file system I/O is done synchronously. 117 Union with underlying file system. [all …]
|
/freebsd/share/doc/psd/01.cacm/ |
H A D | p1 | 4 .OH 'The UNIX Time-Sharing System''PSD:1-%' 5 .EH 'PSD:1-%''The UNIX Time-Sharing System' 12 Time-Sharing System\f1\s10\v'-.2n'*\v'.2n'\s0\fP 35 operating system for the larger Digital Equipment Corporation 42 A hierarchical file system incorporating 49 System command language selectable on a per-user basis, 56 and implementation of the file system 65 time-sharing system. 78 system that runs on the \*sPDP\*n-11/70 and the 85 had to do with details of the implementation of the file system. [all …]
|
H A D | p5 | 10 Such faults cause the processor to trap to a system routine. 12 an illegal action causes the system 60 system 76 a text editing and formatting system. 78 the system 99 we naturally designed the system to make it easy to 103 was that the system 108 interactive system is much more 110 and satisfying to use than a ``batch'' system. 111 Moreover, such a system is rather easily [all …]
|
/freebsd/share/doc/smm/05.fastfs/ |
H A D | 3.t | 30 New file system organization 32 In the new file system organization (as in the 33 old file system organization), 35 A file system is described by its super-block, 36 located at the beginning of the file system's disk partition. 39 This is done when the file system is created; 49 the minimum size of a file system block is 4096 bytes. 50 The size of file system blocks can be any power of two 52 The block size of a file system is recorded in the 53 file system's super-block [all …]
|
H A D | 4.t | 34 is the long term performance of the new file system. 39 that itself contains many directories (to force the system 48 disk request queue on the old file system. 50 Table 2 summarizes the measured throughput of the new file system. 57 operating system does not affect the results. 59 the first to get the system into a known state 73 As Table 2 shows, all file system test runs were on a VAX 11/750. 76 The same number of system calls were performed in all tests; 77 the basic system call overhead was a negligible portion of 86 File System Bus Measured Speed Bandwidth % CPU [all …]
|
H A D | 2.t | 30 Old File System 32 In the file system developed at Bell Laboratories 33 (the ``traditional'' file system), 36 one file system. A file system never spans multiple 41 system, as in the new file system, file systems are really 47 A file system is described by its super-block, 48 which contains the basic parameters of the file system. 49 These include the number of data blocks in the file system, 52 list of all the free blocks in the file system. 54 Within the file system are files. [all …]
|
/freebsd/sbin/mount/ |
H A D | mount.8 | 56 system call to prepare and graft a 58 device or the remote node (rhost:path) on to the file system tree at the point 68 The system maintains a list of currently mounted file systems. 96 root file system which is always remounted to preserve 99 Causes everything to be done except for the actual system call. 112 a file system mount status from read-write to read-only. 114 forces the R/W mount of an unclean file system (dangerous; use with 149 All I/O to the file system should be done asynchronously. 152 flag to set, since it does not guarantee that the file system structure 162 This flag indicates that the file system was mounted by [all …]
|
/freebsd/share/doc/smm/03.fsck/ |
H A D | 2.t | 30 Overview of the file system 32 The file system is discussed in detail in [Mckusick84]; 37 A file system is described by its 39 The super-block is built when the file system is created (\c 43 contains the basic parameters of the file system, 52 of the file system's disk partition. 60 Within the file system are files. 73 \(dgThe actual number may vary from system to system, but is usually in 78 In a file system with a 4096 byte block size, a singly indirect 88 the minimum size of a file system block is 4096 bytes. [all …]
|
/freebsd/share/man/man5/ |
H A D | fstab.5 | 43 it is the duty of the system administrator to properly create 45 Each file system is described on a separate line; 61 remote file system to be mounted. 70 describes the mount point for the file system. 79 describes the type of the file system. 80 The system can support various file system types. 91 describes the mount options associated with the file system. 95 below) plus any additional options appropriate to the file system type. 100 page and the file system specifi [all...] |
/freebsd/share/doc/papers/sysperf/ |
H A D | 2.t | 33 of the system. 36 System maintenance tools 39 observing the basic actions of the system. 47 when the system is active you can judge the system activity in several 50 Ideally, to have a balanced system in activity, 57 If the system is busy, then the count of active jobs may be large, 66 when the system is busy (a ``vmstat 5'' gives all the 67 numbers computed by the system), you can find 72 that are doing high-speed non-buffered input/output, then the system 74 It is often possible to pin down the cause of high system time by [all …]
|
H A D | 3.t | 41 section we describe the changes made to the system. 46 Mail system 48 The mail system was the first culprit identified as a major 49 contributor to the degradation in system performance. 50 At Lucasfilm the mail system is heavily used 61 caused the system load to jump by anywhere from 3 to 6 points. 63 the messages sent from \fIsendmail\fP to the system logging 65 execution and their interference with basic system operation. The 67 \fIsendmail\fP operated; the system call rate jumped dramatically. 68 System accounting information consistently [all …]
|
/freebsd/sbin/fsck_ffs/ |
H A D | fsck_ffs.8 | 35 .Nd file system consistency check and interactive repair 46 In "preen" or "check clean" mode the clean flag of each file system's 58 The kernel takes care that only a restricted class of innocuous file system 82 identifying the file system on which the correction will take place, 84 After successfully correcting a file system, 86 will print the number of files on that file system, 94 will finish the file system checks, then exit with an abnormal 96 This is useful when you want to finish the file system checks during an 117 If the file system is inconsistent the operator is prompted for concurrence 130 If the operator does not have write permission on the file system [all...] |
/freebsd/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/java_api/src/ |
H A D | TestStateMachine.java | 50 System.out.println(msg); in exit() 52 System.out.flush(); in exit() 53 System.err.flush(); in exit() 54 System.exit(status); in exit() 60 System.out.println("open: " + consumer.isOpen()); in printState() 61 System.out.println("enabled: " + consumer.isEnabled()); in printState() 62 System.out.println("closed: " + consumer.isClosed()); in printState() 68 System.out.println("before open"); in beforeOpen() 76 System.out.println(e); in beforeOpen() 87 System.out.println(e); in beforeOpen() [all …]
|
/freebsd/usr.sbin/bluetooth/rtlbtfw/ |
H A D | rtlbtfw.conf | 7 match "system" "USB"; 21 match "system" "USB"; 31 match "system" "USB"; 41 match "system" "USB"; 51 match "system" "USB"; 59 match "system" "USB"; 67 match "system" "USB"; 75 match "system" "USB"; 85 match "system" "USB"; 93 match "system" "USB"; [all …]
|
/freebsd/usr.sbin/extattrctl/ |
H A D | extattrctl.8 | 29 .\" Support for file system extended attribute. 68 is the management utility for extended attributes over the UFS1 file system. 69 It allows the starting and stopping of extended attributes on a file system, 71 disabling of specific extended attributes on a file system. 78 Start extended attribute support on the file system named using 80 The file system must be an UFS1 file system, and the UFS_EXTATTR kernel 83 Stop extended attribute support on the file system named using 122 on the file system identified using 126 Available namespaces are "user" and "system" [all...] |
/freebsd/share/doc/smm/01.setup/ |
H A D | 6.t | 30 .Sh 1 "System operation" 32 This section describes procedures used to operate a \*(4B UNIX system. 33 Procedures described here are used periodically, to reboot the system, 35 system performance, recompile system software and control local changes. 38 In a normal reboot, the system checks the disks and comes up multi-user 42 This will leave the system in single-user mode, with only the console 52 To bring the system up to a multi-user configuration from the single-user 54 all you have to do is hit ^D on the console. The system 67 Unless the system was taken down cleanly, you should run 72 To take the system down to a single user state you can use [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/arm/hisilicon/controller/ |
H A D | sysctrl.yaml | 7 title: Hisilicon system controller 13 The Hisilicon system controller is used on many Hisilicon boards, it can be 14 used to assist the slave core startup, reboot the system, etc. 16 There are some variants of the Hisilicon system controller, such as HiP01, 17 Hi3519, Hi6220 system controller, each of them is mostly compatible with the 18 Hisilicon system controller, but some same registers located at different 19 offset. In addition, the HiP01 system controller has some specific control 22 The compatible names of each system controller are as follows: 23 Hisilicon system controller --> hisilicon,sysctrl 24 HiP01 system controlle [all...] |
/freebsd/share/doc/papers/beyond4.3/ |
H A D | beyond43.ms | 56 update other major components of the system, as well as to offer 69 audit the existing security features of the system, particularly 87 There have been several changes in the system that were included 135 The use of this facility has allowed improvements in the file system's 138 Fat Fast File System 140 The 4.2 fast file system [McKusick84] 219 of the IEEE POSIX P1003.1 system interface standard. 222 P1003.6 (security), P1003.7 (system administration), and P1003.8 226 POSIX related changes to the BSD system have included a new terminal 244 system. [all …]
|
/freebsd/sbin/shutdown/ |
H A D | shutdown.8 | 34 .Nd "close down the system at a given time" 54 to nicely notify users when the system is shutting down, 55 saving them from system administrators, hackers, and gurus, who 65 The system is power cycled (power turned off and then back on) 67 If the hardware doesn't support power cycle, the system will be 72 The amount of time the system is off is dependent on the device 75 The system is halted at the specified 78 The system is halted and the power is turned off 79 (hardware support required, otherwise the system is halted) 83 The system is rebooted at the specified [all …]
|
/freebsd/share/man/man9/ |
H A D | VFS_STATFS.9 | 34 .Nd return file system status 44 macro returns various pieces of information about the file system, 50 The file system. 56 into which information is placed about the file system. 61 related to the file system are as follows: 64 Type of file system. 72 The total number of data blocks in the file system. 74 The number of free blocks in the file system. 78 The total number of file nodes in the file system. 82 The number of synchronous writes since the file system was mounted. [all …]
|