From owner-freebsd-stable@FreeBSD.ORG Wed Jul 31 16:33:19 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 48454C85 for ; Wed, 31 Jul 2013 16:33:19 +0000 (UTC) (envelope-from bsd-lists@1command.com) Received: from udns.ultimateDNS.NET (ultimatedns.net [209.180.214.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 130112AC3 for ; Wed, 31 Jul 2013 16:33:18 +0000 (UTC) Received: from udns.ultimateDNS.NET (localhost [127.0.0.1]) by udns.ultimateDNS.NET (8.14.5/8.14.5) with ESMTP id r6VGXXR3042840 for ; Wed, 31 Jul 2013 09:33:39 -0700 (PDT) (envelope-from bsd-lists@1command.com) Received: (from www@localhost) by udns.ultimateDNS.NET (8.14.5/8.14.5/Submit) id r6VGXS5t042834; Wed, 31 Jul 2013 09:33:28 -0700 (PDT) (envelope-from bsd-lists@1command.com) Received: from udns.ultimatedns.net ([209.180.214.225]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Wed, 31 Jul 2013 09:33:28 -0700 (PDT) Message-ID: <80db7adb40c728a24c9a6fae24d5b562.authenticated@ultimatedns.net> In-Reply-To: <51F930F9.6010405@ShaneWare.Biz> References: <43dfdd386703ea6bd13d43b6a44be342.authenticated@ultimatedns.net> <51F904C7.4070205@ShaneWare.Biz> <839cf247f267918cca2eb14eb0297dcf.authenticated@ultimatedns.net> <51F930F9.6010405@ShaneWare.Biz> Date: Wed, 31 Jul 2013 09:33:28 -0700 (PDT) Subject: Re: Does the image on isc.portsnap.freebsd.org have a virus? From: "Chris H" To: "freebsd-stable" User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2013 16:33:19 -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. Greetings, Yes, I know. That's how it's _supposed_ to work. :) I guess a send(2) pr is in order. Thanks for the reply. --chris > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >