From owner-freebsd-qa@FreeBSD.ORG Thu Jan 8 23:14:14 2004 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CB8D16A4D4 for ; Thu, 8 Jan 2004 23:14:14 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 5F31D43D5D for ; Thu, 8 Jan 2004 23:14:09 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 90887 invoked by uid 1002); 9 Jan 2004 07:14:08 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 9 Jan 2004 07:14:08 -0000 Message-ID: <3FFE545E.1080401@freebsd.org> Date: Fri, 09 Jan 2004 00:12:30 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jin Guojun [NCS]" References: <200401080401.i08414Ld093554@freefall.freebsd.org> <20040107223112.H32001@pooker.samsco.home> <3FFDCE09.AB364ACC@lbl.gov> In-Reply-To: <3FFDCE09.AB364ACC@lbl.gov> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Doug White cc: bmah@freebsd.org cc: re@freebsd.org cc: freebsd-qa@freebsd.org Subject: Re: misc/60349: 5.2-RC1 cannot do NFS installation X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2004 07:14:14 -0000 Jin Guojun [NCS] wrote: > Scott Long wrote: > > >>On further investigation, it's going to be rather difficult to make >>floppy 3 be mandatory. The loader is set up so that loader.rc >>merely stages floppy 2 for the loader to load after it has loaded >>the kernel. There is no way for loader.rc to stage two floppies at >>the same time. >> >>Sysinstall could be changed to either force the loading of hte floppy >>3 modules, or intelligently detect when nfsclient.ko is needed and >>not present, and prompt the user to insert the floppy. However, this >>then requires that sysinstall know what drivers are on floppy 3, >>something that adds to the maintenance burden. It also presents quite >>a bit of risk at this late stage of the process. >> >>My suggestion is to document this in the release notes and/or errata. >>It appears that the problem can be avoided by manually loading >>nfsclient.ko off of floppy 3 when sysinstall starts. Sysinstall appears >>to be equiped to assist with this, so it shouldn't be too hard to >>document. > > > I am not sure what is the difference between "prompt the user to insert the > floppy 3" > and "manually loading nfsclient.ko off of floppy 3". In either way, the > sysinstall needs > to know what things are on floppy 3. > > Since installation is one time task, manually loading nfsclient.ko would not be > a bad solution. The NFS installation is very important for installing clusters. > As long as we can make it work, it is worth to take effort. > > -Jin > > Bruce Mah is going to add some documentation to the release docs to explain how to make nfs installs from floppy work. I'm uncomfortable with chaning sysinstall code this late into the release cycle. Hopefully we can come up with a better fix before 5.3. Scott