Searched refs:NFS (Results 1 – 25 of 164) sorted by relevance
1234567
3 tristate "NFS client support"14 To mount file systems exported by NFS servers, you also need to18 mount(8) man page. More detail about the Linux NFS client21 Below you can choose which versions of the NFS protocol are22 available in the kernel to mount NFS servers. Support for NFS25 To configure a system which mounts its root file system via NFS28 system on NFS" below. You cannot compile this file system as a34 tristate "NFS client support for NFS version 2"38 This option enables support for version 2 of the NFS protocol39 (RFC 1094) in the kernel's NFS client.[all …]
3 tristate "NFS server support"15 protocol. To compile the NFS server support as a module,18 You may choose to use a user-space NFS server instead, in which21 To export local file systems using NFS, you also need to install24 the Linux NFS server implementation is available via the27 Below you can choose which versions of the NFS protocol are28 available to clients mounting the NFS server on this system.29 Support for NFS version 2 (RFC 1094) is always available when39 bool "NFS server support for NFS version 3"42 This option enables support in your system's NFS server for[all …]
2 Setting up NFS/RDMA14 This document describes how to install and setup the Linux NFS/RDMA client17 The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server35 use with NFS/RDMA.46 The first kernel release to contain both the NFS/RDMA client and server was55 An NFS/RDMA mount point can be obtained by using the mount.nfs command in57 version with support for NFS/RDMA mounts, but for various reasons we73 these to create an NFS/RDMA enabled mount command), the installation85 the utils/mount directory. This binary can be used to initiate NFS v2, v3,96 In this location, mount.nfs will be invoked automatically for NFS mounts[all …]
2 NFS Client5 The NFS client8 The NFS version 2 protocol was first documented in RFC1094 (March 1989).9 Since then two more major releases of NFS have been published, with NFSv313 The Linux NFS client currently supports all the above published versions,18 special features of the NFS client that can be configured by system39 used instead of a system's node name when an NFS client identifies itself to42 or loss of state during NFS reboot recovery or transparent state migration.45 anything that is believed to be unique across all NFS clients. An54 This string can be stored in an NFS client's grub.conf, or it can be provided[all …]
2 Mounting the root filesystem via NFS (nfsroot)22 Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS. The23 following text describes on how to use NFS for the root filesystem. For the rest24 of this text 'client' means the diskless system, and 'server' means the NFS33 In order to use nfsroot, NFS client support needs to be selected as54 This is necessary to enable the pseudo-NFS-device. Note that it's not a55 real device but just a synonym to tell the kernel to use NFS instead of63 <server-ip> Specifies the IP address of the NFS server.66 servers for IP autoconfiguration and NFS.73 <nfs-options> Standard NFS options. All options are separated by commas.[all …]
6 This document describes support for pNFS SCSI layouts in the Linux NFS server.7 With pNFS SCSI layouts, the NFS server acts as Metadata Server (MDS) for pNFS,8 which in addition to handling all the metadata access to the NFS export,12 To use pNFS SCSI layouts with the Linux NFS server, the exported file
5 The Linux NFS server now supports the pNFS block layout extension. In this6 case the NFS server acts as Metadata Server (MDS) for pNFS, which in addition7 to handling all the metadata access to the NFS export also hands out layouts11 To use pNFS block layouts with the Linux NFS server the exported file
2 NFS ID Mapper5 Id mapper is used by NFS to translate user and group ids into names, and to8 ways NFS could obtain this information: placing a call to /sbin/request-key11 NFS will attempt to call /sbin/request-key first. If this succeeds, the20 in a custom NFS idmap cache.
2 Kernel NFS Server Statistics8 which the kernel NFS server makes available to userspace. These31 for each NFS thread pool.38 The id number of the NFS thread pool to which this line applies.49 Counts how many NFS packets have arrived. More precisely, this52 (e.g. an NFS or UDP socket or an NFS/RDMA endpoint).54 Depending on the NFS workload patterns and various network stack57 of NFS calls received (which statistic is available elsewhere).60 due to NFS network traffic.63 Counts how many times an NFS transport is enqueued to wait for[all …]
6 implement RPCGSS authentication in kernel RPC servers such as the NFS7 server and the NFS client's NFSv4.0 callback server. (But note that24 Authentication for NFS. Although GSSAPI is itself completely mechanism25 agnostic, in many cases only the KRB5 mechanism is supported by NFS46 NFS Server Legacy Upcall Mechanism67 NFS Server New RPC Upcall Mechanism
13 The NFS Linux kernel server.47 NFS lock manager for Linux kernels older than 2.454 NFS server59 NFS remote quota server
5 SUMMARY = "NFS package groups"12 SUMMARY:${PN}-client = "NFS client"15 SUMMARY:${PN}-server = "NFS server"
8 ==== NFS boot10 To achieve NFS-boot, enable _tar root filesystem_ in the _Filesystem14 NFS-root directory:22 Then, you can execute a NFS-boot from your target.
1 SUMMARY = "Userspace NFS server v3 protocol"3 specification. It provides a daemon for the MOUNT and NFS protocols, which \4 are used by NFS clients for accessing files on the server."
39 + printf("\t-x <port> alternate NFS RPC port\n");46 + fprintf(stderr, "Invalid NFS RPC port\n");85 /* Register NFS service for UDP */94 /* Register NFS service for TCP */
65 bool "Overlayfs: turn on NFS export feature by default"71 the index directory to decode overlay NFS file handles by default.72 In this case, it is still possible to turn off NFS export support76 The NFS export feature creates an index on copy up of every file and83 Note, that the NFS export feature is not backward compatible.
1# ncurses 6.1 - patch 20191123 - Thomas E. Dickey 2# 3# --- ...
6 Coda is an advanced network file system, similar to NFS in that it9 disk. Coda has several advantages over NFS: support for
57 netmask, ethaddr, eth1addr, rootpath (if using NFS root),61 want an NFS root or a ramdisk root:
11 your root filesystem over NFS or copy the contents of this directory19 extract to your SD card or to some directory exposed through NFS,
44 If all underlying filesystems support NFS file handles and export file104 must provide valid d_type in readdir responses, so NFS is not suitable.264 When the NFS export feature is enabled, every copied up directory is274 NFS export support on an overlay filesystem with no upper layer requires330 permissions (used by NFS, for example) being ignored (3).417 With the "inodes index" feature, on the first time mount, an NFS file425 does not support NFS export, lower filesystem does not have a valid UUID or501 When the overlay NFS export feature is enabled, overlay filesystems503 than the behavior when NFS export is disabled.505 On every copy_up, an NFS file handle of the lower inode, along with the[all …]
14 non-block filesystems which provide their own BDI, such as NFS47 most of the write-back cache. For example in case of an NFS
172 If using NFS as part of the setup process, you will also need:173 * NFS root setup on your workstation183 --- Booting from NFS root / kernel via TFTP ---212 box and populate it from another computer, or use a previously booted NFS229 Type 2: NFS241 1. Boot from NFS root
22 network using NFS, you don't need the System V file system support23 (but you need NFS file system support obviously).