Alberto Ruiz wrote: > > > 2007/6/29, Richard Lowe <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>>: > > > > 3.3) Familiarization > > > > FAM-1: Provide a set of packages in the default install > > and network repositories that users would typically > > expect to see with a similar UNIX operating system > > eg. GNU/Linux. > > That's very vague, because it's so hard to gauge "What people > expect", it > varies based on the value of "people". (the longer you've used > something, > the more you come to expect precisely it, and nothing else, as I > think we've > all seen in prior arguments about indiana). > > > People would expect things like tab completion in the shell (and some > shortcuts like Ctrl+R), top, ps aux, vim, tar zxvf to work, they don't > care if they are GNU or not. I think that we should, at least, provide > information to the user, when usual Linux commands are typed, on how to > get the same information. For example, typing top, we could point them > to the equivalent tool in OpenSolaris, kind of the Google's "Did you > mean" or the new stuff in the ubuntu shell. > > Personally, as a Linux user, I find the /usr/sfw /usr/gnu split really > odd, and it gets even worse when default PATH is not managed, I think > that the approach explained above would be less painful, let's try to > provide the same "interfaces" using our tools instead of installing > duplicated tools, and whenever a GNU tool provide a functionality that > OpenSolaris lacks, we just put it. But I think that one and only > installation prefix helps people. I would say that the current Unix path > standards are hard enough to understand to make it even more complex.
The /usr/sfw is being obsoleted, and things in there being moved to either /usr or /usr/gnu, depending on conflicts with existing /usr entries. Ideally /usr/bin *and* /usr/gnu/bin should *both* be on your path (and not to mention some others such dirs too...) - this way when you do a "which" (csh style) or "type" (sh style), you will at least find the tools... If you, as a user, prefer the /usr/gnu equivalent, then simply re-arrange your path in you're login-shell scripts, but it makes sense for compatibility to keep /usr/bin as a first-preference - maybe over time, we could move to the opensource equivalents, but that's not something to be undertaken lightly since users tend to have some very obscure dependencies... I use the bash "type -a <command>" quite a bit to find all occurrences of a given command in my path - and my PATH has lots of entries, gained over many years or working on Solaris... Darren. _______________________________________________ indiana-discuss mailing list [email protected] http://opensolaris.org/mailman/listinfo/indiana-discuss
