[EMAIL PROTECTED] writes: >> I think that its really important that the live cd is a true subset of >> what a user would get from a full indiana (or solaris next as the case >> may be) install. From a usability perspective the closer to the finally >> installed bits the better - including default settings etc. I'd be >> strongly against delivering a gnu userland if that wasn't the default >> when the bits are finally committed to disk. > > The current thinking with OpenSolaris has been to retain backwards > compatibility for commands in existing directories such as /usr/bin and > /usr/sbin and instead introduce the /usr/gnu hierarchy to contain those > commands which conflict with existing versions. Then, a new user > coming from a GNU/Linux background will get most of what they want just > by putting /usr/gnu/bin at the front of their PATH (or at least until > more external open source has been integrated into OpenSolaris). > > I think for the moment that Indiana should follow this precedent since > Indiana should replace Solaris Express and eventually find its way out > in a long-term support release such as Solaris 11^H^HNext. And while > we definitely want to attact new users to OpenSolaris, we certainly > want to avoid creating new issues for existing users of the > technology.
Beyond that (with which I agree), doing otherwise would involve chartering a Major, and a whole lot of ARC legwork, which is rather a lot for you to accomplish in the given timeframe. > Now perhaps we should be making a "switch" from the traditional > user-land being the default and instead promote /usr/gnu to that > position (/usr/sunos anyone?) but that's a discussion for another day. I think "discussion" maybe too kind a term for what would ensue, but yes. :) > In summary, I don't see an issue[1] with delivering the live CD with > both the traditional (default) user-land as well as the /usr/gnu > hierarchy. I think both sets are pretty small, I can't imagine the CD size would be unduly affected. > When new users get created, perhaps an option should be > supplied to provide them with a .profile (or equivalent) that puts > /usr/gnu/* at the front of the appropriate environment variables? Or > as I've seen suggested before, perhaps /usr/bin/bash should do this by > default anyway. > I don't think bash (or any other shell) doing this is why, I think there are many people use those shells but wouldn't want the otherwise alien environment. Though you didn't mention it, I'm also very much against an /etc/alternatives-like setup, it does nothing but create (and promote) chaos. -- Rich _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
