Re: [arch-general] Why not create a new repo specified for games ?

2011-10-31 Thread Oon-Ee Ng
On Tue, Nov 1, 2011 at 1:46 PM, wrote: > > Hi all, > >   I noticed that there are some games in the community repo. > Some of them has _HUGE_ data packages. > >   Why not create a new repo for those games? That will save > some bandwidth if a mirror maintainer decided to not support > games. > >

[arch-general] Why not create a new repo specified for games ?

2011-10-31 Thread goodmenzy
Hi all, I noticed that there are some games in the community repo. Some of them has _HUGE_ data packages. Why not create a new repo for those games? That will save some bandwidth if a mirror maintainer decided to not support games. By far, not everyone play game on our ArchLinux.

Re: [arch-general] [signoff] linux 3.1-3

2011-10-31 Thread Matthew Monaco
On 10/31/2011 03:27 PM, Thomas Bächler wrote: Compared to the last release, a few bugfixes: Fix FS#19234, FS#26674, FS#25939, FS#26528 and a wrong drm error. Please sign off. x86_64, usb reset resume patch works

[arch-general] [signoff] linux 3.1-3

2011-10-31 Thread Thomas Bächler
Compared to the last release, a few bugfixes: Fix FS#19234, FS#26674, FS#25939, FS#26528 and a wrong drm error. Please sign off. signature.asc Description: OpenPGP digital signature

Re: [arch-general] [signoff] linux-3.1-2

2011-10-31 Thread Thomas Bächler
Am 27.10.2011 18:21, schrieb illdred: > On Thu, 27 Oct 2011 10:37:12 +0200 > Thomas Bächler wrote: > >> Am 27.10.2011 06:00, schrieb illdred: >>> and some of the error messages mention something about scsi but fore >>> scrolling past. then the system stops doing anything. >> >> Those are probabl

Re: [arch-general] [signoff] linux-3.1-2

2011-10-31 Thread Thomas Bächler
Am 27.10.2011 18:21, schrieb illdred: > On Thu, 27 Oct 2011 10:37:12 +0200 > Thomas Bächler wrote: > >> Am 27.10.2011 06:00, schrieb illdred: >>> and some of the error messages mention something about scsi but fore >>> scrolling past. then the system stops doing anything. >> >> Those are probabl

Re: [arch-general] [arch-dev-public] [signoff] cryptsetup 1.4.0-1

2011-10-31 Thread Thomas Bächler
Am 31.10.2011 13:18, schrieb Geert Hendrickx: > Apparantly this affects only plain volumes (not luks), > and will be fixed in 1.4.1: > > http://code.google.com/p/cryptsetup/issues/detail?id=115 > > You may want to include the patch already? > http://code.google.com/p/cryptsetup/source/detail?r=66

Re: [arch-general] [arch-dev-public] [signoff] cryptsetup 1.4.0-1

2011-10-31 Thread Geert Hendrickx
Apparantly this affects only plain volumes (not luks), and will be fixed in 1.4.1: http://code.google.com/p/cryptsetup/issues/detail?id=115 You may want to include the patch already? http://code.google.com/p/cryptsetup/source/detail?r=665# Geert -- geert.hendrickx.be :: ge...@hendric

Re: [arch-general] [arch-dev-public] [signoff] cryptsetup 1.4.0-1

2011-10-31 Thread Geert Hendrickx
On Mon, Oct 31, 2011 at 13:11:31 +0100, Thomas Bächler wrote: > Am 31.10.2011 12:54, schrieb Geert Hendrickx: > > Appears to work fine, however I noticed a change in cryptsetup status > > output: > > > > /dev/mapper/cryptswap is active. > >type:PLAIN > >cipher: aes-cbc-essiv:sha256

Re: [arch-general] [arch-dev-public] [signoff] cryptsetup 1.4.0-1

2011-10-31 Thread Thomas Bächler
Am 31.10.2011 12:54, schrieb Geert Hendrickx: > Appears to work fine, however I noticed a change in cryptsetup status output: > > /dev/mapper/cryptswap is active. >type:PLAIN >cipher: aes-cbc-essiv:sha256 > - keysize: 256 bits > + keysize: 0 bits >device: /dev/xvda1 >offse

Re: [arch-general] [arch-dev-public] [signoff] cryptsetup 1.4.0-1

2011-10-31 Thread Bjørn Øivind Bjørnsen
On 31/10/11 12:54, Geert Hendrickx wrote: Appears to work fine, however I noticed a change in cryptsetup status output: /dev/mapper/cryptswap is active. type:PLAIN cipher: aes-cbc-essiv:sha256 - keysize: 256 bits + keysize: 0 bits device: /dev/xvda1 offset: 0 sectors

Re: [arch-general] [arch-dev-public] [signoff] cryptsetup 1.4.0-1

2011-10-31 Thread Geert Hendrickx
Appears to work fine, however I noticed a change in cryptsetup status output: /dev/mapper/cryptswap is active. type:PLAIN cipher: aes-cbc-essiv:sha256 - keysize: 256 bits + keysize: 0 bits device: /dev/xvda1 offset: 0 sectors size:2097152 sectors (both on the existing