9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
A few of our machines need upgrading and we are looking into a selection of processors at present. There are suggestions on the vendor's websites that the L3 cache was specifically introduced for gamers. Is this true? Does having L1, L2 and/or L3 cache help at all in performance or are the... (0 Replies)
Discussion started by: figaro
0 Replies
2. AIX
I have an IBM pseries 7028-6E1 server with a six drive bay that is currently plugged into the scsi backplane of the motherboard. I am going to install a PCIX Ultra320 scsi raid adapter, and swing the drive bay over to it. I am just wondering how this is going to work. Should I power the server... (1 Reply)
Discussion started by: markper
1 Replies
3. UNIX for Dummies Questions & Answers
Folks;
Is there a command to know if my hardware can run 64-bit or 32-bit?
I'm trying to re-install SUSE 64-bit on one of our server but i'm not sure if this server hardware designed for 32-bit only or for both
Any help? (14 Replies)
Discussion started by: Katkota
14 Replies
4. UNIX for Dummies Questions & Answers
I would like to use my sunblade to firewall the connections to my desktop and laptop, these at the minute are on a wifi router. What is the best solution? (0 Replies)
Discussion started by: Kawakaze
0 Replies
5. AIX
I am looking to buy a 7044 - either a 170 or 270.
From what I can find on web searchs the 170 is NOT upgradable to more that one CPU? Is that correct?
Can I upgrade the planer on a 170 to a 270 to support multiple CPU's?
Does anyone have any other suggestion for AIX hardware? (5 Replies)
Discussion started by: dizman67
5 Replies
6. UNIX for Dummies Questions & Answers
I have an old pc, about 133-200 mhz with very little memory and hard-drive. I want to install a small and fast *nix system with ion or some other simple wm for maximal performance. It's supposed to be used as a desktop. If someone could share their experience with older machines and some... (2 Replies)
Discussion started by: riwa
2 Replies
7. Red Hat
HI
I have problem working with S3 Savage KM 133 Video Card on Redhat Linux 9 Enterprise Edition. It hangs up once probing done on Video Card.So i tried insalling Linux with options as to run the set up on 640*480. As knows case i searched the web forums to get help. Please let me know how can i... (0 Replies)
Discussion started by: prakashpichika
0 Replies
8. HP-UX
I've been asked by my copmpany to scour the web for a computer on which we can run HP-UX 11.i --- Is there a certain architecture type that I need or will any Compaq HP computer be fine for running HP-UX 11.i ??
Thanks!! (3 Replies)
Discussion started by: jalburger
3 Replies
9. UNIX for Dummies Questions & Answers
Does anyone know how to install a second Ethernet adapter on a Sun Sparc 10? (2 Replies)
Discussion started by: jskillet
2 Replies
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 tells 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 <jmg@FreeBSD.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry
<ken@FreeBSD.org>.
BSD
March 25, 2014 BSD