From owner-freebsd-stable@FreeBSD.ORG  Wed Jul 31 15:45:01 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id C81318AB
 for <freebsd-stable@freebsd.org>; Wed, 31 Jul 2013 15:45:01 +0000 (UTC)
 (envelope-from FreeBSD@shaneware.biz)
Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net
 [IPv6:2001:44b8:8060:ff02:300:1:6:4])
 by mx1.freebsd.org (Postfix) with ESMTP id 5E6DD28A9
 for <freebsd-stable@freebsd.org>; Wed, 31 Jul 2013 15:45:01 +0000 (UTC)
Received: from ppp247-71.static.internode.on.net (HELO leader.local)
 ([203.122.247.71])
 by ipmail04.adl6.internode.on.net with ESMTP; 01 Aug 2013 01:15:00 +0930
Message-ID: <51F930F9.6010405@ShaneWare.Biz>
Date: Thu, 01 Aug 2013 01:14:57 +0930
From: Shane Ambler <FreeBSD@ShaneWare.Biz>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130516 Thunderbird/17.0.6
MIME-Version: 1.0
To: Chris H <bsd-lists@1command.com>
Subject: Re: Does the image on isc.portsnap.freebsd.org have a virus?
References: <43dfdd386703ea6bd13d43b6a44be342.authenticated@ultimatedns.net>
 <51F904C7.4070205@ShaneWare.Biz>
 <839cf247f267918cca2eb14eb0297dcf.authenticated@ultimatedns.net>
In-Reply-To: <839cf247f267918cca2eb14eb0297dcf.authenticated@ultimatedns.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable <freebsd-stable@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2013 15:45:01 -0000

On 01/08/2013 00:28, Chris H wrote:

> In the first instance, /usr/ports was removed (before initiating portsnap). But before
> the second attempt, I performed a mkdir /usr/ports. But in the end, the results were
> the same;
> portsnap fetch fetched the image, verified the image,
> extracted to /var/db/portsnap/ports, then patched, and exited.
> I did _not_ issue portsnap fetch && portsnap extract.
> So I guess portsnap extract is a noop. Guess it's time to update the portsnap(8)
> man pages to indicate portsnap fetch is no longer an option.

'portsnap fetch' downloads the relevant data to /var/db/portsnap
'portsnap extract' extracts the files to /usr/ports
'portsnap update' updates existing files in /usr/ports

So on a clean system you use portsnap fetch extract
Then to update later you use portsnap fetch update

(you can give multiple commands to portsnap in one go)

If fetch extract works on amd64 and not i386 then you should submit a 
problem report so that it can be fixed.