Recommend sourcing uno env instead of using eval (#231)
diff --git a/README.md b/README.md
index fcdc2ef..741e6ad 100644
--- a/README.md
+++ b/README.md
@@ -38,7 +38,7 @@
cd fluo-uno
./bin/uno fetch accumulo # Fetches binary tarballs of Accumulo and its dependencies
./bin/uno setup accumulo # Sets up Accumulo and its dependencies (Hadoop & ZooKeeper)
-eval "$(./bin/uno env)" # Bash-specific command that sets up current shell
+source <(./bin/uno env) # Bash-specific command that sets up current shell
```
Accumulo is now ready to use. Verify your installation by checking the [Accumulo Monitor](http://localhost:9995/)
@@ -99,7 +99,7 @@
to your ~/.bashrc automatically configure every new shell.
```bash
-eval "$(/path/to/uno/bin/uno env)"
+source <(/path/to/uno/bin/uno env)
```
With `uno` script set up, you can now use it to download, configure, and run Fluo's dependencies.
diff --git a/bin/impl/load-env.sh b/bin/impl/load-env.sh
index b5033ef..d465b5c 100755
--- a/bin/impl/load-env.sh
+++ b/bin/impl/load-env.sh
@@ -53,7 +53,7 @@
fi
function env_error() {
- echo 'Make your shell env match uno.conf by running: eval "$(./bin/uno env)"'
+ echo 'Make your shell env match uno.conf by running: source <(./bin/uno env)'
exit 1
}
