SCSI_UNLOCK_FLOPTICA(9) SCSI mid layer SCSI_UNLOCK_FLOPTICA(9)NAME
scsi_unlock_floptical - unlock device via a special MODE SENSE command
SYNOPSIS
void scsi_unlock_floptical(struct scsi_device * sdev, unsigned char * result);
ARGUMENTS
sdev
scsi device to send command to
result
area to store the result of the MODE SENSE
DESCRIPTION
Send a vendor specific MODE SENSE (not a MODE SELECT) command. Called for BLIST_KEY devices.
AUTHORS
James Bottomley <James.Bottomley@hansenpartnership.com>
Author.
Rob Landley <rob@landley.net>
Author.
COPYRIGHT Kernel Hackers Manual 2.6. July 2010 SCSI_UNLOCK_FLOPTICA(9)
Check Out this Related Man Page
CD(9) BSD Kernel Developer's Manual CD(9)NAME
cd -- CDROM driver for the CAM SCSI subsystem
DESCRIPTION
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com-
mands. Some drives do not behave as the driver expects. See the QUIRKS section for information on possible flags.
QUIRKS
Each CD-ROM device can have different interpretations of the SCSI spec. This can lead to drives requiring special handling in the driver.
The following is a list of quirks that the driver recognize.
CD_Q_NO_TOUCH This flag tell the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what
size it is. This flag is currently unimplemented in the CAM cd driver.
CD_Q_BCD_TRACKS This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal. If the drive seems
to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag.
CD_Q_NO_CHANGER This flag tells the driver that the device in question is not a changer. This is only necessary for a CDROM device with
multiple luns that are not a part of a changer.
CD_Q_CHANGER This flag tells the driver that the given device is a multi-lun changer. In general, the driver will figure this out auto-
matically when it sees a LUN greater than 0. Setting this flag only has the effect of telling the driver to run the initial
read capacity command for LUN 0 of the changer through the changer scheduling code.
CD_Q_10_BYTE_ONLY
This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands. In general these
types of quirks should not be added to the cd(4) driver. The reason is that the driver does several things to attempt to
determine whether the drive in question needs 10 byte commands. First, it issues a CAM Path Inquiry command to determine
whether the protocol that the drive speaks typically only allows 10 byte commands. (ATAPI and USB are two prominent exam-
ples of protocols where you generally only want to send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back
from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead. The only
reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6
byte commands.
FILES
/sys/cam/scsi/scsi_cd.c is the driver source file.
SEE ALSO cd(4), scsi(4)HISTORY
The cd manual page first appeared in FreeBSD 2.2.
AUTHORS
This manual page was written by John-Mark Gurney <gurney_j@efn.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry
<ken@FreeBSD.org>.
BSD September 2, 2003 BSD
Hi all,
I want to create a new user and grant him ONLY transfer files access to a specific directory where he can only upload and read the files. He should be restricted to this activity only.
Regards (6 Replies)
Hi everyone,
I know the following questions are noobish questions but I am asking them because I am confused about the basics of history behind UNIX and LINUX.
Ok onto business, my questions are-:
Was/Is UNIX ever an open source operating system ?
If UNIX was... (21 Replies)
Hi,
Last 2 weeks I have searched many forums and i haven't found the answer for the question:
How to get all command output to Putty title?
Needed it for other programs to know when some jobs on a server is done and is it done right or wrong. Plink stdout and stdin wasn't working, i used many... (1 Reply)
anyone have any idea how do to this with auth_attr?
I suspect if I grant him
solaris.device.:RO::Device Allocation::help=DevAllocHeader.html
that will work but I'm unsure. Just looking for a second opinion. (10 Replies)
I am looking for a stable, reliable system to replace my current Windows systems in the home. These are simple systems that I purchased from the local Big Box store.
I have heard many good things about Unix and it's various children and it sounds like a good option to me. I have worked... (2 Replies)
We have a lot of scripts using cut as :
cut -c 0-8 --works for cut (GNU coreutils) 5.97, but does not work for cut (GNU coreutils) 8.4.
Gives error -
cut: fields and positions are numbered from 1
Try `cut --help' for more information.
The position needs to start with 1 for later... (6 Replies)
I've got a problem with a proxy configuration. We have an LDAP group that lists all users who are authorised to use the proxy to FTP (usually Filezilla) out to the world, and by implication those not in the group should be denied. My users are delighted that this has been enabled and those that... (9 Replies)
hi folks,
how to using tar with exclude directory and compress it using tar.Z
i only know how to exclude dir only with this command below:
tar -cvf /varios/restore/test.tar -X excludefile.txt /jfma/test1/
how to compress it using 1 command?
Thanx
Please use CODE tags as... (6 Replies)
Hello All,
I had recently learnt a bit of Docker(which provides containerization process).
Here are some of my learning points from it.
Let us start first with very basic question:
What is Docker:
Docker is a platform for sysadmins and developers to DEPLOY, DEVELOP and RUN applications ... (7 Replies)
What is the point of this? Whenever I close my shell it appends to the history file without adding this. I have never seen it overwrite my history file.
# When the shell exits, append to the history file instead of overwriting it
shopt -s histappend (3 Replies)
Hello for all,
I am testing the behavior of a 32 bit application running on Solaris 5.10 (SPARC), and realize it reaches 4GB of memory and then crashes.
It doesn't matter the amount of used memory as application is intended to perform many transactions; rather, what I want to achieve is to... (2 Replies)