On Tue, 5 Apr 1994 newsham@uhunix.uhcc.Hawaii.Edu wrote:

> Hi,
>   I just (finally) upgraded the binaries on my system with the
> 940319 binaries from eunet.  I'm still running a 744 kernel for
> the time being.  I've noticed two problems so far though:
> 
>   o mfs doesn't mount properly now.  An IOCTL error occurs.

I'm having no problems with mfs.. I'm running the same configuration as 
you.
  
>   o when I login the tty is set at -echoe so my erase characters
>     show up visibly until I stty echoe.

This doesn't happen to me.
 
> Is the mfs problem due to my /usr/sbin and kernel mismatch?  (Will
> this go away as soon as I upgrade kernels?).

I'm having difficulty with any kernals >744 I don't know why.
  
> Also telnet still reports an ioctl error trying to set the TOS.  I
> thought the 744 kernel had the proper changes for this already and
> that the new binaries worked fine (this problem came in with an
> ioctl change between 720 and 744 kernels as I remember it).

Yeah, I thought the same thing, but apparantly the 940319 binaries are 
still incorrectly compiled?  When I boot with the 940325 kernel, this is 
exactly what happens on my screen, can somebody out there give me a 
clue, because I can't figure it out:

NetBSD 0.9a (GENERIC) #0: Sat Mar 26  06:47:37 EST 1994
  sjr@istari:/usr/local/src/NetBSD-current/sys/arch/amiga/compile/GENERIC

real mem = 8388608
avail mem = 5529600
using 64 buffers containing 524288 bytes of memory
3 Amiga memory segments
segment 0 at 08c00000 size 00800000
segment 1 at 00200000 size 00200000
segment 2 at 00000000 size 00100000
Zorro II memory mapped at 01bfc000-01dfc000
Realtime clock A2000
rtclock 0 [1/9]
par0 [1/6]
grf0: 640x400 4 color custom chips display
grf0 [1/7]
ser0 [1/3]
dma0: a2091dma
a2091scsi: dma bounce buffer at 01dec000
scsi0: scsi id 7
a2091scsi0 [514/3]
sd0: FUJITSU M2614S rev C101, 356178 512 byte blocks
sd0 at a2091scsi0, slave 0
sd3: QUANTUM P105S 910-10-94x rev, 205075 512 byte blocks
sd3 at 2091scsi0, slave 3
sd6: MAXTOR 7345-SCSI rev 0960, 675484 512 byte blocks
sd6 at 2091scsi0, slave 6
changing root device to sd6a
trapsignal(3, 11, 158268, 26a3c, 18048)
Apr  6 16:40:57 init: fatal signal: segmentation fault
trapsignal(5, 11, 158268, 26a3c, 18048)
Apr  6 16:41:31 init: /bin/sh on /etc/rc terminated abnormally, going to 
single user mode.
trapsignal(7, 11, 158268, 26a3c, 18048)
Apr  6 16:41:33 init: fatal signal: segmentation fault
trapsignal(9, 11, 158268, 26a3c, 18048)
Apr  6 16:42:05 init:  /bin/sh on /etc/rc terminated abnormally, going to 
single user mode.
trapsignal(11, 11, 158268, 26a3c, 18048)
Apr  6 16:42:07 init: fatal signal: segmentation fault
trapsignal(13, 11, 158268, 26a3c, 18048)
Apr  6 16:42:42 init:  /bin/sh on /etc/rc terminated abnormally, going to 
single user mode.
trapsignal(15, 11, 158268, 26a3c, 18048)
Apr  6 16:43:14 init: fatal signal: segmentation fault
trapsignal(17, 11, 158268, 26a3c, 18048)
Apr  6 16:43:48 init:  /bin/sh on /etc/rc terminated abnormally, going to 
single user mode.
trapsignal(19, 11, 158268, 26a3c, 18048)
Apr  6 16:43:51 init: fatal signal: segmentation fault
trapsignal(21, 11, 158268, 26a3c, 18048)
Apr  6 16:44:25 init:  /bin/sh on /etc/rc terminated abnormally, going to 
single user mode.
trapsignal(23, 11, 158268, 26a3c, 18048)
Apr  6 16:44:57 init: fatal signal: segmentation fault
trapsignal(25, 11, 158268, 26a3c, 18048)
Apr  6 16:45:00 init:  /bin/sh on /etc/rc terminated abnormally, going to 
single user mode.
trapsignal(27, 11, 158268, 26a3c, 18048)
Apr  6 16:45:34 init: fatal signal: segmentation fault

.

.

.

(continues forever with this same pattern)  What's going on??


 o/ \o/  o  <o   o  o   o Mi dispiace, ma non parlo italiano. :-) 
<|   |  /|\  |> <|><|> <|\ Ciao ragazzi! :-)   diavolo@azure.engin.umich.edu	
/|  / \  /| / \ //  \\ / \  La universita' di Michigan! Va blu!!!!!!!!!!!!!
"""""""""""""""""""""""""""" Finger for PGP Public Key Block and Fingerprint



------------------------------------------------------------------------------