Date: Sat, 20 Feb 1999 17:23:47 -0500 (EST) From: Dennis Ostrovsky <denis.ostrovsky@yale.edu> To: questions@freebsd.org Subject: 2.2.8 -> 3.1: mostly clean sailing :) Message-ID: <Pine.GSO.4.05.9902201633260.20418-100000@mercury.cis.yale.edu>
next in thread | raw e-mail | index | archive | help
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 %
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;
};
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.
TIA.
Dennis
------------------------------------------------------------------------
Dennis Ostrovsky ** Department of Chemistry ** Yale University
E-mail: den@master.chem.yale.edu WWW: http://pantheon.yale.edu/~do33
------------------------------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.05.9902201633260.20418-100000>