Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!lll-winken!uunet!applix!jim
From: jim@applix.UUCP (Jim Morton)
Newsgroups: comp.unix.xenix
Subject: Re: Configuring Xenix
Summary: configure vs. link_xenix
Message-ID: <999@applix.UUCP>
Date: 31 Aug 89 17:19:36 GMT
References: <200959@neabbs.UUCP> <253@jwren.UUCP>
Organization: APPLiX Inc., Westboro MA
Lines: 17

> In article <200959@neabbs.UUCP> richard@neabbs (RICHARD RONTELTAP) writes:
> One thing I have noticed is that the sysadm shell script for linking a new
> kernel is not the same as the /usr/sys/conf/sys/link_xenix script.  I seem
> to recall that the sysadm script does not do a strip on the newly generated
> kernel... Perhaps this could be it?
  
The configure and link_xenix process I believe differs from running a make
on the kernel in that the mini assembler in configure puts some data in the
DATA section, whereas the make with the Development System puts that data
in BSS. This will result in a size difference in /xenix of 100k+. The only
real difference though is the amount of on-disk storage the kernel takes
up -- if you compare the boot time kernel size numbers for a kernel built
each way they come out the same... You can see this happen for yourself
by watching the .s files in /usr/sys/conf.  (Don't strip the kernel!)
--
Jim Morton, APPLiX Inc., Westboro, MA
...uunet!applix!jim    jim@applix.com