On 03/22/10 10:08 AM, Nicolas Williams wrote:
> On Mon, Mar 22, 2010 at 09:46:27AM -0700, Darren Reed wrote:
>    
>> On 22/03/10 07:21 AM, Alan Coopersmith wrote:
>>      
>>> Milan Jurik wrote:
>>>        
>>>> Alan Coopersmith p??e v p? 19. 03. 2010 v 16:39 -0700:
>>>>          
>>>>> Garrett D'Amore wrote:
>>>>>            
>>>>>> I'm also of the opinion that it is a mistake to sacrifice familiarity
>>>>>> for our paying Solaris 10 customers in favor of familiarity for people
>>>>>> coming from Linux.
>>>>>>              
>>>>> But clearly all our paying Solaris 10 customers already have dotfiles to
>>>>> set $PATH, given how useless the default Solaris 10 $PATH is.
>>>>>            
>>>> I would be very carefull with claiming "all our paying Solaris 10
>>>> customers"...
>>>>          
>>> Okay, make it "Any Solaris 10 customer (paying or not) who actually wants
>>> to use the system" - given the lack of some basic commands in the default
>>> path, such as /usr/sbin/ping or /usr/ccs/bin/make, the Solaris 10 default
>>> PATH shows we've long required customers to change the default PATH to
>>> actually make the system usable to either sysadmins or developers.
>>>        
>> And...?
>>
>> I doubt there exists a system where system administrators
>> and/or developers don't customise their path. Go back and
>> read Octave Orgeron's email.
>>      
> Moreover, the new default path is backed into the user's dot files at
> account creation time.
>
> If you deploy Solaris Next in an environment where user accounts already
> exist then those will be completely unaffected.
>
> I don't understand the sturm un drang over the /usr/gnu/bin-first-in-
> default-PATH thing.  It's a NON-ISSUE (except for GNU tools like ls and
> chmod where lack of support for Solaris-specific features creates
> problems.
>    

And "cp".  And make.  And....

This issue is not something "small".  Lets take the discussion where it 
belongs in 2010/067, since that's the case that proposed the /usr/gnu 
path change.

     - Garrett

> Nico
>    

Reply via email to