On 01/09/15 22:01, Dave Higton wrote:
"Chris Young" <chris.young(a)unsatisfactorysoftware.co.uk>
> On Sat, 29 Aug 2015 21:07:47 +0100, Dave Higton wrote:
>> So, have I missed something?
> This, maybe?
There are just a couple of discrepancies when using Ubuntu:
1) root doesn't really exist;
2) "sudo source env.sh", which I had expected to use as the nearest
equivalent, didn't understand source as a command. However,
"source env.sh" /was/ understood - albeit that's of course executed
as ordinary user, not what the docs say to do.
Does this mean I've missed something else?
You can usually get a root shell on systems that use sudo by issuing
"sudo -s". Once there, you can source env.sh in the usual way.
"source" is a shell built-in, so doesn't exist as a binary on the path,
and thus won't work with sudo, as you've discovered.
1. This is security-policy dependent, but generally works unless you've
explicitly configured it otherwise.