From owner-freebsd-ports Sun Jul 30 05:52:09 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id FAA06372 for ports-outgoing; Sun, 30 Jul 1995 05:52:09 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id FAA06350 for ; Sun, 30 Jul 1995 05:52:03 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA11462; Sun, 30 Jul 1995 14:51:45 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA01916; Sun, 30 Jul 1995 14:51:44 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id KAA13917; Sun, 30 Jul 1995 10:47:18 +0200 From: J Wunsch Message-Id: <199507300847.KAA13917@uriah.heep.sax.de> Subject: Re: cvs commit: src/etc inetd.conf To: ache@astral.msk.su (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka) Date: Sun, 30 Jul 1995 10:47:15 +0200 (MET DST) Cc: rgrimes@gndrsh.aac.dev.com, tom@uniserve.com, asami@cs.berkeley.edu, ports@FreeBSD.org, roberto@blaise.ibp.fr In-Reply-To: from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka" at Jul 30, 95 06:40:26 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1284 Sender: ports-owner@FreeBSD.org Precedence: bulk As =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka wrote: > > >> Have you looked at the ports/packages lately? Everyone seems to play > >> by different rules. > > >No, but it ain't a ``true'' BSD port if it don't follow the rules layed > >out for BSD. > > uucp is 'true' BSD port, and it breaks this rule: it can be called > from command line but live in libexec. Time to move it to sbin? The line is not clear, but i think we should refer to the `usual' way of starting it. uucico is usually only started from a command line for debugging purposes, and from cron(8) or uucp(1) otherwise. Similar considerations apply to things like uuxqt. Of course, you could also run cpp, cc1 etc. from a command line, but nevertheless they are (and should be) under /usr/libexec, as they are normally started from cc(1) [or c89(1) :-)]. In addition, there's a cpp frontend in /usr/bin, for those who abuse cpp as a generic macro preprocessor. I think if identd is normally run from inetd, it would belong to libexec; since it's apparently also useful (for some sites) to run it as a standalone daemon, sbin would better suite (IMHO). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)