From: Michael Tokarev <mjt@tls.msk.ru>
To: jeff shia <tshxiayu@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: can I write to the cdrom through writing to the device file sr0?
Date: Thu, 18 Aug 2005 16:48:59 +0400 [thread overview]
Message-ID: <430483BB.4090209@tls.msk.ru> (raw)
In-Reply-To: <7cd5d4b40508180538133ca00f@mail.gmail.com>
jeff shia wrote:
> thank you ,DervishD.
> another question:What is the difference between cdrtools and cdrecord?
> It seems that the fomer is bigger.
cdrtools is a package which includes cdrecord. Or, the other
way 'round, cdrecord is a part of cdrtools package. Nowadays,
anyway.
> On 8/18/05, DervishD <lkml@dervishd.net> wrote:
>
>> Hi Jeff :)
>>
>> * jeff shia <tshxiayu@gmail.com> dixit:
>>
>>>I want to write a cdrw user space driver just like cdreord,but the
>>>cdrecord is too complex and huge!can I write to the cdrom through
>>>writing to the device file sr0,here sr0 is the device file of the
>>>cdrw.
>>
>> Although someone may say that the size of cdrecord is
>>proportional to the author's ego, the crude reality is that cdrecord
>>has to be such complex and huge (well, I don't think it is huge,
>>but...). It has to be complex because cdwriting *is* complex. Take a
>>look at the code and see if you can get rid of things. Nowadays I
>>think that most of the writers out there are SCSI-3/MMC compliant, so
>>you can just use that driver, but that won't probably remove much
>>code.
Well, yes and no. If you have re-writable media, there's a packet
driver for it in recent kernels, and it is possible to (indirectly)
mount and use a cdrw device as normal block device. Ofcourse it'll
only work for data "tracks", not for audio disks.
/mjt
next prev parent reply other threads:[~2005-08-18 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 8:40 can I write to the cdrom through writing to the device file sr0? jeff shia
2005-08-18 10:07 ` DervishD
2005-08-18 12:38 ` jeff shia
2005-08-18 12:48 ` Michael Tokarev [this message]
2005-08-18 13:03 ` jeff shia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=430483BB.4090209@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=tshxiayu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.