Jon Elson wrote:
I assure you I DIDN'T send this 4 times! SourceForge is up to no good
again!
Jon
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications w
John Thornton wrote:
> #!/bin/bash
> cd emc2-2.2.x/src
> ./configure --enable-run-in-place --enable-build-documentation
> echo Starting Make
> make > 1make.txt
> sudo make setuid
> cd ..
> cd ..
>
> My question is how can I pass my password to the "sudo make setuid" line?
>
> The make > 1make.txt
Hi Jon,
After some reading in the man pages I think I need to use the sudo -S option
that
passes the password via the stdin instead of the terminal...
Yep, that worked :)
Thanks
John
On 5 Oct 2008 at 11:44, Jon Elson wrote:
> John Thornton wrote:
> > My question is how can I pass my password
Thanks Jon,
That doesn't quite work as it seems like that the password must be passed after
the
Password: prompt then the enter key...
Thanks for the tips
John
On 5 Oct 2008 at 11:44, Jon Elson wrote:
> John Thornton wrote:
> > My question is how can I pass my password to the "sudo make setui
Stephen Wille Padnos wrote:
>
> Yep. Actually, there may be some errors that don't get logged that
> way. You can also redirect stderr to stdout, if you want to catch those
> also:
> make 2>&1 > 1make.txt
> the 2>&1 redirects file 2 (stderr) to file 1 (stdout), then the >
> redirects stdout to
John Thornton wrote:
> My question is how can I pass my password to the "sudo make setuid" line?
>
>
I can't guarantee this will work with sudo, but the shell mechanism to
pass additional lines to a command goes like this :
progx << 5
next 5 lines are input to "progx"
I tried this and it seem
Hi Steve,
Thanks for the info. I actually want to see the errors in the terminal window
that is
why I just send the normal text to a file.
Thanks
John
On 5 Oct 2008 at 9:18, Stephen Wille Padnos wrote:
> John Thornton wrote:
> >The make > 1make.txt sends the normal output to the file so all
John Thornton wrote:
>I'm sure everyone takes shortcuts to build EMC. I made a couple of shell
>scripts that
>I put in my home directory called go2 and go3.
>
>go2
>
>#!/bin/bash
>cd emc2-2.2.x/src
>./configure --enable-run-in-place --enable-build-documentation
>echo Starting Make
>make > 1make.
I'm sure everyone takes shortcuts to build EMC. I made a couple of shell
scripts that
I put in my home directory called go2 and go3.
go2
#!/bin/bash
cd emc2-2.2.x/src
./configure --enable-run-in-place --enable-build-documentation
echo Starting Make
make > 1make.txt
sudo make setuid
cd ..
cd ..
