[Bug 194744] [PATCH] allow to specify custom keymap when kbdmux used

2015-08-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744 Ed Maste ema...@freebsd.org changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|ema...@freebsd.org

[Bug 194744] [PATCH] allow to specify custom keymap when kbdmux used

2015-10-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744 Oliver Pinter changed: What|Removed |Added See Also|

[Bug 194744] [PATCH] allow to specify custom keymap when kbdmux used

2015-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744 Ed Maste changed: What|Removed |Added Blocks||203349 -- You are

[Bug 194744] [PATCH] allow to specify custom keymap when kbdmux used

2016-01-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744 Oliver Pinter changed: What|Removed |Added Flags||mfc-stable10?

[Bug 194744] [PATCH] allow to specify custom keymap when kbdmux used

2016-03-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744 o...@hardenedbsd.org changed: What|Removed |Added CC||o...@hardenedbsd.org ---

[Bug 194744] [PATCH] allow to specify custom keymap when kbdmux used

2016-03-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744 --- Comment #4 from o...@hardenedbsd.org --- Yes, sorry, I looked the wrong PR. This PR is a dup of 153459. -- You are receiving this mail because: You are on the CC list for the bug. ___

[Bug 194744] [PATCH] allow to specify custom keymap when kbdmux used

2016-03-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744 --- Comment #2 from Ed Maste --- (In reply to Oliver Pinter from comment #0) Is this patch functionally equivalent to the one in PR 153459? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 208275] Kernel panic when reading from /dev/cd0 with a damaged dvd

2016-03-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275 Konstantin Belousov changed: What|Removed |Added CC|

[Bug 208275] Kernel panic when reading from /dev/cd0 with a damaged dvd

2016-03-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275 --- Comment #9 from Fabian Keil --- I agree that moving the n calculation behind the error block is technically sufficient to prevent the panic. I added the NULL check in front of the brelse() because the function

[Bug 208275] Kernel panic when reading from /dev/cd0 with a damaged dvd

2016-03-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275 --- Comment #10 from Konstantin Belousov --- (In reply to Fabian Keil from comment #9) See the comment near the end of cluster_read(), right after the opening '{' of if (reqbp) block. It all comes from r294954. -- You

[Bug 194744] [PATCH] allow to specify custom keymap when kbdmux used

2016-03-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744 Ed Maste changed: What|Removed |Added Resolution|--- |DUPLICATE

[Bug 208275] Kernel panic when reading from /dev/cd0 with a damaged dvd

2016-03-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275 --- Comment #11 from Fabian Keil --- Thanks for the pointer. Somehow I missed that comment. -- You are receiving this mail because: You are on the CC list for the bug. ___

[Bug 208275] Kernel panic when reading from /dev/cd0 with a damaged dvd

2016-03-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275 --- Comment #12 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Tue Mar 29 19:59:45 UTC 2016 New revision: 297401 URL: https://svnweb.freebsd.org/changeset/base/297401 Log: Do not access buffer if

[Bug 208275] Kernel panic when reading from /dev/cd0 with a damaged dvd

2016-03-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275 Fabian Keil changed: What|Removed |Added CC|

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2016-04-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Sylvain Garrigues changed: What|Removed |Added Version|10.3-RELEASE

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2016-04-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Sylvain Garrigues changed: What|Removed |Added CC|

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2016-04-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Sylvain Garrigues changed: What|Removed |Added Attachment #169494|0

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2016-04-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Mark Linimon changed: What|Removed |Added Keywords||patch -- You

[Bug 217994] Kernel panic in native_lapic_setup with 12-CURRENT on EC2 machine

2017-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217994 Konstantin Belousov changed: What|Removed |Added CC|freebsd-current@FreeBSD.org | -- You

[Bug 217994] Kernel panic in native_lapic_setup with 12-CURRENT on EC2 machine

2017-03-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217994 Sylvain Garrigues changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 rai...@ultra-secure.de changed: What|Removed |Added CC||rai...@ultra-secure.de

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Bug ID: 218849 Summary: Remove rc.conf jail configuration via jail_* variables Product: Base System Version: 11.0-RELEASE Hardware: Any OS: Any Status: New

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #4 from Miroslav Lachman <000.f...@quip.cz> --- There is nothing special on jails created by ezjail so the configuration can be converted very easily. I have my own solution for jails with very similar structure and nullfs mount

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #16 from Joe Barbish --- This is my objection to waiting for 12.0 before doing this. When 10.0 came out the removal of the rc.conf method was scheduled to happen at 11.0. Now 3+ years later 11.0 is out

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Brooks Davis changed: What|Removed |Added Resolution|--- |Works As

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 erdge...@erdgeist.org changed: What|Removed |Added CC||erdge...@erdgeist.org ---

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #14 from rai...@ultra-secure.de --- I think the PTB (powers that be) ultimately decided that it's not in the interest of the project to have a tool and (and possibly an API) in base to create jails a la ezjail. At least, that's

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #15 from Mathieu Arnold --- (In reply to Joe Barbish from comment #9) > I see no benefit to dropping rc.conf jail support on a major release over a > minor release. I both cases you are going to suffer the

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Julian Elischer changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #20 from Julian Elischer --- previous comment shoudl have read "I strongly request that the bug be closed again". -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Ngie Cooper changed: What|Removed |Added Status|Closed |Open

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #21 from Miroslav Lachman <000.f...@quip.cz> --- (In reply to Julian Elischer from comment #20) Why? To miss the opportunity to remove deprecated code for the next major release again? Then why we even put warnings to outdated

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Warner Losh changed: What|Removed |Added CC||i...@freebsd.org

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #23 from Miroslav Lachman <000.f...@quip.cz> --- (In reply to Warner Losh from comment #22) I think it turns in to bikeshed now. Are we talking about rc.conf variables to configure jails or about this as dependency for ezjail?

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Jamie Gritton changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #9 from Joe Barbish --- I see no benefit to dropping rc.conf jail support on a major release over a minor release. I both cases you are going to suffer the same consequences of NOT heeding the warning

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #10 from Michael Gmelin --- (In reply to Joe Barbish from comment #9) I tried to give you feedback from real world installations and real world upgrade procedures, as you claimed ezjail isn't relevant any

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #3 from rai...@ultra-secure.de --- Fair enough. But I believe the number of ezjail-jails is significant. Also, as you can see, until now (11.0) it's the 3rd-party tool recommended by the FreeBSD project itself (if you take the

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Miroslav Lachman <000.f...@quip.cz> changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #7 from Joe Barbish --- In reply to comment # 3 which states "But I believe the number of ezjail-jails is significant." This is un-true, since 10.0 was published many ezjail users have been moving to

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #8 from Michael Gmelin --- (In reply to Joe Barbish from comment #7) As maintainer of sysutils/qjail you might look at this like it. I just know that we run hundreds of jails using ezjail and breaking that

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #12 from Ngie Cooper --- For the sake of maintaining POLA, I recommend not breaking it on a dot-release and instead throw the switch on ^/head. I am very much in agreement there with grembo@. I think it would

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Chris Hutchinson changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-04-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Michael Gmelin changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-05-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Thomas Steen Rasmussen / Tykling changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-05-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #26 from Miroslav Lachman <000.f...@quip.cz> --- (In reply to Thomas Steen Rasmussen / Tykling from comment #25) Are you serious? Then why Joe provided the idea how to make ezjail survive this code removal? Did you read the

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-05-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Jonathan Anderson changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-05-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #28 from Miroslav Lachman <000.f...@quip.cz> --- (In reply to Jonathan Anderson from comment #27) I think the opposite way. Or we end up with the same problems as with ezjail, portupgrade, portmaster etc. now. Some features in

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2017-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #29 from Joe Barbish --- Today I submitted PR# 219421. This handbook patch removes all ezjail documentation from the handbook jail chapter and adds an political correct entry which is fair to all the

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2018-02-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 jtkoert...@gmail.com changed: What|Removed |Added CC||jtkoert...@gmail.com ---

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2018-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kyle Evans changed: What|Removed |Added Flags||mfc-stable10-, |

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2018-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kyle Evans changed: What|Removed |Added Assignee|b...@freebsd.org|kev...@freebsd.org -- You are

[Bug 227259] accept()/poll() and shutdown()/close() - not work as in FreeBSD10, may broke many apps

2018-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259 --- Comment #2 from rozhuk...@gmail.com --- I do not understand why shutdown() does not generates POLLHUP/EV_EOF (EV_ERROR then add shutdowned socket) for poll() and kqueue(). -- You are receiving this mail because: You are on the CC list

[Bug 227259] accept() does not wakeup on shutdown()/close()

2018-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259 rozhuk...@gmail.com changed: What|Removed |Added CC||freebsd-current@FreeBSD.org

[Bug 227259] accept()/poll() and shutdown()/close() - not work as in FreeBSD10, may broke many apps

2018-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259 --- Comment #3 from rozhuk...@gmail.com --- Why close() does not wakes thread that sleep on accept()? -- You are receiving this mail because: You are on the CC list for the bug. ___

[Bug 227259] accept()/poll() and shutdown()/close() - not work as in FreeBSD10, may broke many apps

2018-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259 rozhuk...@gmail.com changed: What|Removed |Added Summary|accept() does not wakeup on |accept()/poll() and

[Bug 227259] accept()/poll() and shutdown()/close() - not work as in FreeBSD10, may broke many apps

2018-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259 Conrad Meyer changed: What|Removed |Added CC|freebsd-current@FreeBSD.org |c...@freebsd.org

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

2018-03-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 Charlie Li changed: What|Removed |Added CC|

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

2018-03-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 Charlie Li changed: What|Removed |Added CC|

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

2018-03-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 w.schwarzenf...@utanet.at changed: What|Removed |Added CC|freebsd-current@FreeBSD.org

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

2018-03-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 --- Comment #6 from Charlie Li --- Also could someone remove current@ again? I accidentally used a cached page to comment and didn't pay attention to the CC list. -- You are receiving this mail because: You are

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

2018-03-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 Conrad Meyer changed: What|Removed |Added CC|freebsd-current@FreeBSD.org |c...@freebsd.org

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

2018-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Nicolas Hainaux changed: What|Removed |Added CC||nh.te...@gmail.com --- Comment

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Kubilay Kocak changed: What|Removed |Added Summary|Cannot check battery status |Cannot check battery status

[Bug 208275] Kernel panic when reading from /dev/cd0 with a damaged dvd

2019-01-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275 Oleksandr Tymoshenko changed: What|Removed |Added CC||go...@freebsd.org

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-12-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Andriy Gapon changed: What|Removed |Added Resolution|--- |FIXED Status|In

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-12-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #21 from commit-h...@freebsd.org --- A commit references this bug: Author: avg Date: Thu Dec 20 08:45:41 UTC 2018 New revision: 342278 URL: https://svnweb.freebsd.org/changeset/base/342278 Log: MFC r341632:

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-12-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Andriy Gapon changed: What|Removed |Added Assignee|a...@freebsd.org|a...@freebsd.org

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #20 from commit-h...@freebsd.org --- A commit references this bug: Author: avg Date: Thu Dec 6 12:34:34 UTC 2018 New revision: 341632 URL: https://svnweb.freebsd.org/changeset/base/341632 Log:

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #19 from Andriy Gapon --- I am curious if anyone who had this problem before still has it. Especially, I am curious if they had an error message like in comment#1 and if that message went way. In addition to the prior analysis

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-11-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #16 from Matías Pizarro --- Hi all, FYI, I had the same issue with 13-CURRENT but it now works fine in today';s stable/12 | 12-PRERELEASE which I understand should be the same as 12-RC2. Thanks for your work on this, All the

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-11-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #17 from Mark Johnston --- (In reply to Matías Pizarro from comment #16) There have been several ACPICA updates since the bug was filed, but 13-CURRENT and 12.0 should be in sync. Which revision of 13-CURRENT did you test?

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-11-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #18 from Matías Pizarro --- I was still having this problem on 13-CURRENT r340703 ( https://svnweb.freebsd.org/base?view=revision=340703 ). But that was nearly 6 days ago, I have not tested further down the 13-CURRENT

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2018-11-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kyle Evans changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2018-11-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kubilay Kocak changed: What|Removed |Added Flags|mfc-stable10- | --- Comment #3 from Kubilay

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2018-11-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 --- Comment #4 from Kyle Evans --- (In reply to Kubilay Kocak from comment #3) Hi, Sorry, I should have been informative. =) The commit for this that rewrote the offending parser predated stable/12, r335642; it was merged to stable/11 in

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2018-11-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kubilay Kocak changed: What|Removed |Added Component|kern|bin

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

2018-11-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2019-01-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Kubilay Kocak changed: What|Removed |Added Flags|mfc-stable12? |mfc-stable12+

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2019-03-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Slava changed: What|Removed |Added CC||sl...@planetslav.ca --- Comment #22 from

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2019-03-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #23 from Kubilay Kocak --- (In reply to Slava from comment #22) The fix has been committed and merged to the stable/12 branch, and will be part of the next (12.1) FreeBSD release cut from that branch. If you would not like to

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2019-03-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #24 from Kubilay Kocak --- (In reply to Slava from comment #22) Alternatively, one can apply the commit that was merged to stable/12 in base r342278, and rebuild/reinstall the kernel -- You are receiving this mail because:

[Bug 197921] scheduler: Allow non-migratable threads to bind to their current CPU

2019-05-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921 Kubilay Kocak changed: What|Removed |Added Keywords|patch |needs-patch

[Bug 197921] [patch] [sched] Allow non-migratable threads to bind to their current CPU.

2019-05-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #1 from