[Radiance-general] Help:Setting up a radiance system

[steve michel]

Lars

I installed radiance through synaptic package manager. However if you are 
implying that a user defined configs could allow root access, that's an 
exploit I've never heard of. I will revise my .bashrc to side with caution.

In the meantime searching the installed radiance files I noticed what may be 
examples I would like to test to make sure everything works as expected. One 
such is 'office' and 'cabin' located in the "/usr/share/radiance/obj" 
folder. Before all that is feasible,  some clarifications to files types are 
needed. Ideally, I would like to locate the example files into a user 
project directory rather than system folders. And make sure any 
procedurales, lighting, and materials files are in the share folder.

The http://radsite.lbl.gov/radiance/refer/ray.html#Auxiliary flowchart 
doesn't show the file types in use.

*.lum
*.vf
*.norm
*.vp etc..

any link to a consise descriptions of these files would be of help because 
running the *.rif I found in the lib folder generate errors from missing 
files or includes.









>From: "Lars O. Grobe" <grobe at gmx.net>
>Reply-To: Radiance general discussion 
><radiance-general at radiance-online.org>
>To: Radiance general discussion <radiance-general at radiance-online.org>
>Subject: Re: [Radiance-general] Help:Setting up a radiance system
>Date: Thu, 05 Apr 2007 16:14:45 +0300
>
>Hi...
>
> > the *.cal procedurals were in /usr/share/radiance/lib
>leads to:
>export RAYPATH=.:/usr/lib/radiance/lib:$RAYPATH
>
> > the rad executable was in /usr/lib/radiance/bin
>leads to:
>export PATH=/usr/lib/radiance/bin:$PATH
>
>Use these for your .bashrc! I always append the existing RAYPATH when 
>setting a new one, just not to break anything I might have done before. If 
>there is nothing that has been defined before in this variable, there will 
>be no negative impact as the existing (appended) RAYPATH will just be 
>empty.
>
>Now some comments on your settings:
> > export PATH=.:/usr/lib/radiance/bin:${PATH}
>Possible, but not recommended. Including '.' into your path is dangerous as 
>it opens the possibility of executing programs that you do not want. E.g. 
>someone might have somehow managed to put a executeable named "ls" into a 
>directory of yours, containing some malicious code and a call to ls. If you 
>happen to type "ls" in that directory, not the system tool you expected, 
>but the malicious code would run (with your user rights), and as there was 
>a call to the original "ls" in it, you get the output you expect and will 
>not even realize what happened. So I never have '.' in my PATH. And it is 
>never necessary!
>
> > export PATH=.:/usr/share/radiance/lib:${PATH}
>There are no executeable in /usr/share/radiance/lib, this is not 
>reasonable.
>
> > RAYPATH=.:/usr/share/radiance/lib/
> > export RAYPATH
>
>Ok, but before you used tanother convention for the variable, so use the 
>same here. Just one line, not two.
>
>Ah, and thanks to Jelle I just found that I forgot the '.' in the RAYPATH 
>setting that I describe on my webpage ;-)
>
>CU Lars.
>
>
>_______________________________________________
>Radiance-general mailing list
>Radiance-general at radiance-online.org
>http://www.radiance-online.org/mailman/listinfo/radiance-general

_________________________________________________________________
http://local.live.com/?mkt=en-ca/?v=2&cid=A6D6BDB4586E357F!399