#
# ENBD configuration
#
#comment  "Enhanced network block device"

config BLK_DEV_ENBD
	tristate 'Enhanced network block device driver'
	depends on ENBD
	---help---
	  Saying Y here will build in support for the "enhanced network
	  block device".  Like the plain NBD, this device proxies a remote
	  hard disk or other block device, such as a cdrom or floppy.  The
	  difference between ENBD and NBD is that ENBD is a much more
	  heavyweight solution for an industrial setting - it does automatic
	  reconnects after network brownouts, and uses multiple channels at
	  once to carry the data.  It supports remote ioctls, removable
	  devices, and uses an MD5 sampling technique to accelerate softRAID
	  resyncs.  It will connect through (secure) SSL channels.  It will
	  hide transient errors from overlying softRAID devices, etc.
	  
	  You will need the userspace daemons, which packages are mirrored
	  on several places on the net.  The primary source is
	  ftp://oboe.it.uc3m.es/pub/Programs/nbd/nbd-2.4-current.tgz.
	  
	  If you want to compile this driver as a module ( = code which can
	  be inserted in and removed from the running kernel whenever you
	  want), say M here and read <file:Documentation/modules.txt>.  The
	  module will be called enbd.o.
	  
	  If unsure, say N.

config BLK_DEV_ENBD_IOCTL
	tristate 'Enhanced network block device remote ioctl support'
	depends on BLK_DEV_ENBD
	---help---
          Saying Y here will build in support to ENBD for execution
          of remote ioctls on compatible architectures. This means that
          you can eject a CD on the other machine.

	  If you want to compile this driver as a module ( = code which can
	  be inserted in and removed from the running kernel whenever you
	  want), say M here and read <file:Documentation/modules.txt>.  The
	  module will be called enbd.o.
	  
	  If unsure, say N.
#endmenu  

