From: Elie De Brauwer <eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Elie De Brauwer
<eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 2/3] mem.4: correct /dev/port group in example
Date: Fri, 2 Jan 2015 14:11:37 +0100 [thread overview]
Message-ID: <1420204298-25625-3-git-send-email-eliedebrauwer@gmail.com> (raw)
In-Reply-To: <1420204298-25625-1-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
mem.4 mentions that group for /dev/port should be set to 'mem' however
all other files (/dev/mem and /dev/kmem) use the kmem group in their
examples and on my system /dev/port belongs to kmem. Hence the 'mem'
group was probably a typo:
edb@lapelidb:~$ cat /etc/group | grep -i mem
kmem:x:15:
edb@lapelidb:~$ ls -al /dev/port
crw-r----- 1 root kmem 1, 4 Jan 2 10:00 /dev/port
Signed-off-by: Elie De Brauwer <eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
man4/mem.4 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man4/mem.4 b/man4/mem.4
index fef007e..6688345 100644
--- a/man4/mem.4
+++ b/man4/mem.4
@@ -76,7 +76,7 @@ It is typically created by:
.sp
mknod \-m 660 /dev/port c 1 4
.br
-chown root:mem /dev/port
+chown root:kmem /dev/port
.RE
.SH FILES
.I /dev/mem
--
2.1.3
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-01-02 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 13:11 [PATCH 0/3] mem.4 updates Elie De Brauwer
[not found] ` <1420204298-25625-1-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-02 13:11 ` [PATCH 1/3] mem.4: /dev/kmem depends on CONFIG_DEVKMEM Elie De Brauwer
[not found] ` <1420204298-25625-2-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-06 10:41 ` Michael Kerrisk (man-pages)
2015-01-02 13:11 ` Elie De Brauwer [this message]
[not found] ` <1420204298-25625-3-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-06 10:44 ` [PATCH 2/3] mem.4: correct /dev/port group in example Michael Kerrisk (man-pages)
2015-01-02 13:11 ` [PATCH 3/3] mem.4: Add CONFIG_STRICT_DEVMEM Elie De Brauwer
[not found] ` <1420204298-25625-4-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-06 10:50 ` Michael Kerrisk (man-pages)
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=1420204298-25625-3-git-send-email-eliedebrauwer@gmail.com \
--to=eliedebrauwer-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).