> ...Many sage words from various people elided...
> I thought we're talking about making /bin/sh being ksh93, NOT bash
> Using bash would be the wrong direction. Indiana should make thinks
> BETTER than Linux.

Perhaps different people are talking about slightly different things.  
Here's my attempt at disentanglement.

1)  High order goal (perhaps the highest for Indiana) remove barriers
     to entry for the Linux trained.

A)  Highest order goal for Solaris (classic) don't ever break anything

For (1) I think the primary discussion has been about what default  
shell to provide to user (as an exemplar of this goal, clearly it  
flows into many decisions).

For the question of what to do about /bin/sh (especially since it's  
encumbered) I don't think that having it be ksh93 should be a  
showstopper for the Linux newcomer ... we might be sports and have  
the default prompt be something other than a simple # for root to  
make it explicit that we're in ksh93 (e.g. ksh93#).

Perhaps more entertainingly, can we somehow make RBAC work invisbily  
enough that for the "standard" developer desktop that a special sudo  
is just a default shell function which does the right pfexec (or  
pfksh or whatever the ideal syntax is) and have the SXDE/Indiana  
default be to create a user account which has the right privs?

Retraining their fingers (and minds) is a huge barrier as Tim aptly  
noted. Migrating them to a better facility (if to a first  
approximation it does the "same" thing for the 99% use cases) can be  
a compelling story.

However, if it's "better" but different in the first N things the  
poor user tries, it's not likely to be used enough for the  
"betterness" to matter.

Keith H. Bierman    [EMAIL PROTECTED]   |  [EMAIL PROTECTED]
Strategic Engagement Team                   | AIM:  
kbiermank                |
<speaking for myself, not Sun*> Copyright 2007




_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

Reply via email to