From owner-freebsd-hackers Wed Aug 13 21:49:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA22572 for hackers-outgoing; Wed, 13 Aug 1997 21:49:29 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA22566 for ; Wed, 13 Aug 1997 21:49:27 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id VAA00406; Wed, 13 Aug 1997 21:49:21 -0700 (PDT) To: rdkeys@csemail.cropsci.ncsu.edu cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! In-reply-to: Your message of "Wed, 13 Aug 1997 22:34:39 EDT." <9708140234.AA107103@csemail.cropsci.ncsu.edu> Date: Wed, 13 Aug 1997 21:49:21 -0700 Message-ID: <402.871534161@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is getting a bit rediculous, for sure. I'm sure having a hard time following your use of the english language below, that's for sure. Please use more care if you expect us to actually understand and respond to your bug reports. > The install crashed and refused to install anything after the initial > installation...... someone remarked ``the install bug''????? This doesn't tell me anything. > The system is up, but sysinstall will not install cvsup so I can update > the bloody beast! Even manual installs don't work. How do manual installs of cvsup fail? > The RELENG snap was nuked on freebsd.org, so I can't get a later sysinstall > or updated sources or...... etc....... grrrrrrrr! Are they down in one > of the other trees? If you'd read the documentation you'd see that current.freebsd.org has been offering up-to-date SNAPs for ages. > The two 3.0 snap installs went like clockwork. Everyone said go 2.2.2-RELEAS E, > so, like a fool, I took their advice........BAD BAD BAD. So go back to 3.0 SNAP? I really don't see the issue here. Something worked and so you abandoned it for something which didn't work and now you're flaming us in a manner which isn't even well-specified enough for us to know what the exact problem here is. I'm not forming a good impression of your abilities here. Jordan