Date: Sun, 24 Jan 1999 03:46:53 -0500 From: Christopher Masto <chris@netmonger.net> To: current@FreeBSD.ORG Subject: Running 4.0, a few weirdies Message-ID: <19990124034653.A15039@netmonger.net>
next in thread | raw e-mail | index | archive | help
I just finished a make world and kernel build from sourced cvsuped at around Jan 23, 21:00 EST. There were no build problems, and I saw the crypt backout was in, so I installed it. System seems to be working so far, but with the following suprises: The old "unable to mount /, specified device does not match root device" on booting. My /etc/fstab had (working with -current from just a few weeks ago): /dev/wd0s1a / ufs rw 1 1 I thought this was the new world order.. apparently not. I had to change it back to: /dev/wd0a / ufs rw 1 1 Mucking with the kernel config file's "root on xxx" didn't seem to make any difference. I didn't see anything about this change in /usr/src/UPDATING, and I must have missed its mention on this list. After fixing that, I ran into problems with libcrypt. Specifically, everything seems to be linked against libcrypt.so.3 <insert pause as I get distracted, go to look at something with Netscape, and experience lockup, assuming kernel panic.. back to the old kernel for now> Ahem. As I was saying, everything (well, login, su, cvs, perl, etc.) seems to be linked against libcrypt.so.3, but there was no such version installed. I have in /usr/obj/..blah../tmp/usr/lib: lrwxr-xr-x 1 root wheel 13 Jan 22 19:58 libcrypt.a@ -> libexpcrypt.a lrwxr-xr-x 1 root wheel 14 Jan 22 19:58 libcrypt.so@ -> libexpcrypt.so lrwxr-xr-x 1 root wheel 16 Jan 22 19:58 libcrypt.so.2@ -> libexpcrypt.so.3 lrwxr-xr-x 1 root wheel 16 Jan 22 19:58 libcrypt.so.3@ -> libexpcrypt.so.3 But in /usr/lib: lrwxrwxrwx 1 root wheel 12 Oct 5 08:39 /usr/lib/libcrypt.so@ -> libscrypt.so lrwxrwxrwx 1 root wheel 14 Oct 5 08:39 /usr/lib/libcrypt.so.2@ -> libscrypt.so.2 Which would seem to explain how it happened, but obviously installworld doesn't put these into /usr/lib.. all the other libraries have current timestamps. Speaking of timestamps.. when I booted the new kernel, my clock came up wrong. Really confused me when I reconfigured the kernel and make said it was up to date. Somehow it had gone back about 20 hours. I ntpdated it back to normal, but next time I rebooted, it had gone ahead a couple of hours. I've now booted my week-old kernel, and the time was not altered. That's all that I noticed. I will try another update to get Matt's vm fix.. if it still panics, I'll get a proper backtrace. And yes, I'm using INVARIANTS. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990124034653.A15039>