Re: July 2 22:06 i386 snapshot broken?

[Nick Holland <nick@holland-consulting.net>]

Would I be correct in guessing that you didn't use the snapshot boot
floppy to boot the system?

I got the exact same message by using a RELEASE boot floppy and trying
to Install the snapshot.  My *guess* is this is due to using the
release install script on the snapshot, or perhaps not upgrading your
/etc files properly as per the warnings from the developers (assuming
you did an upgrade).

The reason I guess you didn't use the 7/2 snapshot boot floppy is
because I can't get the floppy29.fs to work on ANY machine I tested
here (tested five) -- I get an error something like "UVM_Fault Fatal
Fault in Supervisor Mode".  Unfortunately, can't get any more accurate
than that without difficulty, as the machine then clears the screen
and reboots itself.

The machines I tested:
* Compaq Deskpro 6000 PII-266, (good PNP, PCI, but a Compaq and thus,
weird), SCSI disk system, 128M RAM.
* Zenith Z-Station EX P-90 (early PCI, PNP BIOS.  Probably buggy), 16M
RAM, IDE drive
* Dell Optiplex P-100 (Dell's wierd 486BIOS extended to PCI, not PNP),
32M RAM, IDE drive
* Unisys CWD5001 P166 (seemingly good PCI, PNP, fairly "normal"
system), 64M RAM, IDE.
* Unisys CWD4001 486/100 (No PCI, fairly "normal" box), 16M RAM, IDE.
(clean installs on each, not upgrades)

Got seemingly the exact same results on all these boxes.

I also tried a bootable CD-R made with the cdrom29.fs from the same
snapshot, got the same result, though only the Compaq is bootable from
CD-ROM.

Comparing notes with a friend, turns out that he experienced the exact
same results I did.

If there is need for a more detailed report (i.e., serial console,
logging output), I can do so with some effort, but as I suspect that
I'm not the first to find this problem and the developers can probably
reproduce it with ease, I didn't feel the need to do that at this
point.

I don't think it is a bad boot floppy, as the kernel obviously loaded
sucessfully, and it was well through the dmesg when it chokes... 
Plus, tried creating images on two different computers using different
programs (dd and rawrite.exe), and five different computers, and got
the same results on a CD-ROM (made from a different file).  

When I tried to use the 2.9-Release boot image to install the
snapshot, I got the same results you reported (Kerberos errors, and
could not log in)...  HOWEVER, the snapshot kernel DID boot properly,
so the problem seems to be only in the boot disk images. 

(that's what I get for not following my own advice about "-current is
for the highly experienced only" 8-)

Nick.


bpalmer wrote:
> 
> I had the same problem w/ the july 1st shapshot.  I get this on bootup and
> login attempt:
> 
> /usr/libexec/ld.so: krb4-or-pass: libcrypto.so.6.0: No such file or
> directory
> 
> I get a few of these in the boot script and also any time I try to login.
> 
> I booted in single mode and did a:
> 
> ln -sf libcrypto.so.5.0 libcrypto.so.6.0
> 
> which is a horible hack,  but seems to work (so far) for most apps...
> 
> - Brandon
> 
> ----------------------------------------------------------------------------
>  b. palmer,  bpalmer@crimelabs.net            pgp:crimelabs.net/bpalmer.pgp5

-- 
http://www.holland-consulting.net/