From owner-freebsd-current Tue Sep 24 17:19:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA27885 for current-outgoing; Tue, 24 Sep 1996 17:19:20 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-34.ut.nl.ibm.net [139.92.42.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA27545; Tue, 24 Sep 1996 17:18:34 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id CAA02049; Wed, 25 Sep 1996 02:13:01 +0200 (MET DST) Date: Wed, 25 Sep 1996 02:13:01 +0200 (MET DST) Message-Id: <199609250013.CAA02049@vector.jhs.no_domain> To: current@freebsd.org cc: serious@freebsd.org, commercial@freebsd.org Subject: Licensing Software From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I plan to soon sell a 3rd party commercial binary FreeBSD product. I either need to : - Develop alone, hooks for such things as - constructing machine IDs (from poking around the system) - user count (for single workstation or multi user server pricing) - link crippled-write, time limited, demo versions - make must be minimal hastle to authors, requiring no change to - sources, just to Link flags - non availability to me (as distributor) of source, but availability of .o files - Or I can maybe develop a mechanism with other interested commercial sellers, so that FreeBSD would have some generic mechanism, & maybe unique product & system keys. - Or I can even buy in such a solution if one's available ? I've read `Sun Expert' in the past, with horror stories of Sun lock managers across nets, & I am not interested in any net strategies, this will be local to the box. I'm not into academic elegant lots-of-effort solutions, I'm after a cheap dirty quick solution, I don't want to spend much time on this, my budgeted work time on this is limited, (& I'd prefer to spend my free on public source, not licence stuff) I have to get something up quickly, & whatever I cobble together, will be simpler to do alone (& keep secret :-), but if other vendors are thinking along similar lines, & interested in some kind of generic mechanism, then I'll try to comply. If anyone has something to give or even sell me, or wants to work with me, please let me know. Thanks. Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/