public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Alan Jenkins <sourcejedi@phonecoop.coop>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cd burning: kernel / userspace?
Date: Tue, 10 Aug 2004 18:05:28 -0400	[thread overview]
Message-ID: <20040810220528.GA17537@animx.eu.org> (raw)
In-Reply-To: <41189AA2.3010908@phonecoop.coop>

> I've followed the latest cdrecord "discussion" on the list, and I can't 
> see why you have to use a userspace program which talks SCSI in order to 
> burn a cd.

I agree.

> Why can't a similar method be used for DAO writing?  Packet writing and 
> Mount Rainer support belongs in the kernel - why not normal cd burning?  
> On modern "burnproof" hardware, it should be possible to use dd to write 
> your disk image to the cdrecorder device.  I'm guessing that this just 
> isn't as interesting, especially with userspace programs available to do 
> the job.

Disclamer: I'm not a kernel hacker.  Just looking at things on how they
appear to me...

I have thought about this myself.  Using CDR/RW with the UDF format would be
simply packet writing.  This is already supported with CDRWs.

However, I usually burn ISO instead of UDF.  How should these instances be
supported:

1) DAO (ISO image burned)
2) TAO single session with or without fixation.  I have burned audio disks
like this before where I would leave off the fixate option and keep burning,
each track is closed.
3) TAO multi session leaving disk open
4) TAO multi session closing disk (probably similar if not the same as 2)
5) blanking a CDRW (fast and/or slow)

Maybe something along the lines of IOCTLs that do these?  Wouldn't it seem
silly to:
cdrwcontrol DAO speed=40 burnproof ....
dd if=my.iso of=/dev/scd0 (sorry, I'm a scsi guy =)

or cdrwcontrol TAO speed=40 ...
dd ..
cdrwcontrol fixate

Ok, enough rambling, I think the idea is out =)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

  reply	other threads:[~2004-08-10 22:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  9:51 cd burning: kernel / userspace? Alan Jenkins
2004-08-10 22:05 ` Wakko Warner [this message]
     [not found]   ` <4119DFB0.6050204@phonecoop.coop>
     [not found]     ` <20040811164109.GA18761@animx.eu.org>
2004-08-11 21:03       ` Alan Jenkins
2004-08-11 21:33         ` Wakko Warner
2004-08-11 21:43           ` Alan Jenkins
2004-08-12  0:12             ` Wakko Warner
2004-08-12  9:07               ` Alan Jenkins
2004-08-12 12:37               ` Sergey Vlasov
2004-08-12 23:06   ` Kevin Fox
2004-08-13  0:13     ` Wakko Warner
2004-08-16 21:37       ` David Lang
2004-08-10 23:50 ` Valdis.Kletnieks
2004-08-16 20:47 ` Pavel Machek

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=20040810220528.GA17537@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sourcejedi@phonecoop.coop \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox