Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!crdgw1!sixhub!davidsen From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr) Newsgroups: comp.unix.i386 Subject: Re: How to make a disaster boot floppy? Message-ID: <1037@sixhub.UUCP> Date: 27 May 90 03:41:15 GMT References: <9005202304.aa13994@PARIS.ICS.UCI.EDU> <187@touch.touch.com> <1990May25.120501.26091@ddsw1.MCS.COM> Reply-To: davidsen@sixhub.UUCP (bill davidsen) Organization: *IX Public Access UNIX, Schenectady NY Lines: 24 In article <1990May25.120501.26091@ddsw1.MCS.COM> nvk@ddsw1.MCS.COM (Norman Kohn) writes: | After having tried under uport 386 the solution of making a new | unix kernel on the floppy that reads the tape, I settled on | the following scheme. Its advantage is that disaster recovery | is simple, the "supplement" disk is readily updated, and | you don't need to keep multiple flavors of boot floppy around | (when the vendor upgrades the os, there's minimal extra work) You describe a method by wich you can reload, but my interpretation of the original request was for something useful to recover... I have a bootable floppy with tape configured, and it has all of the utilities I can possibly fit on one disk. Since most of my systems have a 2nd disk, I have a directory stub called bin2 to hold the mounted 2nd disk of goodies, and on systems which allow it a RAM disk to make the really frequently needed things (df, fsck, ls, etc) available quickly. What you describe is useful (I archived the posting) but not what I think of as a disaster floppy. -- bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen) sysop *IX BBS and Public Access UNIX moderator of comp.binaries.ibm.pc and 80386 mailing list "Stupidity, like virtue, is its own reward" -me