On Sun, 18 Jul 1999, Brian D Chase wrote:

> > Strange things:
> > 	1) If the VAX boots when the 'timed' master is down, timed drops a
> > 		core.
> 
> Hey, be happy that that's the only thing dumping core on you :-)  My root
> filesystem is littered with *.core files.  There were some problems with
> ld.so under 1.4, the 1.4.1 binary release is on its way so hopefully the
> most significant problems experienced with 1.4 will go away.

	Expect a test snapshot of 1.4.1 to be up in a couple of days.

<unnecessarily_complicated_explanation>
	A 1.4.1 kernel built with 1.4 userland is no winner, but a
	1.4.1 kernel (built with a (1.4.1 userland running under a
	1.4.1 kernel built with the 1.4 release userland)) with a 1.4.1
	userland ((built under a 1.4.1. kernel built from the 1.4
	release userland) under the release 1.4 userland) looks like it
	might be better.
	I'm now using it to build the 1.4.1 userland which will be put up
	as a snapshot, unless I get lost in the process :)
</unnecessarily_complicated_explanation>

> > 	2) If I re-launch manually timed, after booting up the linux box,
> > 		usually the VAX hangs.
> 
> Yeah, that's always been the case.  If you get the time set correctly in
> single user mode, everything seems to be fine.  If you try setting the
> time from a cold booted system under multi-user mode, it just hangs.  I've
> never bothered to understand precisely why this happens in multi-user
> mode.  Time to submit a problem report on the matter I guess.
> 
	Please do!

		David/absolute

                -=-  "Just when everything was making sense"  -=-