https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260993
Kubilay Kocak changed:
What|Removed |Added
Assignee|b...@freebsd.org|toolch...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #10 from Colin Percival ---
Some quick notes -- sorry, juggling a bunch of stuff right now and won't have
time to debug this properly until later:
1. Getting 404 errors in response to /bp/ requests is normal and harmless.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260993
--- Comment #3 from Eugene Grosbein ---
Created attachment 230774
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=230774=edit
nanobsd environment
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260993
--- Comment #2 from Eugene Grosbein ---
Created attachment 230773
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=230773=edit
nanobsd make.conf
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260993
--- Comment #1 from Eugene Grosbein ---
Created attachment 230772
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=230772=edit
full build log is over 1000KB, so it comes compressed
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260993
Bug ID: 260993
Summary: [regression] [clang] stable/12 buildworld broken:
fatal error: 'clang/Basic/DiagnosticCommonKinds.inc'
file not found
Product: Base System
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #9 from Some Signup ---
My apologies for the delay in trying to update my machines. It's such a pain
that I put it off until I can't put it off any longer.
If I run freebsd-update with --debug I get to see thousands of errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260257
--- Comment #8 from Alan Somers ---
(In reply to Robert Wing from comment #7)
So far this patch seems to be working. I've installed it on one system that's
experienced two MEDIUM ERRORs since. I'll check on it daily.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260963
--- Comment #2 from Ed Maste ---
I cannot find the referenced report on hackers - could you please add a link to
the mailing list archive? I want to make sure I'm correctly trying to reproduce
the differing behaviour between sc and vt.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260963
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496
--- Comment #52 from Daniel Austin ---
(In reply to Alexander Motin from comment #51)
If it helps, it seems to be enclosure related...
I can use NCQ on my disks and controller in another enclosure (e.g. I have an
Areca 8 bay that's
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260979
Mark Johnston changed:
What|Removed |Added
Status|New |Open
--- Comment #3 from Mark
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260896
--- Comment #3 from Oleg ---
This issue occurs on both of my computers.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185619
Thomas Steen Rasmussen / Tykling changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496
Alexander Motin changed:
What|Removed |Added
CC||m...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260979
--- Comment #2 from Ed Maste ---
(by "this" I mean looking up standalone debug data in a jail-specific
/usr/lib/debug directory)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260979
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260954
Jochen Neumeister changed:
What|Removed |Added
Assignee|b...@freebsd.org|jon...@freebsd.org
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260954
Jochen Neumeister changed:
What|Removed |Added
Summary|waiting for runnimg MySQL |databases/mysqwl57-server:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260962
--- Comment #3 from Graham Perrin ---
(In reply to Andriy Gapon from comment #2)
Sure; if it's installed to FreeBSD then it should either:
a) work (simply) as it does on Linux; or
b) fail with an appropriate error.
Thanks
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260979
Bug ID: 260979
Summary: libproc can fail to find debug symbols for jailed
processes
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260973
--- Comment #2 from Thomas Steen Rasmussen / Tykling ---
This statement
- Rebooting with four jails plus the above ruleset enabled means never getting
any contact to the server at all (ie. the problem manifests from boot).
is not true,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260973
--- Comment #1 from Thomas Steen Rasmussen / Tykling ---
Maybe related https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185619
Also, I forgot to mention, at some point yesterday while trying 100 things I
saw the em0 on the host having
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260962
--- Comment #2 from Andriy Gapon ---
> because some Linux distributions expect
But FreeBSD is not one.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260973
Bug ID: 260973
Summary: pf: firewall rules stop matching when vnet jails share
interface names with the host
Product: Base System
Version: 13.0-STABLE
Hardware: Any
25 matches
Mail list logo
