[9fans] iso?

[9fans] iso?

[Sam]

I'm looking at installing tex and having mounted
/n/sources I see it's a .iso.bz2.  What should
I do with the iso to get the sources mounted
at /sys/src/cmd/tex, or, how do most people handle
the isos?

Cheers,

Sam

Re: [9fans] iso?

[Dan Cross]

> I'm looking at installing tex and having mounted
> /n/sources I see it's a .iso.bz2.  What should
> I do with the iso to get the sources mounted
> at /sys/src/cmd/tex, or, how do most people handle
> the isos?

You've got to bunzip2 the compressed ISO image, mount it, and
install it using replica/pull.

term% bunzip2 < /n/sources/extra/tex.iso.bz2 > /someplace/big/tex.iso
term% 9660srv
term% mount /srv/9660 /n/dist /someplace/big/tex.iso

The install files will then be under /n/dist.  You probably need to
do something like run a script to touch the replica db and log files,
and then run pull.  There's usually a README file inside the ISO
that gives you exact instructions.

If you're installing into a KFS, you shouldn't have any problems.
If you're installing onto a fileserver, you'll need to modify the
replica configuration file.  That's the sort of thing I want
/dist/replica/site for to be included in replica config files
for.

	- Dan C.

Re: [9fans] iso?

[Sam]

I kinda figured this was the procedure.  Unzipping
it to mount it, install, and eventually remove the
iso just seemed like a waste.  Is there any reason
we bz2 the iso on sources?  Does the compression
level warrant losing the ability to mount
the iso directly from sources, or is that just a
fundamentally bad idea?

Sam

On Sun, 16 Feb 2003, Dan Cross wrote:

> > I'm looking at installing tex and having mounted
> > /n/sources I see it's a .iso.bz2.  What should
> > I do with the iso to get the sources mounted
> > at /sys/src/cmd/tex, or, how do most people handle
> > the isos?
>
> You've got to bunzip2 the compressed ISO image, mount it, and
> install it using replica/pull.
>
> term% bunzip2 < /n/sources/extra/tex.iso.bz2 > /someplace/big/tex.iso
> term% 9660srv
> term% mount /srv/9660 /n/dist /someplace/big/tex.iso
>
> The install files will then be under /n/dist.  You probably need to
> do something like run a script to touch the replica db and log files,
> and then run pull.  There's usually a README file inside the ISO
> that gives you exact instructions.
>
> If you're installing into a KFS, you shouldn't have any problems.
> If you're installing onto a fileserver, you'll need to modify the
> replica configuration file.  That's the sort of thing I want
> /dist/replica/site for to be included in replica config files
> for.
>
> 	- Dan C.
>

Re: [9fans] iso?

[Dan Cross]

> I kinda figured this was the procedure.  Unzipping
> it to mount it, install, and eventually remove the
> iso just seemed like a waste.  Is there any reason
> we bz2 the iso on sources?  Does the compression
> level warrant losing the ability to mount
> the iso directly from sources, or is that just a
> fundamentally bad idea?

I don't know; Russ can speak to that I'm sure.  Off the top of my head,
it does seem that without compression, the iso files would be really
too big to be managable (tex.iso is well over 100 MB, if I recall
correctly).  If people were mounting them directly off of sources, that
would also add a lot of traffic to sources (and the MH Internet link).
I don't know if that's the real reason though.

	- Dan C.

Re: [9fans] iso?

[Russ Cox]

The main reason they're bzipped is that they used
to be available only via the web page, and compression
is a no-brainer then.

Given the latency of most connections to sources,
my guess is that you get an enormous saving in time
by downloading it compressed and then dealing with
a local file system.  But maybe not.

In any case, there should be a script to do an install
for you.

Russ