how can I burn a *.rr image?
Carlos M. Buj Ribas
I recently downloaded the software_companion_sparc.rr.bz2 (software
companion cd for salaris 9 sparc). After unzipping the bz2 file I was
supposed to have an iso image file, burn it and ready. But after
unzipping the file I have an .rr file ( software_companion_sparc.rr ).
How can I burn this file? is it already a cd image file?
I would burn it using cdrecord.
Thanks,
Carlos
Simon Barner
What does
% file software_companion_sparc.rr
say?
Simon
Dave Uhring
> What does
>
> % file software_companion_sparc.rr
>
> say?
Probably "data", but it is an ISO image. Just burn it as one.
Joerg Schilling
Carlos M. Buj Ribas <carl...@olibu.com> wrote:
>Hi all,
>
>I recently downloaded the software_companion_sparc.rr.bz2 (software
>companion cd for salaris 9 sparc). After unzipping the bz2 file I was
>supposed to have an iso image file, burn it and ready. But after
>unzipping the file I have an .rr file ( software_companion_sparc.rr ).
>How can I burn this file? is it already a cd image file?
Just call isoinfo -i image -d
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schi...@fokus.fraunhofer.de (work) chars I am J"org Schilling
URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Steve O'Hara-Smith
"Carlos M. Buj Ribas" <carl...@olibu.com> wrote:
> Hi all,
>
> I recently downloaded the software_companion_sparc.rr.bz2 (software
> companion cd for salaris 9 sparc). After unzipping the bz2 file I was
> supposed to have an iso image file, burn it and ready. But after
The rr probably stands for Rockridge, which is a common ISO9660
extension. Try this:
vnconfig /dev/vn0c software_companion_sparc.rr
mount -t CD9660 /dev/vn0c /mnt
ls /mnt
If all is well
umount /mnt
vnconfig -d /dev/vn0c
Then burn like any other ISO.
--
C:>WIN | Solar Thermal Systems
The computer obeys and wins. | http://www.soleire.com/
You lose and Bill collects. | Directable Mirror Arrays
| http://www.sohara.org/
UNIX admin
> mount -t CD9660 /dev/vn0c /mnt
> ls /mnt
>
> If all is well
>
> umount /mnt
> vnconfig -d /dev/vn0c
What is "vnconfig"??? Where does that come from???
Dave Uhring
FreeBSD. Look at the cross-posted NGs. It is their version of lofiadm.
Michael
I dunno, but with linux and freebsd you can mount as a loop device and
read an iso. mount -o loop. Perhaps the vnconfig is an intermediate
step, as solaris does not support loop devices with a mount switch.
<hiding from linux haters>
Michael
Casper H.S. Dik
>UNIX admin wrote:
Solaris would use "lofiadm" the driver which converts files to
block devices which can then be mounted.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
Toomas Soome
man lofiadm
toomas
--
Hildebrant's Principle:
If you don't know where you are going,
any road will get you there.
John Gardner
Cheers
John G
In message <jAgGc.1354633"Carlos M. Buj Ribas"
<carl...@olibu.com>6.54...@telenews.teleline.es>, "Carlos M. Buj Ribas"
Bill Vermillion
man vnconfig would have given you all the information you needed
to know.
vnconfig manipulates vnodes disks - and vnodes are what is used
in FreeBSD. If you look at the entries in /dev you will find
that all devices are character type devices and there are no block
devices.
--
Bill Vermillion - bv @ wjv . com
Bill Vermillion
Casper H.S. Dik <Caspe...@Sun.COM> wrote:
>Michael <no...@none.com> writes:
>
>>UNIX admin wrote:
>
>>>>vnconfig /dev/vn0c software_companion_sparc.rr
>>>>mount -t CD9660 /dev/vn0c /mnt
>>>>ls /mnt
>>>>
>>>>If all is well
>>>>
>>>>umount /mnt
>>>>vnconfig -d /dev/vn0c
>>>
>>>
>>> What is "vnconfig"??? Where does that come from???
>
>>I dunno, but with linux and freebsd you can mount as a loop device and
>>read an iso. mount -o loop. Perhaps the vnconfig is an intermediate
>>step, as solaris does not support loop devices with a mount switch.
>
>
>Solaris would use "lofiadm" the driver which converts files to
>block devices which can then be mounted.
FreeBSD does not have block devices.
Joerg Schilling
>In article <jFMGc.10781$yy1....@newsread2.news.atl.earthlink.net>,
>man vnconfig would have given you all the information you needed
>to know.
Sure?
man vnconfig
Kein Eintrag im Online-Handbuch für vnconfig.
Well this is definitely not available on Solaris. Note that the OP
was interested to burn a Solaris CD image.
Dragan Cvetkovic
> In article <I0Hn0...@wjv.com>, Bill Vermillion <b...@wjv.com> wrote:
>>In article <jFMGc.10781$yy1....@newsread2.news.atl.earthlink.net>,
>
>>man vnconfig would have given you all the information you needed
>>to know.
>
> Sure?
>
> man vnconfig
> Kein Eintrag im Online-Handbuch für vnconfig.
>
>
> Well this is definitely not available on Solaris. Note that the OP
> was interested to burn a Solaris CD image.
>
But not necessarily on Solaris. His User-Agent (Mozilla/5.0 (X11; U;
FreeBSD i386; en-US; rv:1.6) and cross-posting to comp.unix.bsd.freebsd.misc
give a rather strong suspicion that he wanted to do so on a FreeBSD
machine.
Bye, Dragan
--
Dragan Cvetkovic,
To be or not to be is true. G. Boole No it isn't. L. E. J. Brouwer
!!! Sender/From address is bogus. Use reply-to one !!!
Bill Vermillion
Joerg Schilling <j...@cs.tu-berlin.de> wrote:
>In article <I0Hn0...@wjv.com>, Bill Vermillion <b...@wjv.com> wrote:
>>In article <jFMGc.10781$yy1....@newsread2.news.atl.earthlink.net>,
>
>>man vnconfig would have given you all the information you needed
>>to know.
>
>Sure?
>
>man vnconfig
>Kein Eintrag im Online-Handbuch für vnconfig.
>
>Well this is definitely not available on Solaris. Note that the OP
>was interested to burn a Solaris CD image.
I didn't notice this was crossposted to a Solaris group, as all I
read is the freebsd.misc group.
Sorry.
Bill
UNIX admin
> to know.
No it wouldn't, because there is no `vnconfig` on Solaris! `man vnconfig`
was the first thing I did when I read that.
At any rate, on Solaris we use `lofiadm` to create mountable loopback
devices.
> vnconfig manipulates vnodes disks - and vnodes are what is used
> in FreeBSD. If you look at the entries in /dev you will find
> that all devices are character type devices and there are no block
> devices.
I would love to look at entries at /dev on FreeBSD, except that the install
keeps freezing on me at random (regardless of which source I try to install
from).
jpd
On 2004-07-08, UNIX admin <tripi...@hotmail.com> wrote:
> I would love to look at entries at /dev on FreeBSD, except that the install
> keeps freezing on me at random (regardless of which source I try to install
> from).
Hanging at random places sounds like hardware faillure to me. Despite
whatever other OSen you run on it that do work without a hitch. Note
that memory usage patterns differ from OS to OS; so if you have a bad
spot in your memory you may run into it in different ways depending on
OS. ECC can change the picture even further.
Alternatively, turn off things like APM and ACPI (both in the bios and
for the booting kernel, see handbook), fiddle with PnPOS settings, etc.
--
j p d (at) d s b (dot) t u d e l f t (dot) n l .
Eric Enright
>I would love to look at entries at /dev on FreeBSD, except that the install
>keeps freezing on me at random (regardless of which source I try to install
>from).
Maybe not so helpful, but a relevant story.
A while ago a friend of mine and I tried everything we could to
get FreeBSD (5.2.1, maybe .2 IIRC) to install on his notebook (a
Toshiba A10). We experienced issues with kernel boot similar to
yours, and we tried fiddling with ACPI and the APIC, boot options,
etc to no avail.
Turns out, there was some very obscure problem with his
particular notebook in the BIOS that FreeBSD just didn't like.
Linux worked fine, but wouldn't pick up his PCMCIA controller,
which is what eventually led to the motherboard being replaced
(and FreeBSD then working). We discovered the problem by
swapping his drive into someone else's identical notebook model,
where things went smoothly.
--
Eric Enright /"\
ericAtiptsoftDcom \ / ASCII Ribbon Campaign
X Against HTML E-Mail
Public Key: 0xBEDF636F / \
Steve O'Hara-Smith
"UNIX admin" <tripi...@hotmail.com> wrote:
> > man vnconfig would have given you all the information you needed
> > to know.
>
> No it wouldn't, because there is no `vnconfig` on Solaris! `man vnconfig`
> was the first thing I did when I read that.
Well I did rather assume that the OP was trying to burn a copy
of the solaris image he had on a FreeBSD box - that's the only reason
I could think of for this question appearing in c.u.b.f.m.
Michael
> Well I did rather assume that the OP was trying to burn a copy
> of the solaris image he had on a FreeBSD box - that's the only reason
> I could think of for this question appearing in c.u.b.f.m.
A very logical conclusion. If he was so familiar with solaris he would
have known the rr extension.
cdrtools AFAIK can burn non-ISO9660 images e.g. BeOS Max 3 and others.
It's not dependent on ISO9660 like some windows tools. And AFAIK needs
no cue files like Nero. but if rr = ISO9660, then all the better.
that said i've had trouble booting images that were not ISO9660. i'm
not sure if this is due to my CDROM or my own naivete.
michael
Steve O'Hara-Smith
Michael <no...@none.com> wrote:
> cdrtools AFAIK can burn non-ISO9660 images e.g. BeOS Max 3 and others.
Yep cdrecord (and burncd for that matter) can burn arbitrary content
to a CD as data, I've used this feature to burn chunked dumps to CDs - for
the grubby details see the cdrw_bup.pl and cdrw_res.pl scripts lurking
on ftp.sohara.org.