ah that is right, i had forgotten.. i encountered the same problem with the
tahoe binaries.. i started with reno, and then did indeed use the Q tarball=
s
after i had a reno system, and then recompiled the tahoe world once=20
booted into the very confused system that booted a reno kernel from=20
ultrix boot blocks with the Q binaries in userland and the tahoe and Q=20
sources. it all got started with an ultrix boot tape, but unfortunately,
the ultrix disklabels are not compatible so i had to with a (sort of broken
due to flaky tk50 drive) netbsd 1.2 boot tape write a disklabel..=20
this was all on a uvII. once all the pieces were in the right place it
booted right up and ran fine. it's very fast on the old iron.
funny, now im not having nearly as easy go at getting reno to boot on the
4000/600.. (note that i had to copy init into /sbin , maybe a couple=20
other things, for the reno kernel to bring the system up.. :)


happy hacking,
isildur


On Fri, 5 Apr 2002, Jochen Kunz wrote:
> Ahhhm. I had the same idea to get -Tahoe on my VAX. But when I extracted
> vmunix from rootdump.gz I noticed that the binaries are for the Tahoe
> machine, not VAX. Also: usr.tar and src.tar are both cut short.
> Plain 4.3 is pure VAX but dosn't know about disklabels on the disk, so
> this may be hard to get on an disk, that the kernel doesn't know.=20
> So I asume you mean Q. with "4.3 images"?=20
> --=20
>=20
>=20
>=20
> tsch=FC=DF,
>          Jochen
>=20
> Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
>=20