From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 218266] Need article about Linux shutdown process
Date: Fri, 15 Dec 2023 11:34:06 +0000 [thread overview]
Message-ID: <bug-218266-11311-dqcPm2kKyI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218266-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218266
--- Comment #3 from Alejandro Colomar (alx@kernel.org) ---
On Fri, Dec 15, 2023 at 11:24:41AM +0000, bugzilla-daemon@kernel.org wrote:
> No, this is too complex a topic and the current manpages content is clearly
> not
> enough. This is not about using the shutdown command, but about the
> information
> necessary to build an rtl programming language. Perhaps some explanatory
> graphical files are also needed.
I meant in section 7, because that's the Miscellaneous Information
Manual.
The page for the command is shutdown(1).
In section 7 there are some pages that have that style of articles
explaining how to do something. See for example the most recent
addition: string_copying(7).
>
> It is possible, of course, to dramatically simplify the task by making your
> own
> patch for the kernel and describing it, but I think it would be better to
> describe how it works now on the part of the kernel developers. I have
> nothing
> to write about now - there is not enough information about the topic.
Ok.
Have a lovely day,
Alex
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-12-15 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 6:29 [Bug 218266] New: Need article about Linux shutdown process bugzilla-daemon
2023-12-15 10:27 ` [Bug 218266] " bugzilla-daemon
2023-12-15 11:24 ` bugzilla-daemon
2023-12-15 11:34 ` bugzilla-daemon [this message]
2023-12-22 14:09 ` bugzilla-daemon
2023-12-22 19:14 ` bugzilla-daemon
2023-12-25 10:19 ` bugzilla-daemon
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-218266-11311-dqcPm2kKyI@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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