You can make a number of keyboard configuration choices in Fedora. You can choose a keyboard language that supplies the keyboard letters, diacritical marks, and layout appropriate for the language you will be typing in during your console or graphical sessions. Other configuration options include changing the keyboard’s translation table to remap the order of keys on your keyboard, swapping specific keys (such as Caps Lock and Ctrl), or changing the delay period between the press of the key and the appearance of the character onscreen. (This configuration can help you synch the character entry to your typing speed.)

You can make keyboard configuration changes through text-based (console) keyboard commands or by using the graphical user interface.

If you do not use X, use Fedora’s system-config-keyboard command to change your keyboard type and language. This command can be used without an active X session (or if you are using X, from inside a terminal window) like this:

# system-config-keyboard

After you press Enter, you will see the Configure Keyboard dialog, as shown in Figure 4.1.

Figure 4.1. The system-config-keyboard command can be used to choose a keyboard map (language) for Fedora.

This dialog enables you to choose a new keyboard type.

Scroll through the list to highlight a desired keyboard type, and then use the Tab key to highlight the OK button and press Enter. The listings represent entries under the /lib/kbd/keymaps/i386 directory, which are used to associate your keyboard’s layout and keys with a language. The keyboard configuration is stored in the file /etc/sysconfig/keyboard, which might look like this:

KEYBOARDTYPE="pc"
KEYTABLE="us"

If you are using the Fedora desktop during an X session, you can use the graphical interface to select a keyboard language. To open the keyboard configuration dialog box, click the desktop panel System Settings Keyboard menu item, or use the system-config-keyboard client at the command line of a terminal window, like so:

$ system-config-keyboard

After you press Enter, you will be prompted for the root password. Enter the password and click OK. You will then see the Keyboard dialog box shown in Figure 4.2. This dialog box is similar to that displayed by system-config-keyboard.

Figure 4.2. The system-config-keyboard client is used during an X session to choose the language you will be keyboarding in during your desktop sessions.

Scroll through the list of languages, highlight a language, and then click OK to save your change. Table 4.1 lists text-based and graphical commands you can use to manipulate or get information about your keyboard.

The X11 keyboard and other clients can be used to input a keyboard description into a running X server, show current keyboard character translations, change a keyboard map, and set other keyboard (and pointer) preferences. X11 settings are generally contained in a system’s xorg.conf file (see Chapter 6, “The X Window System,” for more information).

As a trivial example, the following short shell script (see Chapter 15 for more information on how to use shell scripts) can be used to blink the keyboard Caps Lock LED on and off each second (press Ctrl+C to stop the blinking) while using the console:

#!/bin/sh
while :
  do
   setleds -L +caps ; sleep 1 ; setleds -L -caps ; sleep 1;
done

Perhaps a more useful example is to switch the Caps Lock and Ctrl keys on your keyboard. Some users might find typing sessions a bit more comfortable if the locations are swapped. There are a number of ways to swap the keys. For your console-based sessions, use the loadkeys command to read in a file containing reverse key values for the keys:

keymaps 0-15
keycode 58 = Control
keycode 29 = Caps_Lock

You can then immediately swap the keys by using loadkeys to read in the file (perhaps named swapkeys) like so:

# loadkeys <swapkeys

The same swapping can be used for your Fedora desktop by editing your /etc/X11/xorg.conf file’s keyboard InputDevice section and adding

Option     "XkbOptions"   "ctrl:swapcaps"

Yet another way to get the same results is to create a file named .Xmodmap in your home directory that contains

remove Lock = Caps_Lock
remove Control = Control_L
keysym Control_L = Caps_Lock
keysym Caps_Lock = Control_L
add Lock = Caps_Lock
add Control = Control_L

Or you can save the settings in a file (such as mykeyswap) and use the xmodmap client to directly read in the new keys like so:

$  xmodmap mykeyswap

Note that this will only work if you use the xterm or rxvt terminal clients. See Chapter 6 for more information about the Fedora desktop.

# system-config-keyboard --text

This section introduces pointer device configuration for Fedora. You will see how to use the graphical gnome-mouse-properties client for configuring a mouse for your desktop.

The Fedora installer will recognize and correctly configure a computer’s pointing device, but if you install a new pointing device, you will need to reconfigure the system for its use.

When using a PS/2 pointing device, a file named /dev/mouse will point to /dev/psaux; when using a USB pointing device, /dev/mouse will point to /dev/input/mice. The /dev/mouse file is a symbolic link, used for the convenience of many Linux applications. It is much more convenient for a program to look for /dev/mouse instead of /dev/input/mice or /dev/psaux.

USB service (most likely initially configured by the installer) is started during the boot process by an entry in the system’s module configuration file, /etc/modprobe.conf:

alias usb-controller usb-uhci

In this example, the PC platform uses a universal host controller interface (UHCI), and the uhci.o kernel module will be loaded from the /lib/modules/2.6-X/kernel/drivers/usb directory when Linux boots. Another USB controller commonly in use is the open host controller interface (OHCI), requiring loading of the ohci.o module to enable USB service.

If your pointing device does not work, you can use the dmesg command to see if Linux has recognized the device during the boot process. This can provide some diagnostic information because Linux or the driver (perhaps a module) usually outputs diagnostic information:

...
usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 15
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hub.c: USB new device connect on bus1/1, assigned device number 2
usb.c: USB device 2 (vend/prod 0x1241/0x1122) is not claimed by any 
active driver.
usb.c: registered new driver hiddev
usb.c: registered new driver hid
input0: USB HID v1.00 Mouse [1241:1122] on usb1:2.0
hid-core.c: v1.8 Andreas Gal, Vojtech Pavlik <[email protected]>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
...

In this example (your output might look different), the kernel has recognized a generic USB mouse. USB support is initially enabled by the usbcore.o kernel module. In this example, the USB controller interface is initialized and configured by loading the usb-uhci.o kernel module, and then additional modules, such as input.o and hid.o, will be loaded to support a mouse (and/or keyboard) USB device.

You can see what modules have been loaded by using the output of the lsmod command. Note that you might see different memory size values, depending on your computer and module version:

# lsmod
...
mousedev         4288 1
hid           18720 0 (unused)
input           3744 0 [mousedev hid]
usb-uhci         21636 0 (unused)
usbcore         59072 1 [hid usb-uhci]

As you can see, USB device support, especially for pointing devices, involves proper loading of a chain of modules rather than a single driver.

After Linux has recognized your hardware, you can use the gnome-mouse-properties command to configure a new pointer. Start the command like this:

$ gnome-mouse-properties

After you press Enter, the Mouse Preferences dialog appears, as shown in Figure 4.3.

Figure 4.3. The gnome-mouse-properties command can be used to configure a new pointing device.

The configuration entry contained in the /etc/X11/xorg.conf and used by X.org for the Fedora desktop, looks like

Section "InputDevice"
    Identifier   "Mouse0"
    # Modified by mouseconfig
    Driver     "mouse"
    Option     "Device"        "/dev/mouse"
    Option     "Protocol"       "PS/2"
    Option     "Emulate3Buttons"    "yes"
    #Option    "ZAxisMapping"      "4 5"
EndSection

This entry enables the use of a USB pointing device during X sessions. See Chapter 6 to learn about X.

The ZAxisMapping entry (disabled in the preceding example) enables scrolling with a mouse that has a combination scroll-wheel and middle button. Many other types of input devices can be used with Linux and X.org. For information about using a mouse with X.org, read the file README.mouse under the /usr/X11R6/lib/X11/doc directory.

Mouse support for copy and paste operations during a Linux console session is provided by the General Purpose Mouse driver (gpm). gpm is a daemon, or software that runs in memory as a background process while you use Linux. If you make the appropriate configuration choices, the /etc/rc.d/init.d/gpm script starts the gpm daemon when Fedora boots. If you are not using X, you can configure Linux to start gpm when booting by using the ntsysv command from the console. Run the ntsysv command as root, like this:

# ntsysv

After you press Enter, you will see the Services dialog, as shown in Figure 4.4.

Figure 4.4. Use the ntsysv command to produce the Services dialog, in which you can select the gpm driver to start at boot time.

Scroll through the list of services using the Up or Down cursor keys to highlight the gpm service. Press the spacebar to toggle use of the service on (an asterisk appears between the brackets) or off (no asterisk). Press the Tab key to highlight the OK button and then press Enter to save your changes. The changes will take effect the next time you boot Fedora.

# chkconfig --level 3 gpm on
# chkconfig --level 5 gpm off

Linux uses /dev/ttySX, /dev/ttyUSBX, or /dev/usb/ttyUSBX for serial ports, where X can range from 0 to 15. Many additional ports can be added to a system using multiport cards or chained USB devices. A PC’s integral serial ports are generally recognized at boot time. To see a list of recognized ports for your system, pipe the dmesg command output through the fgrep command like so:

# dmesg | grep tty
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A

In this example, the grep command reports that two serial ports have been recognized in the dmesg output. Note that the device matching ttyS00 is /dev/ttyS0, despite the kernel output. The PC’s external modem can be attached (most likely using a male DB9 adapter) to either port. Under Linux, nearly all modem-dependent software clients look for a symbolic link named /dev/modem that points to the desired device. This link is not created by default, but as root, you can create this device manually using the ln command like this:

# ln -s /dev/ttyS0 /dev/modem

In this example, /dev/modem will point to the first serial port.

You can also use the graphical X client neat to configure a modem after the initial installation. Internet connection software such as Fedora’s system-config-network client (shown in Figure 4.6) will try to probe the system for an available modem. If a modem is not found, you can manually enter modem data.

Figure 4.6. Fedora’s system-config-network client will probe for an available modem.

KDE provides the kppp client (shown in Figure 4.7) that can also be used to look for and set up a modem when you set up a new Point-to-Point Protocol (PPP) connection. Click the Query Modem button in kppp’s dialog to search for an installed modem.

Figure 4.7. KDE’s kppp client can be used to find and configure an available modem.

Fedora includes command-line–based diagnostic and serial port configuration tools for the system administrator. For example, to get more information about a specific port, you can use the statserial command, along with a designated device like this:

# statserial /dev/ttyS0
Device: /dev/ttyS0

Signal Pin Pin Direction Status Full
Name   (25) (9) (computer)       Name
-----  ---  --- --------- ------ -----
FG      1    -    -         -    Frame Ground
TxD     2    3    out       -    Transmit Data
RxD     3    2    in        -    Receive Data
RTS     4    7    out       1    Request To Send
CTS     5    8    in        0    Clear To Send
DSR     6    6    in        0    Data Set Ready
GND     7    5    -         -    Signal Ground
DCD     8    1    in        0    Data Carrier Detect
DTR    20    4    out       1    Data Terminal Ready
RI     22    9    in        0    Ring Indicator

The sample output is a display of the associated device’s port signals. Another tool is the setserial command that can be used to display port statistics and reconfigure a serial port’s system interrupt or speed. This can be handy when using some serial devices, such as a cellular phone that requires specific serial port characteristics. To get information about a specific port, use setserial, along with the device name like this:

# setserial -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
    Baud_base: 115200, close_delay: 50, divisor: 0
    closing_wait: 3000
    Flags: spd_normal skip_test

In this example, the characteristics of /dev/ttyS0 are displayed. The setserial command can also be used to configure or fine-tune a port’s characteristics using 32 different command-line options and values.

One option for using a legacy serial device such as a modem on a PC that does not have a serial port but supports USB is to use a USB-to-serial converter. These devices provide a serial port dongle and plug in to a USB hub or port. You can see the output and designated serial port by looking at the output of the dmesg command:

usb.c: registered new driver serial
usbserial.c: USB Serial support registered for Generic
usbserial.c: USB Serial Driver core v1.4
usbserial.c: USB Serial support registered for Keyspan PDA
usbserial.c: Keyspan PDA converter detected
usbserial.c: Keyspan PDA converter now attached to ttyUSB0 
(or usb/tts/0 for devfs)
usbserial.c: USB Serial support registered for Keyspan PDA - (prerenumeration)
usbserial.c: USB Serial support registered for Xircom PGS - (prerenumeration)
usbserial.c: USB Serial support registered for Entregra PGS - (prerenumeration)
keyspan_pda.c: USB Keyspan PDA Converter driver v1.1

Linux should recognize and configure a designated serial port (such as /dev/ttyUSBX in the example) when the device is plugged in. Fedora also comes with a number of fax utilities that can be used to configure a system to send or receive phone faxes. One of the easier-to-configure fax utilities is the fax command. As root, you can configure the software by editing a few entries in the /usr/bin/fax shell script:

DEV=modem
FROM="1 555 555-1212"
NAME="Company Name"

The most important entry is DEV=, which will not need to be changed as long as /dev/modem points to an active fax-capable modem. You can also edit /usr/bin/fax to customize other entries, such as the fax viewing command. Use the test command-line option to check the settings like this:

# fax test

Sending a fax using the fax command is straightforward:

# fax send 5551212 document.txt

Use the minicom or xminicom script (used for launching minicom in a terminal window during an X session) for dial-up connections and terminal sessions to remote Linux systems. To configure this terminal program for use with an attached modem, start the client as root with its -s or setup option like this:

# minicom -s

After you press Enter, you will see a setup dialog. Select Serial-Port Configuration and press Enter. You will then see a Configuration Settings dialog as shown in Figure 4.8 that you can use to configure the program to work with an attached modem.

Figure 4.8. Use minicom’s setup dialog to configure the program to work with an attached modem.

Other issues regarding modems focus on Linux notebook users with laptops using controllerless modems. These modems use proprietary software to emulate a hardware modem and are commonly referred to as WinModems due to the software being available only on Windows. Despite the release of binary-only drivers to enable use of some of these modems, these devices remain the bane of Linux notebook and some desktop users.

You might find some support for Lucent (but not Lucent AMR), Motorola SM56-type, the IBM Mwave, and Conexant HSF (not HCF) controllers. At the time of this writing, there was no support for any 3Com or U.S. Robotics controllerless modems. For links to drivers and more information, browse to the Linux Winmodem web page at http://www.linmodems.org.

Use the date command to display or set your Linux system time. This command requires you to use a specific sequence of numbers to represent the desired date and time. To see your Linux system’s idea of the current date and time, use the date command like this:

# date
Wed Jan 10 14:17:01 EDT 2005

To adjust your system’s time (say, to January 27, 2006 at 8 a.m.), use a command line with the month, day, hour, minute, and year, like so:

# date 012606002003
Fri Jan 27 08:00:00 EDT 2003

Use the hwclock command to display or set your Linux system time, display or set your PC’s hardware clock, or to synchronize the system and hardware times. To see your hardware date and time, use hwclock with its --show option like so:

# hwclock --show
Fri 27 Jan 2006 02:17:53 PM GMT -0.193809 seconds

Use hwclock with its --set and --date options to manually set the hardware clock like so:

# hwclock --set --date "01/27/06 08:00:00"
# hwclock --show
Tue 27 Jan 2006 08:00:08 AM GMT -0.151718 seconds

In these examples, the hardware clock has been set using hwclock, which is then used again to verify the new hardware date and time. You can also hwclock to set the Linux system date and time date using your hardware clock’s values with the Linux system date and time.

For example, to set the system time from your PC’s hardware clock, use the --hctosys option like so:

# hwclock --hctosys

To set your hardware clock using the system time, use the --systohc option like so:

# hwclock --systohc

Fedora’s graphical X tool named system-config-date can be used to set your system date and time. Start the client by clicking the desktop menu’s System Settings Date & Time menu item, or from the command line of an X11 terminal window like this:

$ system-config-date &

After you press Enter, you are asked to enter the root password. Type in the root password and click the OK button. You will then see a window, as shown in Figure 4.9.

Figure 4.9. Use Fedora’s system-config-date client to set your system date and time.

Set the date and time by using the calendar and time fields. You can also have your workstation obtain updated date and time information via the network by entering a remote time server hostname in the Network Time Protocol field. This requires that the ntpd time daemon be properly configured and running.

Click the Time Zone tab to change or verify your system’s time zone. The current system time zone is designated by a file named localtime in the /etc directory, and is a copy of the pertinent time zone database file under the /usr/share/zoneinfo directory. For example,

$ ls -l /etc/localtime
-rw-r--r--    1 root    root         1267 Apr  1 16:39 /etc/localtime
$ ls -l /usr/share/zoneinfo/America/New_York
-rw-r--r--    5 root    root         1267 Mar 13 18:00
/usr/share/zoneinfo/_America/New_York

This file changes if you make a time zone change using system-config-date.

The PCMCIA Card Services software provides diagnostic information by one or more high or low beeps upon card insertion. One high and one low beep indicate that a card is recognized, but failed to be configured. A single beep indicates that the card was only recognized. Two high beeps indicate that a card was recognized and configured.

For example, if you use a compact flash storage device and insert it into your notebook while using Fedora, you should hear two high beeps. You can then check to see what device has been assigned to the card by using the dmesg command:

$ dmesg
...
hde: SunDisk SDCFB-8, ATA DISK drive
ide2 at 0x100-0x107,0x10e on irq 3
ide-floppy driver 0.99.newide
hde: 15680 sectors (8 MB) w/1KiB Cache, CHS=245/2/32
 hde: hde1
...

Not all the output is shown here (and yours might look different), but this example shows that the card has been recognized and configured as the /dev/hde device (with a single partition, /dev/hde1). You can then use the device as any other storage medium (see Chapter 39, “Managing the File System,” for more information on using hard drives with Linux).

Other devices can be similarly recognized and configured. For example, if you have a combination ethernet and modem PCMCIA card and insert it into your notebook, you should hear two sets of high beeps (to indicate successful recognition and configuration of the network interface and modem). The Linux kernel will report the interface and device information:

$ dmesg
...
eth0: NE2000 (DL10019 rev 05): io 0x300, irq 3, hw_addr 00:E0:98:06:84:C5
ttyS04 at port 0x0af8 (irq = 3) is a 16450
..

Here, the network interface has been recognized as eth0 (see Chapter 18, “Network Connectivity,” to see how to connect to a network). The modem is configured to use /dev/ttyS04.

Again, troubleshooting problems with PCMCIA cards can be difficult, especially with the explosion in popularity and type of 802.11b/g wireless networking cards. Such troubleshooting is likely to require downloading, building, and installing new drivers.

Fortunately, however, nearly all serial, modem, and Compact Flash storage cards are easily recognized and configured. Many Ethernet cards are also supported. To check on the current support status for many cards, read the file SUPPORTED.CARDS. You will find a copy under the /usr/share/doc/kernel-pcmcia-cs-3.X.XX/ directory (where X.XX is the version of the package) if you install the pcmciautils RPM package.

Although PCMCIA cards can be inserted or removed while using Fedora, be careful when using these cards. For example, do not remove a network card while connected to a remote computer. Do not pull a compact flash card or other storage media card (such as an IBM microdrive) while the card’s filesystem is mounted and in use—you could corrupt the media’s filesystem and experience loss of data.

You can control a PCMCIA device from the command line, and insert and remove the card without physically removing and then inserting the card. Use the cardctl command to control PCMCIA service to one or more card slots on your notebook or desktop PC with a PCMCIA adapter. The cardctl command is used to get and print information about an inserted card, suspend or resume power to a card, reset a card, perform a software insertion or removal, or configure a card according to a particular, predefined scheme (such as using a network in the office or at home). The format of the command is cardctl command slot_number (such as 0 or 1).

For example, if you have inserted a compact flash card, eject the card (after unmounting its filesystem) using the cardctl command and its eject option, along with the card’s slot number like this:

# cardctl eject 0

This can save power when running a notebook. When the card is needed again, you can subsequently “insert” the card like so:

# cardctl insert 0

Linux recognizes CD and DVD drives upon booting if they are attached to your computer’s motherboard with proper cabling and if they are assigned as either a master or slave on an IDE channel. Look through your kernel boot message for the drive device assignment, such as

hdd: DVDROM 10X, ATAPI CD/DVD-ROM drive

If you have a DVD-capable drive, you generally should also have a symbolic link named /dev/dvd that points to your drive’s device because many DVD clients, such as xine or vlc, look for /dev/dvd by default. If you have a CD-RW drive, the Fedora installer inserts a kernel argument into your boot loader’s configuration file that specifies use of the ide-scsi kernel. For example,

append="hdb=ide-scsi"

A similar entry in the grub boot loader’s /etc/grub.conf file would look like this:

kernel boot/vmlinuz-6.5-1.358 ro root=/dev/hda2 hdb=ide-scsi

The first CD-RW drive is assigned to the device /dev/scd0 (although it might still be initially recognized while booting as an IDE device), with subsequent drives assigned to /dev/scd1, and so on. To initialize your drive for use, the following modules should be loaded:

Module        Size Used by Not tainted
sg          30244 0 (autoclean)
sr_mod        15192 0 (autoclean)
cdrom        27872 0 (autoclean) [sr_mod]
ide-scsi       8128 0
scsi_mod       96572 2 [sr_mod ide-scsi]

Look for kernel message output regarding the device such as this:

Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 0x/32x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12

Your ATAPI-based CD-RW drive will then work as a SCSI device under emulation, and the symbolic link /dev/cdrom should point to /dev/scd0. You can also use the cdrecord command (included with Red Hat’s multimedia software packages) to acquire SCSI device information about your drive for later use during a burn operation like this:

# cdrecord -scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
Linux sg driver version: 3.1.22
Using libscg version 'schily-0.5'
scsibus0:
    0,0,0 0) 'HL-DT-ST' 'RW/DVD GCC-4120B' '2.01' Removable CD-ROM
    0,1,0 1) *
    0,2,0 2) *
    0,3,0 3) *
    0,4,0 4) *
    0,5,0 5) *
    0,6,0 6) *
    0,7,0 7) *

The pertinent information—0,0,0 in the example (SCSI bus, device ID, and Logical Unit Number, or lun)—can then be used during a burn operation like this:

# cdrecord -v speed=8 dev=0,0,0 -data -eject file_name.img

In this example, a CD-ROM data image named file_name.img is created on a CD-R or CD-RW media at a speed of 8, and the new disk will be ejected after the write operation has completed. See “Burning CDs in Fedora” in Chapter 10, “Multimedia Applications,” for other ways to create CD-ROMs.

This section provides some basic information you can use if you attach a FireWire CD drive to your system. These drives use a high-speed serial interface, otherwise known as IEEE 1394, which supports data transfers more than 30 times faster than the first version of USB (at speeds up to 400Mbps), although USB 2.0 devices are a bit faster.

Linux has supported FireWire since the advent of the 2.4-series kernel, and now works with many different devices, such as video cameras, VCRs, hard drives, scanners, PCMCIA cards, and CD, DVD, or CD-RW drives. The Fedora installer should recognize most FireWire interface hardware; if so, you will be able to use the device with Linux. One Linux FireWire component, the video1394 kernel module, currently supports more than 120 different digital video cameras. General support exists for many different hard drives and DVD or CD-RW drives.

If you install a FireWire interface after Fedora has been installed, you can initialize support for your device, such as a CD-RW drive, by loading the ieee1394 and ohci1394 kernel modules like this:

# insmod ieee1394
# insmod ohci1394

Next, look for relevant device information from the Linux kernel using the dmesg command:

ohci1394: $Revision: 1.80 $ Ben Collins <[email protected]>
PCI: Found IRQ 10 for device 00:0b.0
PCI: Sharing IRQ 10 with 00:07.5
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[ee000000-ee000800] 
 Max Packet=[2048]
ieee1394: Device added: node 2:1023, GUID 00d0010500007d8e
ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
ieee1394: sbp2: Node 2:1023: Max speed [S400] - Max payload [2048]
scsi1 : IEEE-1394 SBP-2 protocol driver
 Vendor: TEAC Model: CD-W28E Rev: 1.1A
 Type: CD-ROM ANSI SCSI revision: 02

In this example, the FireWire drivers have recognized a CD-RW drive (which will be assigned to /dev/scd1 because another CD-RW is also present on the system). You might also find that the sbp2 kernel module has loaded:

Module        Size Used by Not tainted
sbp2         14400 0
ohci1394       15872 0 (unused)
ieee1394       25768 0 [sbp2 ohci1394]

Again, use the cdrecord command and its -scanbus option to obtain information needed to use the drive under SCSI emulation:

# cdrecord -scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
Linux sg driver version: 3.1.22
Using libscg version 'schily-0.5'
scsibus0:
    0,0,0  0) 'HL-DT-ST' 'RW/DVD GCC-4120B' '2.01' Removable CD-ROM
    0,1,0  1) *
    0,2,0  2) *
    0,3,0  3) *
    0,4,0  4) *
    0,5,0 5)  *
    0,6,0  6) *
    0,7,0  7) *
scsibus1:
    1,0,0 100) 'TEAC  ' 'CD-W28E    ' '1.1A' Removable CD-ROM
    1,1,0 101) *
    1,2,0 102) *
    1,3,0 103) *
    1,4,0 104) *
    1,5,0 105) *
    1,6,0 106) *
    1,7,0 107) *

The pertinent information for the FireWire drive—1,0,0 in the example (a drive attached to SCSI bus 1, assigned device 0 and a lun of 0)—can then be used during a read operation like this:

# export CDDA_DEVICE=1,0,0
# cdda2wav -B
Type: ROM, Vendor 'TEAC  ' Model 'CD-W28E     ' Revision '1.1A' MMC+CDDA
724992 bytes buffer memory requested, 4 buffers, 75 sectors
#Cdda2wav version 1.10_linux_2.4.17-0.13smp_i686_i686 real time sched. 
soundcard support
AUDIOtrack pre-emphasis copy-permitted tracktype channels
  1- 8       no       no   audio  2
Table of Contents: total tracks:8, (total time 52:12.72)
 1.( 5:25.67), 2.( 9:06.65), 3.( 5:50.68), 4.( 5:35.57), 5.( 7:28.35)
 6.( 6:34.60), 7.( 6:07.15), 8.( 6:01.05),

Table of Contents: starting sectors
 1.(    0), 2.( 24442), 3.( 65457), 4.( 91775), 5.( 116957)
 6.( 150592), 7.( 180202), 8.( 207742), lead-out( 234822)
CDINDEX discid: SBRXDC1u_.D2S6U1MWq7ksIYOUE-
CDDB discid: 0x5e0c3a08
CD-Text: not detected
CD-Extra: not detected
samplefile size will be 552301388 bytes.
recording 3130.09600 seconds stereo with 16 bits @ 44100.0 Hz ->'audio'...
percent_done:
100% track 1 successfully recorded
100% track 2 successfully recorded
...

In this example, an environment variable named CDDA_DEVICE with the drive’s SCSI information is created, and the cdda2wav command is used to extract the entire contents of an audio CD into .wav file format, with each track saved in a separate file. Other utilities might only need to know the name of the device, such as /dev/scd1, like this:

# cdparanoia -d /dev/scd1 -B
cdparanoia III release 9.8 (March 23, 2001)
(C) 2001 Monty <[email protected]> and Xiphophorus

Report bugs to [email protected]
http://www.xiph.org/paranoia/

    Couldn't disable kernel command translation layer
Ripping from sector    0 (track 1 [0:00.00])
     to sector 234821 (track 8 [6:01.04])

outputting to track01.cdda.wav
...

In this example, the CD-RW device name is used, and again, all tracks from an audio CD will be extracted and saved as .wav audio files. Other graphical clients, such as xine, grip, and xcdroast, are included with Fedora and can be used to create or copy audio and data CDs. See Chapter 10 for more details on burning CDs.