From owner-freebsd-questions@FreeBSD.ORG Sun Aug 17 02:27:21 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22B4C37B401 for ; Sun, 17 Aug 2003 02:27:21 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9802243FA3 for ; Sun, 17 Aug 2003 02:27:20 -0700 (PDT) (envelope-from freebsduser@comcast.net) Received: from comcast.net (12-225-141-88.client.attbi.com[12.225.141.88](untrusted sender)) by comcast.net (rwcrmhc13) with SMTP id <2003081709272001500l8c78e> (Authid: animotions); Sun, 17 Aug 2003 09:27:20 +0000 Message-ID: <3F3F4A6C.6060708@comcast.net> Date: Sun, 17 Aug 2003 02:27:08 -0700 From: K Anderson User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Questions Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Submit new PR or Submit to an existing PR? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 09:27:21 -0000 Hey folks, Since I didn't get a response asking about the module already existing problem with miibus and if_ed I went and checked for a PR and found what that pretty much matches my problem. It is Problem Report kern/55279. I would like to know if I should either submit a new PR or click on the old submit follow-up link? Here's my reasoning to want to do the follow-up link: I recently cvsup'd and rebuilt my diskless kernel which was also displaying at least the problem with miibus module existing error. But for some strange reason it stopped and now only the server complains about miibus and if_ed. Since both kernels where built on the same maching & use the same everything (with the exception of the diskless kernel runs on systems to be diskless workstations) with the exception of hardware (they do share the same libraries modules and what ever else clone_root copies). Of course miibus being the culprit here. OR Should I submit a whole new PR with the contents of both kernel configuration files? Thanks for your advice. Hopefully one way or the other I can get my kernel configurations to the hands of those that need them and they can determine why the sudden change. On a different note. Somebody foobarred the rl driver to where it shows it is working but is more or less inoperable (ethereal was telling me it was receving invalid packets over the rl interface) I put my old kernel back and the rl interface is back to normal. Do you think this warrents a PR? Oh, and for giggles I rebuilt the kernel several times just to make sure it wasn't something funky. TIA