search for: waaayyy

A really nice example of an instance where an "outlier" was the whole story scientifically and hiding it with statistical summaries, here an "average" of some sort, lost the science. Moral: "Look at your data and think." (Ellis Ott) https://www.sciencenews.org/article/proxima-centauri-flare-may-have-fried-earths-nearest-exoplanet?tgt=nr Cheers, Bert [[alternative

...hing in every attached network and the outside world. For some reason, I cannot ping the outside world if I am comming from the 10.0.0.* network on the diagram. From that network, I can ping 10.0.5.1 (this box) but nothing else. I'm a little stumped. My iptables are completly empty. If this is waaayyy off topic, please contact me off list. But I figured since it was related to the T100P it might be relevant. What can I use to find out why packets destined for the outside world (via 65.78.109.2) are not being routed? Thanks, Matthew -------------- next part -------------- A non-text attachment...

....4.2; I haven't changed anything. So if anyone looks at the R-3.4.2 configure file they should see exactly what I see. Then I scanned through BldDir/config.log and found: LIBnn='lib64' (on line 19901 !!!) So it would appear that Peter D.'s conjecture is correct. OTOH this is waaayyy after the "checking for tclConfig.sh" business, which happens at about line 15101 of config.log. So how does it have an impact on that? And how did LIBnn get to be set to 'lib64'? I certainly didn't do it, and there's nothing about 'lib64' in the environment...

...Nov 2017, at 02:02 , Rolf Turner <r.turner at auckland.ac.nz> wrote: > > Then I scanned through BldDir/config.log and found: > > LIBnn='lib64' > > (on line 19901 !!!) > > So it would appear that Peter D.'s conjecture is correct. > > OTOH this is waaayyy after the "checking for tclConfig.sh" business, which happens at about line 15101 of config.log. So how does it have an impact on that? > > And how did LIBnn get to be set to 'lib64'? I certainly didn't do it, and there's nothing about 'lib64' in the envir...

Rolf, looking at the configure script I believe you need to specify --with-tcl-config=/usr/lib/tcl8.6/tclConfig.sh and similarly --with-tk-config=<location of tkConfig.sh> HTH, Peter On Fri, Nov 17, 2017 at 8:43 PM, Rolf Turner <r.turner at auckland.ac.nz> wrote: > On 18/11/17 17:00, Erin Hodgess wrote: >> >> When I have compiled from sourced on Ubuntu, I did NOT

Hello, I am trying to make the "switchover" to programming my apps in Rails and have a question about database structure. In the past i would structure a many to many like this: categories ---------------------------------------------------- | id | name | ---------------------------------------------------- 1 Some Category 2 Another

On 18/11/17 17:00, Erin Hodgess wrote: > When I have compiled from sourced on Ubuntu, I did NOT include the > "with-tcltk" and it worked fine.? Did you try that, please? In the past I have configured without using the "--with-tcltk" flag, and R of course built just fine. But it *did not* have tcltk capability. When I wanted that capability I had to start using the

>> Oh I don't doubt the basics, red book is red book and bits are >> identically replicable and re rippable bits. > > I don't see any problem with taking innovation as far as is practical > and saying "it's finished, no more updates". Sure, basics :) Again, I'm meaning in regard to about bugs, docs, porting and nits. > If I want to do freedb