Xref: utzoo comp.unix.i386:1722 comp.unix.xenix:8961
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!hrtix!davr
From: davr@hrtix.UUCP (David C. Raines)
Newsgroups: comp.unix.i386,comp.unix.xenix
Subject: Re: ISC ?
Keywords: ISC System V
Message-ID: <276@hrtix.UUCP>
Date: 12 Dec 89 16:38:57 GMT
References: <111059@nstar.UUCP> <431@shiloh.UUCP> <511068@nstar.UUCP>
Reply-To: davr@hrtix.UUCP (David C. Raines)
Followup-To: comp.unix.i386
Organization: Treasure Chest Advertising, Windsor Locks, CT
Lines: 20

In article <511068@nstar.UUCP> larry@nstar.UUCP (Larry Snyder) writes:
>addressed to akcs.larry@nstar - and I still am having some strange problems
>with the kernel needing to be relinked at powerdown - when it's been done on
>on another shutdown. I am using the Hostess board for 8 ports and the normal com
>port as the primary com port - which works (called unix.10 at boot time) but
>after every powerdown my system wants to "re-link" the kernel then after
>rebooting I loose control on all com ports.
>

Larry, it sounds like you have an old unix that was built without
the Hostess driver sitting in a directory where the system wants to link
it to /unix when rebooting (/etc/conf/cf.d, I believe).  It seems
some installpkgs put unix here, which is different from ISC's kconfig.
Kconfig puts it's kernals in subdirectories to /etc/conf/kconfig.d.
Do ls -li on these dirs and the root dir to match up the inodes,
then remove or rename the old unix.

-- 
David Raines			TCA  5 National Dr., Windsor Locks, CT 06096
UUCP:  ...!uunet!hrtix!davr