Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!agate!uclink2.berkeley.edu!alanp From: alanp@uclink2.berkeley.edu (Alan Scott Pearson) Newsgroups: comp.os.386bsd.questions Subject: Re: Second disk... Date: 17 May 1994 11:27:52 GMT Organization: University of California, Berkeley Lines: 25 Message-ID: <2ra9no$oh6@agate.berkeley.edu> References: <CppBt8.A4C@world.std.com> <2quqse$6hm@agate.berkeley.edu> <NILS.94May14201323@guru.stgt.sub.org> NNTP-Posting-Host: uclink2.berkeley.edu In article <NILS.94May14201323@guru.stgt.sub.org>, Cornelis van der Laan <nils@ims.uni-stuttgart.de> wrote: >In article <2quqse$6hm@agate.berkeley.edu> alanp@monoceros.EECS.Berkeley.EDU (Alan Pearson) writes: > >> You said you were able to newfs the drive... did you newfs /dev/rwd1c? >> And this worked??? I don't think this should be allowed to work since >> the c partition is not type 4.2BSD. newfs is wrong in doing that if that >> is what happened. > >On a SUN filesystem, rwd1c is really just an alias for the whole disk >and if you newfs it, you newfs whatever happens to be at the beginning >of your disk. If there's, say, a rwd1a with a size of 20MB, you would >newfs that. You also can mount rwd1c and, in fact, mount rwd1a. > Yes, I suppose I was incorrect in saying the behaviour of newfs was "wrong" since what I meant was "it is not what *I* think it should do." Since partition c has no filesystem type, it doesn't make sense that newfs should be able to create a filesystem using /dev/rwd?c. Of course, Suns interpre- tation that newfs rwd1c == newfs rwd1a is one way to do it, and it could also be argued that it could just assume tc=4.2bsd and make a fs of the size of the whole drive. I suppose I should look to POSIX to say what is "right" and "wrong". alan