On Wed, 29 May 2002, Jochen Kunz wrote:

> On 2002.05.29 17:37 Lord Isildur wrote:
> 
> > I think he mentioned that that 14 hours on a 4k60 was a very
> > low-memory configuration, way lower than 'normal'. 
> That was ragge... 
> I think we can asume that he has at least the 8MB on board. 

he had cranked it down to recognize only 2 megs.. for testing purposes. 

> > on a vax 4000/600, running tahoe, it compiles the _entire_ source tree
> > in under 30 minutes 8-)
> Did you get it stable meanwhile? I would love to have this stuff on my
> VAX 4k400...

I got it stable, but i never did fix some problems with probing the 
q-bus. The result is that booting is not very smooth. I never got the time
to fix it properly, and i decided that when i do , i'll be concentrating on
fixing it in reno (tahoe is so similar on the vax that it should be fixed 
there too) because reno is still almost as fast, and has some of the ffs
improvements, the virtual filesystems, and will be easier to get 'modern' 
things to compile under. It was a huge chore to get anything to compile in
tahoe. well, not _huge_ but it was still a chore (getting a recent gdb to
compile in tahoe was fun!) (bash went pretty easily, as did top, i never got
a prolog interpreter, and i tried half a dozen of them, and cmu common lisp
gave me a big hassle so i just used franz.. i got most of the way through
compiling freeciv 10, but the X11 is R4 and i guess the libraries disagrees
enough that i gave up on it.. i also gave up on compiling ssh under 
tahoe.. and so on and so forth)
Anyway, it is certainly stable, and once it is booted it is just fine. 
Ive had uptimes greater than 100 days with it, and since i dont like to have
computers running idle, i usually had some kind of dumb thing running on it
just to use up cycles :)
contact me off-list and i can get you a copy of my modifications to the 
source. i had to work around the missing emodd instruction in libc as 
well.

isildur