On Aug 21, 2009, at 3:38 PM, Roland Mainz wrote: > John Fischer wrote: >> I am sponsoring this project for Bruce Rothermal who will be >> integrating >> this project via the SFW consolidation. I have set the timer for >> Friday, >> August 28th. The case directory contains this proposal, FOSS check >> list, >> and appropriate man pages. >> >> This project proposes to integrate the Environment Modules within a >> Minor release of Solaris (i.e., Open Solaris). The environment >> modules >> provides an easy modification to a user's environment via TCL >> scripts. >> These scripts set various environmental variables such as PATH, >> MANPATH, >> etc. > [snip] >> 4. Technical Description: >> >> The environment modules package provides for an easy dynamic >> modification of a user's environment via modulefiles. which >> typically instruct the module command to alter or set shell >> environment variables such as PATH, MANPATH, etc. >> >> Command name Notes >> =================================================================== >> module Link or alias to modulecmd >> modulecmd Command interface to the Modules package. > [snip] >> Imported interface Classification Comments >> ======================= ============== >> =================================== >> /lib/ld.so.1 Uncommitted Library provided by >> SUNWcslr >> /usr/lib/libtcl8.4.so Uncommitted Library provided by >> SUNWTcl >> /lib/libdl.so.1 Uncommitted Library provided by >> SUNWcslr >> /lib/libm.so.2 Uncommitted Library provided by >> SUNWlibmsr >> /usr/lib/libX11.so.4 Uncommitted Library provided by >> SUNWxwrtl >> /lib/libnsl.so.1 Uncommitted Library provided by >> SUNWcslr >> /lib/libsocket.so.1 Uncommitted Library provided by >> SUNWcslr >> /lib/libc.so.1 Uncommitted Library provided by >> SUNWcslr >> /lib/libpthread.so.1 Uncommitted Library provided by >> SUNWcslr >> /usr/lib/libXext.so.0 Uncommitted Library provided by >> SUNWxwrtl > > I took a dive in the actual code at > http://modules.cvs.sourceforge.net/viewvc/modules/modules/ to see > how it > works... > 1. ... aren't the shells and their environment files imported > interfaces > too, e.g. shouldn't the list include /usrbin/bash (and ~/.bashrc + > ~/.bash_profile), /usr/bin/ksh (and ~/.profile, ~/.kshrc + ~/.kshrc), > /usr/bin/ksh93 (and ~/.profile,~/.kshrc + ~/.kshrc), /usr/bin/zsh > (erm... I don't know exactly which files zsh uses for startup) etc. ?
So should I include all . (dot) files in general. Because it could be argued that any package of software would use the current running ENVIRONMENT just as this one does. > > 2. Please correct me if I am wrong... but does the "modules" stuff > differ between "login shell" and "interactive shell" ? > If I understand the question correctly modules would only effect the interactive shell. modules changes only occur after the login. I don't really see how you could call modules to modify the ENV before the login. > ---- > > Bye, > Roland > > -- > __ . . __ > (o.\ \/ /.o) roland.mainz at nrubsig.org > \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer > /O /==\ O\ TEL +49 641 3992797 > (;O/ \/ \O;) -------------- next part -------------- Bruce Rothermal Email: bruce.rothermal at sun.com Skype: bruce.rothermal Google Talk: bruce.rothermal at gmail.com
