https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Nicolas Hainaux changed:
What|Removed |Added
CC||nh.te...@gmail.com
--- Comment #
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938
Kyle Evans changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938
Kubilay Kocak changed:
What|Removed |Added
Flags|mfc-stable10- |
--- Comment #3 from Kubilay Kocak
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938
Kubilay Kocak changed:
What|Removed |Added
Component|kern|bin
Flags|mfc-stable1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938
Kubilay Kocak changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
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
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?
Can
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&revision=340703 ). But that was
nearly 6 days ago, I have not tested further down the 13-CURRENT d
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
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:
acpi_{Device,Battery}IsPresent:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
Andriy Gapon changed:
What|Removed |Added
Assignee|a...@freebsd.org|a...@freebsd.org
Status
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: acpi_{Device,Batte
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
Andriy Gapon changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progres
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
Kubilay Kocak changed:
What|Removed |Added
Flags|mfc-stable12? |mfc-stable12+
Keywords|n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275
Oleksandr Tymoshenko changed:
What|Removed |Added
CC||go...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
Slava changed:
What|Removed |Added
CC||sl...@planetslav.ca
--- Comment #22 from S
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
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:
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921
Kubilay Kocak changed:
What|Removed |Added
Keywords|patch |needs-patch
Summary|[pa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744
Ed Maste changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|ema...@freebsd.org
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744
Oliver Pinter changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744
Ed Maste changed:
What|Removed |Added
Blocks||203349
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744
Oliver Pinter changed:
What|Removed |Added
Flags||mfc-stable10?
--
You are receivin
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.
__
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.
___
freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744
o...@hardenedbsd.org changed:
What|Removed |Added
CC||o...@hardenedbsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744
Ed Maste changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275
Fabian Keil changed:
What|Removed |Added
CC||freebsd-current@FreeBSD.org
--- Comm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275
Konstantin Belousov changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment
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
contains a comment that i
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 are receiving this
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.
___
freebsd-current@freebs
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 bread(9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938
Sylvain Garrigues changed:
What|Removed |Added
Version|10.3-RELEASE|11.0-CURRENT
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938
Sylvain Garrigues changed:
What|Removed |Added
CC||freebsd-current@FreeBSD.org
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938
Sylvain Garrigues changed:
What|Removed |Added
Attachment #169494|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217994
Sylvain Garrigues changed:
What|Removed |Added
CC||a...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217994
Konstantin Belousov changed:
What|Removed |Added
CC|freebsd-current@FreeBSD.org |
--
You are receiving this
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
rai...@ultra-secure.de changed:
What|Removed |Added
CC||rai...@ultra-secure.de
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Miroslav Lachman <000.f...@quip.cz> changed:
What|Removed |Added
CC||000.f...@quip.
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
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Chris Hutchinson changed:
What|Removed |Added
CC||portmas...@bsdforge.com
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Michael Gmelin changed:
What|Removed |Added
CC||gre...@freebsd.org
--- Comment #6
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
qjail because qjail uses
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 in anything but a
maj
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 you have been getting for t
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 more.
Even though I a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Conrad Meyer changed:
What|Removed |Added
CC||c...@freebsd.org
--- Comment #11 fr
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 be a great idea to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
erdge...@erdgeist.org changed:
What|Removed |Added
CC||erdge...@erdgeist.org
--- C
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
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 same consequences of
>
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 and the rc.conf method is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Brooks Davis changed:
What|Removed |Added
Resolution|--- |Works As Intended
C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Ngie Cooper changed:
What|Removed |Added
Status|Closed |Open
Flags|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Julian Elischer changed:
What|Removed |Added
CC||jul...@freebsd.org
--- Comment #
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.
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 c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #22 fro
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?
N
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Jamie Gritton changed:
What|Removed |Added
CC||ja...@freebsd.org
--- Comment #24
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Thomas Steen Rasmussen / Tykling changed:
What|Removed |Added
CC||tho...@gibfest.d
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 comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Jonathan Anderson changed:
What|Removed |Added
CC||jonat...@freebsd.org
--- Comme
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 ba
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 jail management utilities in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536
Yuri Victorovich changed:
What|Removed |Added
URL||https://people.freebsd.org/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536
Mark Millard changed:
What|Removed |Added
CC||marklmi26-f...@yahoo.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536
--- Comment #2 from Yuri Victorovich ---
(In reply to Mark Millard from comment #1)
Swap is on /dev/ada0p2.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536
--- Comment #3 from Yuri Victorovich ---
(In reply to Mark Millard from comment #1)
> Do you have anything specific for what controls getting [...].
This is a generic install. No specific options of any kind were set.
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536
--- Comment #4 from Mark Millard ---
(In reply to Yuri Victorovich from comment #2)
Being in a VirtualBox VM the /dev/ada0p2 may not indicate
much about the actual media involved. Microsd card and
spinning rust media are more likely than s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536
--- Comment #5 from Yuri Victorovich ---
(In reply to Mark Millard from comment #4)
> Being in a VirtualBox VM the /dev/ada0p2 may not indicate
> much about the actual media involved.
The physical medium is a traditional spinning HD with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921
Mark Linimon changed:
What|Removed |Added
Flags|mfc-stable12?, |
|mfc-stable11?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921
Zhenlei Huang changed:
What|Removed |Added
CC||z...@freebsd.org
--- Comment #3 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744
Lê Quốc Đạt changed:
What|Removed |Added
CC||datloveyouvt1...@gmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744
--- Comment #7 from Lê Quốc Đạt ---
Comment on attachment 148901
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148901
0001-HBSD-allow-to-specify-custom-keymap-to-kbdmux.patch
148901
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744
--- Comment #7 from Lê Quốc Đạt ---
Comment on attachment 148901
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148901
0001-HBSD-allow-to-specify-custom-keymap-to-kbdmux.patch
148901
--- Comment #8 from Lê Quốc Đạt ---
Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744
Jan Beich changed:
What|Removed |Added
CC|curr...@freebsd.org |
--
You are receiving this mail becau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
jtkoert...@gmail.com changed:
What|Removed |Added
CC||jtkoert...@gmail.com
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700
Charlie Li changed:
What|Removed |Added
CC||freebsd-current@FreeBSD.org
--
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700
Conrad Meyer changed:
What|Removed |Added
CC|freebsd-current@FreeBSD.org |c...@freebsd.org
--- Comment #3 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700
Charlie Li changed:
What|Removed |Added
CC||freebsd-current@FreeBSD.org
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700
w.schwarzenf...@utanet.at changed:
What|Removed |Added
CC|freebsd-current@FreeBSD.org |w.schwarzenf...@utanet.a
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 on the CC list for the bug.
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259
rozhuk...@gmail.com changed:
What|Removed |Added
CC||freebsd-current@FreeBSD.org
-
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
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.
___
freebsd-curre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259
Conrad Meyer changed:
What|Removed |Added
CC|freebsd-current@FreeBSD.org |c...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938
Kyle Evans changed:
What|Removed |Added
Flags||mfc-stable10-,
|
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 receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395
Bug ID: 254395
Summary: bsdinstall: fail script install after BETA3
Product: Base System
Version: 13.0-STABLE
Hardware: Any
OS: Any
Status: New
Keyw
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395
Nathan Whitehorn changed:
What|Removed |Added
CC||nwhiteh...@freebsd.org
--- Comm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395
Ryan Moeller changed:
What|Removed |Added
CC||freql...@freebsd.org
--- Comment #2
1 - 100 of 120 matches
Mail list logo
