Bug 167832 - [patch] swapon(2) (and elsewhere) refer to non-existent block devices
Summary: [patch] swapon(2) (and elsewhere) refer to non-existent block devices
Status: Open
Alias: None
Product: Documentation
Classification: Unclassified
Component: Manual Pages (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2012-05-13 03:40 UTC by Peter Jeremy
Modified: 2020-09-01 00:36 UTC (History)
1 user (show)

See Also:


Attachments
file.diff (16.29 KB, patch)
2012-05-13 03:40 UTC, Peter Jeremy
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Jeremy 2012-05-13 03:40:04 UTC
	swapon(2) states "The swapon() system call makes the block device
	special available to the system" but block devices haven't existed
	in FreeBSD for something like a decade.  There's a similar error
	in the description of the ENOTBLK error.

	Looking further, I've found lots of similar references to block
	devices.

Fix: In all 3 man pages, what is actually wanted is a disk device -
	either real or virtual via md(4).  The following patches use
	"disk" in place of "block" for all relevant non-contrib
	references.  Note that I am unclear of the correct fix to:
	tools/debugscripts/gdbinit.kernel
	share/man/man4/xen.4
	share/man/man4/virtio_blk.4
	share/man/man9/vnode.9
How-To-Repeat: 	man 2 swapon intro mount
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2012-05-13 23:22:22 UTC
Responsible Changed
From-To: freebsd-doc->eadler

I'll take it.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2012-05-16 20:48:54 UTC
State Changed
From-To: open->analyzed

awaiting approval
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2012-06-18 05:31:13 UTC
State Changed
From-To: analyzed->open

needs more work (internal change)
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2012-11-08 20:54:45 UTC
Responsible Changed
From-To: eadler->freebsd-bugs

I won't be dealing with this PR for some time, so give it back to the 
pool
Comment 5 Mark Linimon freebsd_committer freebsd_triage 2020-09-01 00:36:47 UTC
^Triage: reset inaccurate In Progress state.