Path: utzoo!utgpu!watmath!att!dptg!rutgers!apple!brutus.cs.uiuc.edu!wuarchive!wugate!uunet!mcsun!sunic!ifi!acc.uu.no!ivar
From: ivar@acc.uu.no (Ivar Hosteng)
Newsgroups: comp.unix.xenix
Subject: Re: Configuring Xenix
Message-ID: <102@accsys.acc.uu.no>
Date: 30 Aug 89 17:25:15 GMT
References: <200959@neabbs.UUCP> <253@jwren.UUCP>
Organization: Advanced Computer Consultants, Oslo, Norway
Lines: 27

jcw@jwren.UUCP (John C. Wren) writes:

>In article <200959@neabbs.UUCP> richard@neabbs.UUCP writes:
>>[ Xenix kernel from 530K to 230K ]
>> 
>>If you haven't got any fancy stuff like X/Windows or TCP/IP linked in
>>your kernel, 230K is about the right size.
>> 
>>I wonder how you ever got the 530K kernel...

>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?

Stripping the kernel is not wery smart. By doing this you makes it impossible
for the ps, wmstat and the w command (and more, I dont remember them all)
to find the user & proc structures inside the kernel image. This means they 
will fail. My Xenix file is 324002 bytes long and I have all multiscreens
enabled by default. 


-- 
Ivar E. Hosteng,	Advanced Computer Consultans, Oslo, Norway
Internet:		ivar@acc.uu.no
UUCP:			...!{uunet,mcvax,ifi}!acc.uu.no!ivar
'Just what do you think you are doing Dave?'	-HAL9000