Hi,
Hussam Al-Tayeb wrote:
Same issue here. If possible, can one of the developers please take a
look at this?
My name change analysis was wrong.
It seems that cryptsetup is triggering the loading of padlock-aes.ko and
padlock-sha.ko even on hardware that doesn't work with them.
I ignored
Roman Kyrylych wrote:
2008/1/29, JaDa<[EMAIL PROTECTED]>:
Hi Allan
I just post now the PKGBUILD hope that's right now!
I didn't actually test how it builds but inlined a couple of suggestions below:
makedepends=('pkgconfig' 'libtool' 'automake' 'autoconf' 'imagemagick'
'smbc
2008/1/29, JaDa <[EMAIL PROTECTED]>:
> Hi Allan
>
> I just post now the PKGBUILD hope that's right now!
>
I didn't actually test how it builds but inlined a couple of suggestions below:
> makedepends=('pkgconfig' 'libtool' 'automake' 'autoconf' 'imagemagick'
> 'smbclient' 'mesa' 'al
Hi there,
I'm the owner of the domain www.archlinux.eu.
I registered this domain in the sunrise period of dot-eu to avoid commercial
usage or something else.
Actually there is a redirection to archlinux.org.
If the archlinux project is interested in this domain I'd like to spend it to
the pro
On Donnerstag, 31. Januar 2008 23:05 Aaron Griffin wrote:
> The '-' character searching is fixed with the groff package in
> testing. It will move to core soon.
Fantastic. I take the files from testing and now man works well with utf8.
Thanks a lot.
See you, Attila
On Jan 31, 2008 3:28 PM, Attila <[EMAIL PROTECTED]> wrote:
> On Donnerstag, 31. Januar 2008 21:25 Grigorios Bouzakis wrote:
>
> > Regarding the discussion going on in arch-dev-public about changes in
> > man and utf8 compliance.
>
> I support every step to get utf8 and man work together. At the mom
On Donnerstag, 31. Januar 2008 21:25 Grigorios Bouzakis wrote:
> Regarding the discussion going on in arch-dev-public about changes in
> man and utf8 compliance.
I support every step to get utf8 and man work together. At the moment with
LANG=de_DE.utf8 i give NROFF the '-Tascii' option. But this
On Thu, 2008-01-31 at 11:46 +, Neil Darlow wrote:
> Hi,
>
> To clarify.
>
> Neil Darlow wrote:
> > Too me, it looks like these modules have undergone a name change in
> > 2.6.24. I think the required modules are actually being loaded but
> > cryptsetup complains about missing modules.
>
>
On Jan 31, 2008 2:25 PM, Grigorios Bouzakis <[EMAIL PROTECTED]> wrote:
> Regarding the discussion going on in arch-dev-public about changes in
> man and utf8 compliance.
> As far as i remember Roman's feature request [1] wasnt even mentioned.
> At least not recently. Are there any thoughts of repla
Regarding the discussion going on in arch-dev-public about changes in
man and utf8 compliance.
As far as i remember Roman's feature request [1] wasnt even mentioned.
At least not recently. Are there any thoughts of replacing man with
man-db? Or the recent chamges in man and groff make this FR inv
Hi,
To clarify.
Neil Darlow wrote:
Too me, it looks like these modules have undergone a name change in
2.6.24. I think the required modules are actually being loaded but
cryptsetup complains about missing modules.
It appears the following name changes have occurred:
* padlock_aes.ko --> pad
Hi,
I run encrypted swap on my i686 system and thought I would give
kernel26-2.6.24 a try.
During the encrypted swap setup phase of boot I noticed a couple of
errors relating to loading of the aes and sha256 crypto modules.
Too me, it looks like these modules have undergone a name change in
12 matches
Mail list logo
