Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!mcsun!ieunet!dec4ie.ieunet.ie!jkh From: jkh@whisker.lotus.ie (Jordan K. Hubbard) Subject: Re: My experience with the upgrade to patchkit-0.2.2 In-Reply-To: jms@cs.ufh.ac.za's message of Thu, 25 Mar 1993 10: 05:19 GMT Message-ID: <JKH.93Mar27011054@whisker.lotus.ie> Sender: usenet@ieunet.ie (USENET News System) Nntp-Posting-Host: whisker.lotus.ie Organization: Lotus Development Ireland References: <jms.43.733053919@cs.ufh.ac.za> Date: Sat, 27 Mar 1993 01:10:54 GMT Lines: 23 This is very very strange! I've cleaned, reloaded and patched my system to 0.2.2 *several times* now without any of these problems! What's more, I just installed a 386 system this morning for the first time (I.E. formatted new disk, loaded agate.berkeley.edu copy of 0.1) and patched it up to 0.2.2 without a single problem. Are you _sure_ you're starting from a vanilla 0.1 distibution and not some back-up tape potentially made *after* another, earlier version of the patchkit had been applied? Don't forget - you have to unpack bin*, etc* AND src* from the distribution to be absolutely sure.. I had one new installation fail on me in the patch phase, only to find that the problem actually was that the unpack of src* had failed with a 'too many files open' error before I tried to apply the patchkit. Jordan -- Jordan Hubbard Lotus Development Ireland jkh@whisker.lotus.ie 386bsd Patchkit Coordinator All-around nice dude. I do not speak for Lotus as that's not in my job description.