cdrecord and iso
bigbinc
.iso file which is big. But what do I do with it after that. How do I make
sure that cdrecord will turn it into a normal cd like from the store
package.
Is there a flag I need. What will the burnt cd end up with. One .iso file
or a set of other files like normal?
Berlin Brown
big...@hotmail.com
Bit Twister
> I am planning on downloading an iso file from redhat.
> I know I need the
> .iso file which is big. But what do I do with it after that.
download the ascii file with the md5sums also. Then
you can do a md5sum --check md5sums_file_here
to verify your download was a success.
> How do I make
> sure that cdrecord will turn it into a normal cd like from the store
> package.
cannot help there. I use a gui front end /usr/bin/gcombust
> Is there a flag I need. What will the burnt cd end up with. One .iso file
> or a set of other files like normal?
set of files like you find in /
Grant Edwards
> I am planning on downloading an iso file from redhat. I know
> I need the .iso file which is big. But what do I do with it
> after that.
Burn it!
> How do I make sure that cdrecord will turn it into a normal cd
> like from the store package.
Is there different way? :) [Yes, but it's difficult.]
First, do
# cdrecord --scanbus
to figure out what the device numbers are for your burner.
Then do someting like this:
# cdrecord -v dev=1,2,3 speed=8 valhalla-disk1.iso
[put in the proper device numbers, speed, and filename]
The -v will tell cdrecord to print out nice progress messages.
> Is there a flag I need.
No. The default for cdrecord is to do the right thing.
> What will the burnt cd end up with. One .iso file or a set of
> other files like normal?
The latter.
--
Grant Edwards grante Yow! I'm continually
at AMAZED at th'breathtaking
visi.com effects of WIND EROSION!!
Matt Greer
cdrecord treats iso images correctly by default. Just something like
cdrecord -v speed=8 dev=0,0,0 -data image.iso
will do it.
You can also mount the iso as a filesystem and browse through it just as an
added assurance it downloaded correctly
mount -t iso9660 -o ro,loop=/dev/loop0 image.iso /place/it/will/be/mounted
Matt
Joost Kremers
cdrecord -v speed=X dev=X,Y,Z image.iso
this will work just fine. all the info is in `man cdrecord' (there's
an EXAMPLES section that i found very helpful) and in the CD-Writing
HOWTO at <http://www.tldp.org>.
HTH
--
Joost Kremers http://baserv.uci.kun.nl/~jkremers
Ask 8 slackers how to do something, get 10 answers.
-- sl in alt.os.linux.slackware
Terence Parker
attempt to write the CD if there are going to be harddisc intensive cron
jobs running in the background (including those that are scheduled to run a
few minutes after bootup because of having missed an earlier cron job with
your machine turned off). That's if you don't have a burn proof CD-R
drive.... I've managed to wreck several CDs that way and it's very annoying.
Terence
Grant Edwards
> Well seems you have the instructions already. Just make sure
> you don't attempt to write the CD if there are going to be
> harddisc intensive cron jobs running in the background
> (including those that are scheduled to run a few minutes after
> bootup because of having missed an earlier cron job with your
> machine turned off). That's if you don't have a burn proof CD-R
> drive.... I've managed to wreck several CDs that way and it's
> very annoying.
I've never had any problems due to other disk I/O. I often run
mkisofs and pipe the output into cdrecord. That pretty much
guarantees that there's going to be heavy disk I/O going on
during the burn. (This is on a 400MHz and 450MHz K6 systems)
Of course I never put my CD-burner on the same IDE or SCSI bus
as my hard drive, so that probably helps.
--
Grant Edwards grante Yow! Put FIVE DOZEN red
at GIRDLES in each CIRCULAR
visi.com OPENING!!
bigbinc
distribution to download. I have mandrake and redhat 7.1 on purchased disk.
This will be my first download. Just got dsl. I am thinking suse, but I
heard there are a lot of cds to get. shrug.
Berlin Brown
big...@hotmail.com
"bigbinc" <big...@hotmail.com> wrote in message
news:y08U8.18280$wj4.1...@e3500-atl2.usenetserver.com...
Grant Edwards
> Thanks for the help, the next step, I actually have to decide which
> distribution to download. I have mandrake and redhat 7.1 on purchased disk.
> This will be my first download. Just got dsl. I am thinking suse, but I
> heard there are a lot of cds to get. shrug.
I wasn't aware that Suse ISO's were available. Where did you
find them?
--
Grant Edwards grante Yow! Boy, am I glad it's
at only 1971...
visi.com
bigbinc
"Grant Edwards" <gra...@visi.com> wrote in message
news:YHoU8.3468$eH2.3...@ruti.visi.com...
swe...@kickapoo.com
> . . .
>I never put my CD-burner on the same IDE or SCSI bus
> as my hard drive, so that probably helps.
Interesting, but why? The implication always seems to be to put the
cdr as close to the hd as possible, or has this been my presumption
all along.
I have these choices on an all-IDE box:
1. Use Sony crx-145e that is presently IDE slave.
2. Add PCI scsi board (AHA2920)- actually a 'Future Domain'
board- and add
Philips 2600 scsi cdr.
3. Add ISA scsi board (Trantor) and use the Philips 2600 cdr.
#3 would be simple to do and should provide the speed I need, which is
speed=2 (not very fast).
Then on my scsi box I could use the IDE Sony 145e cdr.
A nice overall, but non-intuitive solution. Make any sense?
TIA,
--
sp
--
>
> --
> Grant Edwards grante Yow! Put FIVE DOZEN red
> at GIRDLES in each CIRCULAR
> visi.com OPENING!!
The unlived life is not worth examining.
Lew Pitcher
> gra...@visi.com (Grant Edwards) wrote:
>
>> . . .
>>I never put my CD-burner on the same IDE or SCSI bus
>> as my hard drive, so that probably helps.
>
>Interesting, but why?
For IDE, the IDE bus doesn't support simultaneous execution of commands to
two different devices. So, a read (say) to the HD can block a write to the
CD burner, if both are on the same IDE bus. This may cause the CD burner to
timeout on it's write (buffer underrun or some such) and burn a coaster for
you.
As for real SCSI (as opposed to IDE-SCSI), I don't believe that it has the
same problem. Perhaps the OP will elucidate for us.
>The implication always seems to be to put the
>cdr as close to the hd as possible, or has this been my presumption
>all along.
[snip]
Lew Pitcher, Information Technology Consultant, Toronto Dominion Bank Financial Group
(Lew_P...@td.com)
(Opinions expressed are my own, not my employer's.)
Grant Edwards
>> . . .
>>I never put my CD-burner on the same IDE or SCSI bus
>> as my hard drive, so that probably helps.
>
> Interesting, but why?
If they're on different IDE busses then the CD burner can be
written to at the same time the hard drive is being accessed.
IDE is an ultra-crappy design kludge and doesn't support
multple pending operations. If you put the two on the same IDE
bus, then the CD drive can't be written to if the hard drive is
being read/written (and vice versa). SCSI is a far, far better
design, since it supports multiple overlaped operations (but it
always helps to distribute I/O load as evenly as possible).
> The implication always seems to be to put the cdr as close to
> the hd as possible,
I didn't mean to imply that. The data has to be read from the
hard drive into RAM then written from RAM to the CD burner. If
both are on the same IDE bus these two operations can't
overlap. If they're on different IDE busses then the
operations can overlap (assuming your IDE chipset isn't too
broken). Distance doesn't really make any difference.
> or has this been my presumption all along.
>
> I have these choices on an all-IDE box:
>
> 1. Use Sony crx-145e that is presently IDE slave.
Most motherboards have two IDE busses (all of the ones I've
ever seen). If you're having problems you could try moving the
CD drive to the other IDE bus.
> 2. Add PCI scsi board (AHA2920)- actually a 'Future Domain'
> board- and add Philips 2600 scsi cdr.
>
> 3. Add ISA scsi board (Trantor) and use the Philips 2600 cdr.
>
> #3 would be simple to do and should provide the speed I need, which is
> speed=2 (not very fast).
>
> Then on my scsi box I could use the IDE Sony 145e cdr.
--
Grant Edwards grante Yow! One FISHWICH coming
at up!!
visi.com
Nico Kadel-Garcia
<swe...@kickapoo.com> wrote in message news:ag4943$4im$0...@198.69.29.144...
> gra...@visi.com (Grant Edwards) wrote:
>
> > . . .
> >I never put my CD-burner on the same IDE or SCSI bus
> > as my hard drive, so that probably helps.
>
> Interesting, but why? The implication always seems to be to put the
> cdr as close to the hd as possible, or has this been my presumption
> all along.
That's a manufacturer's policy, to leave all the open bays together and use
the shortest possible cables. But most of them put the IDE hard drive on one
controller, and the IDE CD drive on the other controller.
> I have these choices on an all-IDE box:
>
> 1. Use Sony crx-145e that is presently IDE slave.
Cheap, and CD-RW drives are working fine via IDE. The big limitation is
writing speed, not bus bandwidth.
> 2. Add PCI scsi board (AHA2920)- actually a 'Future Domain'
> board- and add
> Philips 2600 scsi cdr.
It would *work, but waste money unless you have some compelling reason to
use SCSI, such as an external set of drives.
> 3. Add ISA scsi board (Trantor) and use the Philips 2600 cdr.
>
> #3 would be simple to do and should provide the speed I need, which is
> speed=2 (not very fast).
See above.
> Then on my scsi box I could use the IDE Sony 145e cdr.
>
> A nice overall, but non-intuitive solution. Make any sense?
> TIA,
> --
> sp
Very wasteful: for a 2x drive, you could use an external USB 1.1 CD-RW drive
and still avoid buffer under-runs.
If you're going to spend money, get a decent USB 2.0 external drive that you
can swap around or loan to others.