search for: bookeeping

Using dovecot 1.0.10. In the config: namespace public { separator = / hidden = no prefix = Flock/ location = maildir:/home/baratin/PublicMaildir:CONTROL=~/Maildir/control/Flock:INDEX=/var/dovecot/index/%u/Flock } This should be a public mail folder owned by "baratin", "read only" for all other users. Every user has his/her own control and index area

Can wine only be installed on a linux platform or is there a way to download it and run it on windows xp?

Well, I understand what they do and how, I just don''t get why! It seems to me that any time you would have this relationship between two tables...they should be one table! Agile Rails book gives what seems to me to be a lame example for this. They use the example of an "invoice" and an "order". An invoice belongs to an order and an order has one invoice. Seems

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge

Hi all, First thing first: It works, I now no longer have a few dropped frames every 10s on my testbox here with the pageflip i-g-t tests. Random notes: - New design has per-crtc locks to protect the crtc input-side (pageflip, cursor) for r/w and the output state of the crtc (mode, dpms) as read-only. It also required completely revamped fb lifecycle management, those are now refcounted