>I've been planning a snapshot for a while, but then the the R4000
>ld.elf_so thing got in the way.  I've also got some new bootblocks that
>are ready to be committed after I hear the reports of one more test and
>there's also a few funny disk reports - the non-existant drives (not
>recent apparently) and reports of disks that sound like they're showing
>up on asc1 on a 5000/200 instead of asc0.  

I was about to say that the non-existent drives must be pre-SCSI-2
devices. I testsed some old pre-scsi-2, SCSI-1 CCS-ish drives at
Stanford.  Initially they didn't work: the geometry-sense code we
lifted from the MI scsi confused them. Perhaps the same is happening
here?

Waiting for the new bootblocks sounds like a great idea.
Especially since we want to ship these in 1.5.

>I think it'd be better to
>hold off on a snapshot just a little longer...

Emacs. Must fix emacs under X. (Did someone fix it already)?  Didn't
someone report over summer that applying the patches I posted back
whenever actually worked?  That suggests the problem lies elsewhere
than we'd thought.


>>From memory, it takes about 18ish hours on a /260, and another couple
>to build xsrc as well.

On what kind of disks? (a Richocet would take at least 18 hours just
to  update the source...)