Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA5141 ; Tue, 22 Dec 92 04:01:20 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!uunet!sci34hub!gary From: gary@sci34hub.sci.com (Gary Heston) Subject: Re: 386BSD install program - where is it? Message-ID: <1992Dec18.163842.29110@sci34hub.sci.com> Reply-To: gary@sci34hub.sci.com (Gary Heston) Organization: SCI Systems, Inc., Huntsville, Al. References: <1992Dec15.144659.14169@wotan.compaq.com> <1faO02kg2fC=01@JUTS.ccc.amdahl.com> <1992Dec17.134832.9812@moxie.hou.tx.us> Date: Fri, 18 Dec 1992 16:38:42 GMT Lines: 28 In article <1992Dec17.134832.9812@moxie.hou.tx.us> hackney@moxie.hou.tx.us (Greg Hackney) writes: >gab10@griffincd.amdahl.com (Gary A Browning) writes: [ someone ask ] >>> Where is the source code located for the 'install' program that's on >>> the >>> 386BSD dist.fs floppy? >>The source for it was never released. >I wonder why? It sure would be nice to have to make a customized >installation process! It would be particularly useful when running into install problems, as I did last week when playing with my new RLL card. Wierdly enough, the size of the drive affected whether or not INSTALL would work... It locked up on the larger drive (Micropolis 1325, about 100M RLL) but worked OK on the smaller (Qume 540, ~48MB RLL). Having source, or an install script instead of executable, would have made life easier. (Yes, I did finally get the larger drive booting, but most of the /dev entries were missing, and some directories and permissions were missing. And rogue still fails to update the score file. :-) ) -- Gary Heston SCI Systems, Inc. gary@sci34hub.sci.com site admin The Chairman of the Board and the CFO speak for SCI. I'm neither. "Data sheet: HSN-3000 Nuclear Event Detector. The [NED] senses the gamma radiation pulse [from a] nuclear weapon." As if we wouldn't notice...