public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "john at mccabe dot org.uk" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug manual/27207] New: mount examples don't match the mount function signature Date: Tue, 19 Jan 2021 18:07:04 +0000 [thread overview] Message-ID: <bug-27207-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27207 Bug ID: 27207 Summary: mount examples don't match the mount function signature Product: glibc Version: 2.32 Status: UNCONFIRMED Severity: normal Priority: P2 Component: manual Assignee: unassigned at sourceware dot org Reporter: john at mccabe dot org.uk CC: mtk.manpages at gmail dot com Target Milestone: --- In section 31.3.2, "Mount, Unmount, Remount", the signature of the mount function is declared as: int mount (const char *special_file, const char *dir, const char *fstype, unsigned long int options, const void *data) Later in the documentation, the following examples are provided: Example: #include <sys/mount.h> mount("/dev/hdb", "/cdrom", MS_MGC_VAL | MS_RDONLY | MS_NOSUID, ""); mount("/dev/hda2", "/mnt", MS_MGC_VAL | MS_REMOUNT, ""); Both of these examples have the options flags as the 3rd parameter, with an empty string as the 4th. As these are MS_REMOUNT examples, it looks like the 4th parameter in the examples is meant to represent the filesystem type, so the 3rd and 4th parameters are the wrong way round. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-01-19 18:07 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-19 18:07 john at mccabe dot org.uk [this message] 2021-01-19 18:07 ` [Bug manual/27207] " john at mccabe dot org.uk 2021-01-19 18:19 ` john at mccabe dot org.uk 2021-01-20 12:14 ` mtk.manpages at gmail dot com 2021-01-20 13:11 ` john at mccabe dot org.uk 2021-01-20 13:14 ` john at mccabe dot org.uk
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-27207-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).