Rodney W. Grimes scribbled this message on Aug 24:
> Ahhh.. did we just experience a major time warp some place? I just
> received about 15 messages I know I have read before, all dated
> 18 Aug 1999.
if you notice that the bottoms have TWO unsubscribe messages attached..
looks like someone a
> Amancio Hasty wrote...
> > > There is a generic SCSI bus enumerator API, and one for PCI as well. There
> > > isn't a generic API to get trees of devices of any type in the system,
> > > though. With new-bus that might be possible, but having done two
> > > enumerator APIs already (I wrote the
Amancio Hasty wrote...
> > Amancio Hasty wrote...
> > > I have to agree with Matt on this plus the set of defaults is system wide .
> >
> > What are you agreeing with him on? Why not quote what you're talking
> > about?
> >
> > > Is it possible to get a system bus enumeration from the system so
Amancio Hasty wrote...
> I have to agree with Matt on this plus the set of defaults is system wide .
What are you agreeing with him on? Why not quote what you're talking
about?
> Is it possible to get a system bus enumeration from the system so
> a program such a cdrecord can attempt to make a
Ahhh.. did we just experience a major time warp some place? I just
received about 15 messages I know I have read before, all dated
18 Aug 1999.
> < said:
>
> > Or if there is a system call or modification to open such that I can issue :
> > open("pci0:10:0", .)
>
> Don't be silly.
>
>
Amancio Hasty wrote...
> > There is a generic SCSI bus enumerator API, and one for PCI as well. There
> > isn't a generic API to get trees of devices of any type in the system,
> > though. With new-bus that might be possible, but having done two
> > enumerator APIs already (I wrote the CAM and P
> Amancio Hasty wrote...
> > > Amancio Hasty wrote...
> > > > I have to agree with Matt on this plus the set of defaults is system wide .
> > >
> > > What are you agreeing with him on? Why not quote what you're talking
> > > about?
> > >
> > > > Is it possible to get a system bus enumeration fr
> Amancio Hasty wrote...
> > I have to agree with Matt on this plus the set of defaults is system wide .
>
> What are you agreeing with him on? Why not quote what you're talking
> about?
>
> > Is it possible to get a system bus enumeration from the system so
> > a program such a cdrecord can a
< said:
> Or if there is a system call or modification to open such that I can issue :
> open("pci0:10:0", .)
Don't be silly.
> On the kernel side, I hope that the pci code can translate a bus enumeration
> to an actual major , minor device.
No, it knows nothing about special files, nor s
On Wed, 18 Aug 1999, Matthew Dillon wrote:
> Remember that at least for the Yamaha you can set the speed to 6 if
> you are burning CD-R's. 4 is the max for CD-RW's.
When I last used cdrecord (on Solaris) I remember finding that if I tried
to write with a speed that was too high for the
Matthew Dillon wrote:
>
> :Hate to ask, do we support CD-RW?
>
> Yup! In fact, I recommend that you get a 5-pack of CD-RW disks
> so you don't turn your CD-R's into scrap while playing with the
> unit.
Scrap? HA!
http://students.seattleu.edu/hodeleri/Images/CDs.gif
--
Eric Hodel
On 19 Aug, Matthew Dillon wrote:
> It should be noted that the 'cdrecord' program implements a FIFO itself,
> and you can specify the size. The default is 2MB. cdrecord uses a
man cdrecord (v1.8a2?):
---snip---
The default fifo size is currently 4 MB.
---snip---
Bye,
Alex
Please Matt "burn" a summary document ... (Gosh I have been
burning too many CDs 8) )
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
: Another possibility, if you have the RAM, is to use the team(1)
:program (it's in the ports) to buffer the data as it goes to the burner.
:You basically put it into the pipeline between mkisofs and cdrecord, and
:it buffers up to 5MB in memory (default, adjustable). Of course, you've
:got t
Matthew Dillon <[EMAIL PROTECTED]> wrote:
> Finally, when you pipe mkisofs to cdrecord directly it is possible to
> fall behind enough that an error may occur. The CD writer needs a
> continuous stream. There are two solution to this if it occurs: First,
> write at a slower rat
As Bruce Albrecht wrote ...
> Matthew Dillon writes:
> > And to head off another question: When you are recording to a CD-RW
> > you can do a 'quick erase' of the media using 'cdrecord blank=fast'.
> > This does not actually erase the data, so if you have used say 100MB
> > you will only have
> > This does not actually erase the data, so if you have used say 100MB
> > you will only have 550MB left. You can actually erase the media using
> > 'cdrecord blank=all', which takes a while.
> In my experience, this is not true. I have used blank=fast on a CDRW
> that has over 500 MB written,
>
> : > you can do a 'quick erase' of the media using 'cdrecord blank=fast'.
> : > This does not actually erase the data, so if you have used say 100MB
> : > you will only have 550MB left. You can actually erase the media using
> : > 'cdrecord blank=all', which takes a while.
> :
> :In my experi
: > you can do a 'quick erase' of the media using 'cdrecord blank=fast'.
: > This does not actually erase the data, so if you have used say 100MB
: > you will only have 550MB left. You can actually erase the media using
: > 'cdrecord blank=all', which takes a while.
:
:In my experience, this is
> Matthew Dillon writes:
> > And to head off another question: When you are recording to a CD-RW
> > you can do a 'quick erase' of the media using 'cdrecord blank=fast'.
> > This does not actually erase the data, so if you have used say 100MB
> > you will only have 550MB left. You can actual
Matthew Dillon writes:
> And to head off another question: When you are recording to a CD-RW
> you can do a 'quick erase' of the media using 'cdrecord blank=fast'.
> This does not actually erase the data, so if you have used say 100MB
> you will only have 550MB left. You can actually erase t
> Yah, or if you don't want to create yet another environment variable
> you can stick those in the /etc/default/cdrecord file (note: the
> directory is 'default' not 'defaults').
If that is truely the case we need to send-pr it -- ports are *not*
allowed to have application-specific
< said:
> Or if there is a system call or modification to open such that I can issue :
> open("pci0:10:0", .)
Don't be silly.
> On the kernel side, I hope that the pci code can translate a bus enumeration
> to an actual major , minor device.
No, it knows nothing about special files, nor s
> Amancio Hasty wrote...
> > > There is a generic SCSI bus enumerator API, and one for PCI as well. There
> > > isn't a generic API to get trees of devices of any type in the system,
> > > though. With new-bus that might be possible, but having done two
> > > enumerator APIs already (I wrote the
Amancio Hasty wrote...
> > There is a generic SCSI bus enumerator API, and one for PCI as well. There
> > isn't a generic API to get trees of devices of any type in the system,
> > though. With new-bus that might be possible, but having done two
> > enumerator APIs already (I wrote the CAM and P
> Amancio Hasty wrote...
> > > Amancio Hasty wrote...
> > > > I have to agree with Matt on this plus the set of defaults is system wide .
> > >
> > > What are you agreeing with him on? Why not quote what you're talking
> > > about?
> > >
> > > > Is it possible to get a system bus enumeration fr
Amancio Hasty wrote...
> > Amancio Hasty wrote...
> > > I have to agree with Matt on this plus the set of defaults is system wide .
> >
> > What are you agreeing with him on? Why not quote what you're talking
> > about?
> >
> > > Is it possible to get a system bus enumeration from the system so
> Amancio Hasty wrote...
> > I have to agree with Matt on this plus the set of defaults is system wide .
>
> What are you agreeing with him on? Why not quote what you're talking
> about?
>
> > Is it possible to get a system bus enumeration from the system so
> > a program such a cdrecord can a
Amancio Hasty wrote...
> I have to agree with Matt on this plus the set of defaults is system wide .
What are you agreeing with him on? Why not quote what you're talking
about?
> Is it possible to get a system bus enumeration from the system so
> a program such a cdrecord can attempt to make a
On Wed, 18 Aug 1999, Matthew Dillon wrote:
> Remember that at least for the Yamaha you can set the speed to 6 if
> you are burning CD-R's. 4 is the max for CD-RW's.
When I last used cdrecord (on Solaris) I remember finding that if I tried
to write with a speed that was too high for the
I have to agree with Matt on this plus the set of defaults is system wide .
Is it possible to get a system bus enumeration from the system so
a program such a cdrecord can attempt to make an intelligent
decision as to which device is the cd recorder for instance we
know that the system can prin
:
:And once you've found the right dev you can set CDR_DEVICE and CDR_SPEED
:in your shell environment. Saves you from typing it every five minutes.
:Like:
:
:CDR_DEVICE=0,1,0
:CDR_SPEED=4
Yah, or if you don't want to create yet another environment variable
you can stick those in the /etc
As Matthew Dillon wrote ...
> :The device is probably dev=0,1
>
> I'm sorry, I meant 1,0. Also 0,1,0 should work.
>
> Try:
>
> cdrecord dev=1,0 -inq
>
> You should get:
>
> Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling
> scsidev: '0,3,0'
>
> :The device is probably dev=0,1
>
> I'm sorry, I meant 1,0. Also 0,1,0 should work.
>
> Try:
>
> cdrecord dev=1,0 -inq
>
> You should get:
>
> Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling
> scsidev: '0,3,0'
> scsibus: 0 target: 3 lu
:The device is probably dev=0,1
I'm sorry, I meant 1,0. Also 0,1,0 should work.
Try:
cdrecord dev=1,0 -inq
You should get:
Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling
scsidev: '0,3,0'
scsibus: 0 target: 3 lun: 0
Devic
:Is me again 8)
:
:mkisofs -R /mount/dir | cdrecord -v fs=6m speed=2 -dev=0:1:0
:
:Okay, whats the magic device name to access the yamaha cd recorder .
:I have tried several combinations of names with no success.
:
:dmesg says that I have:
:
:cd0 at ahc0 bus 0 target 1 lun 0
:cd0: Removable CD-
Hi Guys
Is me again 8)
mkisofs -R /mount/dir | cdrecord -v fs=6m speed=2 -dev=0:1:0
Okay, whats the magic device name to access the yamaha cd recorder .
I have tried several combinations of names with no success.
dmesg says that I have:
cd0 at ahc0 bus 0 target 1 lun 0
cd0: Removable CD
Again a very good advice.
Got four CD-RW . Two came with the unit and I bought 2 HP CD-RW disks.
Plus got 5 CD-R . Those I will save much much later 8)
Tnks Again!
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current
:Hate to ask, do we support CD-RW?
Yup! In fact, I recommend that you get a 5-pack of CD-RW disks
so you don't turn your CD-R's into scrap while playing with the
unit.
-Matt
:And I will probably bug next the multimedia group;however,
:those
39 matches
Mail list logo
