Date: Wed, 31 Jul 2013 07:58:31 -0700 (PDT) From: "Chris H" <bsd-lists@1command.com> To: "freebsd-stable" <freebsd-stable@freebsd.org> Subject: Re: Does the image on isc.portsnap.freebsd.org have a virus? Message-ID: <839cf247f267918cca2eb14eb0297dcf.authenticated@ultimatedns.net> In-Reply-To: <51F904C7.4070205@ShaneWare.Biz> References: <43dfdd386703ea6bd13d43b6a44be342.authenticated@ultimatedns.net> <51F904C7.4070205@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
Greetings, and thank you for your response. > On 31/07/2013 15:44, Chris H wrote: >> Greetings, >> I know this sounds crazy, and apologies if I am. But I have 2 RELENG_8 servers; >> 1 amd64, and 1 i386. about 3 wks ago, I migrated from cv(sup) updating, to svn on >> the amd64 box. >> After removing cv(sup) related folders, and the ports folder, I used: >> portsnap fetch >> After the fetch completed I ran: >> portsnap extract >> which verified/patched && extracted the image to /usr/ports. >> Tonight, I initiated the same procedure on the i386 server. _BUT_ upon completion of >> the fetch, it proceeded to verify/patch && extract; _not_ to /usr/ports, but to >> /var/db/portsnap/ports. re-examining /etc/portsnap.conf, and re-reading the portsnap(8) >> man >> page, reveals that _both_ .conf files are identical, as were the version(s) used on both >> boxes. An additional attempt to portsnap fetch, resulted in the same (unorthodox) >> behavior. >> What gives?! > > Are you watching as it started or when it finished? > > /var/db/portsnap is used by portsnap to download updates that it uses to > generate the /usr/ports files. > > Just guessing but it may also extract and patch files there before > moving them to /usr/ports Yep. I'm watching it. 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. Thanks again, 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?839cf247f267918cca2eb14eb0297dcf.authenticated>