On Tue, Oct 14, 2008 at 4:19 PM, ./aal <[EMAIL PROTECTED]> wrote: > On Tue, Oct 14, 2008 at 4:12 PM, Steven S. Critchfield <[EMAIL PROTECTED] > > wrote: > >> >> >> ----- "./aal" <[EMAIL PROTECTED]> wrote: >> >> > > >> > > >> > > >> > > Steven, is "sourcing" the same as "dotting in" a script? It sounds >> > > like the way I've seen to reload your .bashrc settings without >> > having >> > > to log out: >> > > >> > > $ echo "FOOBAR=BAZ" >> .bashrc >> > > $ env |grep FOO >> > > $ . .bashrc >> > > $ env |grep FOO >> > > FOOBAR=BAZ >> > > >> > > >> > >> > Good question. >> > >> > is # . <file> >> > the same as # source <file> >> > >> > I use "source /etc/profile" after chrooting >> > would ". /etc/profile" do the same thing? >> >> I am not certain, but I think so. One of the problems with >> . <file> running of apps is when the script issues an exit >> command. The NVIDIA driver install package does this. >> Nothing more fun than suing to root and using . <file> to >> avoid chmoding the file and it exits and exits your root >> shell when you have to fix a problem and reinstall. >> >> -- >> Steven Critchfield [EMAIL PROTECTED] >> >> > > Very true, I use "sh <file>" if I need the output visible and dont want to > bother with logging it to a file > > I also use . or sh to exeute binaries that dont have the X perm set > > which makes me wonder.... can "source" be used to exec a binary file?
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en -~----------~----~----~----~------~----~------~--~---
