Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!uunet!amdahl!JUTS!cd.amdahl.com!gab10
From: gab10@cd.amdahl.com (Gary A Browning)
Newsgroups: comp.os.386bsd.questions
Subject: Re: Disklabel/newfs -
Message-ID: <ef3n028o39G301@JUTS.ccc.amdahl.com>
Date: 9 Mar 93 17:34:34 GMT
References: <1993Mar4.062419.18727@oz.plymouth.edu> <1993Mar4.172411.28968@coe.montana.edu> <CGD.93Mar4205238@eden.CS.Berkeley.EDU> <1ndg8b$ej0@wzv.win.tue.nl>
Sender: netnews@ccc.amdahl.com
Organization: Amdahl Corporation
Lines: 40
In article <1ndg8b$ej0@wzv.win.tue.nl>, guido@gvr.win.tue.nl (Guido van
Rooij) writes:
[ deleted ]
> I disklabel'ed my quantum 120 meg drive with 20 megs of dos with only
> the c, and not the d, parttition. Indeed the c is the whole diskpart
> for 386bsd. I've never had problems without that d partition. Not
> with 0.0 and not with 0.1. Also my second disk, which is completely
> used for 386BSD has no d partition, but just c.
I've never built the 'd' partition either, but it always seems to be there.
My system always gets screwed up if I try to use it for anything else.
Anybody know what partition are 'reserved' in 386BSD? and also for the
second disk? Some people might be getting the FAQ together and this would
be nice to include.
I'll start with what I think and you all can feel free to tear it apart.
I would also like to know why (i.e. disklabel uses it to find the label, or
such).
Boot Disk
---------
a - Root - ?Coded into the kernel?
b - Swap - ?Coded into the kernel?
c - Entire 386BSD - ??
d - Entire disk - ?Assumed by disk drivers?
Non-boot Disks
--------------
c - Entire 386BSD - ??
d - Entire disk - ?Assumed by disk drivers?
Are there any differences for 386BSD dedicated disks vs. a shared disk with
DOS?
--
Gary Browning | Exhilaration is that feeling you get just after a
gab10@cd.amdahl.com | great idea hits you, and just before you realize
| what is wrong with it.