Alan Coopersmith wrote: > > I assume he's talking about ksh93 here - how would the > builtin uname conflict with the real uname and break apps? > > -alan- > > -------- Original Message -------- > Subject: [csw-announce] pkg-get upgrade, for solaris "11" > Date: Thu, 19 Apr 2007 09:48:22 -0400 > From: Philip Brown <phil at blastwave.org> > Reply-To: users at lists.blastwave.org > To: Blastwave Announcements <announce at lists.blastwave.org> > > pkg-get announcement: > > it has been noted that the "new ksh" in Solaris-next, aka solaris 11, > somehow broke pkg-get. > > After finally being provided with some trace data, I have updated > pkg-get, with a workaround for the issue that the new ksh builtin for > uname, conflicts with the output of /bin/uname.
That one of the reasons why PSARC 2006/550 (see http://www.opensolaris.org/os/community/arc/caselog/2006/550/) did not enable all builtins for the first putback, e.g. for the first putback into Solaris we only enable a subset of builtins which has been explicitly tested for compatibilty (and in that case "pkg-get" should work out of the box...) .... ... anyway... there are two ways to work around the problem: 1. Specify the full path to "uname" (POSIX says that builtins must not be used of a full path to the comment is used), e.g. using "/sbin/uname" instead of "uname" should do the trick 2. ksh93 has a command called "builtin" to control the behavour of builtins, e.g. list builtins, load builtins, remove builtin etc.. In this case a $ builtin -d /bin/uname # should disable the builtin... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
