search for: submap

Hi, I am really stuck here. I am trying to setup imap for an external mail server. I have a freebsd server running sendmail / dovecot. I am transfering the existing mail from an exchange 2003 server to the mailserver using imapsync. This works fine, but gives errors when it tries to make a submap, also thunderbird gives an error "Mailbox doesn't allow inferior mailboxes" when I try to make a submap. I found out that it has something to do with the mbox not able to have submaps and there should be a workaround using namespaces. I tried several setups but keep getting errors. Do...

...___________________________________________ dat=data.frame(read.delim(file="all.txt", header = TRUE, sep = "\t", quote="\"", dec=".",na.strings = "NA")) nc=read.shape("astae.shp", dbf.data=TRUE, verbose=TRUE) mappolys=Map2poly(nc) submap <- subset(mappolys, nc$att.data$NAME!="Honolulu, HI") nc$att.data=subset(nc$att.data, nc$att.data$NAME!="Honolulu, HI") nc$att.data[,1]=as.numeric(paste(nc$att.data$MSACMSA)) #attributes(nc$att.data) nc$att.data=merge(nc$att.data, dat, by.x="AREA", by.y="co...

Hello, I have three questions, though all of which already mentioned by other people in the mailing list, about the accuracy of the Vorbis I Specification published on Feb 27. 1. On page 34 section 4.3.4., explanation of the situation where there are only one submap is omitted, and it is difficult to understand that the decoder should assume in such cases that all the audio channels belong to submap #0 in the original order without examining the array [vorbis_mapping_mux] (which is empty). 2. On page 58 section 8.5., it is unclear as to which of the following...

...r, and am having some trouble getting it to work with stereo vorbis data. It's giving me some PCM output which is roughly right, but it has artefacts. I think it's most likely something to do with my handling of floor decode/curve synthesis. My first thoughts are that I'm handling the submap number/floor mapping incorrectly; I'm interested in finding out about this from the documentation; (4.3.2. floor curve decode) [submap_number] = element [i] of vector [vorbis_mapping_mux] What happens if during mapping decoding vorbis_mapping_mux is empty because vorbis_mapping_submaps was 1?...

Hi, In another thread ("PBSmapping and shapefiles") I asked for an easy way to read "shapefiles" and transform them in data that PBSmapping could use. One person is exploring some ways of doing this, but it is possible I'll have to do this "manually". With package "maptools" I am able to extract the information I need from a shapefile but it is

Hello everybody According to "vorbis-spec-ref.html" paragraph: "mappings", the vector [vorbis_mapping_mux] should contain the following: 4. if [vorbis_mapping_submaps] is greater than one, we read channel multiplex settings. For each [j] of [audio_channels] channels: 1. vector [vorbis_mapping_mux] element [j] = read 4 bits as unsigned integer 2. if the value is greater than the highest numbered submap ([vorbis_mapping_submaps] - 1)...

...^^^^^^^^^^^^^^^^^^^ is floor1_partition_class correct ? or should it be floor1_partition_class_list <p>3--------------- According to "vorbis-spec-ref.html" paragraph: "mappings", the vector [vorbis_mapping_mux] should contain the following: 4. if [vorbis_mapping_submaps] is greater than one, we read channel multiplex settings. For each [j] of [audio_channels] channels: 1. vector [vorbis_mapping_mux] element [j] = read 4 bits as unsigned integer 2. if the value is greater than the highest numbered submap ([vorbis_mapping_submaps] - 1)...

Hello, I was testing Fedora 16 (rc2) Xen host, with included Xen 4.1.1 rpms and Linux 3.1.0 dom0 kernel. Fedora 16 PV domUs seem to work nicely. I noticed a problem with Fedora 16 Xen HVM guests though. The F16 guest kernel (Linux 3.1.0) fails with the qemu-dm emulated DVD-ROM drive.. Full HVM guest kernel dmesg attached to this email. See the end of this email for Xen cfgfile for the

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.

...ne pvzone_store; static struct vm_object pvzone_obj; -static int pv_entry_count = 0, pv_entry_max = 0, pv_entry_high_water = 0; +static int pv_entry_count=0, pv_entry_max=0, pv_entry_high_water=0; static int pmap_pagedaemon_waken = 0; static struct pv_entry *pvinit; /* * All those kernel PT submaps that BSD is so fond of */ -#ifdef SMP -extern pt_entry_t *SMPpt; -#define CMAP1 prv_CMAP1 -#define CMAP2 prv_CMAP2 -#define CMAP3 prv_CMAP3 -#define PMAP1 prv_PMAP1 -#define CADDR1 prv_CADDR1 -#define CADDR2 prv_CADDR2 -#define CADDR3 prv_CADDR3 -#define PADDR1 prv_PADDR1 -#else -static pt_entry...

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths