From owner-freebsd-hackers  Wed Mar 22 18:00:18 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA23421 for hackers-outgoing; Wed, 22 Mar 1995 18:00:18 -0800
Received: from ns.gte.com (ns.gte.com [132.197.8.9]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA23414 for <freebsd-hackers@freebsd.org>; Wed, 22 Mar 1995 18:00:17 -0800
Received: by ns.gte.com (8.6.10/8.6.10)
	id UAA18213; Wed, 22 Mar 1995 20:57:49 -0500
Received: from bunny.gte.com(132.197.8.1) by cliff via smap (V1.3)
	id sma018194; Wed Mar 22 20:57:24 1995
Received: by bunny.gte.com (8.6.9/GTEL2.19)
	id UAA05847; Wed, 22 Mar 1995 20:59:02 -0500
Received: by genesis.tiac.net (8.6.9/genesis0.0)
	id UAA18003; Wed, 22 Mar 1995 20:25:42 GMT
Date: Wed, 22 Mar 1995 20:25:42 GMT
From: steve2@genesis.tiac.net (Steve Gerakines)
Message-Id: <199503222025.UAA18003@genesis.tiac.net>
To: freebsd-hackers@FreeBSD.org
Subject: sup average size
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

I am considering keeping my system up to date running -current.  Is it
feasible to do this over a 14.4K slip dialup?  I plan on checking in
about every 24-48 hours.  Any idea what an average transfer size
would be for sup if I updated within that inverval?

Thanks,
- Steve
steve2@genesis.tiac.net