Casper.Dik at Sun.COM wrote:
> >> From: James Carlson <james.d.carlson at sun.com>
> >> Roland Mainz writes:
> >> > BTW: The "real" fix for this problem is to compile the shell scripts -
> >> > in that case the compiled shell script /usr/bin/sleep will just appear
> >> > as "just another binary application" in the $ ps -ef # output ...
> >> > ... the trouble is that the matching kernel module ("shbinexec") was
> >> > added to OS/Net in B106 and we need some builds before we're able to
> >> > request a flag day and make the availablity of the kernel module a
> >> > requirement... ;-/
> >>
> >> I'd guess that the flag day is for BFU and not for the build machines
> >> themselves: you would need to install at least 106 before BFU-ing any
> >> higher.
> >
> >Isn't the new /bin/shcomp, introduced in build 106,
> >needed on the build machines to compile the ksh93 script for sleep?
> >In that case, build 106 would be required for build machines also.
>
> The ONNV build environment must use a native shcomp; it should not use the
> installed shcomp.
Do you mean the OS/Net build environment should use /usr/bin/shcomp from
the build machine and _not_ the "shcomp" binary from the "proto" area
(which is the obvious case, otherwise libc, libast or libshell changes
may bite you...) ?
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.mainz at nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 3992797
(;O/ \/ \O;)
