On Fri, Jun 6, 2008 at 12:09 AM, Nicolas Williams <Nicolas.Williams at sun.com> wrote: > On Thu, Jun 05, 2008 at 11:59:51PM -0500, Mike Gerdts wrote: >> 2. Project Summary >> ... >> 2.2. Risks and Assumptions: >> libfstyp(3LIB) makes use of plug-ins that reside in >> /usr/lib/fs/hsfs. These plug-ins are unlikely to be available >> during early boot and as such ufs mounts that previously >> worked may not work in the absense of vfstab entries unless >> "-F ufs" is used. > > Perhaps early in boot libfstyp could just fallback on default_fs(4), > which we'd then keep. Alternatively, move to /lib/fs/ the plug-ins > needed early in boot.
I was thinking that if we choose to fall back to something (perhaps something that is defined in /etc/default/fs) it should only be done if libfstyp() returns one of the following for that particular file system type. FSTYP_ERR_MOD_NOT_FOUND - Requested file system module not found. FSTYP_ERR_MOD_DIR_OPEN - Directory cannot be opened. FSTYP_ERR_MOD_OPEN - Module cannot be opened. Otherwise we are in the same situation with misleading error messages that were mentioned elsewhere in the thread. I think that keeping /etc/default/fs is not a terribly bad thing, especially considering that volcopy likely still needs a default file system type. > I could sponsor your fasttrack some time next week, but not before. Sounds good, thanks. -- Mike Gerdts http://mgerdts.blogspot.com/
