Big problems with snapshot/20000226, part 2
Thor Lancelot Simon
> Thanks, that helped, but not directly. After reading your message, I
> remembered that I had, in fact, done a complete 'sup' before doing the
> snapshot overlay. In single-user mode, making userland and the kernel
> worked just fine, and the next reboot had me up to date.
>
> I still think that we should have a clearly-documented method of going from
> 1.4.1 to -current that works.
I'm not sure I agree. -current is not a release, it's not supported in many
of the ways that releases are, and, as we say over and over again, it may
be broken in arbitrary ways at any time.
Given those constraints, I'm not sure giving step-by-step instructions to
help the naive upgrade is the best idea in the world.
--
Thor Lancelot Simon t...@rek.tjls.com
"And where do all these highways go, now that we are free?"
Paul Hoffman
Paul Hoffman
snapshot/20000226/binary/sets, went to /, and untarred each of them. No
problems, or so it seems.
The reboot goes well until rc. Two bad things happen:
- In the messages, it says:
creating runtime link editor directory cache.
ldconfig:
libm.so.0 machdep.fpu_present 1:libm387.so.0,libm.so.0: No such file
or directory
The rest of the messages look fine, and it is clear that even the Internet
connection worked because sendmail comes up quickly.
- I try to login at the login: prompt, and it says:
Shared object "libkrb5.so.1" not found
And takes me back to the login prompt. That is, I can't log in. <sigh>
So, I force a reboot into single-user mode, fsck (with no errors reported),
and mount / and /usr. In /usr/lib/, I see that libm.so.0 exists as a link
to libm.so.0.1, which is there. libm387.so.0 exists as a link to
libm387.s0.0.0, which is there.
libkrb5.so.1 was *not* there. As an experiment, I created
/usr/lib/libkrb5.so.1 with "touch" and rebooted. The same symtom: it says
"Shared object "libkrb5.so.1" not found".
Am I hosed? If I can get these files on a floppy, I can get them to the
system, but otherwise I'm going to have to wipe and use a different snapshot.
David Brownlee
> On Thu, Mar 02, 2000 at 11:26:38AM -0800, Paul Hoffman wrote:
> I'm not sure I agree. -current is not a release, it's not supported in many
> of the ways that releases are, and, as we say over and over again, it may
> be broken in arbitrary ways at any time.
>
> Given those constraints, I'm not sure giving step-by-step instructions to
> help the naive upgrade is the best idea in the world.
But it would be useful for developers who want to spend cycles
wokring on code, rather than on fixing an upgrade (particularly
non NetBSD developers who may want to port something across)
David/absolute
Christos Zoulas
Paul Hoffman <phof...@proper.com> wrote:
>I installed 1.4.1 from CD-ROM. I then ftp'd the sets from
>snapshot/20000226/binary/sets, went to /, and untarred each of them. No
>problems, or so it seems.
>
>The reboot goes well until rc. Two bad things happen:
>
>- In the messages, it says:
> creating runtime link editor directory cache.
> ldconfig:
>libm.so.0 machdep.fpu_present 1:libm387.so.0,libm.so.0: No such file
>or directory
>The rest of the messages look fine, and it is clear that even the Internet
>connection worked because sendmail comes up quickly.
You are running ldconfig on an ELF system... Your rc files must be horribly
out of date.
>Am I hosed? If I can get these files on a floppy, I can get them to the
>system, but otherwise I'm going to have to wipe and use a different snapshot.
No you are not hosed. boot single user and do ldd on login. Then check
out /usr/lib/libkrb*
christos