search for: offses

I recently set up a new system to run backuppc on centOS 5 with the archive stored on a raid1 of 750 gig SATA drives created with 3 members with one specified as "missing". Once a week I add the 3rd partition, let it sync, then remove it. I've had a similar system working for a long time using a firewire drive as the 3rd member, so I don't think the raid setup is the cause

...ontained units (code, data, signature) that can be run on a high-secure falcon (currently PMU). It consumes a blob that is built by the kernel and contains the signed firmwares of the low-secure falcons to load and manage. The ACR blob is made of a header describing the managed falcons and the offses of their bootloader, code and data within the blob, as well as bootloader/code/data sections for each falcon. A signed, low-secure falcon firmware in the ACR blob is thus the aggregation of three different components: - An image containing the bl, code and data sections - A descriptor with the...

...hat can be run on a high-secure falcon (currently >> PMU). It consumes a blob that is built by the kernel and contains the signed >> firmwares of the low-secure falcons to load and manage. >> >> The ACR blob is made of a header describing the managed falcons and the >> offses of their bootloader, code and data within the blob, as well as >> bootloader/code/data sections for each falcon. >> >> A signed, low-secure falcon firmware in the ACR blob is thus the aggregation >> of three different components: >> >> - An image containing the b...

...;>> PMU). It consumes a blob that is built by the kernel and contains the >>>> signed >>>> firmwares of the low-secure falcons to load and manage. >>>> >>>> The ACR blob is made of a header describing the managed falcons and the >>>> offses of their bootloader, code and data within the blob, as well as >>>> bootloader/code/data sections for each falcon. >>>> >>>> A signed, low-secure falcon firmware in the ACR blob is thus the >>>> aggregation >>>> of three different componen...

Hi, I am new to dovecot and have just got it up and running on mandrake 8.2. Dovecot seems to be running OK, I can telnet in and log in and Mail on OS X will get the folder list but if a client selects a mail box I get an error back. I cannot find any help anywhere on the errors I'm getting so I hope this is the right place to ask. Please see the log file below. Any clues to the problem

...is built by the kernel and contains the >>>>>> signed >>>>>> firmwares of the low-secure falcons to load and manage. >>>>>> >>>>>> The ACR blob is made of a header describing the managed falcons and the >>>>>> offses of their bootloader, code and data within the blob, as well as >>>>>> bootloader/code/data sections for each falcon. >>>>>> >>>>>> A signed, low-secure falcon firmware in the ACR blob is thus the >>>>>> aggregation >>>...

..., data, signature) that can be run on a high-secure falcon (currently > PMU). It consumes a blob that is built by the kernel and contains the signed > firmwares of the low-secure falcons to load and manage. > > The ACR blob is made of a header describing the managed falcons and the > offses of their bootloader, code and data within the blob, as well as > bootloader/code/data sections for each falcon. > > A signed, low-secure falcon firmware in the ACR blob is thus the aggregation > of three different components: > > - An image containing the bl, code and data section...

...;> (currently >>> PMU). It consumes a blob that is built by the kernel and contains the >>> signed >>> firmwares of the low-secure falcons to load and manage. >>> >>> The ACR blob is made of a header describing the managed falcons and the >>> offses of their bootloader, code and data within the blob, as well as >>> bootloader/code/data sections for each falcon. >>> >>> A signed, low-secure falcon firmware in the ACR blob is thus the >>> aggregation >>> of three different components: >>> &gt...

...onsumes a blob that is built by the kernel and contains the >>>>> signed >>>>> firmwares of the low-secure falcons to load and manage. >>>>> >>>>> The ACR blob is made of a header describing the managed falcons and the >>>>> offses of their bootloader, code and data within the blob, as well as >>>>> bootloader/code/data sections for each falcon. >>>>> >>>>> A signed, low-secure falcon firmware in the ACR blob is thus the >>>>> aggregation >>>>> of thre...

This patch series introduces the VHD library. It is based on the blktap2 one, with changes coming from the blktap2.5 one. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>