Hi Everyone, I agree Jason. And I still want to voice the need for the new OGB to have a community conference to define the standards for OpenSolaris. Things like this should be decided in the open as a community. I'd even like to see a real standard created that will help defuse these issues and provide consistency. Last time I checked, Solaris is UNIX no Linux. The same should be true for OpenSolaris. GNU should be nothing more than another userland flavor under /usr/gnu with g* sym-links in /usr/bin. The default userland tools should be POSIX and Open Group Single Unix Specification compliant. Enhancing our userland tools is the way to go, not taking the short-cut to GNU and selling out.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Virtualization Architect and Consultant Web: http://unixconsole.blogspot.com E-Mail: unixconsole at yahoo.com *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* ----- Original Message ---- From: Jason King <ja...@ansipunx.net> To: John Plocher <john.plocher at gmail.com> Cc: Alan Coopersmith <Alan.Coopersmith at sun.com>; Garrett D'Amore <gdamore at sun.com>; shell-discuss at opensolaris.org; PSARC-ext at sun.com; Milan Jurik <Milan.Jurik at sun.com>; johansen at sun.com; Darren Reed <Darren.Reed at sun.com> Sent: Tue, March 23, 2010 9:39:27 PM Subject: Re: More ksh93 builtins On Tue, Mar 23, 2010 at 7:55 PM, John Plocher <john.plocher at gmail.com> wrote: > On Tue, Mar 23, 2010 at 4:47 PM, Darren Reed <Darren.Reed at sun.com> wrote: >> >> Enjoy (the fact that S10 does not have bash or /usr/gnu or ...). > > > Worse yet (this is no surprise to most, I'm sure, but pity our poor users...): > > On your new OpenSolaris system, create a tar archive of, say, your web > document root that you want to move over to another system: cd > /export/website; tar cf ~/mywebsite.tar . > > scp it over to your other OpenSolaris system, you know, the one you > really use, with ksh93 and a real guru's PATH that starts with > /usr/bin :-) Try to extract your website: cd /export/mynewsite; tar > xf ~/mywebsite.tar > > It probably won't work, because gnutar does not create tar archives > that are compatible with OpenSolaris' tar. > > Repeat for the entire set of gratuitously different tools; the > incompatibilities bite both ways, btw, so this isn't really an "I hate > gnu binutils" rant :-) > > The missing *ARCHITECTURE* bit is why it is OK to produce a system > with superficially interchangeable parts that don't actually work well > together. It is all well and good to say that it is "familiar", but > having familiar tools that don't work does nobody any favors. Unfortunately, that seems to be the only justification -- that it will be familiar to a group of people who honestly seem likely to have little to 0 interest in *solaris (so the theoretical dollars they might pay for support remain just that). Even more bizarre when there's a solution with an active community that is more than willing to work with everyone, and provide the best of all worlds, but seems to keep being treated like a red-headed stepchild compared to the 'favored' GNU son. What I'd like to see is perhaps an _open_ case *cough* that lays out the direction. Personally, I'd like to see it somewhere along the lines of: - The AST tools gradually replace the legacy Solaris tools, and be the preferred default. As they are replaced and conflicts arise between either legacy Sun, POSIX, BSD, or Gnu behavior that can be documented on a case by case basis. - If AST doesn't have a replacement for a Solaris tool (but BSD/GNU does), conflicts as to retain/retire the Solaris tool vs. the other tools is done on a case by case basis when it's decided to retire the Solaris tool - The GNU tools continue to be delivered to /usr/gnu/bin, with the g* aliases in /usr/bin _______________________________________________ opensolaris-arc mailing list opensolaris-arc at opensolaris.org
