01-30-2009
I'm not sure, but I think this is for OPTIONAL drivers. Your CD/DVD ROM device is called a "drive". The software that interfaces this device is called a "driver". Maybe that will clear things up.
9 More Discussions You Might Find Interesting
1. Red Hat
Linux RedHat Cluster Manager InstallationAdministrationGuide (0 Replies)
Discussion started by: merlin
0 Replies
2. UNIX for Dummies Questions & Answers
Hello, I had install the rock cluster 4.3 version on my pcs..but i can't access into the desktop...may i know what is the problem? (1 Reply)
Discussion started by: joannetan9984
1 Replies
3. UNIX for Dummies Questions & Answers
hi, may i know how to run mpi after i had install the rock cluster? is there any guidelines or examples? (0 Replies)
Discussion started by: joannetan9984
0 Replies
4. High Performance Computing
Here are steps for installing the Solaris 10 11/06 OS, Solaris Cluster (formerly Sun Cluster) 3.2 software, QFS 4.5, and Oracle 10gR2 RAC. Also provided are instructions on how to configure QFS and Solaris Volume Manager for use with Oracle 10gR2 RAC.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
5. High Performance Computing
Gurus,
I have several questions :
1. Does Solaris 10/OpenSolaris has some kind of web based management tools ?
Currently I am using WebMin. It worked fine, however I am very curious to use
the tools provided by Sun Microsystem.
Please advise for package name and how to activate.... (0 Replies)
Discussion started by: Zepiroth
0 Replies
6. Solaris
While performing, solaris 10 U7 interactive initial installation I selected 'End User System Support' software group as below:
Select Software ___________________________________________________________
Select the Solaris software to install on the system.
NOTE: After selecting a software... (0 Replies)
Discussion started by: ramnagaraj
0 Replies
7. High Performance Computing
Hi,
I've installed mpich2 v. 1.2.1p1 on a cluster of dual-processors with the default options (in previous versions I used 'ssm' device, but now I use 'nemesis').
I'd like that every time I execute a job (e.g. with 2 MPI-processes), each job's process be dispatched on a different machine... (0 Replies)
Discussion started by: Sonia_
0 Replies
8. Solaris
Hello.
I'm trying to install two-node Solaris cluster. All nodes has three NICs (elxl0-elxl2). elxl0 is plumbed, other interfaces - not.
At firstnode I started scinstall, made custom install, wrote hostnames of all two nodes and choose elxl1/elxl2 for cluster interconnection.
After... (1 Reply)
Discussion started by: megabyte2003
1 Replies
9. Solaris
Hi Admins,
I came across an error while installing patch cluster on solaris.
# ./installcluster --s10cluster
ERROR: Another instance of an install script is already running for target
boot
environment '/'.
I did killed the related processes. Now there is no any process running from ps... (1 Reply)
Discussion started by: snchaudhari2
1 Replies
LEARN ABOUT DEBIAN
atapicam
ATAPICAM(4) BSD Kernel Interfaces Manual ATAPICAM(4)
NAME
atapicam -- CAM XPT (transport) module for ATAPI devices
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device scbus
device ata
device atapicam
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
atapicam_load="YES"
DESCRIPTION
The ATAPI/CAM module allows ATAPI devices (CD-ROM, CD-RW, DVD drives, floppy drives such as Iomega Zip, tape drives) to be accessed through
the SCSI subsystem, cam(4).
ata(4) and scbus(4) must be configured in the kernel as well. The SCSI target drivers (cd(4), da(4), or st(4)) can then be used to access
the devices. The generic passthrough device, pass(4), can also be used to send SCSI commands directly to the devices through the CAM API.
A separate CAM bus is created for each ATA bus in the system. On each of these buses, target ID 0 is assigned to the master device, and ID 1
is assigned to the slave (provided they are ATAPI devices).
IMPLEMENTATION NOTES
Some SCSI commands are intercepted by the driver, and undergo special processing in order to work around limitations of ATAPI devices. Such
limitations can be consequences of the ATAPI specification. For example, ATAPI devices do not implement the 6-byte versions of MODE_SELECT,
MODE_SENSE, READ, or WRITE. They can also be common bugs, such as hanging when queried for extended INQUIRY information.
EXAMPLES
device ata
device atapicam
device scbus
device cd
device pass
Add the atapicam driver to the kernel.
camcontrol devlist
Print the list of all devices available through CAM.
mount -t cd9660 /dev/cd0 /mnt
Mount a CD-ROM from an ATAPI CD-ROM drive (the command above assumes that the ATAPI drive is the only CD-ROM unit).
SEE ALSO
ata(4), cam(4), scsi(4), atacontrol(8), camcontrol(8)
HISTORY
The ATAPI/CAM driver first appeared in FreeBSD 4.8 and FreeBSD 5.0.
AUTHORS
The ATAPI/CAM driver was written by Thomas Quinot <thomas@FreeBSD.org>.
BUGS
atapicam and ATAPI-specific target drivers (acd(4), ast(4), and afd(4)) can be configured in the same kernel. Simultaneous access to the
same device through the SCSI generic drivers and the ATAPI-specific drivers may cause problems and is strongly discouraged.
BSD
October 22, 2009 BSD