Re: Re: OpenSS7 GPL'd LiS.

Ragnar,

I'm too deep into the release cycle to change much now.  Perhaps
I could release it as 2.18.0.1 if that would help.  If that
works for you I will investigate and get back.


On Tue, 12 Apr 2005, Ragnar Paulson wrote:

> I too did not notice that there were variants in the wild with
> the same name but operating under a different license.  
> 
> I have imported the entire LiS-2.18.0 into CVS, tagged it as
> LiS-2-18-0 and will maintain the source based on submissions
> to this mailing list.  I have even less broad test abilities
> than Dave, so I will rely on visual inspection, compiler and
> this mailing list for code review.  Consequently large patches
> may take a considerable amount of time before they are
> released.
> 
> On the other hand, I believe the bulk of LiS is stable and
> will not change much.  It is not my intention to add new
> features or components to LiS.  LiS needs to support STREAMS
> on a wide variety of operating systems and platforms.  It does
> not need to include drivers and modules the use STREAMS
> however useful they might be.  Don't ask me to include your
> wonderful gadget module in the next release of LiS ... create
> your own package.  

Please remove Ole's versions of timod and tirdwr, they are
seriously broken.  Ldl is seriously broken (and is GPL), perhaps
you should remove it.  There are races in new functions
lis_freezestr and lis_unfreezestr.  Both lis_qprocsoff/on and
lis_un/freezestr are broken and unusable in the SVR 4.2 MP
sense.  There are still open/close race bugs.  You will need to
handle unexported symbols in 2.6.10 kernels.  Opening streams
drivers is broken on devfsd kernels.  Additional bugs in most
SREAMS functions are documented in the manual pages released
with the OpenSS7 release.

Please do not include our strxnet package, our inet driver or
our working timod/tirdwr modules.  They are (and have always
been) GPL code.  There has always been a confusion since it was
inluded in LiS, as some companies have been using it believing
that it is under the terms of the LGPL when it is not.

It would probably be a good idea to remove cdi, dlpi, npi, tpi
and xti header files as nothing else uses them and they conflict
with release packages.

> 
> Releases will be made quarterly (unless there are no changes)
> or as needed in case of emergency.  They will be published to
> our FTP site in the lis directory.
> ftp://ftp.wanware.com/lis/LiS-2.18.0.tgz is a copy of the GCOM
> package.

LiS-2.18.0 does not build on SuSE 9.1, SuSE 9.2, EL4, FC3,
MDK10.1 with current kernels.  It also does not build for
recent kernels and distro release kernels in the 2.4 series.

Is that an emergency?  Users of these systems can I suppose read
back in the archives and hand patch LiS-2.18.0 in the mean time.

> 
> Expect LiS-2.18.1.tgz sometime this summer, and future
> releases as reported above.  

Good timing, I hope to have LiS replaced by then.

> 
> Brian, please rename your "copy" (as per your original e-mail
> you have the copy) that has been GPLed.

Could you maybe use LiS-2.18.2 this summer and save me the
trouble of changing a release that is already cut.

> 
> Ragnar Paulson
> The Software Group Limited
> 
> _______________________________________________
> Linux-streams mailing list
> [email protected]
> http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams

-- 
Brian F. G. Bidulock    ¦ The reasonable man adapts himself to the ¦
[email protected]    ¦ world; the unreasonable one persists in  ¦
http://www.openss7.org/ ¦ trying  to adapt the  world  to himself. ¦
                        ¦ Therefore  all  progress  depends on the ¦
                        ¦ unreasonable man. -- George Bernard Shaw ¦