Path: utzoo!attcan!uunet!snorkelwacker.mit.edu!usc!ucsd!mvb.saic.com!ncr-sd!simasd!jadpc!jdeitch
From: jdeitch@jadpc.cts.com (Jim Deitch)
Newsgroups: comp.unix.sysv386
Subject: Re: ISC 2.2 q/ TCP 1.2.0 questions/problems
Message-ID: <1991Jan24.084450.934@jadpc.cts.com>
Date: 24 Jan 91 08:44:50 GMT
References: <319@stiatl.UUCP> <1991Jan22.134156.10071@nstar.rn.com> <323@stiatl.UUCP>
Distribution: na
Organization: Network Engineering Technologies, San Diego, CA.
Lines: 43

In article <323@stiatl.UUCP> bgi@stiatl.UUCP (Brad Isley) writes:
>larry@nstar.rn.com (Larry Snyder) writes:
>
>>bgi@stiatl.UUCP (Brad Isley) writes:
>
>>>I'm building smail 3.1.19 for ISC 2.2 right now.  I'll keep you posted on
>>>my progress.  Porting to this OS is NOT trivial.
>
>>Hmm?  I have smail3 from uunet (even though it says smail3.19 is
>>is actually smail3.18) and it compiles fine (no porting required)
>>under Interactive Unix..
>
>>As a matter of fact, I've installed it on 3 different machines - without
>>the need to change a single line of code..
>
>What I was referring to was getting the Bezerkely/SYSV mixture configured.
>All the default setups work fine.  If you want to use Bezerkely features
>under SYSV you have to go mangle the config stuff down in os/config.  For
>the folks like us who aren't very familiar with sendmail and network jargon
>it's not trivial.
>
>Like I said, it's not trivial.   But it's not really difficult, either.
>The problem was the time wasted just figuring out what had to be done to
>get it past the compiler the way you want it built.  I haven't done any
>testing on what I was able to compile, but I did get SMTP support compiled.
>
>Cheers!
>-- 
>-----------------------------\      / ..and Apple thought GUI was theirs!.. \
> bgi@stiatl.uucp 841-4169      \---| Yer local zymurgist & Amiga hacker/user |
>          OR                        \ Klein bottle for sale- Inquire within /
> brad@slammer.UUCP 925-9663           Brad Isley,  Sales Technologies, Inc.

Hmm...All I did was to use the bsd networking choice and had no
problem.  I am using ISC 2.2.0 and am more pleased than anything.  I
hate a cryptic control file.

Jim

-- 
ARPANET:    jadpc!jdeitch@nosc.mil
INTERNET:   jdeitch@jadpc.cts.com
UUCP:	    nosc!jadpc!jdeitch