_netdev and no_netdev options missing from manpage for fstab(5)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| util-linux (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
The manual page for mount(8) mentions using "_netdev" and "no_netdev" in the options field in /etc/fstab However, it is not listed in the manual page for fstab(5) If "_netdev" and "no_netdev" are valid mount options that can be used in /etc/fstab, then they should be listed and described in the manual page for fstab(5).
Here is what mount(8) has to say about "_netdev"
_netdev
The filesystem resides on a device that requires network access
(used to prevent the system from attempting to mount these
"no_netdev" is missing from mount(8), too. That can be fixed at the same time.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: mount 2.20.1-5.1ubuntu2
ProcVersionSign
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Sat Oct 27 20:32:34 2012
InstallationDate: Installed on 2012-10-16 (11 days ago)
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64+mac (20121015)
MarkForUpload: True
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
| Lars Noodén (larsnooden) wrote | #1 |
| Lars Noodén (larsnooden) wrote | #2 |
| Ubuntu Foundations Team Bug Bot (crichton) wrote | #3 |
| tags: | added: patch |
The attachment "manual page for fstab(5)" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.
[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]