From owner-freebsd-chat Mon Sep 21 11:37:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01848 for freebsd-chat-outgoing; Mon, 21 Sep 1998 11:37:22 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from terror.hungry.com (terror.hungry.com [199.181.107.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA01821 for ; Mon, 21 Sep 1998 11:37:10 -0700 (PDT) (envelope-from fn@hungry.com) Received: (qmail 28506 invoked by uid 507); 21 Sep 1998 18:36:40 -0000 To: chat@FreeBSD.ORG Subject: Re: Network Computers References: <199809211723.KAA17886@kithrup.com> From: Faried Nawaz Date: 21 Sep 1998 11:36:39 -0700 In-Reply-To: sef@kithrup.com's message of 21 Sep 1998 10:25:16 -0700 Message-ID: Lines: 19 X-Mailer: Gnus v5.4.37/XEmacs 19.16 Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org People at my former school actually did something like this. The computer lab PCs (running DOS/Win3.11 or Win95) and Macs would compare the contents of their local hard drives with certain servers, and sync everything (registry, apps on the local disk, etc). The local drives were mainly used for caching web pages and temp space for documents/apps. Every student had to login (authentication was done via Novell servers) before using the machines, and their personalized Windows/Mac settings were stored on their network drives. Whenever they logged out/shutdown the machine, the system would save their settings and resync with the server. It worked out pretty well, though it made for 3-5 minute reboots. The worst-case scenario was when the local drive was accidentally/maliciously deleted; it would require someone to come up and manually update the hard drive image (via a floppy or something). Then again, it was an academic environment, and people could always move to another computer or lab if things were down. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message