On Mon, Dec 21, 2009 at 3:33 PM, Dominik Szczerba <span dir="ltr"><<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div>Matthew Knepley wrote:<br>
> On Mon, Dec 21, 2009 at 3:20 PM, Dominik Szczerba <<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a><br>
> <mailto:<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>>> wrote:<br>
><br>
> With sudo you gain administrative rights (still depends on the actual<br>
> sudoers config) - in principle you can harm your system by mistake (sudo<br>
> rm -fr /usr/lib/* ...). That is why it is normally not allowed on large<br>
> multiuser systems. It should be possible to use any non-system software<br>
> without it.<br>
><br>
><br>
>> Installation is almost always done with root permission. If you want to<br>
>> be pendatic,<br>
>> you can create other users for specific tasks, like the webserver, but<br>
>> you STILL<br>
>> sudo to that user.<br>
<br>
- From Wikipedia:<br>
<br>
"The sudo (...) command is a program for some Unix and Unix-like<br>
computer operating systems that allows users to run programs with the<br>
security privileges of another user (normally the superuser, a.k.a. root)."<br>
<br>
If "another user" is the superuser (which it often is in popular linux<br>
distros) if you are lucky you can render your system non-bootable (if<br>
you are not you can lose data).<br>
<br>
I strongly discourage anybody using superuser for compilation - or God<br>
forbid - entrusting oneself to installation scripts of 3rd party<br>
programs on critical systems [*].<br></blockquote><div><br>So if its own Wikipedia, it must be correct. This is silly. Using sudo for installation<br>is standard. If you do not want to do it, don't.<br><br> Matt<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dominik<br>
<br>
[*] General attitude, not just Petsc.<br>
<br>
><br>
>> Matt<br>
><br>
><br>
> Dominik<br>
<div class="im">><br>
><br>
> Matthew Knepley wrote:<br>
>> On Mon, Dec 21, 2009 at 3:13 PM, Dominik Szczerba<br>
</div>> <<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a> <mailto:<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>><br>
<div class="im">>> <mailto:<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a> <mailto:<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>>>> wrote:<br>
><br>
>> Why use sudo in the first place?<br>
>> I am not a mac user, but normally on unix sudo is the last thing you<br>
>> want to use during everyday work (provided that you are at all allowed<br>
>> to use it).<br>
><br>
><br>
>>> Not sure why you would think that. In fact, sudo is the safe way<br>
> to do<br>
>>> things<br>
>>> and recommended for everyday usage.<br>
><br>
>>> Matt<br>
><br>
><br>
>> Dominik<br>
><br>
>> Satish Balay wrote:<br>
>>> Perhaps 'sudo' is not proegating PETSC_DIR,PETSC_ARCH variables<br>
>>> properly?<br>
><br>
>>> Try 'sudo /bin/bash' and do the whole install in that shell.<br>
><br>
>>> BTW: you have a typo with PETSC_ARCH further down.. And we recommend<br>
>>> using COPTFLAGS, FOPTFLAGS --with-debugging=0 for optimziation<br>
> builds.<br>
><br>
>>> Satish<br>
><br>
</div><div><div></div><div class="h5">>>> On Mon, 21 Dec 2009, <a href="mailto:hxie@umn.edu">hxie@umn.edu</a> <mailto:<a href="mailto:hxie@umn.edu">hxie@umn.edu</a>><br>
> <mailto:<a href="mailto:hxie@umn.edu">hxie@umn.edu</a> <mailto:<a href="mailto:hxie@umn.edu">hxie@umn.edu</a>>> wrote:<br>
><br>
>>>> Hi,<br>
>>>><br>
>>>> My operation system is Mac OS X 10.6.2. I unzip the petsc under<br>
>>>> /usr/local/petsc-3.0.0-p10.<br>
>>>> I use the following to configure petsc.<br>
>>>> -------<br>
>>>> sudo ./config/configure.py --CFLAGS=-O3 --FFLAGS=-O3<br>
>>>> --with-mpi-dir=/usr/local/mpich2-1.2.1 --with-fortran<br>
> --with-shared=0<br>
>>>> --with-fc=gfortran<br>
>>>> -------<br>
>>>><br>
>>>> And I run the following commands:<br>
>>>> ----<br>
>>>> export PETS_ARCH=darwin10.2.0-c-debug;<br>
>>>> PETSC_DIR=/usr/local/petsc-3.0.0-p10; export PETSC_DIR<br>
>>>> ----<br>
>>>><br>
>>>> When I run " sudo make all", it gives some errors:<br>
>>>> -----<br>
>>>> makefile:15: /conf/base: No such file or directory<br>
>>>> makefile:16: /conf/test: No such file or directory<br>
>>>> make: *** No rule to make target `/conf/test'. Stop.<br>
>>>> -----<br>
>>>><br>
>>>> It seems it cannot find the PETSC_DIR. (I use x11. "echo $SHELL"<br>
> gets<br>
>>>> "/bin/bash")<br>
>>>> Do I need to add "PETSC_DIR = /usr/local/petsc-3.0.0-p10" in the<br>
>> makefile<br>
>>>> file? Thanks.<br>
>>>><br>
>>>> Bests,<br>
>>>> Hui<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
><br>
><br>
><br>
>> --<br>
</div></div>>> What most experimenters take for granted before they begin their<br>
>> experiments is infinitely more interesting than any results to which<br>
>> their experiments lead.<br>
>> -- Norbert Wiener<br>
><br>
<br>
> --<br>
> What most experimenters take for granted before they begin their<br>
> experiments is infinitely more interesting than any results to which<br>
> their experiments lead.<br>
> -- Norbert Wiener<br>
<div class="im"><br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
<br>
</div>iEYEARECAAYFAksv6akACgkQ/EBMh9bUuzI6OgCfbVX3klLEC1hxmvP3Oi+ONrC+<br>
N+EAoK+JjmWiGo6MzszvRmoEK7p/vJao<br>
=UNSb<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br><br clear="all"><br>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener<br>