From owner-freebsd-current Fri Jan 10 11:25:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA27245 for current-outgoing; Fri, 10 Jan 1997 11:25:54 -0800 (PST) Received: from ipro.com (farad.ipro.com [204.179.121.96]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA27240 for ; Fri, 10 Jan 1997 11:25:52 -0800 (PST) Received: from ipro.ipro.com by ipro.com (8.7.4/SMI-SVR4) id LAA25150; Fri, 10 Jan 1997 11:25:09 -0800 (PST) Message-Id: <199701101925.LAA25150@ipro.com> X-Sender: kingram@ipro.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 10 Jan 1997 11:32:31 -0800 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), FreeBSD-current@freebsd.org From: Ken Ingram Subject: Re: Adding Hard Drives - Prepping Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I understand slices,partitions,filesystems and mounting. In fact the histrionics I've gone through to simply add 1Gb to a newsserver has been quite instructional I will actually have something to contribute when all is said and done. Is devfs something about 'device file system' or something thereabout? And truly, what does knolwedge of partitions, &tc. have to do with making a standard. I still would need that info now if things had been easier. As it stands I got what I was looking for: a rather intense intro to 'Adding Hard Drives - Prepping' At 09:31 AM 1/10/97 +0100, J Wunsch wrote: >As Terry Lambert wrote: > >> I happen to agree with Ken here. >> >> When will devfs be standard so we can implement physical to logical >> translation layers and make this whole problem go away? > >That's only one part of the story. You still have to understand the >difference between slices, partitions, filesystems, and mounting. > >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE >Never trust an operating system you don't have sources for. ;-) > > --Ken ________________________________________________________________________ Ken Ingram kingram@ipro.com | ------------------------------------------------------------------------ POST NO BILLS