Stephen Hahn writes: > 1. Must /usr/gnu be a subdirectory of /usr, or can it be a separate > filesystem?
It'd be simpler there. But any place would probably do. > 2. Should /usr/gnu have a structure that allows old versions of > specific tools to be delivered, along with the best-current (i.e. > most preferred of recent) version? Ouch. The other key question related to that is the operation with zones. A sparse zone will inherit /usr and thus get a read-only copy of /usr/gnu -- meaning that every zone has the same tools as the global zone. Perhaps not what was desired. The multi-version question is just plain ugly, because some tools have non-trivial (and incompatible!) configuration file formats. Having multiple versions at once means solving those problems as well. (Maybe a `uidfs' would solve it. It mounts on /usr and each user gets to pick and choose the objects he wants to see in /usr/bin. Just kidding. Really. ;-}) > 3. Are the g-prefixed commands in /usr/bin still required, or do we > stop adding new ones? Unless there's a portability reason to have the g* forms (I don't think we're the only platform with "gcc," "gmake," and "gawk," so having those is goodness), I wouldn't think we'd necessarily want to add more of them. They're sometimes handy for users who want to stay in a traditional UNIX environment and occasionally grab GNU-ish tools (with /usr/sfw/bin or /usr/gnu/bin or whatever at the _end_ of the $PATH), but that handiness isn't very substantial. I don't need "ups" for /usr/ucb/ps, so I probably don't need "gps" for GNU ps. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
