From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 214721] New: initrd(4) man-page lacks information for kernel behaviour if linuxrc mounted an fs
Date: Thu, 14 Oct 2021 14:18:25 +0000 [thread overview]
Message-ID: <bug-214721-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=214721
Bug ID: 214721
Summary: initrd(4) man-page lacks information for kernel
behaviour if linuxrc mounted an fs
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: mishaparem@gmail.com
Regression: No
Where:
https://man7.org/linux/man-pages/man4/initrd.4.html
Section: Boot-up operation
Part: 6.
-AND-
Section: NOTES
-OR-
https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/man4/initrd.4
lines: 138-141
-AND-
lines: 441-474
What:
initrd(4), Section Boot-up operation, part 6. (lines 138-141) says:
"
If /linuxrc is not executed or when /linuxrc terminates, the
normal root filesystem is mounted. (If /linuxrc exits with
any filesystems mounted on the initial root filesystem, then
the behavior of the kernel is UNSPECIFIED. See the NOTES
section for the current kernel behavior.)
"
However, the NOTES section (lines 441-474):
Does NOT contain "current kernel behavior" if "/linuxrc exits with any
filesystems mounted on the initial root filesystem".
Proposed solution:
Add a description of the current kernel behavior, when /linuxrc exits with any
filesystems mounted on the initial root filesystem.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2021-10-14 14:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-214721-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox