[296] in Zephyr Mailing List
Re: undead zwgcs
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Sep 15 11:03:53 1998
To: sfreed@gilasoft.com
Cc: Greg Hudson <ghudson@MIT.EDU>, zephyr@MIT.EDU
In-Reply-To: Your message of "Tue, 15 Sep 1998 06:18:08 MDT."
<Pine.BSI.4.02.9809150611590.4314-100000@taos.gilasoft.com>
Date: Tue, 15 Sep 1998 10:58:58 EDT
From: Greg Hudson <ghudson@MIT.EDU>
> Are there any plans to release a more current version of zephyr?
Unfortunately, there's a bit of a packaging problem on our end.
Zephyr development here has moved back into the regular Athena tree,
and the in-tree versions of com_err and ss went away in the process.
So if we shipped what we have right now, it would be somewhat less
convenient to build than 2.0.4 is. It's not like it's impossible to
work around this, but it's no longer a matter of simply wrapping up
what we have and sending it out.
> the 2.0.4 release is with its set of problems such as you can't run
> zephyrd on a host with multiple ethernet cards as well as others
> such as the one mentioned above.
I'm actually not sure what the failure mode is for running the zephyr
server on a multi-homed host, and I doubt the current sources do
anything to help. (I know what the problem is for clients, and that
has been fixed, except on Solaris between 2.0 and 2.5.1 where you
can't productively call getsockname() on a connected UDP socket.)
[There are also, unfortunately, security problems in 2.0.4, and I feel
pretty lame for not addressing them in the external release somehow.]
