Searched full:unix (Results 1 – 25 of 77) sorted by relevance
1234
| /Documentation/admin-guide/cifs/ |
| D | usage.rst | 143 Unix Extensions standard (e.g. almost any version of Samba ie version
146 not have a server that supports the Unix extensions for CIFS (such as Samba
147 2.2.5 or later). To enable the Unix CIFS Extensions in the Samba server, add
150 unix extensions = yes
153 are also useful (on the Samba server) when the majority of clients are Unix or
177 which may not be what you want, although if the CIFS Unix extensions are
199 later, but only for remote clients using the CIFS Unix extensions, and will
267 configured for Unix Extensions (and the client has not disabled
296 which do support the CIFS Unix extensions, such as a
302 the server supports the Unix Extensions then the uid
[all …]
|
| D | authors.rst | 16 side of the original CIFS Unix extensions and reviewing and implementing
19 for proving years ago that very good smb/cifs clients could be done on Unix-like
|
| D | introduction.rst | 31 CIFS Unix extensions, and the Linux client also supports SMB3 POSIX extensions,
|
| /Documentation/filesystems/smb/ |
| D | cifsroot.rst | 22 A CIFS root mount currently requires the use of SMB1+UNIX Extensions
38 To enable SMB1+UNIX extensions you will need to set these global
43 unix extension = yes # default
|
| /Documentation/ABI/stable/ |
| D | syscalls | 4 on it and other Unix based interfaces. It will only be added to
|
| /Documentation/security/ |
| D | credentials.rst | 37 In a standard UNIX filesystem, for instance, this will be defined by the
44 the same set as in (2) - in standard UNIX files, for instance, this is the
100 A traditional UNIX file, for example, includes a permissions mask that
104 in question). UNIX file permissions do not allow the arbitrary
127 1. Traditional UNIX credentials.
155 These are manipulated implicitly by changes to the traditional UNIX
183 that don't fit into the other standard UNIX credentials. They are for
234 * UNIX UID, GID, mode;
238 * UNIX exec privilege escalation bits (SUID/SGID);
|
| D | landlock.rst | 82 processes (e.g. through a Unix domain socket). Such access rights will then be
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-aggregator.rst | 14 devices. Access control to these devices is provided by standard UNIX file
20 using standard UNIX file ownership and permissions. Furthermore, this
|
| /Documentation/filesystems/nfs/ |
| D | rpc-server-gss.rst | 70 The newer upcall mechanism uses RPC over a unix socket to a daemon
77 userspace program over a regular unix socket. The gssproxy protocol does not
|
| /Documentation/devicetree/bindings/rtc/ |
| D | qcom-pm8xxx-rtc.yaml | 46 four-byte nvmem cell holding a little-endian offset from the Unix
|
| /Documentation/filesystems/ |
| D | coda.rst | 144 ``rmdir``, ``chmod`` in a Unix ontext. Similar calls exist in the Win32
293 The Unix implementation of this mechanism has been through the
360 Unix the CodaCred has proven sufficient to implement good security
704 under Unix.
711 This create call differs from the Unix one in that it is not invoked
714 under Unix. There should be no flags argument; this is used in open
960 for Unix and Windows systems. For Unix systems the Coda FS Driver is
1078 srcname and destname are 0 terminated strings. Strings in Unix
1263 Allows mounting multiple Coda "filesystems" on one Unix mount point.
1628 1. The message queues should have open and close routines. On Unix
|
| D | 9p.rst | 10 v9fs is a Unix implementation of the Plan 9 9p remote filesystem protocol.
45 mount -t 9p `namespace`/acme /mnt/9 -o trans=unix,uname=$USER
119 unix specifying a named pipe mount point
|
| D | hfs.rst | 54 HFS is not a UNIX filesystem, thus it does not have the usual features you'd
|
| D | isofs.rst | 21 Unix for the most part doesn't know how to deal with Unicode.
|
| /Documentation/admin-guide/ |
| D | README.rst | 13 Linux is a clone of the operating system Unix, written from scratch by
15 the Net. It aims towards POSIX and Single UNIX Specification compliance.
17 It has all the features you would expect in a modern fully-fledged Unix,
47 general UNIX questions. I'd recommend looking into the documentation
|
| /Documentation/filesystems/ext4/ |
| D | orphan.rst | 6 In unix there can inodes that are unlinked from directory hierarchy but that
|
| /Documentation/admin-guide/sysctl/ |
| D | net.rst | 42 ethernet Ethernet protocol unix Unix domain sockets
426 2. /proc/sys/net/unix - Parameters for Unix domain sockets
430 unix_dgram_qlen limits the max number of datagrams queued in Unix domain
|
| /Documentation/accounting/ |
| D | delay-accounting.rst | 30 thread group (corresponding to a traditional Unix process). This is a commonly
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-output.rst | 55 time to permit Unix tool chains, programming a device and then writing
|
| D | dev-capture.rst | 57 time to permit Unix tool chains, programming a device and then reading
|
| /Documentation/block/ |
| D | stat.rst | 72 standard UNIX 512-byte sectors, not any device- or filesystem-specific
|
| /Documentation/virt/gunyah/ |
| D | index.rst | 83 Unlike UNIX file descriptors, there is no path-based or similar lookup of
|
| /Documentation/core-api/ |
| D | timekeeping.rst | 35 Returns the time in relative to the UNIX epoch starting in 1970
|
| /Documentation/userspace-api/media/dvb/ |
| D | intro.rst | 123 currently six Unix-style character devices for video, audio, frontend,
|
| /Documentation/networking/ |
| D | tipc.rst | 22 Have you ever wished you had the convenience of Unix Domain Sockets even when
|
1234