Quoth Nils Goroll on Thu, Feb 07, 2008 at 10:59:00AM -0800:
> I would like to suggest a project to get the infrastructure to publish my code
> and to allow others to work with it.
> 
>     - A short (one or a few words) synopsis of the Project's purpose,
>       and an optional shortened or decorative name (see 4.1).
> 
> Suggested Project name (with a bit of self-irony): Everest
> 
> Suggested Project name for those who don't like this kind of
> humor: smf-mount

Either is fine by me.

>     - A list of Community Groups sponsoring the Project.
> 
> would SMF sponsor this?

I think we should.  You might also seek sponsorship from the storage
community.

>     - A list of Participants constituting the initial Project Team,
>       including a single individual who will serve as the preferred
>       point of contact for matters regarding the Project.
> 
> me (nigoroll)
> looking for others
> 
>     - A one-paragraph description of the Project, for an audience of
>     Participants who may not be familiar with the area in which work
>     is proposed.  This should contain a brief description of the
>     problem(s) the Project is expected to solve, and of the manner in
>     which it will do so.
> 
> In Solaris, there exists not generic method to mount filesystems which
> depend upon each other but are of different FSTypes like NFS, ZFS, UFS
> or lofs. The classic is that a lofs mount of an NFS mount or even an
> UFS mount fails (in some cases), if simply being added to the vfstab.
> The projects aims to provide a framework and (a) tool(s) (suggested
> name: mountadm) to allow for arbitrary mountpoints to be configured
> to be automatically mounted (including filesystem-check) and unmounted
> in the right order, which is determined by technical dependecies between them.

Are you also planning on allowing administrators to make service
instances depend on filesystem mounts?

>     - A listing of related ongoing or proposed Projects, including
>     information about any dependencies on or by this Project and any
>     duplication of purpose or overlap with other ongoing work.  This
>     listing should also include the name of the consolidation the
>     Project Team is targeting, if applicable.
> 
> ZFS, which does not normally integrate into a general mount/umount
> concept.

You should also say that you're targeting the O/N consolidation.


David

Reply via email to