From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 14:53:09 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E05F37B401 for ; Mon, 7 Jul 2003 14:53:09 -0700 (PDT) Received: from histidine.utmb.edu (histidine.utmb.edu [129.109.59.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id D002343FBD for ; Mon, 7 Jul 2003 14:53:08 -0700 (PDT) (envelope-from bdodson@scms.utmb.EDU) Received: from histidine.utmb.edu (localhost [127.0.0.1]) by histidine.utmb.edu (8.12.9/8.12.9) with ESMTP id h67Lr7pJ028271; Mon, 7 Jul 2003 16:53:08 -0500 (CDT) (envelope-from bdodson@histidine.utmb.edu) Received: (from bdodson@localhost) by histidine.utmb.edu (8.12.9/8.12.9/Submit) id h67Lr74F028268; Mon, 7 Jul 2003 16:53:07 -0500 (CDT) From: "M. L. Dodson" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <16137.60355.414841.512621@histidine.utmb.edu> Date: Mon, 7 Jul 2003 16:53:07 -0500 To: Thierry Herbelot In-Reply-To: <200307072232.38920.thierry@herbelot.com> References: <16137.53692.783846.229641@histidine.utmb.edu> <200307072232.38920.thierry@herbelot.com> X-Mailer: VM 7.14 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid cc: current@freebsd.org Subject: Re: nfs installs of 5.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: bdodson@scms.utmb.EDU List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2003 21:53:09 -0000 Thierry Herbelot writes: > Le Monday 07 July 2003 22:02, M. L. Dodson a =E9crit : > > Background: > > I posted this on questions, but got no response. Since this used > > to work, I thought it might be a 5.x issue. >=20 > indeed, see later >=20 > > $subject seems broken for me for 5.1 miniinst.iso > > > > Export /cdrom from 10.2.1.4; exports line: > > /cdrom -maproot=3D0 -alldirs -network 10.2 -mask 255.255.0.0 > > > > Nfs server setup, on 4.8-STABLE, is well tested and known to > > work. > > > > When prompted for nfs info during install, give 10.2.1.4:/cdrom, > > netmask 255.255.0.0 (same subnet as target machine) -> configure > > install target network (ip 10.2.1.200) -> get error: > > > > Error mounting 10.2.1.4:/cdrom on /dist: no such file or directory= > > > > On ttyv4 find error messages (hand copied): > > mount_nfs: can't update /var/db/mountdtab for 10.2.1.4:/cdrom > > mount_nfs: Operation not supported by device > > > > On ttyv4 I can cd to /dist >=20 > this may be due to kernel being unable to dynamically load nfs_clien= t.ko >=20 > I saw this when building a jumpstart server for 5.1 (PXE automatic i= nstall=20 > from another 5.1 server). >=20 > I went around by stopping the boot loader in the boot phase, loading= manually=20 > the nfs module, then proceeding with the install. >=20 > =09TfH That certainly makes sense. I might gently suggest to RE, etc that they might want to reconsider the decision to put nfs on the extra drivers floppy (I assume that is where it is). This really trips up newbies (and some of us not so newbies). I ran across this trying to help someone install 5.0 for the first time. He had a bunch of machines to install (no cdroms), so I suggested nfs and was completely surprised when it did not work. I verified that he was not doing something obviously wrong before I posted. He was very confused because he consulted essentially all the FreeBSD books that had anything to say on the subject and could not see what he was doing wrong (nor did I). This does not present a good first impression for the project. The nfs install, being documented in all the books, is much more important than individual ethernet drivers. If nfs cannot be put in the install kernel, then the nfs option should be removed from sysinstall. All this IMO, of course. Bud Dodson --=20 M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790