> James Carlson wrote: > > I've answered the same question more than once: you > should _not_ be > > putting _anything_ into /usr/bin. Nothing. No > symlinks, no files, no > > directories. Nothing at all. > > > > /usr/bin (and /usr/sbin) belong to the system > itself. Please do read > > filesystem(5); it describes how directories are > used in System V and > > in Solaris. > > > > So what does *your* $PATH look like?
Let me show you something: this is from a production system. [EMAIL PROTECTED]/]> cat /etc/PATH /usr/xpg4/bin:/usr/bin:/opt/SUNWspro/bin:/opt/SUNWspro/prod:/usr/ccs/bin:/opt/abcd/bin:/usr/sfw/bin:/usr/openwin/bin:/usr/dt/bin Notice that I have a file called "/etc/PATH". This file normally does not exist on Solaris, but it does on HP-UX, where it was assimilated from. There is a package that we developed inhouse, which, when installed on the system, automatically delivers /etc/PATH and /etc/MANPATH, with those preconfigured values, as well as /etc/csh* files and some terminal handling code. These files are read by csh(1) and tcsh(1), so they are no use for non C-shell family, but since tcsh(1) is our standard *interactive* shell *everywhere*, this works phenomenally, providing a clean and consistent environment (see that prompt up there? Even that's standardized.) You might have also noticed "/opt/abcd" in the /etc/PATH up there. While the name has been changed to "abcd" to protect the innocent, that's where our private software stack gets delivered. And wouldn't you know it, all the binaries delivered in "/opt/abcd" are in the $PATH. > And how often have you had to field support questions from people who > installed a > packaged, tried to run it, and got told it "wasn't there"? Never. Ever. Highly standardized environment, delivered automatically as part of the standard RunTime Platform(TM). This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
