similar to: Precedence of access parameters

Hello all,, Im looking for a simple function to produce a crosstab from a dumped sql query result. Its very hard to produce crosstabs with most databases (Access being the exception), so with the vast array of R packages, Im sure this has to have already been implemented somewhere. Examples are always good: Take a csv dump like name code user1 100 user2 100 user1 200 user2 210 user1 300 user2

Can anyone tell me how to add routes from plugin? I know it is possible because of this changeset: http://dev.rubyonrails.org/changeset/2967 but i didn''t find way how to do it. retro -- Posted via http://www.ruby-forum.com/.

Hi All! On my samba server I`ve got some stuff with require authorization. I create needed users for that. These users belong to the same group - private. But now I want to restrict them even more - I want to bind them to particular IPs. Eg user1 will be able to connect to private share only from user1_IP, user2 from user2_IP. How can I do this with samba ? Here is my private share

On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote: > On Thu, 22 Jan 2015 12:43:43 +1100 > David Gibson <david at gibson.dropbear.id.au> wrote: > > > On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote: > > > With virtio-1, we support more than 32 feature bits. Let's extend both > > > host and guest features to 64, which should

On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote: > On Thu, 22 Jan 2015 12:43:43 +1100 > David Gibson <david at gibson.dropbear.id.au> wrote: > > > On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote: > > > With virtio-1, we support more than 32 feature bits. Let's extend both > > > host and guest features to 64, which should

On Thu, Jan 29, 2015 at 10:24:00AM +0100, Thomas Huth wrote: > > Hi, > > On Thu, 29 Jan 2015 11:11:32 +1100 > David Gibson <david at gibson.dropbear.id.au> wrote: > > > On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote: > > > On Thu, 22 Jan 2015 12:43:43 +1100 > > > David Gibson <david at gibson.dropbear.id.au> wrote: > >

On Thu, Jan 29, 2015 at 10:24:00AM +0100, Thomas Huth wrote: > > Hi, > > On Thu, 29 Jan 2015 11:11:32 +1100 > David Gibson <david at gibson.dropbear.id.au> wrote: > > > On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote: > > > On Thu, 22 Jan 2015 12:43:43 +1100 > > > David Gibson <david at gibson.dropbear.id.au> wrote: > >

On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote: > With virtio-1, we support more than 32 feature bits. Let's extend both > host and guest features to 64, which should suffice for a while. > > vhost and migration have been ignored for now. [snip] > diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h > index f6c0379..08141c7 100644 > ---

On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote: > With virtio-1, we support more than 32 feature bits. Let's extend both > host and guest features to 64, which should suffice for a while. > > vhost and migration have been ignored for now. [snip] > diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h > index f6c0379..08141c7 100644 > ---

Only cosmetic and documentation changes since v5. --- Greg Kurz (8): virtio: introduce virtio_is_little_endian() helper tun: add tun_is_little_endian() helper macvtap: introduce macvtap_is_little_endian() helper vringh: introduce vringh_is_little_endian() helper vhost: introduce vhost_is_little_endian() helper virtio: add explicit big-endian support to memory

Only cosmetic and documentation changes since v5. --- Greg Kurz (8): virtio: introduce virtio_is_little_endian() helper tun: add tun_is_little_endian() helper macvtap: introduce macvtap_is_little_endian() helper vringh: introduce vringh_is_little_endian() helper vhost: introduce vhost_is_little_endian() helper virtio: add explicit big-endian support to memory

Hi, I have was testing some of the different ring types with my polycom 500, and the ALERT_INFO settings. Now when my phone receives a call it won't ring. All the other phones ring fine, and my phone wasn't the only one I rebooted with the changed sip.conf and impd.conf. I have reverted back to a standard sip.conf and impd.conf and I still can not get my phone to ring for any incoming

Hello, I have a data manipulation problem that I can easily resolve by using perl or python to pre-process the data, but I would prefer to do it directly in R. Given, for example: month length ratio monthly1 monthly2 1 Jan 23 0.1 9 6 2 Jan 45 0.2 9 6 3 Jan 16 0.3 9 6 4 Feb 14 0.2 1 9 5 Mar 98 0.4 2 2 6 Mar 02 0.6

On Fri, Oct 11, 2019 at 06:25:18PM -0700, Ram Pai wrote: > From: Thiago Jung Bauermann <bauerman at linux.ibm.com> > > In order to safely use the DMA API, virtio needs to know whether DMA > addresses are in fact physical addresses and for that purpose, > dma_addr_is_phys_addr() is introduced. > > cc: Benjamin Herrenschmidt <benh at kernel.crashing.org> > cc:

On Fri, Oct 11, 2019 at 06:25:18PM -0700, Ram Pai wrote: > From: Thiago Jung Bauermann <bauerman at linux.ibm.com> > > In order to safely use the DMA API, virtio needs to know whether DMA > addresses are in fact physical addresses and for that purpose, > dma_addr_is_phys_addr() is introduced. > > cc: Benjamin Herrenschmidt <benh at kernel.crashing.org> > cc:

Hello, Does R have any facility to create a plot that looks similar to this: http://www.augustcouncil.com/~tgibson/barmatrix.jpg Thank you, -TAG Todd A. Gibson

On Mon, Aug 12, 2019 at 07:51:56PM +1000, David Gibson wrote: > AFAICT we already kind of abuse this for the VIRTIO_F_IOMMU_PLATFORM, > because to handle for cases where it *is* a device limitation, we > assume that if the hypervisor presents VIRTIO_F_IOMMU_PLATFORM then > the guest *must* select it. > > What we actually need here is for the hypervisor to present >

On Mon, Aug 12, 2019 at 07:51:56PM +1000, David Gibson wrote: > AFAICT we already kind of abuse this for the VIRTIO_F_IOMMU_PLATFORM, > because to handle for cases where it *is* a device limitation, we > assume that if the hypervisor presents VIRTIO_F_IOMMU_PLATFORM then > the guest *must* select it. > > What we actually need here is for the hypervisor to present >

On 17.05.2011, at 08:47, David Gibson wrote: > From: Alexey Kardashevskiy <aik at ozlabs.ru> > > The recently added pseries machine does not currently support PCI > emulation. For the (upcoming) kvm case, this is quite difficult to do > because the preferred HV mode for the host kernel does not allow MMIO > emulation (a hardware limitation). > > Therefore, to

On 17.05.2011, at 08:47, David Gibson wrote: > From: Alexey Kardashevskiy <aik at ozlabs.ru> > > The recently added pseries machine does not currently support PCI > emulation. For the (upcoming) kvm case, this is quite difficult to do > because the preferred HV mode for the host kernel does not allow MMIO > emulation (a hardware limitation). > > Therefore, to