On Sat 27 Oct 2018 at 11:29:35 (-0400), Gene Heskett wrote: > On Saturday 27 October 2018 11:03:56 Matthew Crews wrote: > > > -------- Original Message -------- > > On Oct 27, 2018, 06:58, Curt wrote: > > > > On 2018-10-27, Gene Heskett wrote: > > >> Might be nice, but several of the dependecies can only be satisfied > > >> if on stretch, and the curl command lines don't work on wheezy. At > > >> all. > > > > > >At any rate a curl command line that proves > > >inoperable on Wheezy arouses > > >the interest of even the most jaded observer. > > > > Correct me if I'm wrong, but Wheezy is no longer supported, and Jessie > > is barely supported. Except as a curiosity, why would you want to use > > a web browser on Wheezy these days? > > Because its main application (LinuxCNC) is married to a 32 bit install, > wheezy ATM. > > I understand a stretch version is being worked on, but the increased > latency involved in a 64 bit context switch is very very hard to > tolerate on real machinery. Real time kernels that actually work are > virtually non-existant on 64 bit machinery. I have one that almost works > on armhf, but it loves to throw away mouse and keyboard events, but that > goes away, or gets worse if you reboot. And a good reboot is good till > the next power bump on that machine, running Jessie..
That explains why you run wheezy at all. But it doesn't explain why you run a web browser on wheezy or on a computer that's required to have good realtime performance. I thought you ran a LAN of computers there. > > Especially when the expectation of > > security updates and compatible software for modern web browsing is > > nearly, if not completely, zero. > > Its certainly getting that way. Cheers, David.
