From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam To: <9fans@cse.psu.edu> Subject: Re: [9fans] iso? In-Reply-To: <200302161722.h1GHM9M12724@augusta.math.psu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Date: Sun, 16 Feb 2003 12:38:16 -0500 Topicbox-Message-UUID: 6317099e-eacb-11e9-9e20-41e7f4b1d025 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. >