Date: Mon, 20 Jul 2009 17:22:27 -0700 From: Kip Macy <kmacy@freebsd.org> To: Aristedes Maniatis <ari@ish.com.au> Cc: freebsd-current@freebsd.org, Jurgen Weber <jurgen@ish.com.au> Subject: Re: Problematic upgrade from 7.2 to 8.0 with ZFS file system Message-ID: <3c1674c90907201722vcff2ea4pb779da6e3524d175@mail.gmail.com> In-Reply-To: <4A64FC12.9050709@ish.com.au> References: <4A5D4D25.3040908@ish.com.au> <3c1674c90907201501j42f29bfbl987419edf04b1a8b@mail.gmail.com> <4A64F35E.6070501@ish.com.au> <3c1674c90907201556n7dbd385fucb2d49aa2b1a1416@mail.gmail.com> <4A64FC12.9050709@ish.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> My only suggestions are improving the freebsd-update tool (is Colin Percival > reading this?) to give relevant feedback, moving UPDATING to somewhere > useful for non-source updaters and ensuring the docs clearly state the > seriousness of this particular issue. When the import was done, there should have been a minimal compat layer so that v6 tools wouldn't die when talking to a v13 system. It is too late for 8.0 to do that, depending on time and complexity I'll look in to doing that for 7.3. At this juncture there isn't a convenient stop-gap. Given that there is no central source to read for individuals updating. I think it makes sense for freebsd-update to at the very least check if it is installing on a system running ZFS v6. You'll need to talk to Colin Percival about his availability to do that. Cheers, Kip
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3c1674c90907201722vcff2ea4pb779da6e3524d175>