Re: Failsafe on kernel panic

2013-02-02 Thread Andrey Zonov
On 1/20/13 6:07 PM, Willem Jan Withagen wrote: > On 17-1-2013 4:18, Ian Lepore wrote: >> On Wed, 2013-01-16 at 23:27 +0200, Sami Halabi wrote: >>> Thank you for your response, very helpful. >>> one question - how do i configure auto-reboot once kernel panic occurs? >>> >>> Sami >>> >> >> From src/s

Re: acpi resume related patch

2013-02-02 Thread Jakub Lach
Does not apply cleanly for me on 9-STABLE. I've tried svn patch acp(...) and patch http://freebsd.1045724.n5.nabble.com/acpi-resume-related-patch-tp5780721p5783166.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@f

Re: acpi resume related patch

2013-02-02 Thread Andre Goree
On 01/25/13 03:44, Andriy Gapon wrote: > > If you have ACPI suspend/resume working, if it used to work but stopped > working > at some time, if it never worked, but you are still hoping, could you please > test the following patch and report back? > > http://svn.freebsd.by/files/acpi-apic-wakeup

Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9

2013-02-02 Thread Stefan Bethke
Am 30.01.2013 um 07:21 schrieb Kimmo Paasiala : > On Wed, Jan 30, 2013 at 7:27 AM, James wrote: >> I was able to correct the problem as well by prefixing strnvis, avoiding the >> symbol collision. I also found PR: ports/172941 which also has a fix. >> >> Using my patch or the patch in ports/1729

Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9

2013-02-02 Thread Mark Linimon
On Fri, Feb 01, 2013 at 11:53:03AM -0600, Brooks Davis wrote: > I'm not sure why I'm being jumped on in this weeks old report of a > now-fixed problem. I'm sorry, I'm that far behind in email. I did not realize the problem had already been solved. More often than not the problem is simply "throw

Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9

2013-02-02 Thread Kimmo Paasiala
On Sun, Feb 3, 2013 at 4:06 AM, Mark Linimon wrote: > On Fri, Feb 01, 2013 at 11:53:03AM -0600, Brooks Davis wrote: >> I'm not sure why I'm being jumped on in this weeks old report of a >> now-fixed problem. > > I'm sorry, I'm that far behind in email. I did not realize the problem > had already