* the preferred coding style is based on the linux kernel coding-style.
Available here:
- https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/process/coding-style.rst
+ https://docs.kernel.org/process/coding-style.html
* use 'FIXME:' with a good description, if you want to inform others
that something is not quite right, and you are unwilling to fix the
* This file may be redistributed under the terms of the
* GNU Lesser General Public License
*
- * https://www.kernel.org/doc/html/latest/filesystems/erofs.html
+ * https://docs.kernel.org/filesystems/erofs.html
*/
#include <stddef.h>
#include <string.h>
#: ../sys-utils/mount.8.adoc:1108
msgid ""
"For a detailed description of the effect of this option please refer to "
-"https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html?highlight=overlayfs"
+"https://docs.kernel.org/filesystems/overlayfs.html"
msgstr ""
#. type: Labeled list
msgid ""
"*powertop*(8),\n"
"*systemd-rfkill*(8),\n"
-"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/driver-api/rfkill.rst[Linux "
+"https://docs.kernel.org/driver-api/rfkill.html[Linux "
"kernel documentation]\n"
msgstr ""
#. type: Plain text
#: ../sys-utils/zramctl.8.adoc:103
msgid ""
-"link:http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/blockdev/zram.rst[Linux "
+"https://docs.kernel.org/admin-guide/blockdev/zram.html[Linux "
"kernel documentation]"
msgstr ""
*sg_persist*(8)
-Linux documentation at: <https://www.kernel.org/doc/Documentation/block/pr.txt>
+Linux documentation at: <https://docs.kernel.org/block/pr.html>
iSCSI specification at: <https://datatracker.ietf.org/doc/html/rfc3720>
NVMe-oF specification at: <https://nvmexpress.org/nvme-over-fabrics-part-two/>
*xino=*{**on**|**off**|**auto**}::
The "xino" feature composes a unique object identifier from the real object st_ino and an underlying fsid index. The "xino" feature uses the high inode number bits for fsid, because the underlying filesystems rarely use the high inode number bits. In case the underlying inode number does overflow into the high xino bits, overlay filesystem will fall back to the non xino behavior for that inode.
+
-For a detailed description of the effect of this option please refer to https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html?highlight=overlayfs
+For a detailed description of the effect of this option please refer to https://docs.kernel.org/filesystems/overlayfs.html
*metacopy=*{**on**|**off**}::
When metadata only copy up feature is enabled, overlayfs will only copy up metadata (as opposed to whole file), when a metadata specific operation like chown/chmod is performed. Full file will be copied up later when file is opened for WRITE operation.
*powertop*(8),
*systemd-rfkill*(8),
-https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/driver-api/rfkill.rst[Linux kernel documentation]
+https://docs.kernel.org/driver-api/rfkill.html[Linux kernel documentation]
include::man-common/bugreports.adoc[]
== SEE ALSO
-link:http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/blockdev/zram.rst[Linux kernel documentation]
+link:https://docs.kernel.org/admin-guide/blockdev/zram.html[Linux kernel documentation]
include::man-common/bugreports.adoc[]