How to get informations on each type of filesystem in /proc/filesystems
How do we get detailed information (history, what is used for, etc.) on each filesystem or pseudo filesystem displayed by :
cat /proc/filesystems
Example : nodev, sysfs, rootfs, ramfs, bdev, proc , cgroup, cpuset, tmpfs, devtmpsfs, debugfs, securityfs, sockfs, dax, pipefs, anon_inodefs, configfs, devpts, hungelbfs, autofs, pstore, mqueue, selinuxfs, binfmt_misc, etc.
linux filesystems mount proc
asked Jan 9 at 21:44
Omar BISTAMIOmar BISTAMI
49119
add a comment |
How do we get detailed information (history, what is used for, etc.) on each filesystem or pseudo filesystem displayed by :
cat /proc/filesystems
Example : nodev, sysfs, rootfs, ramfs, bdev, proc , cgroup, cpuset, tmpfs, devtmpsfs, debugfs, securityfs, sockfs, dax, pipefs, anon_inodefs, configfs, devpts, hungelbfs, autofs, pstore, mqueue, selinuxfs, binfmt_misc, etc.
linux filesystems mount proc
asked Jan 9 at 21:44
Omar BISTAMIOmar BISTAMI
49119
1
seeman 5 filesystemsandman 5 proc.
– DopeGhoti
Jan 9 at 22:11
Thank you for the answer , i have found some of the information indeed in man pages. (you could have added this as answer :) ).
– Omar BISTAMI
Jan 10 at 9:37
add a comment |
How do we get detailed information (history, what is used for, etc.) on each filesystem or pseudo filesystem displayed by :
cat /proc/filesystems
Example : nodev, sysfs, rootfs, ramfs, bdev, proc , cgroup, cpuset, tmpfs, devtmpsfs, debugfs, securityfs, sockfs, dax, pipefs, anon_inodefs, configfs, devpts, hungelbfs, autofs, pstore, mqueue, selinuxfs, binfmt_misc, etc.
linux filesystems mount proc
asked Jan 9 at 21:44
Omar BISTAMIOmar BISTAMI
49119
How do we get detailed information (history, what is used for, etc.) on each filesystem or pseudo filesystem displayed by :
cat /proc/filesystems
Example : nodev, sysfs, rootfs, ramfs, bdev, proc , cgroup, cpuset, tmpfs, devtmpsfs, debugfs, securityfs, sockfs, dax, pipefs, anon_inodefs, configfs, devpts, hungelbfs, autofs, pstore, mqueue, selinuxfs, binfmt_misc, etc.
linux filesystems mount proc
linux filesystems mount proc
asked Jan 9 at 21:44
Omar BISTAMIOmar BISTAMI
49119
asked Jan 9 at 21:44
Omar BISTAMIOmar BISTAMI
49119
asked Jan 9 at 21:44
Omar BISTAMIOmar BISTAMI
49119
asked Jan 9 at 21:44
Omar BISTAMIOmar BISTAMI
49119
asked Jan 9 at 21:44
Omar BISTAMIOmar BISTAMI
49119
49119
1
seeman 5 filesystemsandman 5 proc.
– DopeGhoti
Jan 9 at 22:11
Thank you for the answer , i have found some of the information indeed in man pages. (you could have added this as answer :) ).
– Omar BISTAMI
Jan 10 at 9:37
add a comment |
1
seeman 5 filesystemsandman 5 proc.
– DopeGhoti
Jan 9 at 22:11
Thank you for the answer , i have found some of the information indeed in man pages. (you could have added this as answer :) ).
– Omar BISTAMI
Jan 10 at 9:37
1
1
see
man 5 filesystems and man 5 proc.– DopeGhoti
Jan 9 at 22:11
see
man 5 filesystems and man 5 proc.– DopeGhoti
Jan 9 at 22:11
Thank you for the answer , i have found some of the information indeed in man pages. (you could have added this as answer :) ).
– Omar BISTAMI
Jan 10 at 9:37
Thank you for the answer , i have found some of the information indeed in man pages. (you could have added this as answer :) ).
– Omar BISTAMI
Jan 10 at 9:37
add a comment |
1 Answer
1
active
oldest
votes
nodev isn't a filesystem. It's a qualifier on the filesystems - specifically, it means the filesystem listed in field two doesn't have a device associated with it. Yeah, there's a lot of those - over 75% of them on a typical modern Linux.
In addition to the man pages DopeGhoti pointed out, there are also manpages for a number of the specific filesystems in section 5, including ext4, sysfs, and tmpfs. Beyond that, there's generally fairly copious amount of documentation about them in the Documentation directory of the linux kernel source. (It's not quite as scary as the linux kernel source code. It's all technically in English, rather than in C with frequent helpful comment blocks like the kernel source.)
answered Jan 10 at 4:21
Ed GrimmEd Grimm
613
New contributor
Ed Grimm is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Thank you Ed Grimm for your answer, when you say documentation directory of Linux kernel source, are you talking about the git ?
– Omar BISTAMI
Jan 10 at 9:37
1
Last time I looked at the contents of the Documentation directory, it was the complement of the source. The source files were abstruse C code with helpful comment blocks in English; the docs were abstruse English with helpful comment blocks in C. (:
– DopeGhoti
Jan 10 at 15:34
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493562%2fhow-to-get-informations-on-each-type-of-filesystem-in-proc-filesystems%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
nodev isn't a filesystem. It's a qualifier on the filesystems - specifically, it means the filesystem listed in field two doesn't have a device associated with it. Yeah, there's a lot of those - over 75% of them on a typical modern Linux.
In addition to the man pages DopeGhoti pointed out, there are also manpages for a number of the specific filesystems in section 5, including ext4, sysfs, and tmpfs. Beyond that, there's generally fairly copious amount of documentation about them in the Documentation directory of the linux kernel source. (It's not quite as scary as the linux kernel source code. It's all technically in English, rather than in C with frequent helpful comment blocks like the kernel source.)
answered Jan 10 at 4:21
Ed GrimmEd Grimm
613
New contributor
Ed Grimm is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Thank you Ed Grimm for your answer, when you say documentation directory of Linux kernel source, are you talking about the git ?
– Omar BISTAMI
Jan 10 at 9:37
1
Last time I looked at the contents of the Documentation directory, it was the complement of the source. The source files were abstruse C code with helpful comment blocks in English; the docs were abstruse English with helpful comment blocks in C. (:
– DopeGhoti
Jan 10 at 15:34
add a comment |
nodev isn't a filesystem. It's a qualifier on the filesystems - specifically, it means the filesystem listed in field two doesn't have a device associated with it. Yeah, there's a lot of those - over 75% of them on a typical modern Linux.
In addition to the man pages DopeGhoti pointed out, there are also manpages for a number of the specific filesystems in section 5, including ext4, sysfs, and tmpfs. Beyond that, there's generally fairly copious amount of documentation about them in the Documentation directory of the linux kernel source. (It's not quite as scary as the linux kernel source code. It's all technically in English, rather than in C with frequent helpful comment blocks like the kernel source.)
answered Jan 10 at 4:21
Ed GrimmEd Grimm
613
New contributor
Ed Grimm is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Thank you Ed Grimm for your answer, when you say documentation directory of Linux kernel source, are you talking about the git ?
– Omar BISTAMI
Jan 10 at 9:37
1
Last time I looked at the contents of the Documentation directory, it was the complement of the source. The source files were abstruse C code with helpful comment blocks in English; the docs were abstruse English with helpful comment blocks in C. (:
– DopeGhoti
Jan 10 at 15:34
add a comment |
nodev isn't a filesystem. It's a qualifier on the filesystems - specifically, it means the filesystem listed in field two doesn't have a device associated with it. Yeah, there's a lot of those - over 75% of them on a typical modern Linux.
In addition to the man pages DopeGhoti pointed out, there are also manpages for a number of the specific filesystems in section 5, including ext4, sysfs, and tmpfs. Beyond that, there's generally fairly copious amount of documentation about them in the Documentation directory of the linux kernel source. (It's not quite as scary as the linux kernel source code. It's all technically in English, rather than in C with frequent helpful comment blocks like the kernel source.)
answered Jan 10 at 4:21
Ed GrimmEd Grimm
613
New contributor
Ed Grimm is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
nodev isn't a filesystem. It's a qualifier on the filesystems - specifically, it means the filesystem listed in field two doesn't have a device associated with it. Yeah, there's a lot of those - over 75% of them on a typical modern Linux.
In addition to the man pages DopeGhoti pointed out, there are also manpages for a number of the specific filesystems in section 5, including ext4, sysfs, and tmpfs. Beyond that, there's generally fairly copious amount of documentation about them in the Documentation directory of the linux kernel source. (It's not quite as scary as the linux kernel source code. It's all technically in English, rather than in C with frequent helpful comment blocks like the kernel source.)
answered Jan 10 at 4:21
Ed GrimmEd Grimm
613
New contributor
Ed Grimm is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Jan 10 at 4:21
Ed GrimmEd Grimm
613
New contributor
Ed Grimm is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Jan 10 at 4:21
Ed GrimmEd Grimm
613
answered Jan 10 at 4:21
Ed GrimmEd Grimm
613
613
New contributor
Ed Grimm is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Ed Grimm is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Ed Grimm is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Thank you Ed Grimm for your answer, when you say documentation directory of Linux kernel source, are you talking about the git ?
– Omar BISTAMI
Jan 10 at 9:37
1
Last time I looked at the contents of the Documentation directory, it was the complement of the source. The source files were abstruse C code with helpful comment blocks in English; the docs were abstruse English with helpful comment blocks in C. (:
– DopeGhoti
Jan 10 at 15:34
add a comment |
Thank you Ed Grimm for your answer, when you say documentation directory of Linux kernel source, are you talking about the git ?
– Omar BISTAMI
Jan 10 at 9:37
1
Last time I looked at the contents of the Documentation directory, it was the complement of the source. The source files were abstruse C code with helpful comment blocks in English; the docs were abstruse English with helpful comment blocks in C. (:
– DopeGhoti
Jan 10 at 15:34
Thank you Ed Grimm for your answer, when you say documentation directory of Linux kernel source, are you talking about the git ?
– Omar BISTAMI
Jan 10 at 9:37
Thank you Ed Grimm for your answer, when you say documentation directory of Linux kernel source, are you talking about the git ?
– Omar BISTAMI
Jan 10 at 9:37
1
1
Last time I looked at the contents of the Documentation directory, it was the complement of the source. The source files were abstruse C code with helpful comment blocks in English; the docs were abstruse English with helpful comment blocks in C. (:
– DopeGhoti
Jan 10 at 15:34
Last time I looked at the contents of the Documentation directory, it was the complement of the source. The source files were abstruse C code with helpful comment blocks in English; the docs were abstruse English with helpful comment blocks in C. (:
– DopeGhoti
Jan 10 at 15:34
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493562%2fhow-to-get-informations-on-each-type-of-filesystem-in-proc-filesystems%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
see
man 5 filesystemsandman 5 proc.– DopeGhoti
Jan 9 at 22:11
Thank you for the answer , i have found some of the information indeed in man pages. (you could have added this as answer :) ).
– Omar BISTAMI
Jan 10 at 9:37