Man page for apt-get wodim Command
This tutorial shows the man page for man wodim in linux.
Open terminal with 'su' access and type the command as shown below:
Result of the Command Execution shown below:
wodim write data to optical disk media
wodim [options] track1...trackn
There may be similarities and differences between this program and
other disk recording application(s). See the CREDITS and AUTHORS sec
tions below to learn about the origin of wodim.
wodim is used to record data or audio Compact Discs on an Orange Book
CD Recorder or to write DVD media on a DVD Recorder.
The device is the device file or label offered by the operating system
to access the recorder with SCSI GENERIC (sg) interface. Note that some
operating systems may provide separate device nodes for block oriented
and sg access. For example, on older Linux systems, the sg access was
available through /dev/sg... files while the block oriented access was
done through associated (but not identical) /dev/hd... and /dev/sr...
(or /dev/scd... ) files.
In any case, the user running wodim needs read and write access to the
particular device file on a Linux system. It is recommended to be root
or install the application as suid root, because certain versions of
Linux (kernel) limit the set of SCSI commands allowed for non root
users. Even if usage without root identity is possible in many cases,
some device drivers still may fail, show unexplainable problems and
generally the problems become harder to debug. The risk for buffer
underruns is also increased. See the PROCESS SCHEDULING PRIORITY sec
tion below for more details.
There is an alternative way of specifying the device, using the tradi
tional SCSI descriptions in form of devicetype:bus/target/lun specifi
cation. However, the success of this method is not guaranteed since it
requires an adaptation scheme for your architecture, and the numbers
may vary depending on the hardware internal numbering or on the order
of hot plug device detection. If your operating system does not provide
a sufficient framework for keeping this numbers persistent, don't rely
on them. See scanbus and devices options below for details.
There are emulated SCSI compatible device systems, using the SCSI pro
tocols transported over various hardware/media types. The most known
examples is ATAPI ("IDE burners") or USB storage ("external USB case").
If the pseudo SCSI b/t/l device address specification is used instead
of the native one, you need to prepend the "devicetype:" description to
the emulated "bus/target/lun" device address.
If a file /etc/wodim.conf exists, the parameter to the dev= option may
also be a drive name label in that file (see FILES section).
As a special exception, the device specification can be 1 or just
omitted, which invokes automatic guessing of an appropriate device for
the selected operation. However, this guessing is not available every
where and is not reliable; it is only available for the user's conve
nience in simple environments.
In Track At Once mode, each track corresponds to a single file that
contains the prepared data for that track. If the argument is ` ',
standard input is used for that track. Only one track may be taken
from stdin. In the other write modes, the direct file to track rela
tion may not be implemented. In clone mode, a single file contains
all data for the whole disk. To allow DVD writing on platforms that do
not implement large file support, wodim concatenates all file arguments
to a single track when writing to DVD media.
PROCESS SCHEDULING PRIORITY
Wodim tries to get higher process priority using different methods.
This is important because the burn process is usually a realtime task,
no long delays should occur while transmitting fresh data to the
recorder. This is especially important on systems with insufficient RAM
where swapping can create delays of many seconds.
A possible workaround on underpowered systems is the use of the burn
free or similar feature, allowing the recorder to resume.
Root permissions are usually required to get higher process scheduling
On SVr4 compliant systems, wodim uses the real time class to get the
highest scheduling priority that is possible (higher than all kernel
processes). On systems with POSIX real time scheduling wodim uses real
time scheduling too, but may not be able to gain a priority that is
higher than all kernel processes.
In order to be able to use the SCSI transport subsystem of the OS, run
at highest priority and lock itself into core wodim either needs to be
run as root, needs to be installed suid root or must be called via
RBACs pfexec mechanism.
General options must be before any track file name or track option.
Print version information and exit.
v Increment the level of general verbosity by one. This is used
e.g. to display the progress of the writing process.
V Increment the verbose level in respect of SCSI command transport
by one. This helps to debug problems during the writing
process, that occur in the CD/DVD Recorder. If you get incom
prehensible error messages you should use this flag to get more
detailed output. VV will show data buffer content in addition.
Using V or VV slows down the process and may be the reason for
a buffer underrun.