From owner-freebsd-current Fri Jan 14 22:33:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat200.60.mpoweredpc.net [142.177.200.60]) by hub.freebsd.org (Postfix) with ESMTP id A664A156E9 for ; Fri, 14 Jan 2000 22:33:41 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id CAA93380; Sat, 15 Jan 2000 02:29:08 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 15 Jan 2000 02:29:08 -0400 (AST) From: The Hermit Hacker To: Matthew Dillon Cc: Rod Taylor , freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... In-Reply-To: <200001150555.VAA96077@apollo.backplane.com> 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 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