Matthew Gyurgyik:
> May not be much help, but
>
> Prior to 3.2 I had to use "echo USB0 > /proc/acpi/wakeup" to allow
> my keyboard/mouse to wake up the computer (USB0 was disabled by
> default). Now with 3.2 this no longer the case (USB0 is enabled by
> default).
On the contrary, this is ext
Ah, indeed. I verified this with bsdtar itself and reported the bug
upstream. It's http://code.google.com/p/libarchive/issues/detail?id=225
for anyone interested. Hope they fix it soon.
On Fri, Jan 20, 2012 at 12:07 AM, Thomas Bächler wrote:
> This looks like a new bug in bsdtar/libarchive - whic
In ArchHaskell we are heavy users of mkarchroot/makechrootpkg for
building packages. When setting up the root chroot pacman is
configured with a local db located at `/repo`, this makes already
built packages available as dependencies later on in a multi-package
build, and by using makechrootpkg's
On 20/01/12 22:11, Magnus Therning wrote:
> In ArchHaskell we are heavy users of mkarchroot/makechrootpkg for
> building packages. When setting up the root chroot pacman is
> configured with a local db located at `/repo`, this makes already
> built packages available as dependencies later on in a
I know arch tries to keep to upstream but their seems some
discrepencies that you may or may not be aware of so thought I'd share.
The crypt man page says glibc may not support blowfish (stronger than
nists recommendation) and that seems true when used via the commandline
(very short output).
The
On Jan 20, 2012 2:10 AM, "Florian Pritz" wrote:
>
> On 20.01.2012 02:18, David J. Haines wrote:
> > On Thu, Jan 19, 2012 at 8:08 PM, Tavian Barnes
> > wrote:
> >> On 19 January 2012 18:23, Dmitry Korzhevin
wrote:
> >>> a funny bug in the Xorg server that could allow attackers with
physical
> >>>
On Friday 20 January 2012 07:30:53 am Allan McRae wrote:
> On 20/01/12 22:11, Magnus Therning wrote:
> > In ArchHaskell we are heavy users of mkarchroot/makechrootpkg for
> > building packages. When setting up the root chroot pacman is
> > configured with a local db located at `/repo`, this make
On Fri, Jan 20, 2012 at 13:30, Allan McRae wrote:
[...]
> touch /repo/repo.db
Ah, how silly, I didn't try that. Indeed, it seems to work.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http:
On Fri, Jan 20, 2012 at 7:53 AM, David J. Haines wrote:
> On Jan 20, 2012 2:10 AM, "Florian Pritz" wrote:
>>
>> On 20.01.2012 02:18, David J. Haines wrote:
>> > On Thu, Jan 19, 2012 at 8:08 PM, Tavian Barnes
>> > wrote:
>> >> On 19 January 2012 18:23, Dmitry Korzhevin
>> >> wrote:
>> >>> a funn
Am 20.01.2012 02:08, schrieb Tavian Barnes:
> IMO, it's not an X.Org or configuration bug, it's a bug in all the
> screen lockers.
>
> http://seclists.org/oss-sec/2012/q1/217
>
This post is horribly wrong.
1) The documentation cited is from Xorg 6.8, which is terribly old.
2) The options cited
I stand corrected in my "interim" language.
David J. Haines
dhai...@gmail.com
On Fri, Jan 20, 2012 at 10:56 AM, Thomas Bächler wrote:
> Am 20.01.2012 02:08, schrieb Tavian Barnes:
>> IMO, it's not an X.Org or configuration bug, it's a bug in all the
>> screen lockers.
>>
>> http://seclists.org
El 20/01/12 04:10, Florian Pritz escribió:
On 20.01.2012 02:18, David J. Haines wrote:
On Thu, Jan 19, 2012 at 8:08 PM, Tavian Barnes
wrote:
On 19 January 2012 18:23, Dmitry Korzhevin wrote:
a funny bug in the Xorg server that could allow attackers with physical
access to a machine to bypas
On 20.01.2012 18:38, Sébastien le Preste de Vauban wrote:
> El 20/01/12 04:10, Florian Pritz escribió:
>> On 20.01.2012 02:18, David J. Haines wrote:
>>> On Thu, Jan 19, 2012 at 8:08 PM, Tavian Barnes
>>> wrote:
On 19 January 2012 18:23, Dmitry Korzhevin wrote:
> a funny bug in the Xorg
El 20/01/12 15:07, Florian Pritz escribió:
On 20.01.2012 18:38, Sébastien le Preste de Vauban wrote:
El 20/01/12 04:10, Florian Pritz escribió:
On 20.01.2012 02:18, David J. Haines wrote:
On Thu, Jan 19, 2012 at 8:08 PM, Tavian Barnes
wrote:
On 19 January 2012 18:23, Dmitry Korzhevin wro
On 01/19/2012 12:35 PM, Nils wrote:
I believe closed nvidia drivers will shift the symbol. I tested it myself on
ati and intel graphics, both 32 and 64 bit and it looked good, both on Linux
and Windows. Other users with ati and intel GPU's had no problem. But two
persons with an nvidia card ha
On 01/20/2012 04:32 AM, Kevin Chadwick wrote:
I know arch tries to keep to upstream but their seems some
discrepencies that you may or may not be aware of so thought I'd share.
The crypt man page says glibc may not support blowfish (stronger than
nists recommendation) and that seems true when us
No. Everything is fine. I just removed the auto-insert of that item because the
issue is fixed. You already pulled the fixed version were the user is free
(again) to enter whatever he wants :)
Nils
On Fri, 20 Jan 2012 22:25:54 +0100
Michi wrote:
> On 20.01.2012 01:08, Nils wrote:
> > Thank yo
On Fri, 20 Jan 2012 13:52:37 -0600
"David C. Rankin" wrote:
> On 01/19/2012 12:35 PM, Nils wrote:
> > I believe closed nvidia drivers will shift the symbol. I tested it myself
> > on ati and intel graphics, both 32 and 64 bit and it looked good, both on
> > Linux and Windows. Other users with a
I just noticed today after a fresh reboot that whenever my laptop
connects now wirelessly, I get a new message in dmesg saying:
Intel AES-NI instructions are not detected.
Figuring was a bad boot or something along those lines I tried a couple
more reboots, to no avail. It is still mentioning t
On Fri, 20 Jan 2012 14:17:22 -0800
Don Juan wrote:
> Not sure if I am getting what you mean here but to me sounds like you
> did not complete what is in the wiki in regards to running blowfish,
> since you need AUR package and what not and it says there is more to do
> than change a single file
On 01/20/2012 03:04 PM, Kevin Chadwick wrote:
On Fri, 20 Jan 2012 14:17:22 -0800
Don Juan wrote:
Not sure if I am getting what you mean here but to me sounds like you
did not complete what is in the wiki in regards to running blowfish,
since you need AUR package and what not and it says there i
On Sat, Jan 21, 2012 at 12:02 AM, Don Juan wrote:
> I just noticed today after a fresh reboot that whenever my laptop connects
> now wirelessly, I get a new message in dmesg saying:
> Intel AES-NI instructions are not detected.
>
> Figuring was a bad boot or something along those lines I tried a c
On 01/20/2012 03:40 PM, Jan Steffens wrote:
On Sat, Jan 21, 2012 at 12:02 AM, Don Juan wrote:
I just noticed today after a fresh reboot that whenever my laptop connects
now wirelessly, I get a new message in dmesg saying:
Intel AES-NI instructions are not detected.
Figuring was a bad boot or s
On Fri, 20 Jan 2012 15:42:51 -0800
Don Juan wrote:
> On 01/20/2012 03:40 PM, Jan Steffens wrote:
> > On Sat, Jan 21, 2012 at 12:02 AM, Don Juan wrote:
> >> I just noticed today after a fresh reboot that whenever my laptop connects
> >> now wirelessly, I get a new message in dmesg saying:
> >> In
On 01/20/2012 03:51 PM, Leonid Isaev wrote:
On Fri, 20 Jan 2012 15:42:51 -0800
Don Juan wrote:
On 01/20/2012 03:40 PM, Jan Steffens wrote:
On Sat, Jan 21, 2012 at 12:02 AM, Don Juan wrote:
I just noticed today after a fresh reboot that whenever my laptop connects
now wirelessly, I get a ne
On 01/20/2012 03:51 PM, Leonid Isaev wrote:
On Fri, 20 Jan 2012 15:42:51 -0800
Don Juan wrote:
On 01/20/2012 03:40 PM, Jan Steffens wrote:
On Sat, Jan 21, 2012 at 12:02 AM, Don Juan wrote:
I just noticed today after a fresh reboot that whenever my laptop connects
now wirelessly, I get a ne
26 matches
Mail list logo
