From owner-freebsd-current Fri Jan 14 23:16:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 6BDFB15288 for ; Fri, 14 Jan 2000 23:16:17 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id CAA10595; Sat, 15 Jan 2000 02:11:53 -0500 (EST) (envelope-from efutch@nyct.net) Date: Sat, 15 Jan 2000 02:11:53 -0500 (EST) From: "Eric D. Futch" To: The Hermit Hacker Cc: Matthew Dillon , Rod Taylor , freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just thinking of something, I don't know how feasible it is. Couldn't you setup a CVS repository with all the files you need. You could even have it keep track of different sets of files for each class/course right? Kinda like how FreeBSD keeps track of -stable and -current seperately. When they plug in, just have it to cvsup and fetch the most recent material for this class. It might be a little more complicated this way though. Just an idea... -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Sat, 15 Jan 2000, The Hermit Hacker wrote: On Fri, 14 Jan 2000, Matthew Dillon wrote: > > :Hmm.. My main thoughts for this was the hoarding issue. As the school would > :like to allow students to 'link up' via laptops and have them synchronized via > :the same mechanism. > : > :Their current solution is to copy a 1.8GB disk image across the network onto > :the drives and use that as a normal local disk. The copy time takes several > :minutes. If for some reason 50 people decided to do this at the same time you > :could see where some network lag would come from. > > There are lots of ways of syncing up that do not require sending the > entire image over the network every time. Syncing is something you could > do with an NFS mount quite easily, combined with something like cpdup > (see /usr/ports/sysutils/cpdup). we use rdist on our network to keep our production servers in sync...we tend to avoid 'nfs traffic' as much as possible... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message