Lines Matching full:mount
17 be adjusted on the fly via 'mount -o remount ...'
33 1) There is always a kernel internal mount which you will not see at
37 This mount does not depend on CONFIG_TMPFS. If CONFIG_TMPFS is not
47 Remember to create the directory that you intend to mount tmpfs on
50 This mount is _not_ needed for SYSV shared memory. The internal
51 mount is used for that. (In the 2.3 kernel versions it was
52 necessary to mount the predecessor of tmpfs (shm fs) to use SYSV
55 3) Some people (including me) find it very convenient to mount it
63 tmpfs has three mount options for sizing:
84 mount with such options, since it allows any user with write access to
89 tmpfs has a mount option to set the NUMA memory allocation policy for
91 adjusted on the fly via 'mount -o remount ...'
109 system, the mount option memory policy will be applied with a NodeList,
130 Note that trying to mount a tmpfs with an mpol option will fail if the
136 mount options. It can be added later, when the tmpfs is already mounted
137 on MountPoint, by 'mount -o remount,mpol=Policy:NodeList MountPoint'.
140 To specify the initial root directory you can use the following mount
153 tmpfs has a mount option to select whether it will wrap at 32- or 64-bit inode
161 On a 32-bit kernel, inode32 is implicit, and inode64 is refused at mount time.
169 So 'mount -t tmpfs -o size=10G,nr_inodes=10k,mode=700 tmpfs /mytmpfs'