>
> If they hit continue, does Sage work as expected?
>>
>
> As far as I can tell, yes. The permissions of DOT_SAGE and the notebook
> are initialized and the user is asked for a password.
>
Oh, so it works? Then yes, it is safe. That really was just to warn
against the situation Ivan descri
> If they hit continue, does Sage work as expected?
>
As far as I can tell, yes. The permissions of DOT_SAGE and the notebook are
initialized and the user is asked for a password.
> This was implemented in http://trac.sagemath.org/ticket/15732 because
>> Sage needs to write to some files in
>> Another possibility is to use a snapshot image for each desktop or
>> something - that is what some admins I know do, though I confess I do not
>> know how that works. Maybe your situation is not a lab.
>>
>
> I'm not sure I understand what you are suggesting here. I do have a lab,
> so i
On Dec 5, 2014, at 9:36 AM, Jérôme Tremblay
wrote:
On Friday, December 5, 2014 11:32:34 AM UTC-5, kcrisman wrote:
> When I run sage as admin, everything works fine. However, when my users
>> try to run Sage, they get a warning that they are trying to execute Sage
>> from a read-only filesystem.
On Friday, December 5, 2014 11:32:34 AM UTC-5, kcrisman wrote:
>
> When I run sage as admin, everything works fine. However, when my users
>> try to run Sage, they get a warning that they are trying to execute Sage
>> from a read-only filesystem.
>>
>>
> This was implemented in http://trac.sage
>
> When I run sage as admin, everything works fine. However, when my users
> try to run Sage, they get a warning that they are trying to execute Sage
> from a read-only filesystem.
>
>
This was implemented in http://trac.sagemath.org/ticket/15732 because Sage
needs to write to some files in .s
