SBP_TARG(4) BSD Kernel Interfaces Manual SBP_TARG(4)NAME
sbp_targ -- Serial Bus Protocol 2 (SBP-2) Target Mode devices driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device sbp_targ
device firewire
device scbus
device targ
Alternatively, to load the driver as a module at boot time, place the following lines in loader.conf(5):
firewire_load="YES"
cam_load="YES"
sbp_targ_load"YES"
DESCRIPTION
The sbp_targ driver provides support for SBP-2 target mode. This driver is supposed to work with cam(4), targ(4) and firewire(4). You also
need to use scsi_target(8), which can be found in /usr/share/examples/scsi_target, to provide actual devices.
EXAMPLES
# mdconfig -a -t malloc -s 10m
md0
# scsi_target 0:0:0 /dev/md0
(Assuming sbp_targ0 on scbus0)
SEE ALSO cam(4), firewire(4), targ(4), camcontrol(8), fwcontrol(8), kldload(8), scsi_target(8)AUTHORS
The sbp_targ driver was written by Hidetoshi Shimokawa.
BUGS
This driver is currently under development. It does not work correctly in multi-initiator environments or after the bus topology has been
changed.
BSD November 7, 2003 BSD
Check Out this Related Man Page
SBP(4) BSD Kernel Interfaces Manual SBP(4)NAME
sbp -- Serial Bus Protocol 2 (SBP-2) Mass Storage Devices driver
SYNOPSIS
kldload firewire
kldload cam
kldload sbp
or
device sbp
device firewire
device scbus
device da
device cd
device pass
DESCRIPTION
The sbp driver provides support for SBP-2 devices that attach to the FireWire (IEEE 1394) port. It should work with SBP-2 devices which the
CAM layer supports, for example, HDDs, CDROM drives and DVD drives.
Some users familiar with umass(4) might wonder why the device is not detached at the CAM layer when the device is unplugged. It is detached
only if the device has not been plugged again during several bus resets. This is for preventing to detach an active file system even when
the device cannot be probed correctly for some reason after a bus reset or when the device is temporary disconnected because the user changes
the bus topology. If you want to force to detach the device, run ``fwcontrol -r'' several times or set hw.firewire.hold_count=0 by
sysctl(1).
Some (broken) HDDs do not work well with tagged queuing. If you have problems with such drives, try ``camcontrol [device id] tags -N 1'' to
disable tagged queuing.
SEE ALSO cam(4), firewire(4), camcontrol(8), fwcontrol(8), kldload(8), sysctl(8)AUTHORS
The sbp driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa.
This manual page was written by Katsushi Kobayashi.
BSD May 20, 2002 BSD
Friends I'm facing a big problem trying to extend the netfilter. Somone please help me with your quick reply (any hint) as I've to meet a deadline.
My problem is that I've written a new netfilter target module and its corresponding userspace program for iptables to change the packet type of a... (0 Replies)
I have a Microdia web cam. Some times it won't work if and only if there is a "HV7131R image sensor detected" statement in the boot up.
In this case when I try to get a .png snapshot all I get is a frame full of what appears to be white noise only it is mostly green.
Here is the command I am... (0 Replies)
I have been reading prep questions for my second unix academy exam, and there's a nuance, I'm not sure I understand it correctly.
I've been under impression from my readings of book by Evi Nemeth and from unix academy DVDs I've been watching, that kernel's modules are drivers. I think of it, as... (25 Replies)
Hi everyone,
I am not sure if I understand how mdadm --create /dev/md0 --level=container works?
A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device?
I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the... (0 Replies)