Hi Nico, Nicolas Williams p??e v po 22. 03. 2010 v 12:08 -0500: > 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. >
It is issue for some of us and our point of view. ACLs impacts ls, chmod (cp, tar?). Linker incompatibility impacts those who invokes linker directly. I do not care about "sleep" command differences, where I care it is sacrifice Solaris specific features (which we present as our significant difference against competitors) for some other minor features. We see and hear "it is temporary". Roadmap? Solaris ls was improved by community member to level matching GNU ls. Still GNU ls is in system. Why? What are rules to remove GNU tool from prefered PATH if it is in conflict with Solaris features? Aren't you see confusing for newcommers simple scenario which is happening on OpenSolaris today? OK, cool, I have ZFS and I heard ACLs are supported there. How should I work with them. I am Linux guru, so let's try setattr. No, it is not here. Hmmmmm. docs.sun.com. Great it say ls/chmod is supporting it. OMG, not mine. OMG, what is wrong? Crappy Solaris, what a mess. Yes, we have "grep -R" and "tar xzf" for these users now. But we are presenting them very inconsistent situation now. Yes, old Solaris users will survive it most probably (unhappy that we are leaving them with old tools saying GNU is future even if incompatible and with lack of features), it will cost them only some time and money. Best regards, Milan
