https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261024
PauAmma changed:
What|Removed |Added
CC||paua...@gundo.com
--- Comment #1 from Pa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261024
Graham Perrin changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261024
Bug ID: 261024
Summary: regdomain.xml refers to non-existent
http://ftp.ics.uci.edu/pub/ietf/http/related/iso3166.t
xt for a complete list of country/region codes
Prod
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=59912
--- Comment #11 from Shawn Webb ---
The Cross-DSO CFI implementation in llvm favors mremap, though it does contain
a fallback in the case mremap doesn't exist. If FreeBSD were to provide an
official mremap syscall implementation, both the li
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=59912
Shawn Webb changed:
What|Removed |Added
CC||shawn.w...@hardenedbsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209821
--- Comment #68 from David Sebek ---
(In reply to Dani from comment #65)
See patch in comment #67. It is a reduced version of the patch from comment #41
rebased against FreeBSD 12.3. I tested the patch with FreeBSD 12.3, and it
fixes the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209821
--- Comment #67 from David Sebek ---
Created attachment 230798
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=230798&action=edit
[PATCH] [releng/12.3] efi: loader: Inline copy_finish function in amd64
trampoline
This is a simpli
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261011
Sergio Carlavilla Delgado changed:
What|Removed |Added
CC||carlavi...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261011
Bug ID: 261011
Summary: docs.freebsd.org/en/books/design-44bsd Table heading
text unreadable in dark mode theme (white text on
white background)
Product: Documentation
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #12 from Colin Percival ---
Don't worry about portsnap vs. freebsd-update -- it's basically the same code.
If HTTP requests are getting mangled that's a very clear sign as to where the
problem is. A couple questions about that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260898
--- Comment #15 from Bob Frazier ---
Using the 'workaround' settings I have occasionally seen problems in video
playback. The problems are MUCH less frequent but have not completely been
resolved.
In one case a video suddenly went 'out of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260257
Warner Losh changed:
What|Removed |Added
Status|New |In Progress
--- Comment #9 from Warn
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209821
--- Comment #66 from David Sebek ---
(In reply to Dani from comment #65)
I think there were two reasons why UEFI boot froze on some systems. Before the
changes in 13-STABLE and 14-CURRENT, the kernel needed to be loaded to a
specific physic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209821
--- Comment #65 from Dani ---
(In reply to Ed Maste from comment #64)
Hey Ed, thanks for the hint. I guess you mean the patches from comment #38 or
comment #41 ? Both don't apply against a clean 12.3 src, so i'm not sure how
much sense tha
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261005
--- Comment #1 from Mario Richber ---
More examples
root@beastie:~ # hostname beastie.my.labs.example.com
root@beastie:~ # hostname -d
my.lple.example.com
root@beastie:~ # hostname beastie.my.test.labs.example.com
root@beastie:~ # hostnam
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261005
Bug ID: 261005
Summary: hostname -d is not resolved domain information
correctly
Product: Base System
Version: 13.0-RELEASE
Hardware: arm64
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260489
--- Comment #5 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=457750da86f17598be135b3cc706f4275560749d
commit 457750da86f17598be135b3cc706f4275560749d
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #11 from Some Signup ---
My apologies: please note, my last post referred to freebsd-update when on that
occasion I was using portsnap. But I often see the same end result of failed
downloads when using freebsd-update - the symp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260962
--- Comment #4 from Andriy Gapon ---
(In reply to Graham Perrin from comment #3)
My personal preference: do not install it on FreeBSD.
--
You are receiving this mail because:
You are the assignee for the bug.
19 matches
Mail list logo