public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <sourcejedi@phonecoop.coop>
To: linux-kernel@vger.kernel.org
Subject: cd burning: kernel / userspace?
Date: Tue, 10 Aug 2004 10:51:30 +0100	[thread overview]
Message-ID: <41189AA2.3010908@phonecoop.coop> (raw)

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.

The current Mount Rainer allows you to treat a MR formatted CD-RW as a 
big floppy disk - to read and write to /dev/cdrecorder just like 
/dev/floppy.  The packet writing patch takes a different approach - 
using a separate device which is bound to the cdrecorder device, but 
AFAIK this is a temporary measure, and the ultimate goal is make this 
work the same way - the way the user would expect:

1. Insert a recordable media (e.g. cdrw).
2. Perform any necessary formatting (e.g. cdmrw -d /dev/cdrecorder -f full)
3. Access cdrecorder device (e.g. mount /dev/cdrecorder -tudf -onoatime 
/mnt/cdrecorder)

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.

Unfortunately I'm no kernel hacker, so I have no idea whether this is 
practical, and if so how much work would be involved.  I have plenty of 
time to investigate the idea, and upgrade myself from a mere C 
programmer.  Any advice would be appreciated.

Alan Jenkins

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  9:51 Alan Jenkins [this message]
2004-08-10 22:05 ` cd burning: kernel / userspace? Wakko Warner
     [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=41189AA2.3010908@phonecoop.coop \
    --to=sourcejedi@phonecoop.coop \
    --cc=linux-kernel@vger.kernel.org \
    /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