Date: Tue, 20 Aug 2024 17:31:53 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 280097] Warning printed when FIBs are expanded is unhelpful and confusing Message-ID: <bug-280097-7501-uLYAnFApik@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280097-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-280097-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280097 --- Comment #16 from Jeremy Cooper <jeremy.fbbg@baymoo.org> --- (In reply to Zhenlei Huang from comment #15) No, this is not clear enough for me. My issue is not with the word "ifaddrs= "; it with these two points, which I will repeat again: 1. The user needs to know why the message was generated at this particular point in the boot process. 2. The user needs to know that this message is a reminder, not the detectio= n of an immediate problem, and given just a tiny hint about how to make the mess= age go away. As a kernel developer it may be very clear to you why the message was generated. But it's not at all clear to the average admin. This message scr= olls by very quickly at boot and is VERY hard to interpret in its current form. The message needs to address both of these points. And to do that, it needs= to: 1. Mention that setting "net.fibs" is what triggered the message. 2. Give actionable steps that the user can take to eliminate the problem. My wording accomplishes both of these. I just ask that you still solve both issues if you choose to change it. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280097-7501-uLYAnFApik>