From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 06:30:34 2004 Return-Path: Delivered-To: freebsd-current@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75F4716A4CE for ; Sat, 11 Dec 2004 06:30:34 +0000 (GMT) Received: from area51.capnet.state.tx.us (area51.capnet.state.tx.us [141.198.193.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2909C43D1F for ; Sat, 11 Dec 2004 06:30:34 +0000 (GMT) (envelope-from trorki@area51.capnet.state.tx.us) Received: from area51.capnet.state.tx.us (localhost.capnet.state.tx.us [127.0.0.1])iBB6SEHY037606; Sat, 11 Dec 2004 00:28:14 -0600 (CST) (envelope-from trorki@area51.capnet.state.tx.us) Received: from localhost (stu@localhost)iBB6SEeA037603; Sat, 11 Dec 2004 00:28:14 -0600 (CST) X-Authentication-Warning: area51.capnet.state.tx.us: stu owned process doing -bs Date: Sat, 11 Dec 2004 00:28:14 -0600 (CST) From: trorki@area51.capnet.state.tx.us X-X-Sender: stu@area51.capnet.state.tx.us To: Kris Kennaway In-Reply-To: <20041210205951.GA54091@xor.obsecurity.org> Message-ID: <20041210235009.O37514@area51.capnet.state.tx.us> References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041208180601.T29045@area51.capnet.state.tx.us> <20041210205951.GA54091@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@www.freebsd.org cc: trorki@area51.capnet.state.tx.us Subject: AMD64 -current ISOs and cvsup repository: Was: Re: -current ISOs and update cvsup sites for AMD64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: trorki@area51.capnet.state.tx.us List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 06:30:34 -0000 On Fri, 10 Dec 2004, Kris Kennaway wrote: > On Fri, Dec 10, 2004 at 10:50:11AM -0600, trorki@area51.capnet.state.tx.us > > I've looked at snapshots.jp.freebsd.org and snapshots.se.freebsd.org > > and can't find a recent snapshot ISO to get -current for AMD64. > > Am I missing the directory, or what? Someone please let me know where > > to get a recent ISO > The above site; talk to the admins about why they're not being > produced (probably it's just an oversight). The last AMD64 -current ISO on snapshots.se and snapshots.jp was in October, if I'm looking at the right directories. A month and a half is hardly an "oversight", since October isn't even in the 6.0 timeframe. Maybe terminology has changed since summer, but all the -current sources peter out at the end of October, and no 6.0 build seems to have ever worked on snapshots.se, to judge from the log files. I'd like some help with AMD64 -current, yes AMD64 6.0-current. Am I making this clear??? I haven't played with -current since before the switch to 6.0 as -current, so the last ISO I used (and still have) is a 5.x-current from July. I want a clean AMD64 6.0-current ISO to start with, and that would presumedly be AFTER November 05, preferably very recent... > >, and where I should point cvsup for the updates. > Updates to what? amd64 isn't different from the other architectures; > you can read the documentation on using and configuring cvsup in the > handbook, and if you have further specific questions then ask them > then. The information isn't IN the handbook, or is obscure. If it was there to read, I wouldn't have asked the list. Duh. Since I mentioned cvsup you might/maybe get the idea that I know how to use it. Duh. Since I can't find the snapshots where they are expected, they might be somewhere else, and I'd probably need to cvsup from somewhere else, too, which is why I asked. Duh. Would somebody that actually uses -current on AMD64 tell me how to get a recent ISO, and which servers are carrying the AMD 6.0-current branch so I can cvsup updates? Please don't reply to the list if you don't know what the hell I'm asking about. stu