*BSD News Article 2027


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!mips!mips!zaphod.mps.ohio-state.edu!cs.utexas.edu!rice!news.Rice.edu!rich
From: rich@Rice.edu (Richard Murphey)
Subject: Re: Kernel Building.
In-Reply-To: berry@enuxha.eas.asu.edu's message of Thu, 16 Jul 1992 23:27:12 GMT
Message-ID: <RICH.92Jul18160346@kappa.Rice.edu>
Sender: news@rice.edu (News)
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
References: <1992Jul16.232712.2439@ennews.eas.asu.edu>
Date: Sat, 18 Jul 1992 22:03:46 GMT
Lines: 31

In article <1992Jul16.232712.2439@ennews.eas.asu.edu> berry@enuxha.eas.asu.edu (Joel R. Berry) writes:
   Hello All,
      I checked the FAQ and saw no mention about what to do after
   one compile the 386bsd system.  I used config and created a machine
   configuration which matched my current machine.  I did a config 
   MACHINE and all was well.  I went into /sys/compile/MACHINE and
   did a make depend  ( I applied the make depend bug fixes earlier ) and
   proceeded to do a make.  Now I have this wonderful 386bsd file which
   until now i have been moing into the / directory.  Is this how it is 
   done?  I moving from a System V environment where the kernel configs
   were done by a program "kconfig".  These usually created the 
   kernel environment for you.  Is there a book which will show
   me how to do this.  In particular I need /dev/com2 to show up.  I
   dont know what to do.  Do I mkdev with the approp. numbers?  Any help
   would be GREATLY appreciated.  Thanks.
     joel berry
     berry@enuxha.eas.asu.edu

Ready-to-print PostScript files for each section of the net2 system
maintainer's manual are on nova.cc.purdue.edu in
pub/386bsd/submissions/bsd.manuals.

smm.02.config.ps.Z describes kernel configuration for the vax, however
some of it is relevant to 386BSD.  There is no freely available
rewrite for 386BSD that I know of.

More specificly, for /dev/com2 you might look at the MAKEDEV script
which is generated when you configure the kernel.  Ideally, it should
have a mknod command with the appropriate numbers for each device.
Rich
--