Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!sei.cmu.edu!fs7.ece.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!ww0r+ From: ww0r+@andrew.cmu.edu (Walter Wong) Newsgroups: comp.unix.ultrix Subject: Re: CD-rom > TK50? Message-ID: Date: 9 Jun 91 00:15:20 GMT References: <1991Jun5.111537.1885@cl.cam.ac.uk> <91155.133326JIW2@psuvm.psu.edu>, <1991Jun6.161522.1430@hollie.rdg.dec.com> Organization: Humanities and Social Sciences, Carnegie Mellon, Pittsburgh, PA Lines: 24 In-Reply-To: <1991Jun6.161522.1430@hollie.rdg.dec.com> urban@ianet.enet.dec.com (Rob Urban) writes: > You are correct that all you need is the "bootstrap" file (called > the "miniroot" around DEC, I think). This is a special boot+kernel > file that runs standalone (including memdisk). On our distribution of Ultrix 4.2 (RISC), this file was included in the ROOT dump. You can extract it by typing in "restore xvf ROOT vmunix.sas" On a side note, in our environment, it would be very nice if we chould change install.1 such that another menu item choice is presented. In order to do this, we need to be able to modify the install.1 shell script in vmunix.sas. This basically involves gnu-emacs'ing the boot kernel (kinda icky, huh?). It would be really nice if DEC either pulled over install.1 from the server (in the network installation case), or provided instructions on how to build your own vmunix.sas (specifically, just how do I stuff a recognizable filesystem into this kernel?) Walter ----- internet:Walter.Wong@andrew.cmu.edu bitnet:r746ww0r@cmccvb