search for: covers

After fresh installation of CentOS 6.2 on my server, I get following errors in my dmesg output: ------- MTRR default type: uncachable MTRR fixed ranges enabled: 00000-9FFFF write-back A0000-BFFFF uncachable C0000-D7FFF write-protect D8000-E7FFF uncachable E8000-FFFFF write-protect MTRR variable ranges enabled: 0 base 000000000 mask C00000000 write-back 1 base 400000000 mask

Good Day All, Today I looked at the dmesg log and I notice that the following messages regarding mtrr_gran_size/mtrr_chunk_size. I am currently running CentOS 6.3 and I installed CentOS 6.2 and 6.1 and I was seeing the same errors. When I installed CentOS 5.8 on the same laptop I do not see these errors. $ lsb_release -a LSB Version:

Hi, I have server that has been running 5.x - 5.8 for a few years without issue and decided to move it to a fresh install of 6.2. First thing I noticed is a good part of the log has these mtrr messages finally ending with "mtrr_cleanup: can not find optimal value" and "please specify mtrr_gran_size/mtrr_chunk_size". I have been searching around and reading the kernel docs

Dear list, I would like to apply my own colours to a stacked area plot, done with qplot, but I have not succeeded... What do I have so far (I am dealing with the development of cover of specific groups of plants): library(ggplot2) library(RODBC) channel <- odbcConnect("myusername", case="tolower") sql <- "select trial, cover_of, dateofsurvey, cover from

HI, Dear R community, I have the following codes to calculate the commulative coverage. I want to save the output in a vector, How to do this? test<-seq(10, 342, by=2) #cover is a vector cover_per<-function (cover) { for (i in min(cover):max(cover)) {print(100*sum(ifelse(cover >= i, 1, 0))/length(cover))} } result<-cover_per(test) > result NULL Can anyone help me this this?

...en Solaris and Linux systems. Here the application opens its control files and some data files. At some specific point the logfiles beginn to differ: with the Solaris samba server, the ArcView application reads the data files with 4k blocks in a sequential manner like this: [...] read_file (daten/covers/dhm_offset/o1000c/arc.adf): pos = 0, size = 4096, returned 4096 read_file (daten/covers/dhm_offset/o1000c/arc.adf): pos = 4096, size = 4096, returned 4096 read_file (daten/covers/dhm_offset/o1000c/arc.adf): pos = 8192, size = 4096, returned 4096 read_file (daten/covers/dhm_offset/o1000c/arc.a...

...en Solaris and Linux systems. Here the application opens its control files and some data files. At some specific point the logfiles beginn to differ: with the Solaris samba server, the ArcView application reads the data files with 4k blocks in a sequential manner like this: [...] read_file (daten/covers/dhm_offset/o1000c/arc.adf): pos = 0, size = 4096, returned 4096 read_file (daten/covers/dhm_offset/o1000c/arc.adf): pos = 4096, size = 4096, returned 4096 read_file (daten/covers/dhm_offset/o1000c/arc.adf): pos = 8192, size = 4096, returned 4096 read_file (daten/covers/dhm_offset/o1000c/arc.a...

Coverity generates false positives when read_atomic() and write_atomic() are called with pointers to objects smaller than 64 bits (because it can''t see that the 64-bit access in the switych statement is dead code). I don''t want to automatically suppress all ofthose, because read_atomic() and write_atomic() could still be called with mis-cast pointers, but for atomic_t accessors

With these versions: ii autoconf 2.54-2 automatic configure script builder ii automake1.6 1.6.3-2 A tool for generating GNU Standards-complian I am unable to build the autoconfiscations. autoheader gives: autoheader2.50: error: AC_CONFIG_HEADERS not found in configure.in What versions are you using? (btw, I do think it would be a very good idea to start using

Hi folks! I''m about five weeks into Rails; this is my first question after lurking for a little while. I''m writing an app to help a printer verify that the information on magazine covers is correct; this verification happens across several organizations, and for several magazine titles. When a particular cover is "stalled" in one status for two long, the app needs to figure out who should get a warning message. The way the db is designed right now is: table "use...

....] [2005/12/12 14:37:16, 3] smbd/process.c:switch_message(900) switch message SMBreadX (pid 16879) conn 0x84431d0 [2005/12/12 14:37:16, 4] smbd/uid.c:change_to_user(217) change_to_user: Skipping user change - already user [2005/12/12 14:37:16, 10] smbd/fileio.c:read_file(105) read_file (daten/covers/dhm_offset/o1000c/arc.adf): pos = 831488, size = 512, returned 512 [2005/12/12 14:37:16, 3] smbd/reply.c:send_file_readX(2585) send_file_readX fnum=10031 max=512 nread=512 [2005/12/12 14:37:16, 5] lib/util.c:show_msg(454) [2005/12/12 14:37:16, 5] lib/util.c:show_msg(464) size=571 smb_com=0x2e...

Hi all, I'm not sure if you are aware, but libvorbis has been scanned by the Coverity static analysis team : http://scan.coverity.com/ For libvorbis, it found 8 possible bugs. To fix these bugs Coverity need a repesentative from the project to contact them for access to the coverity reporting facilities. The reason I am keen to see Xiph take up this challenge is that when all

When trying to play vorbis or opus files that have large cover sizes >1MB on android 8.0 built in player, they fail to play. Removing the cover allows them to play.  Has anyone encountered this before or know if it is a known android or opus/vorbis bug?

...- so a measure of how well we preserve locations through the whole compiler. "PC ranges covered" is, for each variable in each lexical scope, dividing the number of program text bytes covered by the variable by the number of program text bytes in the lexical scope. If a variable location covers 10 bytes of a scope that is 20 bytes in size, then that's 50% coverage. The headline "PC ranges covered" is the average of all variables in the program -- better at measuring how long we can track known locations. (Obviously there are upsides and downsides of aggregating like this)....

Hi Michal 2012/1/10 Michal Hlavinka <mihl-guest at alioth.debian.org> > Author: mihl-guest > Date: Tue Jan 10 09:10:04 2012 > New Revision: 3383 > URL: http://trac.networkupstools.org/projects/nut/changeset/3383 > > Log: > Creating a branch for Coverity reported problems > I'm very interested there! Have you been able to get NUT part of the Coverity Scan

CentOS 6.4, current, Dell PE R720. Had an issue today with a bus error, and googling only found two year old references to problems with non-Dell drives (we just added two WD Reds, and mdadm raided them). So, looking through dmesg and /var/log/messages, I ran into a *lot* of G gran_size: 128K chunk_size: 256K num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size:

Hello I am trying to plot a 20 x 20 grid of points with the colors of each point refering to percent cover of that specific point So basically the point are all the same size and their position on the graph is base on their coordinates (x,y). I want the color (a grey scale from white=0 to black =100) to represent the values of each of these point (cover) Here is what my data looks like

Hey We have a static analyzer setup for Xen called Coverity. It allows the code to be inspected for bugs and such. Originally I setup this so that we could make sure that there are no bugs that cause security issues - and as such invited only folks on the security Xen mailing list. But there are other folks who I am sure would like to contribute and as Coverity is pretty amazing at analyzing

The Wine development release 1.5.17 is now available. What's new in this release (see below for details): - Sub-pixel font anti-aliasing in the DIB engine. - Support for automatic installation of ActiveX controls. - Automatic fallback to TLS 1.0 for secure connections. - Beginnings of the DirectWrite text analyzer. - Better handling of font outlines in OpenGL. - Various bug fixes.

I have a dataset I need to sort: test.df<-data.frame(Zone=c("Floodplain", "Lake", "Shoreline"),Cover=c(50,60,70)) However, I don't want it sorted ascending/descending but in an order that I define via a vector: sort.v<-data.frame(c("Lake","Shoreline","Floodplain")) I realize I could probably just create the vector of