From owner-freebsd-questions Sun Feb 21 23:49:30 1999 Delivered-To: freebsd-questions@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 2FD46119F3 for ; Sun, 21 Feb 1999 23:47:43 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id JAA48791; Mon, 22 Feb 1999 09:45:39 +0200 (EET) (envelope-from ru) Date: Mon, 22 Feb 1999 09:45:39 +0200 From: Ruslan Ermilov To: Dennis Ostrovsky Cc: questions@FreeBSD.ORG Subject: Re: 2.2.8 -> 3.1: mostly clean sailing :) Message-ID: <19990222094538.B40215@ucb.crimea.ua> Mail-Followup-To: Dennis Ostrovsky , questions@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.17i In-Reply-To: ; from Dennis Ostrovsky on Sat, Feb 20, 1999 at 05:23:47PM -0500 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 20, 1999 at 05:23:47PM -0500, Dennis Ostrovsky wrote: > So I went from 2.2.8 to 3.1 last night...took a while, but everything went > ok more or less. > > I've got a few questions though, since some things aren't working so well. > > 1) What do I do about the port libraries? Surely I won't have to rebuild > everything. The library seems to be there, it's just not being recognized. > Now these libraries were built on 2.2.8, so does this mean I should add > /usr/local/lib to the ldconfig_paths_aout variable? I tried doing ldconfig > -R -aout but xv still wouldn't run. > > iridium:/home/do33 % xv > ld.so failed: Can't find shared library "libjpeg.so.9.0" > iridium:/home/do33 % ldconfig -r | grep jpeg > 72:-ljpeg.9 => /usr/local/lib/libjpeg.so.9 > 78:-ljpeg.8 => /usr/local/lib/libjpeg.so.8 > 84:-ljpeg.7 => /usr/local/lib/libjpeg.so.7 > iridium:/home/do33 % The `upgrade' had to move your local libraries into /usr/local/lib/aout. If you upgraded your /etc properly, your system should automatically ldconfig /usr/local/lib/aout at startup. Try `ldconfig -r -aout'. > 2) named is kind of giving me some problems. Should I be using named.conf > or named.boot? Here's the syslog output. My ethernet card is on fxp0, > although it's listening on lo0. > > Feb 20 15:37:23 iridium named[96]: starting. named 8.1.2 Sat Feb 20 > 01:16:36 EST 1999 root@iridium.hgs.yale.edu > Feb 20 15:37:23 iridium named[96]: /etc/namedb/named.conf:22: syntax error > near forwarders > Feb 20 15:37:23 iridium named[96]: cache zone "" (IN) loaded (serial 0) > Feb 20 15:37:23 iridium named[96]: master zone "0.0.127.IN-ADDR.ARPA" (IN) > loaded (serial 19980427) > Feb 20 15:37:23 iridium named[96]: listening on [127.0.0.1].53 (lo0) > Feb 20 15:37:23 iridium named[96]: Forwarding source address is > [0.0.0.0].1024 > Feb 20 15:37:23 iridium named[97]: group = bind > Feb 20 15:37:23 iridium named[97]: user = bind > Feb 20 15:37:23 iridium named[97]: Ready to answer queries. > Feb 20 15:37:23 iridium named[97]: sysquery: sendto([192.5.5.241].53): No > route to host > > The named.conf file has: > > forwarders { > 130.132.1.10 130.132.1.11 130.132.1.9; > }; > /usr/sbin/named-bootconf perl script will convert your named.boot into new named.conf format. > 3) For some reason rc.network fails to execute a start_if file I have in > my /etc directory, which worked fine under 2.2.8. Executing it manually > works fine however. Also, I'm not using any rc.conf file, I just modified > the /etc/defaults/rc.conf file, which in retrospect is probably not the > best way of doing things. > > -rwx------ 1 root wheel 38 Sep 11 17:39 start_if.fxp0* > > I use it to start the dhcp client. > Works for me. What `ident /etc/rc.network' is saying? Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message