On 21-Sep-01 Chiriki, Naidu (CAP, GCF) wrote:
> 'cdrecord dev=0,0,0 *' . The files include
> some tar files and gz files.
this would be ok for audio files (*.wav) but definitely not for data files.
> I have faced three problems with it.
> 1. I am not able to use the burned CD in normal PC CDROM. I am able to see
> the contents and copy them. I get CE errors while opening the tar files and
> gz files. Where as if I mount the CDROM on the same Redhat, I am able to
> see
> the files and use them also. I read in it in cdrecord man page that it
> cannot be used on non CD RW drives. Is it true? or is there any
> alternative.
> This is one of my requirement to read the CD in other PCs.
I have no idea why you can mount a CD like that.
What you will have to do is creating a ISO9660 CD-Image containing all files
you want on the CD. In Linux/cdrtools mkisofs is the right program.
scenario:
All files you want to burn are in ~/somewhere/burn
cd ~/somewhere
mkisofs -v -r -J -o ~/Image.img burn
-v : verbose, tells you whats happening, status reports, etc.
-r : rock ridge extension, i.e. long file names and user
ownership/accessrights conserved, but read access allowed for
everybody (-R would keep access right exactly)
WinXX will not understand tha extension and show kripled short file names
-J : win joliet extension so win can also see the long file names
-o filename : the outputfile where to write everything. In principle it's
possible to do this "on the fly" without an image, but lets stick to
the basics first.
With -o ~/Image.img your home directory should have lots of free disc
space.
burn is the directory containing all files (and dirs).
On the finished CD the directory burn will not show up anymore.
This will take some time
Now burn it:
cdrecord -v -data ~/Image.img
-v : verbose, tells how far cdrecord got already
-data : not really necessary, just makes sure that it will really be a data
CD and nothing else
This will take some time too.
After that the CD is a valid ISO9660 CDROM.
For all the rest please read manpages of mkisofs, cdrecord and the README
files (especially README.multi if you want to burn several times to the same
CD, each time adding new files.) coming with the cdrtools package.
> 2. If I use mkisofs like 'mkisofs -R -o cdimage.raw *', and later mount
> them
> using 'mount cdimage.raw -r -t iso9660 -o loop /mnt', I get all the files
> in
> all sub dirs listed in one place. I can't see my directory structure. I
> read
> the man pages of cdrecord or mkisofs and it was mentioned about it. But is
> there any way out for this?
>
Hmm.. seems yxou tried that already. But I never had that effect you describe.
Hmm.... You will have files and directories in ./ ?
Then mkisofs will strip the highest directory name off. just go one level
higher and tell mkisofs instead of * the directory name where all the files
are. There was some discussion on how to handle this in a nice way if you
specify files and directories at the same time but it seems the default
behaviour is (still ?) used on your version.
> 3. Is there any possibility to blank out a CDROM after writing it or can
> use
> it for read/write like Direct CD software in PCs can provide this facility.
> There I can use a CDR like a floppy, but only in CD RW drives. If I wanted
> to use it in non CD RW drives, I close the CD and there after I can't write
> on to it. Is there any tool like this in Redhat?
there is a (very?) experimental packet writing in cdrecord. Seems nobody is
using it.
As man cdrecord will tell you you can blank CD-RW, obviously no CD-R can be
blanked for repeated writing. Blanking for erasing incriminating data is
quite easy in microwave ovens...... Don't switch on too long so.
K.-H.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
