ZFS Boot Support Binding Change [PSARC/2008/301 Self Review]

[Don Cragun]

>Date: Tue, 06 May 2008 15:01:42 -0700 (PDT)
>From: Mark Maybee <maybee at jurassic.eng.sun.com>
>
>The ZFS Boot project team wishes to record the following information:
>
>Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
>This information is Copyright 2008 Sun Microsystems
>1. Introduction
>    1.1. Project/Component Working Name:
>	 ZFS Boot Support Binding Change
>    1.2. Name of Document Author/Supplier:
>	 Author:  Lori Alt
>    1.3  Date of This Document:
>	06 May, 2008
>4. Technical Description
>
>A. SUMMARY
>
>This case seeks to change the binding of PSARC/2006/370 (ZFS Boot
>Support) from minor binding to patch binding.
>
>B. PROBLEM
>
>The selection of "minor" for the binding of this case was
>an error in the original case filing.  ZFS Boot Support was
>always intended for integration into a Solaris update release.
>It doesn't establish any interface changes that would prevent
>it from being implemented as a patch.  It has been designed
>from the outset as a feature that could be back-ported to
>an update release and released as a patch.
>
>C. PROPOSED SOLUTION
>
>Change the binding from "minor" to "patch".

Given that ZFS does not yet conform to POSIX and UNIX standards
requirements (even though the zfs(1M) man page says that ZFS provides a
"standard POSIX file system"), that Solaris 8, 9, and 10 and their
updates are covered by several UNIX branding licenses, and that
(according to PSARC 2006/370) it is not possible to go back to a UFS
root after upgrading to a ZFS root, I STRONGLY object to allowing a
patch binding for this case unless a TCR is attached saying that this
feature can't be patched into earlier releases until all POSIX and UNIX
standards conformance bugs have been fixed.

I'm sorry that this information is not available outside of Sun, but
for those inside Sun, the heading "for ZFS:" on web page
http://stds-test.sfbay/resources/brand_status.html can be used as a
guide to known ZFS standards conformance bugs.

The fact that ZFS was granted a conformance waiver to be integrated
into the ON-NV gate before it passed the test suites (with a promise
that the bugs would be fixed before Nevada is released) can't be used
as a waiver for branded products that are already shipping.  Sun has
certified to The Open Group and many of our enterprise customers that
Solaris 8 and its updates, Solaris 9 and its updates, and Solaris 10
and its updates (current and future) do and will continue to conform to
UNIX branding requirements.

 - Don

>
>6. Resources and Schedule
>    6.4. Steering Committee requested information
>   	6.4.1. Consolidation C-team Name:
>		ON
>    6.5. ARC review type: Automatic
>    6.6. ARC Exposure: open