Portsnap - Revision history

216.102.199.81 at 19:06, 9 December 2009

2009-12-09T19:06:14Z

Jimbo: Reverted edits by 196.25.52.36 (Talk); changed back to last version by Jimbo

2008-12-18T04:09:27Z

Reverted edits by 196.25.52.36 (Talk); changed back to last version by Jimbo

Jimbo at 19:59, 28 May 2007

2007-05-28T19:59:24Z

82.171.39.195: fix the version which is in ports and note it is also in the base system since 5.5 and 6.1

2006-04-02T14:33:51Z

fix the version which is in ports and note it is also in the base system since 5.5 and 6.1

24.16.241.179 at 21:59, 25 November 2005

2005-11-25T21:59:52Z

24.16.241.179 at 21:58, 25 November 2005

2005-11-25T21:58:31Z

24.16.241.179 at 21:57, 25 November 2005

2005-11-25T21:57:05Z

199.249.176.251 at 15:39, 22 September 2005

2005-09-22T15:39:32Z

137.131.205.145 at 17:43, 21 July 2005

2005-07-21T17:43:32Z

24.87.209.6 at 20:01, 4 April 2005

2005-04-04T20:01:30Z

@@ Line 13: / Line 13: @@
 Portsnap avoids these problems by operating over HTTP, signing the snapshots, and using more sophisticated delta compression to distribute the snapshots.
-Version 1.0 of portsnap is in the FreeBSD base system since FreeBSD 5.5 and 6.1 and in the FreeBSD ports tree as sysutils/portsnap.
+Version 1.0 of portsnap is in the FreeBSD base system since FreeBSD 5.5 and 6.1 and in the FreeBSD ports tree as sysutils/portsnap on older versions.
 ----

@@ Line 27: / Line 27: @@
   # '''portsnap update'''
-In order to avoid problems with “flash crowds” accessing the portsnap servers, portsnap fetch will not run from a cron job. Instead, a special portsnap cron command exists, which waits for a random duration up to 3600 seconds before fetching updates.
+In order to avoid problems with “flash crowds” accessing the portsnap servers, '''portsnap fetch''' will not run from a cron job. Instead, there is a special command, '''portsnap cron''', which waits for a random duration up to 3600 seconds and then functions just like '''portsnap fetch'''.
-In addition, it is strongly recommended that portsnap update not be run from a cron job, since it is liable to cause major problems if it happens to run at the same time as a port is being built or installed. However, it is safe to update the ports INDEX files, and this can be done by passing the "<tt>-I</tt>" flag to portsnap. (Obviously, if "<tt>portsnap -I update</tt>" is run from cron, then it will be necessary to run portsnap update without the "<tt>-I</tt>" flag at a later time in order to update the rest of the tree.)
+In addition, it is strongly recommended that portsnap update not be run from a cron job, since it is liable to cause major problems if it happens to run at the same time as a port is being built or installed. However, it is safe to update the ports INDEX files, and this can be done by passing the '''-I''' flag to portsnap. (Obviously, if '''portsnap -I update''' is run from cron, then it will be necessary to run portsnap update without the '''-I''' flag at a later time in order to update the rest of the tree.)
-Adding the following line to /etc/crontab will cause portsnap to update its compressed snapshot and the INDEX files in /usr/ports/, and will send an email if any installed ports are out of date:
+Adding the following line to [[/etc/crontab]] will cause portsnap to update its compressed snapshot and the INDEX files in /usr/ports/, and will send an email if any installed ports are out of date:
-3 * * * root portsnap -I cron update && pkg_version -vIL=
+3 * * * root portsnap -I cron update && [[pkg_version]] -vIL=
-'''Note:''' If the system clock is not set to the local time zone, replace "3" with a random value between 0 and 23, in order to spread the load on the portsnap servers more evenly.
+'''Note:''' Consider replacing the "3" above with a random value between 0 and 23, in order to spread the load on the portsnap servers more evenly.
 See also: [[updating the system]]
 [[Category:Ports and Packages]]

@@ Line 13: / Line 13: @@
 Portsnap avoids these problems by operating over HTTP, signing the snapshots, and using more sophisticated delta compression to distribute the snapshots.
-Version 0.9.5 of portsnap is in the FreeBSD ports tree as sysutils/portsnap.
+Version 1.0 of portsnap is in the FreeBSD base system since FreeBSD 5.5 and 6.1 and in the FreeBSD ports tree as sysutils/portsnap.
 ----

@@ Line 13: / Line 13: @@
 Portsnap avoids these problems by operating over HTTP, signing the snapshots, and using more sophisticated delta compression to distribute the snapshots.
-Version 0.9.1 of portsnap is in the FreeBSD ports tree as sysutils/portsnap.
+Version 0.9.5 of portsnap is in the FreeBSD ports tree as sysutils/portsnap.
 ----

@@ Line 34: / Line 34: @@
 3 * * * root portsnap -I cron update && pkg_version -vIL=
 See also: [[updating the system]]
 [[Category:Ports and Packages]]

@@ Line 8: / Line 8: @@
 * CVSup is insecure. The protocol uses no encryption or signing, and any attacker who can intercept the connection can insert arbitrary data into the tree you are updating.
 * CVSup isn't end-to-end. Related to the previous point, this means that anyone who can compromise a CVSup mirror can feed arbitrary data to the people who are using that mirror.
-* CVSup isn't designed for frequent small updates. While CVSup is very good at distributing CVS trees, and is very efficient for updating a tree which has been significantly changed (eg, by a month or more of commits), it has transmits a list of all the files in the tree, which makes it quite inefficient if only a few files have changed.
+* CVSup isn't designed for frequent small updates. While CVSup is very good at distributing CVS trees, and is very efficient for updating a tree which has been significantly changed (eg, by a month or more of commits), it transmits a list of all the files in the tree, which makes it quite inefficient if only a few files have changed.
 * CVSup uses a custom protocol. This can cause problems for people behind firewalls -- outgoing connections on port 5999 need to be permitted -- and it needs a heavyweight server (cvsupd).

@@ Line 13: / Line 13: @@
 Portsnap avoids these problems by operating over HTTP, signing the snapshots, and using more sophisticated delta compression to distribute the snapshots.
-Version 0.3.1 of portsnap is in the FreeBSD ports tree as sysutils/portsnap.
+Version 0.9.1 of portsnap is in the FreeBSD ports tree as sysutils/portsnap.
 ----
@@ Line 19: / Line 19: @@
   # '''cd /usr/ports/sysutils/portsnap'''
   # '''make install clean'''
   # '''portsnap fetch''' (this will download a large file)
   # '''portsnap extract''' (this will update the ports tree)