How to export environment variable from a bash script

dimaash · 07-17-2005, 04:16 PM

Hi everyone!

I am new to bash scripting. I am trying to write a simple bash script to automate some command typping. Let's say that i can type on command prompt: "export LFS=/mnt/lfs". Then when i type on that same prompt "echo $LFS", i have the output "/mnt/lfs". Now what i dont know how to do (and i tried to read up on this and tried by trial and error, but without success.) is how to export that same variable $LFS but from a bash script. In other words, when my bash script finishes and when i type "echo $LFS" i want to have the same result: "/mnt/lfs". Can anyone enlighten me on this?

Thanks. Appriciate in advance.

eddiebaby1023 · 07-17-2005, 04:39 PM

Quote:

Originally posted by dimaash
Hi everyone!

I am new to bash scripting. I am trying to write a simple bash script to automate some command typping. Let's say that i can type on command prompt: "export LFS=/mnt/lfs". Then when i type on that same prompt "echo $LFS", i have the output "/mnt/lfs". Now what i dont know how to do (and i tried to read up on this and tried by trial and error, but without success.) is how to export that same variable $LFS but from a bash script. In other words, when my bash script finishes and when i type "echo $LFS" i want to have the same result: "/mnt/lfs". Can anyone enlighten me on this?

Thanks. Appriciate in advance.

Variables can only be exported to subordinate processes, you can't pass them back up to the parent. If you really want your script to affect the parent shell's environment, run the script as

Code:

.  ./yourscript

Hint: don't put an exit statement in your script, or your shell will terminate.

jrdioko · 07-17-2005, 04:47 PM

What exactly are you trying to accomplish with the script? You can always put export statements in your .bashrc file if you want them to affect everything.

dimaash · 07-17-2005, 05:53 PM

jrdioko:

I am trying to automate the building process of Linux from Scratch (I know that there is an ALFS out there, but i want to do something rather small and my way, and at the same time grab the opportunity to learn bash). As you know, it is a long process and as you go further and further in it, there are more and more commands to type. So, if let's say somewhere near the middle of that build process i accidently destroy toolchain or temporary environment i would probably restart all over again since i don't have the knowledge to fix the problem. So, i thought it would be nice to put all those commands in a bash script and let it run up to the point where i screwed up.

jrdioko · 07-17-2005, 06:14 PM

It seems like you could put global export statements in .bashrc and then have the script do the rest, but that's probably not proper shell scripting design. I'll let someone else jump in.

chicken76 · 07-31-2009, 08:35 AM

Quote:

Originally Posted by eddiebaby1023

Variables can only be exported to subordinate processes, you can't pass them back up to the parent. If you really want your script to affect the parent shell's environment, run the script as

Code:

.  ./yourscript

Hint: don't put an exit statement in your script, or your shell will terminate.

I'm also trying to pass some variables to a parent script. Any other ways to do it?
Your method seems to work. I don't know why, though. Can you direct me to some documentation on what that leading dot is and why it works? (i'm not going to include it without understanding what it does, or it will backfire; it always does)

colucix · 07-31-2009, 08:42 AM

Quote:

Originally Posted by chicken76

Your method seems to work. I don't know why, though. Can you direct me to some documentation on what that leading dot is and why it works? (i'm not going to include it without understanding what it does, or it will backfire; it always does)

From man source or man bash_builtins

Code:

  .  filename [arguments]
  source filename [arguments]
         Read  and  execute commands from filename in the current shell environment and return the exit
         status of the last command executed from filename.

plus http://www.tldp.org/LDP/abs/html/abs...html#SOURCEREF

DElimitER · 08-14-2010, 08:20 AM

Hi...
You can export and add new variables to current shell with function, because function is executing in current shell...Functions rule!

kusanagiyang · 08-24-2010, 12:22 AM

Quote:

Originally Posted by DElimitER

Hi...
You can export and add new variables to current shell with function, because function is executing in current shell...Functions rule!

...not sure i get it
how about a simple working example... thanks

Tinkster · 08-24-2010, 12:40 AM

Goodness ... a corpse dug up twice!

kusanagiyang · 08-24-2010, 12:47 AM

Quote:

Originally Posted by Tinkster

Goodness ... a corpse dug up twice!

look
i m not smart, ok!

Tinkster · 08-24-2010, 12:58 AM

Quote:

Originally Posted by kusanagiyang

look
i m not smart, ok!

Not sure what that was a reference to ... I'm referring
to the fact that this thread is from 2005; it died, got
re-animated in August 2009, died, and got dug up again in
August this year.

Cheers,
Tink

jrdioko · 08-24-2010, 01:03 AM

Quote:

Originally Posted by Tinkster

Not sure what that was a reference to ... I'm referring
to the fact that this thread is from 2005; it died, got
re-animated in August 2009, died, and got dug up again in
August this year.

Cheers,
Tink

Crazy. Also crazy Tinkster is still around, I think I remember him from 2005...

kusanagiyang · 08-24-2010, 01:09 AM

Quote:

Originally Posted by eddiebaby1023

Variables can only be exported to subordinate processes, you can't pass them back up to the parent. If you really want your script to affect the parent shell's environment, run the script as

Code:

.  ./yourscript

Hint: don't put an exit statement in your script, or your shell will terminate.

really appreciated it.
i just dont know why it works

konsolebox · 08-24-2010, 04:17 AM

. (or source in bash) reads the script to the current process or environment while just running ./script.sh will spawn a new process based from the type of executable referred to the header of the script. For example

Code:

#!/bin/bash

will call bash.