From owner-freebsd-current Mon Jun 1 05:02:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23049 for freebsd-current-outgoing; Mon, 1 Jun 1998 05:02:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.175.134.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23035 for ; Mon, 1 Jun 1998 05:02:04 -0700 (PDT) (envelope-from schilling@fokus.gmd.de) Received: from sherwood.gmd.de (sherwood [193.175.133.102]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id OAA20840; Mon, 1 Jun 1998 14:02:01 +0200 (MET DST) Received: (from jes@localhost) by sherwood.gmd.de (8.8.8+Sun/8.8.8) id OAA16937; Mon, 1 Jun 1998 14:01:35 +0200 (MET DST) Date: Mon, 1 Jun 1998 14:01:35 +0200 (MET DST) From: Joerg Schilling Message-Id: <199806011201.OAA16937@sherwood.gmd.de> To: dufault@hda.com, schilling@fokus.gmd.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From dufault@hda.hda.com Fri May 29 20:12:29 1998 >> >I'm sure it will be straight forward to hook up to your library. >> >> Seems to be interesting, please send me a pointer. >Only if you promise not to give me trouble about errx - as a FreeBSD >utility their coding standard says to use that, and when >in Rome do as the Romans do. To make it portable, I'll need to replace them with my routines comerr() comerrno() errmsg() and errmsgno() wich I am using since 1982 - long before BSD intruduced things like that. I have no problems with these functions as I believe that it neccessary to have readable error messages and perror() don't makes good error messages. The problem that I have with the *BSD functions is that they make the programs non-portable. *BSD programs are often much better than GNU utilities but no-one can use them outside BSD. I believe the suing with AT&T has been won and there is no need to make programs look like they are not from a UNIX system. Please: - Put all non standard library extensions into a separate libbsd and make this library portable. ( you may add this library to the default library list of the compiler on *BSD so there will be no need to change makefiles) - Make sure that programs don't rely on nonstandard modifications of historical UNIX include files if there is a reason to compile and run these programs on a non *BSD system ( e.g. it is a non BSD kernel specific program). - Write man pages that use the stanmdard UNIX -man macros and not non-standard modifications. >If it is no longer available for anonymous ftp I'll put it up >here. I'll get back to you. I only found /sbin/scsi on the ftp server ... please give me a hint. P.S. I believe that the real problem might be that your program comes with a BSD license while my software comes with GPL. In any case, it seems to be a good idea to have a combination of a command line interpreter which allows easy sending of arbitrary commands and a portable SCSI transport library. Jörg EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) If you don't have iso-8859-1 schilling@fokus.gmd.de (work) chars I am J"org Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message