(Illustration by Gaich Muramatsu)
It did turn out to be just an impatience error -- I should have waited for venus to initialize. I have no further problems with either kernel 2.1.127 or 2.1.130. I still think the "check kernel date" error in the subject above is pretty vague, though. Also, in an unrelated question, is it usual for codasrv to be taking up 116 megs of ram? :) 1:51pm up 12 min, 1 user, load average: 0.00, 0.07, 0.10 39 processes: 38 sleeping, 1 running, 0 zombie, 0 stopped CPU states: 0.7% user, 0.9% system, 0.0% nice, 198.5% idle CPU0 states: 0.2% user, 0.3% system, 0.0% nice, 99.0% idle CPU1 states: 0.2% user, 0.3% system, 0.0% nice, 99.0% idle Mem: 257244K av, 245804K used, 11440K free, 19860K shrd, 89584K buff Swap: 513936K av, 236K used, 513700K free 14304K cached PID USER PRI NI SIZE RSS SHARE LC STAT %CPU %MEM TIME COMMAND 152 root -5 -5 116M 116M 1312 1 S < 0.0 46.5 0:16 codasrv 232 root 0 0 9360 9360 1684 0 S 0.0 3.6 0:01 XF86_SVGA 147 root 2 0 5420 5420 1644 1 S 0.1 2.1 0:02 venus 250 root 0 0 1388 1388 1160 1 S 0.0 0.5 0:00 xconsole 235 root 0 0 1208 1204 1068 0 S 0.0 0.4 0:00 xdm 219 root 2 0 1176 1152 784 1 S 0.1 0.4 0:03 sshd 221 ben 7 0 1028 1028 748 0 S 0.0 0.3 0:00 zsh 190 root 0 0 984 984 752 1 S 0.0 0.3 0:00 xntpd 158 root 0 0 868 856 600 1 S 0.0 0.3 0:00 updatesrv 157 root 0 0 832 820 616 1 S 0.0 0.3 0:00 updateclnt 138 root 0 0 816 816 664 1 S 0.0 0.3 0:00 startserver 176 lp 0 0 824 812 600 1 S 0.0 0.3 0:00 lpd 224 root 0 0 808 792 700 1 S 0.0 0.3 0:00 xdm 280 ben 17 0 728 728 548 0 R 1.3 0.2 0:00 top 201 root 0 0 700 696 532 0 S 0.0 0.2 0:00 amd Yikes! That's one big process. Ben -- Brought to you by the letters A and N and the number 11. "Bill Gates is a talented evil man." -- Chip Salzenberg Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.Received on 1998-11-30 17:05:54