>Number:         11511
>Category:       kern
>Synopsis:       no easy way to determine current dump device
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 16 17:08:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Luke Mewburn
>Release:        today ;-)
>Organization:
Luke Mewburn  <lukem@wasabisystems.com>  http://www.wasabisystems.com
Luke Mewburn     <lukem@netbsd.org>      http://www.netbsd.org
Wasabi Systems - providing NetBSD sales, support and service.
>Environment:
System: NetBSD argo.akimbo.com.au 1.5_BETA2 NetBSD 1.5_BETA2 (ARGO) #0: Thu Nov 16 19:55:34 EST 2000 lukem@argo.akimbo.com.au:/z/src/netbsd-1-5/src/sys/arch/i386/compile/ARGO i386

>Description:
	there doesn't seem to be an easy way with swapctl(8) or
	swapctl(2) to determine the current dump device, even though
	you set it with those tools.

>How-To-Repeat:
	rtfm swapctl(8). use swapctl(8).

>Fix:
	maybe return it with swapctl(2)'s SWAP_STATS command, with an
	entry with a flag called SWF_DUMP.

	of course, SWAP_NSWAP might have to return 1 more to take this
	potential new entry into account (because you might not be
	swapping onto the dump device.)

	food for thought for mrg, really ;-)
>Release-Note:
>Audit-Trail:
>Unformatted: