On Tue, Jul 16, 2013 at 6:34 PM, mert <472114...@qq.com> wrote:
> Hi,
> I noticed there's alway an 'Unable to dock' error message after suspend
> to RAM:
>
>
> Arch kernel: ACPI: Low-level resume complete
> Arch kernel: PM: Restoring platform NVS memory
> Arch kernel: Enabling non-boot
[2013-07-21 18:56:28 -0400] Leonid Isaev:
> Is there a particular reason why the images themselves are signed as
> opposed to only their checksum files? For instance, Fedora provides
> sha256sums with inline sigs [1], and verifying image checksum + checksum file
> signature is _much_ less CPU
Hi,
One of the ways to verify an archlinux iso image is via its gpg
signature. However, doing this on an atom/geode system with < 1GiB of RAM is
definitely not fun. And I suppose it also takes noticeable time to sign, even
on an opteron/xeon server.
Is there a particular reason why
On 07/19/2013 08:31 PM, Robert Spahr wrote:
> On Tue, 9 Jul 2013 11:13:08 +0100
> M Saunders wrote:
>
>> But it'd be interesting to hear from
>> people running Arch on production servers, how well it works for them
>> and what (if any) problems they've faced.
>
> Mike,
>
> As an artist that mak
4 matches
Mail list logo