joe@oregon.uoregon.edu (Joe St Sauver) (09/29/89)
I recently had occaision to try doing a BuildDisk on an OD from a NeXT with a 330 Meg (that is now running 1.0) Near what (should have been) the end of the BuildDisk, I began to get obnoxious "Disk Full" errors and ended up after 3+ hours of work with an unbootable disk. I assume that this phenomena is related to the fact that some days back I built Common Lisp and TeX on the 330. My question to you all is this, "Is there a way to build a bootable OD without having to go in and manually trim/compress my 330?" At the risk of starting the fires a-burning again, I really have to believe that it would have been a nice gesture on NeXT's part to either (a) warn the user that DiskBuild can't run from a given configuration due to the current size of the files which would be copied to the OD, or (b) ask the user what directories he'd like to omit, or (c) copy the stuff that absolutely has to be present to be bootable first, and copy the Digital Librarian literature files and some of the other non-essential stuff last on a space-available basis. The current wait-three-hours-and-get-slapped-in-the-face approach is *HIGHLY* frustrating. Anyhow, suggestions for working around this baby would be appreciated. Joe St Sauver (JOE@OREGON.UOREGON.EDU or JOE@OREGON) Statistical Programmer and Consultant University of Oregon Computing Center