Proposal: block(4)

Proposal: block(4)

[Mark Robson]

Hi,

Looking at the sd(4) man page, there appear to be some BLK* ioctls
documented, but these don't really belong here, as some of them apply to all
block devices.

Should the common functions of a block device appear on a new page, block(4)
and refer to hd(4), sd(4), ram(4) etc as necessary?

I would create one if there was some interest.

Regards

Mark
--
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

Re: Proposal: block(4)

[Christoph Hellwig]

On Sun, Sep 12, 2010 at 03:51:56PM +0100, Mark Robson wrote:
> Hi,
> 
> Looking at the sd(4) man page, there appear to be some BLK* ioctls
> documented, but these don't really belong here, as some of them apply to all
> block devices.
> 
> Should the common functions of a block device appear on a new page, block(4)
> and refer to hd(4), sd(4), ram(4) etc as necessary?
> 
> I would create one if there was some interest.

Yes, please do.  Besides the completely generic ioctls implemented in
blkdev_ioctl it would also be good to have a manpage for the "generic
scsi" ioctls in scsi_cmd_ioctl.

--
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