From owner-freebsd-hackers Tue Oct 1 22:06:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA03291 for hackers-outgoing; Tue, 1 Oct 1996 22:06:52 -0700 (PDT) Received: from answerman.mindspring.com (answerman.mindspring.com [204.180.128.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA03286 for ; Tue, 1 Oct 1996 22:06:48 -0700 (PDT) Received: from borg.mindspring.com (borg.mindspring.com [204.180.128.14]) by answerman.mindspring.com (8.7.5/8.7.3) with ESMTP id BAA29635; Wed, 2 Oct 1996 01:06:43 -0400 (EDT) Received: from bogus.mindspring.com (user-168-121-39-4.dialup.mindspring.com [168.121.39.4]) by borg.mindspring.com (8.6.12/8.6.12) with SMTP id BAA21364; Wed, 2 Oct 1996 01:06:40 -0400 Message-Id: <1.5.4.32.19961002050641.008b1050@mindspring.com> X-Sender: kpneal@mindspring.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 02 Oct 1996 01:06:41 -0400 To: "Justin T. Gibbs" From: "Kevin P. Neal" Subject: Re: VPS mailing list, BSD interest? Cc: Jason Thorpe , Poul-Henning Kamp , James Graham , hackers@freebsd.org, tech-kern@NetBSD.ORG Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 01:12 PM 10/1/96 -0700, Justin T. Gibbs wrote: >>Just where do you propose to keep this information? >> >>(Hint: it's going to be machine-dependent.) > >VxFS runs on many different different platforms and uses this approach, but >I would expect a per OS not per machine type solution. I haven't given it >a tremendous amount of thought, but I assumed that it would be part of the >BSD disklabel. Know of a good online source of info on VxFS? Perhaps a good book that might show up in a university library? >>How does the way the ccd is configured not allow you to move your >>disks around (to different controllers, etc.)? >> >>(Hint: it doesn't.) > >Last time I looked at CCD, it did. What I mean by moving my disks around >is handling situations like, "Gee, I'm not getting enough bandwidth using >only one controller here. I think I'll buy a second one and split up my >disks." After turning off the machine, sticking in the new controller and >messing with some cables, I should be able to simply power on the system >and have everything work transparently. The coolest would be the kernel sysloging messages like "spare bandwidth on controller Y, suggest moving data over there off of controller X." Or even for disks. Or even for virtual partitions. -- XCOMM Kevin P. Neal, Sophomore, Comp. Sci. \ kpneal@pobox.com XCOMM "Corrected!" -- Old Amiga tips file \ kpneal@eos.ncsu.edu XCOMM Visit the House of Retrocomputing: / Perm. Email: XCOMM http://www.pobox.com/~kpn/ / kevinneal@bix.com