similar to: Development version of R fails a regression test

Dear r-devel list members, By placing a call to the new (with R 2.15.1) globalVariables() in the development version of the Rcmdr package, I've succeeded in reducing the "notes" produced by R CMD check from dozens to two. But I still get the following notes, even though '.commander.done' is in the call to globalVariables(): ------------- snip ------------ * checking R code

I am looking to only sync directories not any files within them.. Is there a switch/trick available for this in rsync ? Thanks for any suggestions !! Tim Nelson Senior UNIX Systems Administrator OSI Support Services, Inc. 2520 N. 170th Street New Berlin, WI 53151 T: 262-780-2134 F: 262-780-2050 E: tim.nelson@osioutsourcing.com Outsourcing services are primarily performed by OSI

On Wed, Aug 14, 2019 at 3:31 PM Karol Herbst <kherbst at redhat.com> wrote: > > This reverts commit 9251a71db62ca9cc7e7cf364218610b0f018c291. > > This was never discussed with anybody Nouveau related and we would have NACKed > this change immediately. > > We have a better workaround, which makes it actually work with Nouveau. No idea > why the comment mentions the

It's hard to figure out what systems are actually affected and right now I don't see a good way of removing those... But I'd like to see thos getting removed and drivers fixed instead (which happened at least for nouveau). And as mentioned before, I prefer people working on fixing issues instead of spending time to add firmware level workarounds which are hard to know to which

On Fri, Jul 17, 2020 at 9:52 PM Alex Hung <alex.hung at canonical.com> wrote: > > On 2020-07-17 1:05 p.m., Karol Herbst wrote: > > It's hard to figure out what systems are actually affected and right now I > > don't see a good way of removing those... > > > > But I'd like to see thos getting removed and drivers fixed instead (which > > happened

First three patches are removing ACPI workarounds which should have never landed. The last four are adding a workaround to nouveau which seem to help quite a lot with the RTD3 issues with Nouveau, so let's discuss and get wider testing of those and see if there is any fallout or laptops where the issues don't get fixed. Karol Herbst (7): Revert "ACPI / OSI: Add OEM _OSI string to

Hello. I'm trying to make some graphics with nationalized labels (pdf for use in LaTeX document). On console (displayed on screen) using all looks ok: ----------------------------------------\/ data<-rnorm(100) hist(data,main='Rozk?ad g?sto?ci punkt?w', xlab='Warto?? na osi y', ylab='Cz?sto?? wyst?powania') -------------------------------------------/\ But

> -----Original Message----- > From: Karol Herbst <kherbst at redhat.com> > Sent: Thursday, August 15, 2019 9:25 AM > To: Limonciello, Mario > Cc: Dave Airlie; LKML; Linux ACPI Mailing List; dri-devel; nouveau; Rafael J . > Wysocki; Alex Hung; Ben Skeggs; David Airlie > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to > enable dGPU

Hello everyone, Recently I have been testing my customized Xen 4.2 networking setup. It works pretty good and I would like to share it with anyone who is interested. The relevant files can be found here: https://github.com/slacks42/xenscripts Benefit: configure the Xen related networking devices with one understandable bash script. Please note that this is all still work in progress. For

On Thu, Aug 15, 2019 at 10:15 AM Karol Herbst <kherbst at redhat.com> wrote: > > On Thu, Aug 15, 2019 at 4:13 PM Alex Deucher <alexdeucher at gmail.com> wrote: > > > > On Thu, Aug 15, 2019 at 10:04 AM Karol Herbst <kherbst at redhat.com> wrote: > > > > > > On Thu, Aug 15, 2019 at 3:56 PM <Mario.Limonciello at dell.com> wrote: > >

Hello. I need your help, DomU xen network diconnects randomly, how do you monitoring this? When I connect to vnc server in the hosts, DomU is running, then I open the DomU, after that guest network responds. DomU Debian 6.03 over Centos 5.7 and Xen 3.03. My network configuration: eth0 Link encap:Ethernet HWaddr 68:B5:99:78:AA:6D inet addr:192.168.5.230 Bcast:192.168.5.255

> -----Original Message----- > From: Takashi Iwai <tiwai at suse.de> > Sent: Thursday, August 15, 2019 9:57 AM > To: Alex Deucher > Cc: Karol Herbst; Limonciello, Mario; nouveau; Rafael J . Wysocki; LKML; dri-devel; > Linux ACPI Mailing List; Alex Hung; Ben Skeggs; David Airlie > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to >

On Fri, Apr 24, 2015 at 03:15:27PM +0200, Joerg Schilling wrote: > Stephen Harris <lists at spuddy.org> wrote: > > > Bash was bigger than ksh in the non-commercial Unix world because of ksh88 > > licensing problems. Back in 1998 I wanted to teach a ksh scripting > > course to my local LUG, but AT&T (David Korn himsef!) told me I couldn't > > give

IPS HLBR - Version 1.0 can detect malicious traffic using regular expressions Version 1.0 of Hogwash Light BR, released march 5th 2006, brings two interesting new features. The first one is the ability of using regular expressions to detect intrusion attempts and e-mails with virus or phishing. The second is the use of lists with banned words. HLBR is an IPS (Intrusion Prevention System) that

Unfortunately, our lawyers say that they can't give legal advice in this context. My question would be, what are people looking for that the MIT or 2-clause BSD license don't provide? They're short, clear, widely accepted and very permissive. Another possibility might be to dual-license packages with both an OSI-approved license and whatever-else-you-like, e.g. 'MIT |

This reverts commit 28586a51eea666d5531bcaef2f68e4abbd87242c. The original commit message didn't even make sense. AMD _does_ support it and it works with Nouveau as well. Also what was the issue being solved here? No references to any bugs and not even explaining any issue at all isn't the way we do things. And even if it means a muxed design, then the fix is to make it work inside the

This reverts commit 9251a71db62ca9cc7e7cf364218610b0f018c291. This was never discussed with anybody Nouveau related and we would have NACKed this change immediately. We have a better workaround, which makes it actually work with Nouveau. No idea why the comment mentions the Nvidia driver and assumes it gives any weight to the reasoning.... we don't care about out of tree drivers. Nouveau

On Thu, Aug 15, 2019 at 10:04 AM Karol Herbst <kherbst at redhat.com> wrote: > > On Thu, Aug 15, 2019 at 3:56 PM <Mario.Limonciello at dell.com> wrote: > > > > > -----Original Message----- > > > From: linux-acpi-owner at vger.kernel.org <linux-acpi-owner at vger.kernel.org> On > > > Behalf Of Dave Airlie > > > Sent: Wednesday,

On 2020-07-17 1:05 p.m., Karol Herbst wrote: > It's hard to figure out what systems are actually affected and right now I > don't see a good way of removing those... > > But I'd like to see thos getting removed and drivers fixed instead (which > happened at least for nouveau). > > And as mentioned before, I prefer people working on fixing issues instead > of

On Thu, Aug 15, 2019 at 1:35 AM Alex Hung <alex.hung at canonical.com> wrote: > > On Wed, Aug 14, 2019 at 3:31 PM Karol Herbst <kherbst at redhat.com> wrote: > > > > This reverts commit 9251a71db62ca9cc7e7cf364218610b0f018c291. > > > > This was never discussed with anybody Nouveau related and we would have NACKed > > this change immediately. >