[9fans] KFS between 4ed and 3ed

[9fans] KFS between 4ed and 3ed

[Lucio De Re]

This is odd.  I booted a 3ed system with a 4ed disk and almost
panicked when KFS announced its intention to "format" the disk.

Once the system was actually up, I started disk/kfs and mounted
the disk and was relieved to discover that the disk is still
readable, at least under 3ed.

Any idea what that was all about?  I shut the system down cleanly,
was there anything else I ought to have known?

What will happen when I try to use the disk in its 4ed impersonation?

++L

Re: [9fans] KFS between 4ed and 3ed

[Russ Cox]

Assuming you told it not to ream the disk,
rebooting with a 4e kernel should just work.

Russ

Re: [9fans] KFS between 4ed and 3ed

[Lucio De Re]

On Wed, Aug 07, 2002 at 04:57:39PM -0400, Russ Cox wrote:
>
> > What will happen when I try to use the disk in its 4ed impersonation?
>
> With a 3e kernel, most of the binaries
> won't work (new system call interface).
>
One day I'll unlearn to squeeze all information out of my e-mail
for the sake of brevity :-(

What I meant was, I'm going to use the disk in its previous role,
which was in a strictly 4ed workstation and/or CPU server.  Will
it even boot?

> Kfs shouldn't have tried to ream the disk.
>
It certainly didn't succeed, as tar of the entire filesystem delivers
929026560 bytes of readable data.  What worries me is whether I'll
be able to access that filesystem once I reboot the 3ed system I'm
using presently.  I think I'll back up the whole lot as soon as I
have a host to do it to.

++L

Re: [9fans] KFS between 4ed and 3ed

[Russ Cox]

> What will happen when I try to use the disk in its 4ed impersonation?

With a 3e kernel, most of the binaries
won't work (new system call interface).

Kfs shouldn't have tried to ream the disk.

Russ