Re: [sage-devel] why chrome kiosk mode in sage appliance??

Hi, On Mon, Nov 28, 2016 at 10:28:27AM +0100, Stan Schymanski wrote: > Awesome, thanks again! The Live CD works very well, the only thing I had to > add is sudo apt-get install cifs-utils, before being able to access our > samba shares. Note that if you do: sudo apt-get install

Re: [sage-devel] why chrome kiosk mode in sage appliance??

Awesome, thanks again! The Live CD works very well, the only thing I had to add is sudo apt-get install cifs-utils, before being able to access our samba shares. Plus I didn't find an obvious way of changing the keyboard layout, so we installed the needed layout and uninstalled the standard

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Sun, Nov 27, 2016 at 04:23:55PM +0100, Stan Schymanski wrote: > Sorry, I got confused, you are absolutely right, only the MAC address is > relevant for the intranet and that one does not change. I think I also got > confused about the requirement to reboot when trying out the Ubuntu Live CD. >

Re: [sage-devel] why chrome kiosk mode in sage appliance??

Sorry, I got confused, you are absolutely right, only the MAC address is relevant for the intranet and that one does not change. I think I also got confused about the requirement to reboot when trying out the Ubuntu Live CD. I thought it was possible to try without rebooting, but I can't find

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Sun, Nov 27, 2016 at 02:50:22PM +0100, Stan Schymanski wrote: > Wow, thank you! Is it required to boot into the live image, or could one > also run it within windows, similar to the Ubuntu live usb sticks? The > problem with booting into the live image is that one would probably lose > intranet

Re: [sage-devel] why chrome kiosk mode in sage appliance??

Wow, thank you! Is it required to boot into the live image, or could one also run it within windows, similar to the Ubuntu live usb sticks? The problem with booting into the live image is that one would probably lose intranet connectivity. Stan On 11/27/2016 02:33 PM, Thierry wrote: An

Re: [sage-devel] why chrome kiosk mode in sage appliance??

Hi, On Sun, Nov 27, 2016 at 02:23:54PM +0100, Stan Schymanski wrote: [...] > I will test the different options mentioned in this thread before I get the > next student to use sagemath in windows. Could the relevant bits of this > thread or some links/instructions to try out alternative methods be

Re: [sage-devel] why chrome kiosk mode in sage appliance??

Sorry for the long delay in replying. We do have Windows enterprise on our institute computers (whichever version is the deemed the latest reliable one), so Thomas should be able to install the Docker image. The only problem is that by now he is in the final stage of his project, so we don't

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Wed, Nov 16, 2016 at 2:28 AM, William Stein wrote: > On Tue, Nov 15, 2016 at 2:35 PM, Dima Pasechnik wrote: >> >> >> On Tuesday, November 15, 2016 at 9:35:23 PM UTC, William wrote: >>> >>> On Tue, Nov 15, 2016 at 1:18 PM, Dima Pasechnik

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Wednesday, November 16, 2016 at 1:28:44 AM UTC, William wrote: > > On Tue, Nov 15, 2016 at 2:35 PM, Dima Pasechnik > wrote: > > > > > > On Tuesday, November 15, 2016 at 9:35:23 PM UTC, William wrote: > >> > >> On Tue, Nov 15, 2016 at 1:18 PM, Dima Pasechnik

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Tue, Nov 15, 2016 at 2:35 PM, Dima Pasechnik wrote: > > > On Tuesday, November 15, 2016 at 9:35:23 PM UTC, William wrote: >> >> On Tue, Nov 15, 2016 at 1:18 PM, Dima Pasechnik wrote: >> > as >> >

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Tuesday, November 15, 2016 at 9:35:23 PM UTC, William wrote: > > On Tue, Nov 15, 2016 at 1:18 PM, Dima Pasechnik > wrote: > > as > https://docs.docker.com/docker-for-windows/#download-docker-for-windows > > says: > > "Docker for Windows requires 64bit Windows 10 Pro,

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Tue, Nov 15, 2016 at 1:18 PM, Dima Pasechnik wrote: > as https://docs.docker.com/docker-for-windows/#download-docker-for-windows > says: > "Docker for Windows requires 64bit Windows 10 Pro, Enterprise and Education > (1511 November update, Build 10586 or later) and Microsoft

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Tuesday, November 15, 2016 at 5:10:40 PM UTC, William wrote: > > > > On Tuesday, November 15, 2016, Dima Pasechnik > wrote: > >> >> >> On Tuesday, November 15, 2016 at 2:29:30 PM UTC, Erik Bray wrote: >>> >>> On Mon, Nov 14, 2016 at 6:43 PM, William Stein

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Tuesday, November 15, 2016, Dima Pasechnik wrote: > > > On Tuesday, November 15, 2016 at 2:29:30 PM UTC, Erik Bray wrote: >> >> On Mon, Nov 14, 2016 at 6:43 PM, William Stein wrote: >> > On Mon, Nov 14, 2016 at 8:40 AM, Erik Bray

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Tuesday, November 15, 2016 at 2:29:30 PM UTC, Erik Bray wrote: > > On Mon, Nov 14, 2016 at 6:43 PM, William Stein > wrote: > > On Mon, Nov 14, 2016 at 8:40 AM, Erik Bray > wrote: > >> On Mon, Nov 14, 2016 at 4:49 PM, William Stein

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Mon, Nov 14, 2016 at 6:43 PM, William Stein wrote: > On Mon, Nov 14, 2016 at 8:40 AM, Erik Bray wrote: >> On Mon, Nov 14, 2016 at 4:49 PM, William Stein wrote: >>> On Mon, Nov 14, 2016 at 6:21 AM, Stan wrote:

Re: [sage-devel] why chrome kiosk mode in sage appliance??

I think this was actually a problem with autosave we had for about one week. Of course we didn't know that at the time. I'm not sure why to say, except the root problem is probably solved, and if not there is a straightforward way to just use plain jupyter in SMC anyways. On Tuesday, November

Re: [sage-devel] why chrome kiosk mode in sage appliance??

OK, I just asked Thomas to send me the email thread about his problem with SMC. His communication was with William Stein and Harald Schilly, and related to lost bits of a jupyter notebook that were not even recoverable using the revert button or the backup utility, plus bits started

Re: [sage-devel] why chrome kiosk mode in sage appliance??

This is amazing, I had no idea there was a way to run SMC locally already. Interestingly, https://hub.docker.com/u/sagemath/ points to sagemath.org as homepage, but I couldn't find a link to hub.docker.com at sagemath.org. I think it would be great to point to this resource at least on the

Re: [sage-devel] why chrome kiosk mode in sage appliance??

Dear William, Thanks for the quick reply. The problem Thomas experience in SMC was that parts of his worksheet just disappeared and were not to be found in the snapshots. He could recover them from the log files and painfully put them in again, only to experience that bits started disappearing

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Monday, November 14, 2016 at 5:44:01 PM UTC, William wrote: > > On Mon, Nov 14, 2016 at 8:40 AM, Erik Bray > wrote: > > On Mon, Nov 14, 2016 at 4:49 PM, William Stein > wrote: > >> On Mon, Nov 14, 2016 at 6:21 AM, Stan >

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Mon, Nov 14, 2016 at 8:40 AM, Erik Bray wrote: > On Mon, Nov 14, 2016 at 4:49 PM, William Stein wrote: >> On Mon, Nov 14, 2016 at 6:21 AM, Stan wrote: >>> Dear all, >>> >>> A student of mine has been using SMC because the sage

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Mon, Nov 14, 2016 at 4:49 PM, William Stein wrote: > On Mon, Nov 14, 2016 at 6:21 AM, 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

Re: [sage-devel] why chrome kiosk mode in sage appliance??

On Mon, Nov 14, 2016 at 6:21 AM, 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