Hi,
I want to ask a question regarding to the authorization problems on
input/output operations.
How can we have the value of $FG_ROOT and $FG_HOME in Nasal scripts. Is it
possible? Is there a globally defined macro for them?
I want to write a Nasal function that creates a file under $FG_ROOT,
Behlül UÇAR wrote:
I want to write a Nasal function that creates a file under $FG_ROOT, I want
it to be portable, I mean both works on windows and linux machines.
I'm a bit doubtful about the 'portability' of writing to $FG_ROOT in
general, simply because this directory is supposed not to be
On Fri, 4 Sep 2009, Behlül UÇAR wrote:
Hi,
I want to ask a question regarding to the authorization problems on
input/output operations.
How can we have the value of $FG_ROOT and $FG_HOME in Nasal scripts. Is it
possible? Is there a globally defined macro for them?
I want to write a Nasal
Thanks both of you for your answers,
I was thinking about modifying $FG_ROOT/Nasal/IOrules file for beating the
permission issue but I hadn't thought about file permissions especially in
linux.
Then there are two solutions for beating this problem;
First is creating an empty and permanent file
Behlül UÇAR wrote:
And the second is creating ~/home/FlightGear/ folder and working under it.
As far as I remember FlightGear will create a ~/.fgfs/ directory by
default - if you don't prevent it from doing so,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its
On Fri, 2009-09-04 at 17:38 +0300, Behlül UÇAR wrote:
Thanks both of you for your answers,
I was thinking about modifying $FG_ROOT/Nasal/IOrules file for beating
the permission issue but I hadn't thought about file permissions
especially in linux.
IOrules is there for a reason, and it
6 matches
Mail list logo
