[10:06] smoser: So on line 17 it will print ($HOME) versus the variable contents [10:08] smoser: that second script looks really good === mgagne is now known as Guest12514 [13:23] arkin, i was just trying to show that without a shell, enviroment variables are not interpreted.. there is *no* shell involved there to do that expansion/replacement. [13:23] echo is '/bin/echo' as found in path. [13:23] probably should have written that, as reading it it is confusing. [13:55] smoser: Yeah, OK, I think I sort of understand this... bash is still kind of new to me [13:55] so when you echo using bash, bash first replaces variables and such before sending to echo ? [13:55] whereas in runcmd if you send an array, it simply pipes to echo but not through bash (if thats possible) ? [13:57] right. [13:57] well, not pipe to echo, just doesn't use a shell. uses 'exec' [14:05] smoser: hmm ok thanks, suprised at how big cloud-init is, had not heard of it until DO but now I'm seeing AWS use it [14:14] arkin: It's supported by AWS, GCE, Azure and OpenStack (to name the big players). [14:14] Odd_Bloke: Impressive [14:19] arkin: That also means that anywhere that provides an EC2- or OpenStack-compatible interface can normally be enabled pretty easily. :) [14:20] Odd_Bloke: Yea its quite cool what I've done so far === Guest12514 is now known as mgagne === mfisch is now known as Guest15777 === Guest15777 is now known as mfisch