Subject: [FreeVMS] Re: Network Protocol Implementation
Date: Wed Jul 17 2002 - 11:10:12 CEST
On Tue, Jul 16, 2002 at 04:19:40PM -0700, Daniel O'Neill wrote:
> On Tuesday 16 July 2002 02:10, you wrote:
> > On Tue, Jul 16, 2002 at 12:48:08AM -0700, Daniel O'Neill wrote:
> > > On Monday 15 July 2002 00:36, you wrote:
> > > > On Sun, Jul 14, 2002 at 12:10:52PM -0700, Daniel O'Neill wrote:
> > > > > Is there currently any interest in network protocol implementation,
> > > > > or am I being a bit premature?
> > > > >
> > > > > The reason for this question, is I would consider now a crucial stage
> > > > > to start deploying IPv6 in both kernel and userspace areas of
> > > > > freevms. I can construct a small development team for this task, but
> > > > > I cannot do it alone.
> > >
> > Are you looking out to do TCPIP$INETACP or another network ACP?
> actually, that's a bit more work than i'm qualified for. basically, i was
> more interested in just handling a specific part of the tcp stack, INET6 the
> ipv6 area. appearantly it's a package deal, but if you'd like i can try to
As said previously, there is already a IPv6 stack with BSD interface available.
(And HP itself has a Unix-based stack for VMS)
We can not do VMS-specifics like
status = SYS$QIOW(0,net_chan, IO$_SETMODE, iosb, 0, 0,
&lhst_adrs, 0, 0, 0);
instead of socket(2). (I suppose socket is implemented by QIO).
A FreeVMS implementation will be QIO-based.
> coordinate a stack development team. at worst, i might be able to bring you
> a handful of developers you might find a use for elsewhere. i may not be the
> best coder but i know a good one when i see one :)
Do they have any VMS experience?
-- Liste de diffusion FreeVMS Pour se désinscrire : mailto:email@example.com?subject=unsubscribe
This archive was generated by hypermail 2b25 : Wed Jul 17 2002 - 11:10:41 CEST