[9fans] cdrw? dvdrw ?

[9fans] cdrw? dvdrw ?

[steve.simon]

Hi,

Are cd-burners/cdrw drives standardised these days such that plan9 can burn
CDs any current drive - at one time only a few where supported.

If so do these work for R/W's as well as WORM disks?

Also are/all any dvd writers be supported ?

Thanks,

-Steve

Re: [9fans] cdrw? dvdrw ?

[Russ Cox]

> Are cd-burners/cdrw drives standardised these days such that plan9 can burn
> CDs any current drive - at one time only a few where supported.

> If so do these work for R/W's as well as WORM disks?

CD-RWs and CD-Rs, yes.  If by WORM you mean CD-R, yes.
(I've never seen them named WORM, but I suppose they are.)

> Also are/all any dvd writers be supported ?

I haven't tried but I believe that writing to DVDs
will just work in cdfs.  Someone (Richard Miller?)
was trying this at one point.  

The hard part there is creating the images.
Most systems won't read 9660 images burnt to DVD.
If you don't care about other systems reading the
DVD, then arbitrary byte streams should just work,
if not immediately then with minimal effort.

Russ

Re: [9fans] cdrw? dvdrw ?

[Richard Miller]

> I haven't tried but I believe that writing to DVDs
> will just work in cdfs.  Someone (Richard Miller?)
> was trying this at one point.  

No, my writable dvd drive is a DVD-RAM, which is block-addressable
like a hard drive so you can write to it with kfs or venti.  The
drawback is you can't read the discs in any other kind of dvd player.
And they cost too much.

-- Richard

Re: [9fans] cdrw? dvdrw ?

[jmk]

If you haven't purchased one yet, and you have the money, look at the
Sony DRU500A. It handles CD-R/-RW, DVD-R/-RW and DVD+R/+RW. Bruce Ellis
(brucee) purchased one and was quite impressed.

[9fans] deadlock in page(1)

[Richard Miller]

When page calls gs to display a postscript file which uses \r as a line
terminator (not \n or \r\n), deadlock ensues.  Here's a correction (which
may also reduce the need for the '-P' option):

/sys/src/cmd/page/ps.c:429 a ps.c:430,434
> 	/*
> 	 * If last line terminator is \r, gs will read ahead to check for \n
> 	 * so send one to avoid deadlock.
> 	 */
> 	write(ps->gsfd, "\n", 1);

-- Richard Miller

Re: [9fans] deadlock in page(1)

[bwc]

[-- Attachment #1: Type: text/plain, Size: 152 bytes --]

Is this a problem in pdf2ps also?  When I ps2pdf'ed fossil.pdf and sent the
result to my HP4000, the printer hung.  Had to power cycle it.

 Brantley

[-- Attachment #2: Type: message/rfc822, Size: 1805 bytes --]

From: Richard Miller <miller@hamnavoe.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: [9fans] deadlock in page(1)
Date: Wed, 8 Jan 2003 11:40:28 0000
Message-ID: <10448d781152600dab2fec6cee720288@hamnavoe.demon.co.uk>

When page calls gs to display a postscript file which uses \r as a line
terminator (not \n or \r\n), deadlock ensues.  Here's a correction (which
may also reduce the need for the '-P' option):

/sys/src/cmd/page/ps.c:429 a ps.c:430,434
> 	/*
> 	 * If last line terminator is \r, gs will read ahead to check for \n
> 	 * so send one to avoid deadlock.
> 	 */
> 	write(ps->gsfd, "\n", 1);

-- Richard Miller

Re: [9fans] deadlock in page(1)

[Richard Miller]

> Is this a problem in pdf2ps also?

No, it was specifically an interaction between page and gs.

Re: [9fans] deadlock in page(1)

[Russ Cox]

I don't think pdf2ps has this problem.
Pdf2ps generates enormous files, since
they're just 300dpi (maybe 600dpi?) bitmaps.

They take a long time to print.

Better just to use fossil.ps.