Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!news.cs.indiana.edu!umn.edu!umeecs!dip.eecs.umich.edu!dmuntz From: dmuntz@dip.eecs.umich.edu (Daniel A Muntz) Newsgroups: comp.unix.bsd Subject: Re: selling 386BSD (was Re: 386BSD on CD-ROM?) Message-ID: <1992Aug14.160938.22432@zip.eecs.umich.edu> Date: 14 Aug 92 16:09:38 GMT Article-I.D.: zip.1992Aug14.160938.22432 References: <1992Aug11.190949.1496@Informatik.TU-Muenchen.DE> <1992Aug12.100430.3467@Urmel.Informatik.RWTH-Aachen.DE> <1557@hcshh.hcs.de> Sender: news@zip.eecs.umich.edu (Mr. News) Organization: University of Michigan EECS Dept., Ann Arbor Lines: 22 In article <1557@hcshh.hcs.de> hm@hcshh.hcs.de (Hellmuth Michaelis) writes: >In <1992Aug12.100430.3467@Urmel.Informatik.RWTH-Aachen.DE> kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes: >>Strangely, Chris Dimetrios (excuse wrong spelling) recently mentioned >>in a patch he posted that he had put his *own* Copyright note on the patches. > >conclusion: in every piece of software, i will put an equivalent copyright > notice in. i spend an enormous amount of time writing an pccons > device driver (watch out for it), and i do not like it, if some- > one else is making money with it. > Aaaagggghhhhh! If everyone starts putting their own copyrights in the code we might as well all buy BSD386. When a university wants to start using a software package, the u lawyers have to evaluate all of the licensing/copyright garbage associated with it. If they have to evaluate every file on an individual basis, possibly having to contact > 100 people, institutional use of 386bsd is threatened. The copyright notice included by cgd sets a bad precedent, especially if code containing new restrictions is integrated into the Jolitz' release. We'll have to start rewriting 386bsd code to produce an unencumbered 386bsd release :-/ -Dan