Thanks for responses.

I almost responded first thing this am. Having waited I've let
my brain engage. At least into low gear. :-)

> > I've ftp'd all the binary packages from the distribution ...
> > no kernel
>
> You need the install FAQ

Ok. Let me rephrase that. As per sect 3.20 of the FAQ, I like to
do things in non-standard ways. I wouldn't expect everybody to have
a TK50 drive, and don't think there would be that many who would want
to create the ~90 floppies necessary to transfer everything.
There's always another way.

I had a TK50. Just bought it recently and borrowed a controller.
It lasted all of 1 write pass, and 0 read passes before it failed on me.
Later with a friend's help I was going after the miniroot kernel.

However the suggestion of re-reading the FAQ is a valid one. I had
overlooked that 'racopy' has become 'copy'. That would explain one
problem I had.

I also realize my error when it comes to cpio. Silly me. Got it in
my mind that file2 was the cpio archive of the start of the root.
It's not. It's a filesystem that needs to be copied.

> > I've even tried to pull the one out of tk50-file2,

> generic kernel gets installed to your ra0b partition as part of the 
> install process. The you copy it to ra0a.

All the more reason I wanted to try to pull it out. Again that
still doesn't explain why it doesn't sit in one of the available
gzipped tar images or as one itself. If the generic kernel of the
miniroot will run on a 630/730/750/2000/3000 then it's perfect to
provide as a generic kernel in the distributable binaries area.

On the other hand, you've given me some light and I realize I can grab
the RX install to pull the kernel out of it, assuming that it's not a
copy of the pre-alpha release. Or better yet, I'll just vms-copy the
miniroot over to the a partition of drive 2, either mount or boot it and
pull out the kernel that way. 


Thanks for the help!

Zach