search for: anachronistic

...freezes, and eventually > the entire system freezes. Disable msaa until this is fixed. > > This happens on both nv3x and nv4x cards. Ugh. This is aka "you ran out of vram, goodbye". We don't really handle that case extremely well. I feel really bad doing this :( The issue is anachronistic applications like soffice that don't keep with the limitations of GPUs of the days of yore. So we end up penalizing people who do use applications of the day. But the practical issue is that people do upgrade, and people do run these applications, and so it makes sense to keep it off by defaul...

Hi, Given that R reports Type I sums of squares, isn't it a bit anachronistic that it re-orders terms in formulae? > d <- expand.grid(y=rnorm(8), + A=factor(c(1,2)), + B=factor(c(1,2)), + C=factor(c(1,2))) > summary(aov(y ~ A+B+A:B+C,data=d)) Df Sum Sq Mean Sq F value Pr(>F) A 1 8.294e-34 8.294e-3...

Hello, Freebsd-stable. BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of errors on every start and doesn't answer on requests for 30-60 seconds after that. Errors are like this: Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1567: unexpected error: Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53:

...oesn't say much/anything about layering. 'A Public Header File *is* a Module' <https://llvm.org/docs/CodingStandards.html#a-public-header-file-is-a-module> section talks about modules of functionality, mostly trying to describe why a header file should be self contained - but uses anachronistic language about modules that doesn't line up with the implicit or explicit modules concepts in use today, I think. I propose making this wording a bit more explicit, including: 1) Headers should be standalone (include all their dependencies - this is mentioned in the "is a Module" pi...

.... >CHS means Cylinder/Head/Sector addressing method. I knew that, actually. >The Master Boot Record (MBR) at the beginning of the stick has >a partition table with block addresses in two alternative forms. Hummm... so the world has not entirely done away with the kludgy, antiquated and anachronistic old C/H/S addressing scheme just yet, eh? Too bad. We should be rid of it once and for all. (As I understand it, it has been AT LEAST more than a decade and a half... or maybe two... since the notion of physical/addressable cylinders had any relevance to any actual products on the market.) >...

...; doesn't say much/anything about layering. 'A Public Header File is a Module'<https://llvm.org/docs/CodingStandards.html#a-public-header-file-is-a-module> section talks about modules of functionality, mostly trying to describe why a header file should be self contained - but uses anachronistic language about modules that doesn't line up with the implicit or explicit modules concepts in use today, I think. I propose making this wording a bit more explicit, including: 1) Headers should be standalone (include all their dependencies - this is mentioned in the "is a Module" pi...

...hing > about layering. 'A Public Header File *is* a Module' > <https://llvm.org/docs/CodingStandards.html#a-public-header-file-is-a-module> section > talks about modules of functionality, mostly trying to describe why a > header file should be self contained - but uses anachronistic language > about modules that doesn't line up with the implicit or explicit > modules concepts in use today, I think. > > I propose making this wording a bit more explicit, including: > > 1) Headers should be standalone (include all their dependencies - this > is mention...

> > We have identified a bug in auth process, and are working with a fix. > It works for me in 2.2.30-2 -- Angel L. Mateo Mart?nez Secci?n de Telem?tica ?rea de Tecnolog?as de la Informaci?n y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

...anything > about layering. 'A Public Header File *is* a Module' > <https://llvm.org/docs/CodingStandards.html#a-public-header-file-is-a-module> section > talks about modules of functionality, mostly trying to describe why a > header file should be self contained - but uses anachronistic language > about modules that doesn't line up with the implicit or explicit modules > concepts in use today, I think. > > I propose making this wording a bit more explicit, including: > > 1) Headers should be standalone (include all their dependencies - this is > mentioned...

...; about layering. 'A Public Header File *is* a Module' >> <https://llvm.org/docs/CodingStandards.html#a-public-header-file-is-a-module> section >> talks about modules of functionality, mostly trying to describe why a >> header file should be self contained - but uses anachronistic language >> about modules that doesn't line up with the implicit or explicit modules >> concepts in use today, I think. >> >> I propose making this wording a bit more explicit, including: >> >> 1) Headers should be standalone (include all their dependencies -...

http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.5 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.5 Problems Corrected: * If DISABLE_IPV6=Yes in shorewall.conf then harmless error messages referring to $RESTOREBASE are generated during shorewall stop. * An anachronistic comment about enabling mangling has been removed from shorewall.conf. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

...file changed, 3 insertions(+), 10 deletions(-) diff --git a/m4/guestfs_c.m4 b/m4/guestfs_c.m4 index e91446f..7250294 100644 --- a/m4/guestfs_c.m4 +++ b/m4/guestfs_c.m4 @@ -43,22 +43,15 @@ fi dnl This, $nw, is the list of warnings we disable. nw= nw="$nw -Waggregate-return" # anachronistic -nw="$nw -Wc++-compat" # We don't care about C++ compilers nw="$nw -Wundef" # Warns on '#if GNULIB_FOO' etc in gnulib nw="$nw -Wtraditional" # Warns on #elif which we use often -nw="$nw -Wcast-qual&quo...

Hi, > Hummm... so the world has not entirely done away with the kludgy, > antiquated and anachronistic old C/H/S addressing scheme just yet, > eh? It must actually have been your preparation of the USB stick which has chosen a FAT filesystem with CHS. I refer to this statement of yours, of Fri, 17 Jan 2014 13:48:21 -0800: >> Furthermore, and separately, regardless of the install method (L...

Hi, Dan, This patch fixes strange behavior on IA64, that IDLE is scheduled more than Dom0 with default sEDF scheduler. The key point is reprogram_ac_timer at the end of ac_timer dispatcher, which programs local apic timer with expire of next ac_timer on x86. Higher precision lapic timer can trigger ac_timer more precisely than simply done in PIT interrupt handler. That works perfectly on x86

...doesn't say much/anything about layering. 'A Public Header File is a Module' <https://llvm.org/docs/CodingStandards.html#a-public-header-file-is-a-module> section talks about modules of functionality, mostly trying to describe why a header file should be self contained - but uses anachronistic language about modules that doesn't line up with the implicit or explicit modules concepts in use today, I think. > > I propose making this wording a bit more explicit, including: > > 1) Headers should be standalone (include all their dependencies - this is mentioned in the "...

...rom Kony 2012 redrawn as a bar chart in R: http://bit.ly/HylxcT Sanjiv Das uses R to analyze when banks should modify distressed home loans, and which banks are still too big to fail: http://bit.ly/HylyO8 Step-by-step tutorials to get Hadoop running with R on Amazon EC2: http://bit.ly/Hylxd0 How anachronistic is the language of Downton Abbey, really? http://bit.ly/HylxcZ . (And if you don't know what Downton Abbey is: http://bit.ly/HylxcY .) SAP integrates R with its HANA in-memory database: http://bit.ly/HylxcX Tips on using the "lubridate" package to simplify working with times and dat...

.../lib/compat.h there is a definition for p(read|write) that conflicts with the one in /usr/include/unistd.h On this box, there is a macro appended to the definition (to control whether or not THROW is defined in C++ "mode"). This is regulated by using the macro __THROW. I assume this is anachronistic. 2) There was an odd overflow bug in the quota module. (Yes, would you believe that user quotas are used + enforced on this Frankenbox?) I assume it's a rarely seen issue because few Dovecot users compile the software in caves on computers powered by horse-pulled generator wheels. I suspect...

...anything > about layering. 'A Public Header File *is* a Module' > <https://llvm.org/docs/CodingStandards.html#a-public-header-file-is-a-module> section > talks about modules of functionality, mostly trying to describe why a > header file should be self contained - but uses anachronistic language > about modules that doesn't line up with the implicit or explicit modules > concepts in use today, I think. > > I propose making this wording a bit more explicit, including: > > 1) Headers should be standalone (include all their dependencies - this is > mentioned...

...anything > about layering. 'A Public Header File *is* a Module' > <https://llvm.org/docs/CodingStandards.html#a-public-header-file-is-a-module> section > talks about modules of functionality, mostly trying to describe why a > header file should be self contained - but uses anachronistic language > about modules that doesn't line up with the implicit or explicit modules > concepts in use today, I think. > > I propose making this wording a bit more explicit, including: > > 1) Headers should be standalone (include all their dependencies - this is > mentioned...

https://bugs.freedesktop.org/show_bug.cgi?id=91037 Bug ID: 91037 Summary: desktop freezes shortly after boot with NV11 [GeForce2 MX/MX 400] Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium