From owner-freebsd-questions Thu Oct 9 10:24:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14004 for questions-outgoing; Thu, 9 Oct 1997 10:24:13 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13983 for ; Thu, 9 Oct 1997 10:24:03 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id KAA03127; Thu, 9 Oct 1997 10:23:57 -0700 (PDT) Date: Thu, 9 Oct 1997 10:23:57 -0700 (PDT) From: Doug White Reply-To: Doug White To: "Ronald F. Guilmette" cc: freebsd-questions@FreeBSD.ORG Subject: Re: Identd problems In-Reply-To: <1359.876259168@monkeys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 7 Oct 1997, Ronald F. Guilmette wrote: > It seems that I failed to actually have the executable for the identd > program installed on the FreeBSD box, and that's probably what caused > this problem. yup -- identd isn't included with the system because it has crypto. > But I don't understand why these messages seemed to just keep going and > going. Shouldn't the inetd daemon just give up after a short while if > it doesn't find the necessary executable to invoke? It should return ``connection refused'' to the offending connection/program. What did the log messages look like? > Separately, can someone please just tell me how one goes about installing > optional packages (e.g. the identd package) on FreeBSD after you have done > the basic OS install already? Sorry. I know this is a dumb question, but > sadly, I only bought the FreeBSD CD-ROM and not the book, and I don't really > feel like spending an hour or more trying to scrounge this one bit of info > from the www.freebsd.org web site. [ Summary: lazy. :-) ] No problem. FreeBSd has two systems, depending on how much CPU and flexibility you want. 1. Packages: Precompiled programs ready to run. Just fetch and type ``pkg_add package.tgz'' as root to install. 2. Ports: Sets of patches and instructions on how to compile and install a program. Justpull the directory for the port and type ``make'' from the top level directory; the port will fetch teh source archive, patch, configure, and compile for you. Run ``make install'' as root to install. Packages are nice since you don't have to compile, but not all programs are available as packages due to practicality or licensing concerns. Ports are updated faster and are smaller initially but need to have the source archive and take time to compile. I started out liking packages but eventually switched to ports, since you can specify the port to stop just before building so I can tweak the program's configuration to my local needs before continuing with the build. packages, you get what someone else wanted you to get (but it does mesh with the system layout). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major