On Tuesday, November 15, 2016 at 11:32:11 AM UTC, Stan wrote: > > You mean to start the VM (sage is started within the VM automatically), > ssh into it, shut down sage and restart with the options I want? Not sure > how to ssh into the VM, > Yes; even better, modify .xinitrc not to start Sage at all... Then, see Section 8 in https://wiki.sagemath.org/SageAppliance/Sage-5-x-or-6-x on how to ssh an don what port.
but I'll play again with the .xinitrc. > > > > On Tuesday, November 15, 2016 at 11:11:39 AM UTC+1, Dima Pasechnik wrote: >> >> >> >> On Tuesday, November 15, 2016 at 9:52:02 AM UTC, Stan wrote: >>> >>> Thanks, Volker. I just installed the VB image on my linux laptop and I >>> can access the jupyter notebook through my local firefox on >>> http://localhost:8000. So it seems to be a windows issue that Thomas >>> can't. Do you have an idea what dodgy windows programs could be the reason? >>> Antivirus? If you know of any way how to get around this, it would be >>> great. Thanks! >>> The problem with File -> Close and Halt is that this option is not >>> available e.g. after downloading a jupyter file, as there is only the >>> download window left, without any menu commands. How would I have to edit >>> .xinitrc to get a full browser? We already removed the --kiosk option but >>> it didn't make a difference. >>> >> >> I'd say that you can just ssh into VM and run Sage at shell prompt with >> whatever options you like. >> >> >>> >>> Cheers >>> Stan >>> >>> On Monday, November 14, 2016 at 9:50:59 PM UTC+1, Volker Braun wrote: >>>> >>>> The recommended (for power users) way to run the virtual machine is >>>> using their host browser, just go to http://localhost:8000. This >>>> requires a non-broken windows networking stack, though (and various dodgy >>>> windows programs can interfere). >>>> >>>> In the kiosk mode you can still go back,e.g. open a notebook and then >>>> File -> Close and Halt. >>>> >>>> If you really do want a full browser inside the VM (with a virtualbox >>>> menu on top) then you can edit ~/.xinitrc inside the vm. >>>> >>>> >>>> >>>> >>>> On Monday, November 14, 2016 at 3:21:32 PM UTC+1, Stan wrote: >>>>> >>>>> Dear all, >>>>> >>>>> A student of mine has been using SMC because the sage appliance in >>>>> virtualbox did not appear very useful with the jupyter notebook. Now that >>>>> he encountered a critical bug in SMC (reported offline), he is back with >>>>> the sage appliance in VB but it is truly a nightmare. The installation >>>>> instructions are still specific for sagews, not jupyter, but we at least >>>>> managed to change the working directory to something he can access. What >>>>> we >>>>> haven't managed, is to get out of the kiosk mode in chrome. There is no >>>>> obvious possibility of opening several tabs, no address bar to get back >>>>> to >>>>> the directory page and no back button. This means that every time he >>>>> wants >>>>> to go back, e.g. after downloading the worksheet, he has to restart the >>>>> virtual machine! I don't understand why chrome was chosen instead of >>>>> firefox, and I have no idea why it is set up in kiosk mode. Is there any >>>>> sensible way to productively work with the sage appliance using the now >>>>> standard jupyter notebook?? I'm sorry if my frustration shows in these >>>>> lines, I probably should have asked earlier, but I am wondering a bit if >>>>> those that created the sage appliance actually use it themselves. I >>>>> don't, >>>>> which is why it never occurred to me how difficult to use it might be. >>>>> Thanks for your help! >>>>> >>>>> Cheers >>>>> Stan >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
