注册 登录  
 加关注
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

My Unix World

不要迷恋Unix,Unix只是计算世界很小的一部分!

 
 
 

日志

 
 

man of wodim 2  

2008-11-26 13:16:29|  分类: L-Tools |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |
TRACK OPTIONS
Track options may be mixed with track file names.

isrc=ISRC_number
Set the International Standard Recording Number for the next
track to ISRC_number.

index=list
Sets an index list for the next track. In index list is a comma
separated list of numbers that are counting from index 1. The
first entry in this list must contain a 0, the following numbers
must be an ascending list of numbers (counting in 1/75 seconds)
that represent the start of the indices. An index list in the
form: 0,7500,15000 sets index 1 to the start of the track, index
2 100 seconds from the start of the track and index 3 200 sec-
onds from the start of the track.

-audio If this flag is present, all subsequent tracks are written in
CD-DA (similar to Red Book) audio format. The file with data
for this tracks should contain stereo, 16-bit digital audio with
44100 samples/s. The byte order should be the following: MSB
left, LSB left, MSB right, LSB right, MSB left and so on. The
track should be a multiple of 2352 bytes. It is not possible to
put the master image of an audio track on a raw disk because
data will be read in multiple of 2352 bytes during the recording
process.

If a filename ends in .au or .wav the file is considered to be a
structured audio data file. wodim assumes that the file in this
case is a Sun audio file or a Microsoft .WAV file and extracts
the audio data from the files by skipping over the non-audio
header information. In all other cases, wodim will only work
correctly if the audio data stream does not have any header.
Because many structured audio files do not have an integral num-
ber of blocks (1/75th second) in length, it is often necessary
to specify the -pad option as well. wodim recognizes that audio
data in a .WAV file is stored in Intel (little-endian) byte
order, and will automatically byte-swap the data if the CD
recorder requires big-endian data. wodim will reject any audio
file that does not match the Red Book requirements of 16-bit
stereo samples in PCM coding at 44100 samples/second.

Using other structured audio data formats as input to wodim will
usually work if the structure of the data is the structure
described above (raw pcm data in big-endian byte order). How-
ever, if the data format includes a header, you will hear a
click at the start of a track.

If neither -data nor -audio have been specified, wodim defaults
to -audio for all filenames that end in .au or .wav and to -data
for all other files.

-swab If this flag is present, audio data is assumed to be in byte-
swapped (little-endian) order. Some types of CD-Writers e.g.
Yamaha, Sony and the new SCSI-3/mmc drives require audio data to
be presented in little-endian order, while other writers require
audio data to be presented in the big-endian (network) byte
order normally used by the SCSI protocol. wodim knows if a CD-
Recorder needs audio data in big- or little-endian order, and
corrects the byte order of the data stream to match the needs of
the recorder. You only need the -swab flag if your data stream
is in Intel (little-endian) byte order.

Note that the verbose output of wodim will show you if swapping
is necessary to make the byte order of the input data fit the
required byte order of the recorder. wodim will not show you if
the -swab flag was actually present for a track.

-data If this flag is present, all subsequent tracks are written in
CD-ROM mode 1 (Yellow Book) format. The data size is a multiple
of 2048 bytes. The file with track data should contain an
ISO-9660 or Rock Ridge filesystem image (see mkisofs for more
details). If the track data is an ufs filesystem image, fragment
size should be set to 2 KB or more to allow CD-drives with 2 KB
sector size to be used for reading.

-data is the default, if no other flag is present and the file
does not appear to be of one of the well known audio file types.

If neither -data nor -audio have been specified, wodim defaults
to -audio for all filenames that end in .au or .wav and to -data
for all other files.

-mode2 If this flag is present, all subsequent tracks are written in
CD-ROM mode 2 format. The data size is a multiple of 2336 bytes.

-xa If this flag is present, all subsequent tracks are written in
CD-ROM XA mode 2 form 1 format. The data size is a multiple of
2048 bytes. The XA sector sub headers will be created by the
drive. With this option, the write mode is the same as with the
-multi option.

-xa1 If this flag is present, all subsequent tracks are written in
CD-ROM XA mode 2 form 1 format. The data size is a multiple of
2056 bytes. The XA sector sub headers are part of the user data
and have to be supplied by the application that prepares the
data to be written.

-xa2 If this flag is present, all subsequent tracks are written in
CD-ROM XA mode 2 form 2 format. The data is a multiple of 2324
bytes. The XA sector sub headers will be created by the drive.

-xamix If this flag is present, all subsequent tracks are written in a
way that allows a mix of CD-ROM XA mode 2 form 1/2 format. The
data size is a multiple of 2332 bytes. The XA sector sub head-
ers are part of the user data and have to be supplied by the
application that prepares the data to be written. The CRC and
the P/Q parity ECC/EDC information (depending on the sector
type) have to be supplied by the application that prepares the
data to be written.

-cdi If this flag is present, the TOC type for the disk is set to
CDI. This only makes sense with XA disks.

-isosize
Use the ISO-9660 file system size as the size of the next track.
This option is needed if you want wodim to directly read the
image of a track from a raw disk partition or from a TAO master
CD. In the first case the option -isosize is needed to limit the
size of the CD to the size of the ISO filesystem. In the second
case the option -isosize is needed to prevent wodim from reading
the two run out blocks that are appended by each CD-recorder in
track at once mode. These two run out blocks cannot be read and
would cause a buffer underrun that would cause a defective copy.
Do not use this option on files created by mkisofs and in case
wodim reads the track data from stdin. In the first case, you
would prevent wodim from writing the amount of padding that has
been appended by mkisofs and in the latter case, it will not
work because stdin is not seekable.

If -isosize is used for a track, wodim will automatically add
padding for this track as if the -pad option has been used but
the amount of padding may be less than the padding written by
mkisofs. Note that if you use -isosize on a track that contains
Sparc boot information, the boot information will be lost.

Note also that this option cannot be used to determine the size
of a file system if the multi session option is present.

-pad If the track is a data track, 15 sectors of zeroed data will be
added to the end of this and each subsequent data track. In
this case, the -pad option is superseded by the padsize= option.
It will remain however as a shorthand for padsize=15s. If the
-pad option refers to an audio track, wodim will pad the audio
data to be a multiple of 2352 bytes. The audio data padding is
done with binary zeroes which is equal to absolute silence.

-pad remains valid until disabled by -nopad.

padsize=#
Set the amount of data to be appended as padding to the next
track to #. Opposed to the behavior of the -pad option, the
value for padsize= is reset to zero for each new track. wodim
assumes a sector size of 2048 bytes for the padsize= option,
independent from the real sector size and independent from the
write mode. The megabytes mentioned in the verbose mode output
however are counting the output sector size which is e.g. 2448
bytes when writing in RAW/RAW96 mode. See fs= option for possi-
ble arguments. To pad the equivalent of 20 minutes on a CD, you
may write padsize=20x60x75s. Use this option if your CD-drive
is not able to read the last sectors of a track or if you want
to be able to read the CD on a Linux system with the ISO-9660
filesystem read ahead bug. If an empty file is used for track
data, this option may be used to create a disk that is entirely
made of padding. This may e.g. be used to find out how much
overburning is possible with a specific media.

-nopad Do not pad the following tracks - the default.

-shorttrack
Allow all subsequent tracks to violate the Red Book track length
standard which requires a minimum track length of 4 seconds.
This option is only useful when used in SAO or RAW mode. Not
all drives support this feature. The drive must accept the
resulting CUE sheet or support RAW writing.

-noshorttrack
Re-enforce the Red Book track length standard. Tracks must be at
least 4 seconds.

pregap=#
Set the pre-gap size for the next track. This option currently
only makes sense with the TEAC drive when creating track-at-once
disks without the 2 second silence before each track.
This option may go away in future.

-preemp
If this flag is present, all TOC entries for subsequent audio
tracks will indicate that the audio data has been sampled with
50/15 microsec pre-emphasis. The data, however is not modified
during the process of transferring from file to disk. This
option has no effect on data tracks.

-nopreemp
If this flag is present, all TOC entries for subsequent audio
tracks will indicate that the audio data has been mastered with
linear data - this is the default.

-copy If this flag is present, all TOC entries for subsequent audio
tracks of the resulting CD will indicate that the audio data has
permission to be copied without limit. This option has no
effect on data tracks.

-nocopy
If this flag is present, all TOC entries for subsequent audio
tracks of the resulting CD will indicate that the audio data has
permission to be copied only once for personal use - this is the
default.

-scms If this flag is present, all TOC entries for subsequent audio
tracks of the resulting CD will indicate that the audio data has
no permission to be copied anymore.

tsize=#
If the master image for the next track has been stored on a raw
disk, use this option to specify the valid amount of data on
this disk. If the image of the next track is stored in a regular
file, the size of that file is taken to determine the length of
this track. If the track contains an ISO 9660 filesystem image
use the -isosize option to determine the length of that filesys-
tem image.
In Disk at Once mode and with some drives that use the TEAC pro-
gramming interface, even in Track at Once mode, wodim needs to
know the size of each track before starting to write the disk.
wodim now checks this and aborts before starting to write. If
this happens you will need to run mkisofs -print-size before and
use the output (with `s' appended) as an argument to the tsize=
option of wodim (e.g. tsize=250000s).
See fs= option for possible arguments.


EXAMPLES
For all examples below, it will be assumed that the CD/DVD-Recorder is
connected to the primary SCSI bus of the machine. The SCSI target id is
set to 2.

To record a pure CD-ROM at double speed, using data from the file cdim-
age.raw:

wodim -v speed=2 dev=2,0 cdimage.raw

To create an image for a ISO 9660 filesystem with Rock Ridge exten-
sions:

mkisofs -R -o cdimage.raw /home/joerg/master/tree

To check the resulting file before writing to CD on Solaris:

mount -r -F fbk -o type=hsfs /dev/fbk0:cdimage.raw /mnt

On Linux:

mount cdimage.raw -r -t iso9660 -o loop /mnt

Go on with:
ls -lR /mnt
umount /mnt

If the overall speed of the system is sufficient and the structure of
the filesystem is not too complex, wodim will run without creating an
image of the ISO 9660 filesystem. Simply run the pipeline:

mkisofs -R /master/tree | wodim -v fs=6m speed=2 dev=2,0 -

The recommended minimum FIFO size for running this pipeline is 4
MBytes. As the default FIFO size is 4 MB, the fs= option needs only be
present if you want to use a different FIFO size. If your system is
loaded, you should run mkisofs in the real time class too. To raise
the priority of mkisofs replace the command

mkisofs -R /master/tree
by
priocntl -e -c RT -p 59 mkisofs -R /master/tree

on Solaris and by

nice --18 mkisofs -R /master/tree

on systems that don't have UNIX International compliant real-time
scheduling.

wodim runs at priority 59 on Solaris, you should run mkisofs at no more
than priority 58. On other systems, you should run mkisofs at no less
than nice --18.

Creating a CD-ROM without file system image on disk has been tested on
a Sparcstation-2 with a Yamaha CDR-400. It did work up to quad speed
when the machine was not loaded. A faster machine may be able to han-
dle quad speed also in the loaded case.

To record a pure CD-DA (audio) at single speed, with each track con-
tained in a file named track01.cdaudio, track02.cdaudio, etc:

wodim -v speed=1 dev=/dev/cdrw -audio track*.cdaudio

To check if it will be ok to use double speed for the example above.
Use the dummy write option:

wodim -v -dummy speed=2 dev=/dev/cdrw -audio track*.cdaudio

To record a mixed-mode CD with an ISO 9660 filesystem from cdimage.raw
on the first track, the other tracks being audio tracks from the files
track01.cdaudio, track02.cdaudio, etc:

wodim -v dev=2,0 cdimage.raw -audio track*.cdaudio

To handle drives that need to know the size of a track before starting
to write, first run

mkisofs -R -q -print-size /master/tree

and then run

mkisofs -R /master/tree | wodim speed=2 dev=2,0 tsize=XXXs -

where XXX is replaced by the output of the previous run of mkisofs.

To copy an audio CD in the most accurate way, first run

cdda2wav dev=2,0 -vall cddb=0 -B -Owav

and then run

wodim dev=2,0 -v -dao -useinfo -text *.wav

This will try to copy track indices and to read CD-Text information
from disk. If there is no CD-Text information, cdda2wav will try to
get the information from freedb.org instead.

To copy an audio CD from a pipe (without intermediate files), first run

cdda2wav dev=1,0 -vall cddb=0 -info-only

and then run

cdda2wav dev=1,0 -no-infofile -B -Oraw - | \
wodim dev=2,0 -v -dao -audio -useinfo -text *.inf

This will get all information (including track size info) from the
*.inf files and then read the audio data from stdin.

If you like to write from stdin, make sure that wodim is called with a
large enough FIFO size (e.g. fs=128m), reduce the write speed to a
value below the read speed of the source drive (e.g. speed=12), and
switch the burn-free option for the recording drive on by adding
driveropts=burnfree.

To set drive options without writing a CD (e.g. to switch a drive to
single session mode), run

wodim dev=1,0 -setdropts driveropts=singlesession

If you like to do this when no CD is in the drive, call

wodim dev=1,0 -force -setdropts driveropts=singlesession

To copy a CD in clone mode, first read the master CD using:

readcd dev=b,t,l -clone f=somefile

or (in case the CD contains many sectors that are unreadable by inten-
tion) by calling:

readcd dev=1,0 -clone -nocorr f=somefile

will create the files somefile and somefile.toc. Then write the CD
using:

wodim dev=1,0 -raw96r -clone -v somefile



ENVIRONMENT
CDR_DEVICE
This may either hold a device identifier that is suitable to the
open call of the SCSI transport library or a label in the file
/etc/wodim.conf.

CDR_SPEED
Sets the default speed value for writing (see also speed=
option).

CDR_FIFOSIZE
Sets the default size of the FIFO (see also fs=# option).

CDR_FORCERAWSPEED
If this environment variable is set, wodim will allow you to
write at the full RAW encoding speed a single CPU supports.
This will create high potential of buffer underruns. Use with
care.

CDR_FORCESPEED
If this environment variable is set, wodim will allow you to
write at the full DMA speed the system supports. There is no
DMA reserve for reading the data that is to be written from
disk. This will create high potential of buffer underruns. Use
with care.

RSH If the RSH environment is present, the remote connection will
not be created via rcmd(3) but by calling the program pointed to
by RSH. Use e.g. RSH=/usr/bin/ssh to create a secure shell
connection.

Note that this forces wodim to create a pipe to the rsh(1) pro-
gram and disallows wodim to directly access the network socket
to the remote server. This makes it impossible to set up per-
formance parameters and slows down the connection compared to a
root initiated rcmd(3) connection.

RSCSI If the RSCSI environment is present, the remote SCSI server will
not be the program /opt/schily/sbin/rscsi but the program
pointed to by RSCSI. Note that the remote SCSI server program
name will be ignored if you log in using an account that has
been created with a remote SCSI server program as login shell.


FILES
/etc/wodim.conf
Default values can be set for the following options in
/etc/wodim.conf. For example: CDR_FIFOSIZE=8m or CDR_SPEED=2

CDR_DEVICE
This may either hold a device identifier that is suitable
to the open call of the SCSI transport library or a label
in the file /etc/wodim.conf that allows to identify a
specific drive on the system.

CDR_SPEED
Sets the default speed value for writing (see also speed=
option).

CDR_FIFOSIZE
Sets the default size of the FIFO (see also fs=# option).

CDR_MAXFIFOSIZE
Sets the maximum size of the FIFO (see also fs=# option).

Any other label
is an identifier for a specific drive on the system.
Such an identifier may not contain the characters ',',
'/', '@' or ':'.

Each line that follows a label contains a TAB separated
list of items. Currently, four items are recognized: the
SCSI ID of the drive, the default speed that should be
used for this drive, the default FIFO size that should be
used for this drive and drive specific options. The val-
ues for speed and fifosize may be set to -1 to tell wodim
to use the global defaults. The value for driveropts may
be set to "" if no driveropts are used. A typical line
may look this way:

teac1= 0,5,0 4 8m ""

yamaha= 1,6,0 -1 -1 burnfree

This tells wodim that a drive named teac1 is at scsibus
0, target 5, lun 0 and should be used with speed 4 and a
FIFO size of 8 MB. A second drive may be found at scsi-
bus 1, target 6, lun 0 and uses the default speed and the
default FIFO size.


SEE ALSO
cdda2wav(1), readcd(1), scg(7), fbk(7), mkisofs(8), rcmd(3), ssh(1).


NOTES
On Solaris you need to stop the volume management if you like to use
the USCSI fallback SCSI transport code. Even things like wodim -scanbus
will not work if the volume management is running.

Disks made in Track At Once mode are not suitable as a master for
direct mass production by CD manufacturers. You will need the disk at
once option to record such disks. Nevertheless the disks made in Track
At Once will normally be read in all CD players. Some old audio CD
players however may produce a two second click between two audio
tracks.

The minimal size of a track is 4 seconds or 300 sectors. If you write
smaller tracks, the CD-Recorder will add dummy blocks. This is not an
error, even though the SCSI-error message looks this way.

The Yamaha CDR-400 and all new SCSI-3/mmc conforming drives are sup-
ported in single and multi-session.

You should run several tests in all supported speeds of your drive with
the -dummy option turned on if you are using wodim on an unknown sys-
tem. Writing a CD is a real-time process. NFS, CIFS and other network
file systems won't always deliver constantly the needed data rates. If
you want to use wodim with CD-images that are located on a NFS mounted
filesystem, be sure that the FIFO size is big enough. If you want to
make sure that buffer underruns are not caused by your source disk, you
may use the command

wodim -dummy dev=2,0 padsize=600m /dev/null

to create a disk that is entirely made of dummy data.

There are also cases where you either need to be root or install wodim
executable with suid-root permissions. First, if you are using a device
manufactured before 1999 which requires a non-MMC driver, you should
run wodim in dummy mode before writing data. If you find a problem
doing this, please report it to the cdrkit maintainers (see below).

Second, certain functionality may be unusable because of Linux's SCSI
command filtering. When using wodim for anything except of pure data
writing, you should also test the process in dummy mode and report
trouble to the contact address below.

If you still want to run wodim with root permissions, you can set the
permissions of the executable to suid-root. See the additional notes of
your system/program distribution or README.suidroot which is part of
the cdrkit source.

You should not connect old drives that do not support disconnect/recon-
nect to either the SCSI bus that is connected to the CD-Recorder or the
source disk.

A Compact Disc can have no more than 99 tracks.

When creating a disc with both audio and data tracks, the data should
be on track 1 otherwise you should create a CDplus disk which is a
multi session disk with the first session containing the audio tracks
and the following session containing the data track.

Many operating systems are not able to read more than a single data
track, or need special software to do so.

If you have more information or SCSI command manuals for currently
unsupported CD/DVD/BR/HD-DVD-Recorders, please contact the cdrkit main-
tainers (see below).

Many CD recorders have bugs and often require a firmware update to work
correctly. If you exprience problems which cannot be solved or
explained by the notes above, please look for instructions on the home-
page of the particular manufacturer.

Some bugs will force you to power cycle the device or to reboot the
machine.

The FIFO percent output is computed just after a block of data has been
written to the CD/DVD-Recorder. For this reason, there will never be
100% FIFO fill ratio while the FIFO is in streaming mode.


DIAGNOSTICS
You have 9 seconds to abort wodim start after you see the message:

Starting to write CD at speed %d in %s mode for %s session. In most
shells you can do that by pressing Ctrl-C.

A typical error message for a SCSI command looks like:

wodim: I/O error. test unit ready: scsi sendcmd: no error
CDB: 00 20 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 25 00 00 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x25 Qual 0x00 (logical unit not supported) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.002s timeout 40s

The first line gives information about the transport of the command.
The text after the first colon gives the error text for the system call
from the view of the kernel. It usually is: I/O error unless other
problems happen. The next words contain a short description for the
SCSI command that fails. The rest of the line tells you if there were
any problems for the transport of the command over the SCSI bus. fatal
error means that it was not possible to transport the command (i.e. no
device present at the requested SCSI address).

The second line prints the SCSI command descriptor block for the failed
command.

The third line gives information on the SCSI status code returned by
the command, if the transport of the command succeeds. This is error
information from the SCSI device.

The fourth line is a hex dump of the auto request sense information for
the command.

The fifth line is the error text for the sense key if available, fol-
lowed by the segment number that is only valid if the command was a
copy command. If the error message is not directly related to the cur-
rent command, the text deferred error is appended.

The sixth line is the error text for the sense code and the sense qual-
ifier if available. If the type of the device is known, the sense data
is decoded from tables in scsierrs.c . The text is followed by the
error value for a field replaceable unit.

The seventh line prints the block number that is related to the failed
command and text for several error flags. The block number may not be
valid.

The eight line reports the timeout set up for this command and the time
that the command really needed to complete.

The following message is not an error:

Track 01: Total bytes read/written: 2048/2048 (1 sectors).
wodim: I/O error. flush cache: scsi sendcmd: no error
CDB: 35 00 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 05 80 00 00 27 0A 00 00 00 00 B5 00 00 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0xB5 Qual 0x00 (dummy data blocks added) Fru 0x0
Sense flags: Blk -2147483609 (valid)
cmd finished after 0.002s timeout 40s

It simply notifies, that a track that is smaller than the minimum size
has been expanded to 300 sectors.

BUGS
wodim has even more options than ls.

There should be a recover option to make disks usable, that have been
written during a power failure.


CREDITS
Joerg Schilling (schilling@fokus.fhg.de)
For writing cdrecord and libscg which represent the most
part of wodim's code.


Bill Swartz (Bill_Swartz@twolf.com)
For helping me with the TEAC driver support

Aaron Newsome (aaron.d.newsome@wdc.com)
For letting me develop Sony support on his drive

Eric Youngdale (eric@andante.jic.com)
For supplying mkisofs

Gadi Oxman (gadio@netvision.net.il)
For tips on the ATAPI standard

Finn Arne Gangstad (finnag@guardian.no)
For the first FIFO implementation.

Dave Platt (dplatt@feghoot.ml.org)
For creating the experimental packet writing support,
the first implementation of CD-RW blanking support, the
first .wav file decoder and many nice discussions on
cdrecord.

Chris P. Ross (cross@eng.us.uu.net)
For the first implementation of a BSDI SCSI transport.

Grant R. Guenther (grant@torque.net)
For creating the first parallel port transport implemen-
tation for Linux.

Kenneth D. Merry (ken@kdm.org)
for providing the CAM port for FreeBSD together with
Michael Smith (msmith@freebsd.org)

Heiko Eiszfeldt (heiko@hexco.de)
for making libedc_ecc available (needed to write RAW
data sectors).


MAILING LISTS
If you want to actively take part on the development of wodim, you may
join the developer mailing list via this URL:

https://alioth.debian.org/mail/?group_id=31006

The mail address of the list is: debburn-devel@lists.alioth.debian.org


AUTHORS
wodim is currently maintained as part of the cdrkit project by its
developers. Most of the code and this manual page was originally writ-
ten by:

Joerg Schilling
Seestr. 110
D-13353 Berlin
Germany

This application is a spinoff from the original program "cdrecord"
delivered in the cdrtools package [1] created by Joerg Schilling, who
deserves the most credits for its success. However, he is not involved
into the development of this spinoff and therefore he shall not be made
responsible for any problem caused by it. Do not refer to this applica-
tion as "cdrecord", do not try to get support for wodim by contacting
the original authors.

Additional information can be found on:
https://alioth.debian.org/projects/debburn/

If you have support questions, send them to

debburn-devel@lists.alioth.debian.org

If you have definitely found a bug, send a mail to this list or to

submit@bugs.debian.org

writing at least a short description into the Subject and "Package:
cdrkit" into the first line of the mail body.
  评论这张
 
阅读(378)| 评论(0)
推荐 转载

历史上的今天

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2017